workflows: ci: add riscv64 musllinux, stable ABI builds - #277
Conversation
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
|
Which platform is more popular in the niche riscv64 world, manylinux or muslinux? Do we have any PyPI download statistics that might give us an idea if this is really necessary? We already have 26 workflows for this package. Maybe we should poke again at the idea of a limited api abi3 wheel, that would make this all more palatable. |
For now it is definitely manylinux, but getting cffi wheels for musllinux would also go a long way to improving Python compatibility in that area, if our experiences adding riscv64 wheels in the RISE registry (and upstream, with Rust-based packages) are any indicator. I don't have numbers on musllinux consumption specifically. We can certainly look into the ab3 wheel. |
Set a STABLE_ABI_BUILD variable to check so that the freethreaded builds can be handled separately. Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Also drop the cp39 build for riscv64, to make it consistent with the other platforms. Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
|
There are a lot of errors on my initial rework to add abi3 wheels, so I'll convert this back to a draft for now. |
|
Hah, yeah, it is definitely not a simple flip-a-flag change. My inclination is to leave riscv64-muslinux out of the mix for now. |
threexc
changed the title
2 participants
Following up the recent merge from #227, add musllinux riscv64 builds for cffi.
Here is a dry run on my fork, with extra
revertmecommits added to strip out other architectures/platforms for testing:https://github.com/threexc/cffi/actions/runs/34350063320