-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix build pipelin to run on MacOS m1 architecture and/or BigSur #2
Comments
I have an M1 Max chip MBP. What can I do to help with item 2? |
Would also love a wheel for MacOS ARM 🙏 |
Any news? |
There's a pre-release for Azure pipeline that contains macOS Arm64. |
Partially Yes. But it also depends if there will be free runners for Open source projects. At this moment, one of problems is that I do not have access to macOS m1 machine. There is currently one CI provider that provides macOS ARM runners. My current plan is to modernize the building process and try to setup workflow on macos arm CI, it the test passes then we will be happy. If not, then may be a problem. |
If we could only use our local macs... I understand the CI steps, including tests are critical but, I mean, I tried to compiled imagecodecs on my mac m1 myself, using homebrew mostly but it failed. |
It is not needed. Apple supports cross-compiling. There are also other options for building wheels. The core problem is access to the device for debugging the build process when it fails. |
The imagecodecs 2023.3.16 release includes macosx_arm64 wheels. |
Thank you so much! It's now working for me on my mac. We can close this ticket. |
The current build pipeline seems to fail on MacOs m1 with BigSur on building
dav1d
library.Until CI providers have images with MacOs 10.15 there is no problem because of backward compatibility but the pipeline should be prepared to run on 11.* images.
So looking for volunteers who could:
After solving this it will be possible to provide python 3.9 wheels for macOS ARM and be prepared for python 3.10.
The text was updated successfully, but these errors were encountered: