-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial Android Support: alternate #280
base: master
Are you sure you want to change the base?
Initial Android Support: alternate #280
Conversation
It was not effective, and it was visible using Android Studio.
Translated to CMake from a patch on the Yocto project: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python3/0002-Don-t-do-runtime-test-to-get-float-byte-order.patch?h=zeus It avoids the execution of a program on the target device, and produces a clearer endianness result.
It avoids the need for checking it by running a program on the target platform.
…piling They are already present in source releases, so it is possible to ignore the regeneration step. We do that only when cross-compiling, because it is not possible to build for both the host and the target with a single pass of CMake.
Nice, I'll try it later, but
But in Github Actions I got:
|
@victorpaleologue Thanks for working on the Android support 🙏 and thanks @o01eg for reviewing. Working on the backlog of pull request, is there anything else from #262 that we should add here ? |
@jcfr I suppose it could be useful to add Github Actions CI build here at least. |
Hello,
I have been using the branch by @o01eg to build Python for Android (from this PR: #262) and managed to make it work with some extra changes.
I hope this set of changes will be interesting as well.
To avoid requiring to connect to a target device while building (which is hard to achieve on simpler buildfarms), I had to provide certain definitions manually. I tested the build with the following definitions: