I was wondering why we build with the MacOS 11.3 SDK specifically? Is there something special about that version? I just tested the MacOS 15.5 SDK because I already had it on my computer from working on something else and it built fine. Browser works as expected.
Is it for backwards compatibility or is there some other reason?
MacOS SDK Question
Moderator: dbsoft
Forum rules
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
-
Basilisk-Dev
- Astronaut
- Posts: 540
- Joined: 2022-03-23, 16:41
- Location: Chamber of Secrets
-
dbsoft
- Project Contributor
- Posts: 515
- Joined: 2020-02-21, 17:35
Re: MacOS SDK Question
It is the latest most stable SDK from the MacOS 11 series. It supports both Intel and Apple Silicon (ARM64).
There can be bugs in SDK, so I like to find one that works for my purposes and stick with it until there is a reason to change.
We are currently not using any features that require newer SDKs. There are probably many SDKs that would work, it just eliminates some unknowns.
In the future the SDKs will be Apple Silicon only, so if I move to a later SDK for some reason it will probably be in the 12-26 range so I can use the same SDK on Intel and Apple Silicon.
There can be bugs in SDK, so I like to find one that works for my purposes and stick with it until there is a reason to change.
We are currently not using any features that require newer SDKs. There are probably many SDKs that would work, it just eliminates some unknowns.
In the future the SDKs will be Apple Silicon only, so if I move to a later SDK for some reason it will probably be in the 12-26 range so I can use the same SDK on Intel and Apple Silicon.