Replies: 3 comments 7 replies
-
Just today I added cibuildwheel based support for macos arm64 builds. When you talk about aarch64 you mean linux/android arm64 builds? The runtime of the build-python action is already way too long for me to let it run regularly, therefore it is only started manually / or on a release. I would not mind if it took say 30%-50% longer. On the other hand, a simple |
Beta Was this translation helpful? Give feedback.
-
It looking like you could use Cirrus combined with GHA to build natively, while not needing to manage a self hosted instance. I stumbled across the updates Something like this https://github.com/pikepdf/pikepdf/blob/main/.cirrus.yml combined with a wait like this https://github.com/pikepdf/pikepdf/blob/main/.github/workflows/build.yml#L49 looks to end up with wheels, built natively, then transferred to GHA for actual uploading to pypi. If that seems ok, I can look into it more |
Beta Was this translation helpful? Give feedback.
-
I'm using paperless-ngx, which is using zxing-cpp for proper barcode detection. The software runs on a raspberry pi 5 (aarch64). But building aarch64 wheels is causing a lot of time and cpu usage. |
Beta Was this translation helpful? Give feedback.
-
I'd like to use this in a project which supports armv7, aarch64 and x86_64. The armv7 wheel should be buildable with PiWheels now, so that leaves aarch64 as a remaining arch I'd like to not need to build for myself.
cibuildwheel
supports building wheels for aarch64 through emulation. But emulation is slower, so the would make the wheel building slower. With some other jobs in the workflow, it probably wouldn't add that much time, though that does add some complication and duplication unfortunately.So before I explore too much, is there any desire for adding wheels for this arch?
Beta Was this translation helpful? Give feedback.
All reactions