Improve qualcomm end-to-end user experience
Open
@abhinaykukkadapu is already working on this.
Since Mar 12, 2026.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
This is a task to capture all the things we need to improve in Qualcomm user flow:
- Improve AOT experience
- Improve build from source
- Improve building binaries workflow
Current top pain points:
- Fragmented entry points and user experience downloading QNN sdk and Android NDK, libc++ - unify the download paths, be transparent instead of silently downloading 2+GB sdks
- Retry downloads on failures
- Start from partial downloads on retry
- Cache downloaded sdks
- Build QNN on linux by default (enable via pybind.cmake) - enable download QNN_SDK during cmake
- In build from source path, enable QNN by default on linux
- Make glibc search and fallback transparent
- Manage all QNN sdk version config at a single point instead of hardcoded paths
- Set all env vars after downloading the sdk
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.