-
Notifications
You must be signed in to change notification settings - Fork 9
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
Bundles with unified macOS binary are broken #36
Comments
That extra .nib file looks like some issue was discovered in macOS 10.13. |
I will just ignore the mismatch and use the MainMenu.nib from the ARM build. See: |
Fixed via 23f93f1 ... even though I think it is more of a workaround. We gamble that newer macOS versions will keep on supporting the older binary plist format in |
All recent bundles with a unified binary for macOS (i.e., both x64 and ARMv8) are not usable, such as:
Meaning, the ones with the newer
OSVM 2023.12
. This is because the folder structure is different between x64 and ARMv8:We build x64 for macOS 10.9 and later. We build ARMv8 for macOS 11.0 and later.
We had to switch GitHub Actions runner from
macos-10.15
tomacos-11
. With it, we seem to use XCode 13.2.1. Through that, theusr/bin/ibtool
seems to produce an output that is now different to ensure compatibility for macOS 10.9 and later, which results inMainMenu.nib
being a folder (or bundle) with two different .nib files.More interestingly, none of those keyedobjects* files matches the MainMenu.nib from the ARMv8 build, which has compatibility for macOS 11.0 and later.
Thus, our code for creating the unified binary is broken. The .nib files do not match anymore.
All other bundles are not affected. macOS users should download dedicated x64 or ARMv8 bundles for now. The all-in-one is thus not working for macOS.
The text was updated successfully, but these errors were encountered: