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)
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, andsetup.pylater relies onauditwheel repairexclusions to avoid bundling ROCm user-space libraries.This RFC proposes changing the packaging model so a release builder that has
only:
llvm-projectcan 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)