-
Notifications
You must be signed in to change notification settings - Fork 87
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
universal2 build improvements #495
Conversation
Some shared libraries require a native version of the library/tools for cross compiling. Changing the order would prevent that. |
But the native version is already built last on arm64? Lines 527 to 532 in 2e10577
|
Ah yes. That should be fixed. Arm64 native CI is untested AFAIK |
I've removed the second change, leaving just the |
Could you give an example of one such library? |
|
I attempted to test this with a custom
but it wouldn't even build on arm64. If you're able to demonstrate, that would be helpful. |
If you aren't able to demonstrate, it would be good if you were able to Approve this PR for my |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll have a look at the ordering later this week. Sed change is fine.
To give more information about my situation, Sure, a workaround for this could be for me to just run |
I think the issue with both |
Two suggested changes when building universal2 wheels.
Instead of presuming the length of the string to replace in the following code, use
sed
. This will allow$py_osx_ver
to vary in length.multibuild/osx_utils.sh
Lines 513 to 514 in 2e10577
When building for universal2 on x86-64, run the cross build first and then the native build. This will mean that the more natural native variables are in place when the code is finished, for anything that might run afterwards.