Goal
Track progress of upstreaming riscv64 wheel support to all 33 upstream projects we currently fork and build wheels for.
Each fork has an issue describing the upstream approach (cibuildwheel with QEMU, self-hosted native runners, or cross-compilation). As upstream projects add riscv64 to their CI, we can retire our forks one by one.
Upstream Issues by Package
Rust packages (maturin)
Rust + C packages
C/C++ packages
C + Fortran
Large C++ projects
Approach
For each package, the upstream issue describes three strategies:
- cibuildwheel with QEMU — add
linux_riscv64 to existing CI (recommended for most)
- Self-hosted native runners — use our BananaPi F3 boards
- Cross-compilation — for Rust/maturin or C/C++ toolchain packages
Success criteria
A package is "done" when the upstream project publishes manylinux_2_39_riscv64 wheels on PyPI and we can retire our fork.
Context
Goal
Track progress of upstreaming riscv64 wheel support to all 33 upstream projects we currently fork and build wheels for.
Each fork has an issue describing the upstream approach (cibuildwheel with QEMU, self-hosted native runners, or cross-compilation). As upstream projects add riscv64 to their CI, we can retire our forks one by one.
Upstream Issues by Package
Rust packages (maturin)
Rust + C packages
C/C++ packages
C + Fortran
Large C++ projects
Approach
For each package, the upstream issue describes three strategies:
linux_riscv64to existing CI (recommended for most)Success criteria
A package is "done" when the upstream project publishes
manylinux_2_39_riscv64wheels on PyPI and we can retire our fork.Context