-
Notifications
You must be signed in to change notification settings - Fork 38
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
MacOS dmg file not supported #21
Comments
Hi Rémi, Finally, there is an "issue" with QM on macOS caused by the fact that QM is not sourced from the Apple Store. The workaround has been described in the following places:
These are all places that came to my mind, but please let me know if you think of any other places or ways to make this information stand out and become available to QM users, like yourself. Thanks again for reporting, |
QM is indeed built as an Apple-silicon-only app (see image), which means Intel-based Macs that are still supported by Apple and are capable of running the newly released macOS Sequoia--such as mine--cannot run QM. Is it possible for you to build QM as a universal binary instead of an Apple-silicon-only binary (see https://developer.apple.com/documentation/apple-silicon/porting-your-macos-apps-to-apple-silicon)? |
We want to support the x86-based Macs, but we've already replaced our old Mac machines with newer ARM-based ones. The default Qt installer doesn't offer options to build "universal binaries" when run on the ARM-based Macs. Frankly, Apple pushing the burden of their hardware incompatibilities on all the vendors is a bit unfair... |
Hello,
first of all, thank you very much for your incredible work!
I work on macOS sonoma processor intel and the application QM modeling tools works perfectly until version 5.3.0. However, from this version onwards the following .dmg even applying the function $ xattr -c qm_-macos.dmg produces the following error “You can't open the application ‘qm’ because this application is not supported on this Mac.”
Are you aware of the problem? Is there a possible fix?
Best regards,
Rémi
The text was updated successfully, but these errors were encountered: