Replies: 1 comment
-
It looks like PyO3 0.9.2 fixed a bug where 32-bit Python was not properly detected, but since PyOxidizer hasn't been updated in a while, it doesn't depend on a version with that bugfix. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I understand that armv7 is not officially supported yet, as it was already mentioned here. But can I make PyOxidizer to build for that target architecture by providing a custom Python distribution?
What I have done so far:
Creating an armv7 docker image based on debian jessie with rust and pyoxidizer (version 0.24.0, installed by cargo install) available
Create a new pyoxidizer project inside a corresponding armv7 docker container
Inside
pyoxidizer.bzl
I replaceddist = default_python_distribution()
bydist = PythonDistribution(local_path="...", sha256="...")
.(The
target-triple
argument is necessary, since otherwise PyOxidizer would try to callx86_64-linux-gnu-gcc
, which is of course not available on my armv7 host system.)Unfortunately, the build process stops due to the following error:
This is really strange since I tested my custom python build on a Raspberry Pi 4. So I am pretty sure that my python interpreter is not a 64-bit application.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions