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
[Feature request] Add macOS arm64 to Cirrus CI #12599
Comments
Cirrus does not have arm64 vms for macOS yet from what I can see. |
I think it does: https://cirrus-ci.org/guide/macOS/ It's probably new though. |
Messing around with it here |
Bear in mind it should fail because of #12577
Another known issue to be aware of is that it won’t build if qt@6 is installed. See #12477 ~ |
@clienthax I was having a look at your branch, and there are a few points about the build script I noticed. When building for Arm on macOS there are a few CMake commands that are different than for x86: -DPNG_ARM_NEON=ON <-- This is the Arm SIMD instruction set and should be on |
Just bumping this since Cirrus CI now builds the macOS artefacts using an Arm64 VM. It should be easier to implement now than before. |
I wonder if arm64 compilation is possible now and if it is could a universal2 build be done |
ill also look into building separately |
For now it's best to just have arm64 separately in CI, universal2 build is not really interesting to spend time building on CI until the arm64 build works properly |
Quick summary
Add macOS arm64 to Cirrus CI
Details
Cirrus CI currently only provides x86_64 macOS builds.
As of writing, compilation for arm64 is broken (not just on Macs). See #12577Edit: fixedThere are occasionally regressions that are introduced that go unnoticed since there are no Arm CI builds. This can be prevented with a Cirrus test build.
One argument that may be given for not doing this is that arm64 support on macOS is not fully implemented. However several 2D games such as Dragon's Crown and some of the Arkedo series do actually work.
Edit: Cirrus CI now builds the x86 macOS artefacts using an Arm64 VM, so cross-compilation is not an issue.
The text was updated successfully, but these errors were encountered: