Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[macOS] Issues introduced by macOS 10.14 and 10.15 #4109
This issue replaces issue #3455
Description of issues introduced by macOS 10.14 and 10.15
1) "The Battle for Wesnoth" would like to receive keystrokes from any application.
Apple added some new privacy monitoring tools to his new macOS 10.15 Catalina. Problem is that for some reason macOS thinks that Wesnoth want's to receive keystrokes (for hotkeys (probably)) even while we aren't inside wesnoth.
And the log is full of these messages:
2) Notarizing - Enable hardened runtime
Apple wants to control even apps, distributed outside of the Mac AppStore. Wesnoth is in available in Mac AppStore right now, but that doesn't mean, we can pass notarizing requirements without any problems. We have to enable hardened runtime for wesnoth. I was trying to enable hardened runtime once but there was some problem with it and I can't remember exactly which. I need to test it more. For more informations about notarizing, use this link: https://developer.apple.com/news/?id=06032019i .
3) OpenGL deprecation (Long term issue)
Long story short: In macOS 10.14 apple deprecated OpenGL in favour of Metal. That's sad information for wesnoth as wesnoth 1.15 was planned to migrate to the OpenGL.
So far there are these options:
referenced this issue
Jun 8, 2019
Issue 1: This may indicate a problem with other platforms. I'd suggest a separate PR against 1.14 and/or Master, and not just for macOS (initially) so we can check.
Issue 2: Probably macOS-specific. Sounds like a good idea, if you can get it working. Probably needs a quick check to see if the changes should be cross-platform, but I'd be surprised if they are.
Issue 3: Isn't this a non-issue? We don't use OpenGL. Agreed macOS probably won't take it out any time soon, but this IS Apple and they do what they want, so it might go away tomorrow. If we're truly not using OpenGL, is there a problem with eliminating it completely?
Issue 2: Enabling hardened runtime is question of checking one checkbox in Xcode project. I already checked it once, but I have to revert that change an I am not sure why. 9ee9721
Issue 3: Yes, it is, but branch 1.15 is still planed to be merged with OpenGL branch.
There are no immediate plans, sure, but it's still a possibility in the future. In any case, I don't think Apple will outright drop OpenGL for a very long time, and even if it eventually does, I expect something like MoltenGL will be readily available by then.
As for the other issues, personally I don't really care about #2 and thus won't comment on it, but regarding #1... is it possible it's either a bug in SDL or an unfortunate side-effect of how SDL handles input?