-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
maybe adapt Mac build script to macOS 10.15 madness #6128
Comments
if we choose option 2, what is the lowest version it would run on? |
If we build on macOS 10.14, I don't think there is any guarantee that it runs on older Macs than that. |
I think option 2 is reasonable. |
Now that we increased the min supported macOS version re spesmilo#6128 anyway. Per spesmilo#3685 (comment), Qt 5.14 needs at least macOS 10.13
Now that we increased the min supported macOS version re spesmilo#6128 anyway. Per spesmilo#3685 (comment), Qt 5.14 needs at least macOS 10.13
Now that we increased the min supported macOS version re #6128 anyway. Per #3685 (comment), Qt 5.14 needs at least macOS 10.13
Now that we increased the min supported macOS version re spesmilo#6128 anyway. Per spesmilo#3685 (comment), Qt 5.14 needs at least macOS 10.13
macOS 10.15 "Catalina" continues the walled garden lock-down tradition of Apple,
in turn making things harder for developers, again.
see pyinstaller/pyinstaller#4629
AFAIU:
Options:
We could build two binaries, a modern and a legacy/compat one.
The modern binary would be built on either 10.14 or 10.15, and we would try to comply with all the maddeningly more and more complex quirks they want.
The legacy binary would be built on 10.11 (as now), without any of the new requirements they impose.
Then, users of modern Macs would use the modern binary, and users of older Macs could use the legacy binary.
We could build just a modern binary, that only runs on new Macs.
We could build just a legacy binary which is effectively what our current build script does. This runs on old Macs; and can be made to run on modern Macs too, at least for now, but the users need to go deep into the system settings every time they want to run such a binary for the first time.
We could even stop building binaries for MacOS completely because what Apple is doing is increasingly frustrating and is taking up non-negligible time of ours.
The text was updated successfully, but these errors were encountered: