-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
WIP: Windows arm64 builds - help needed #93
base: main
Are you sure you want to change the base?
Conversation
The problem here is that the We should upgrade to the latest libffi and in a separate commit/PR add support for arm/arm64 builds. I'll start looking into upgrading libffi now. |
I pushed a commit to the Also, if we're going to implement ARM64, what do you think about doing ARM as well? I feel like it should be trivial to do both once you get 1 working? If you don't want to deal with the scope bloat, I can work on ARM once you get ARM64 working. |
Thanks for help. Unfortunately, this week I've busy, so I could look into it next week. I've Surface Pro X, so I can test it on the real device and that's why I would like to have python3 for arm64. ARM32 should run too. |
Only do this if you're keen - it seems like ARM is not going to be an important user or server platform anytime soon, and the IoT applications aren't as compelling as they once were. ARM64 is the main priority for everyone. |
Hello,
I'm trying to add Windows ARM64 compatibility in your python-build-standalone. I started working with it. OpenSSL is compiled, libffi checks done, but
https://github.com/adiantek/python-build-standalone/runs/3770671733?check_suite_focus=true#step:7:7470 why
-march64
is ignored?And I don't know why build system is 32-bit... Build system should be
x86_64-w64-cygwin
, and host/target aarch64: