SDK-Free Wheel Packaging and Backend Autodetection
@sjfeng1999 is already working on this.
Since Jul 7, 2026.
- Dominant language
- Python
- Stars
- 282
- Forks
- 120
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 67
Description
The original FlyDSL wheel build assumes a ROCm development environment at build time. In particular, the JIT runtime wrapper includes HIP headers, links hip::host / hip::amdhip64, and setup.py later relies on auditwheel repair exclusions to avoid bundling ROCm user-space libraries.
This RFC proposes changing the packaging model so a release builder that has
only:
llvm-project- the FlyDSL source tree
can build a backend-capable wheel without installing ROCm or CUDA SDKs. Vendor driver/runtime dependencies should be resolved lazily on the user's machine.
The same design prepares the codebase for a future dual-backend wheel (rocdl;nvvm)
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.