-
Notifications
You must be signed in to change notification settings - Fork 227
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
Native Apple M1 releases (arm64) #2357
Comments
I‘d prefer universal builds. Why should we provide 3 macOS binaries? Doesn’t that confuse people? How much work are universal builds? |
Yep, a single build would be best (+ legacy...).
I can't judge. I think it's possible ( |
My initial tests were done on macos-11 with latest Xcode. While we can do that if we have a dedicated M1 build, we decided against updating to those versions for the existing build (see #2463). Per the docs, it should be sufficient:
|
@hoffie is this likely to make 3.9.0? |
@pljones I think this would need macOS builds with Qt 6 |
Moved to 3.9.1. |
Qt is supposed to have rather good support for universal binaries ( Raw |
Re-Opening as the universal build is something for the next version. |
I've opened new issues for the two remaining items of this issue (universal binaries, signing). I'm therefore closing this issue. |
Has this feature been discussed and generally agreed?
Apple M1 is currently supported via Rosetta 2. There is demand for native builds. This issue tracks the required work.
Describe the solution you'd like
Describe alternatives that have been considered
There've been no reports about problems with running the x86_64 builds via Rosetta 2 on M1. Still, running something latency-critical as Jamulus via potentially avoidable translation layers sounds non-optimal.
The text was updated successfully, but these errors were encountered: