Xcode 27 raises the bar for the deployment target to macOS 12, and my customers still request binaries for 10.9.
What’s your strategy? Staying at Xcode 26 as long as possible (which at least supports 10.13), or just freeze the releases for people with <=12.? Does anybody have actual market share data?
BTW: XCode 26 isn’t compatible with macOS 27 (Golden Gate)
My current plan is my build machine keeps running Tahoe and Xcode 26, my dev machine runs the latest Xcode and my CMake file sets the deployment target based on the XCode version.
I think next major version of my product I drop Big Sur and earlier. People on old machines can download old versions if they need to install.
Food for thought on the development of these stats: do you see any major shift to newest MacOS versions in the last couple of months? Reason being: the collaboration for Pages & Numbers etc. got rail-roaded for older MacOS versions ever since the release of this creator studio suite. I always liked to stay a few versions behind, but this just got extremely enjoying on a production Mac.
I’m wondering if that makes people currently for example on Sequoia move to Golden Gate rather sooner than they would have.
When you say your customers still request binaries for 10.9, do they also expect those binaries to have all the latest updates? I’ve certainly worked at places where we would freeze the release for older systems so the binaries were still downloadable but no updates would be released for those systems. New products would also be limited to newer OS versions. My impression was that this worked well and was a reasonable compromise. I think generally speaking customers who wanted to run older systems weren’t interested in updates. They normally had a system that worked for them and they wanted to keep it that way, but that could still mean the occasional re-install.
Yes, and when they do, they’re usually satisfied with an older version; it’s mostly users with older versions of Pro Tools who request the older versions. My current products are compatible with 10.13. The jump to 12 affects nearly 2,5% of the market share (according to the numbers above)—that’s really a lot. I think I’ll keep my build system on Xcode 26 for a while longer.
Altough I think it’s a valid thought to raise the deployment target over time and give users with older systems the option to use older releases I don’t like apple dictating the time point of this step because your newly bought hardware doesn’t support that.
We just bought new mac machines for our CI with macOS 27 installed which can’t be downgraded to macOS 26, attempting to install it just fails with a message that the hardware doesn’t support macOS 26. Since installation of Xcode 26 is also not possible, the only solution currently seems to run a macOS 26 VM on them, which is a major pain.
If anyone knows any trick to either downgrade a brand new machine to macOS 26 or somehow trick macOS 27 to install Xcode 26 please share your knowledge
I haven’t tried this, although I’ve definitely done something like this a long time ago. You could try copying the SDK from Xcode 26 and putting it on your macOS 27 machine then setting SDKROOT to the path of the SDK and seeing how far that gets you. However, looking at the release notes for Xcode 27 it also says
The minimum supported deployment target on macOS for the C++ standard library has been increased to 11.0.
So I think that change would only allow you to use macOS 11 as your minimum deployment target.
So if the macOS 26 installer refuses to install on the primary volume because the hardware is too new for it, does installing it to a second volume change this constraint and somehow makes the os acceppt the hardware?
I tried to create a macOS 26 VM using Parallels, but unfortunately it seems that the internal virtualization platform doesn’t allow it. Apparently, though, VMs created on macOS 26 are supposed to run on 27 (though I haven’t tried that). Come on, Apple, why do you always do this to us?
So we have -target x86_64-apple-macos10.11 and -isysroot /Applications/Xcode-26.6.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX26.5.sdk.
After linking a universal binary we see the message
/Users/ghrunner-2/actions-runner-2/_work/JUCE-dev/JUCE-dev/examples/DemoRunner/Builds/MacOSX/DemoRunner.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 26.5.99. (in target 'DemoRunner - App' from project 'DemoRunner')