Xcode 27 MACOSX_DEPLOYMENT_TARGET>=12

Xcode 27 raises the bar for the deployment target to macOS 12, and my customers still request binaries for 10.9. :smiling_face_with_tear:

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)

Here are my current usage stats:

1.	macOS 26 (Tahoe)	     45.12%
2.	macOS 15 (Sequoia)	     25.76%
3.	macOS 27 (Golden Gate)   11.08%
4.	macOS 14 (Sonoma)	      8.84%
5.	macOS 13 (Ventura)	      4.46%
6.	macOS 12 (Monterey)	      2.39%
7.	macOS 11 (Big Sur)	      1.09%
8.	macOS 10.15 (Catalina)	  0.6%
9.	macOS 10.14 (Mojave)	  0.37%
10.	macOS 10.13 (High Sierra) 0.26%
11.	macOS 10.12 (Sierra)	  0.02%

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.

4 Likes

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.

1 Like

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.

1 Like

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 :wink:

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.

A VM may be the best solution in the short term.

Make a second APFS volume next to Mac HD and install the old OS alongside the pre-installed one. Then you can dual boot instead of using a VM.

1 Like

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?

Yes! The original OS has to be installed, but not exclusively. You won’t be able to install Sierra, but 26 is probably fine.

1 Like

Since installation of Xcode 26 is also not possible

Are you sure? Can you do the following?

brew install xcodes
xcodes install 26.6

I think that will give you Xcode 26.6 alongside Xcode 27. Then you can do something like

xcodes select 26.6

to set Xcode 26 as the default.

That process is from my memory only - the actual commands needed may be slightly different.

I was a bit imprecise here. Xcode 26 can be installed, but attempting to use it results in an error message:

Interesting to learn that Xcode can be installed through homebrew though!

Edit: I might need to re-check if it was really 26.6. Does that specific version matter for macOS 27 compatibility?

You might try to run Xcode from the terminal (didn’t checked it yet): /Applications/Xcode.app/Contents/MacOS/Xcode

Actually tried that first since it‘s a CI buildnode, didn‘t work either

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?

I’ve checked what’s running in our CI.

We have some machines running macOS 27.2, with Xcode 26.6 installed via xcodes and set as the default, and macOS 10.11 as a deployment target.

Here’s an example build command:

xcodebuild -project examples/DemoRunner/Builds/MacOSX/DemoRunner.xcodeproj -configuration Release -parallelizeTargets -verbose ONLY_ACTIVE_ARCH=NO WARNING_CFLAGS="-Wreorder -Werror" GCC_TREAT_WARNINGS_AS_ERRORS=YES -arch x86_64 ${ARM_ARCH} OTHER_CODE_SIGN_FLAGS="--timestamp" CODE_SIGN_INJECT_BASE_ENTITLEMENTS=NO HEADER_SEARCH_PATHS='$(HEADER_SEARCH_PATHS) $(HOME)/SDKs/VST2_SDK'

The first line printed by xcodebuild is:

  Command line invocation:
      /Applications/Xcode-26.6.0.app/Contents/Developer/usr/bin/xcodebuild -project examples/DemoRunner/Builds/MacOSX/DemoRunner.xcodeproj -configuration Release -parallelizeTargets -verbose ONLY_ACTIVE_ARCH=NO "WARNING_CFLAGS=-Wreorder -Werror" GCC_TREAT_WARNINGS_AS_ERRORS=YES -arch x86_64 -arch arm64 OTHER_CODE_SIGN_FLAGS=--timestamp CODE_SIGN_INJECT_BASE_ENTITLEMENTS=NO "HEADER_SEARCH_PATHS=$(HEADER_SEARCH_PATHS) $(HOME)/SDKs/VST2_SDK"

Here’s a compilation command:

    /Applications/Xcode-26.6.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c++ -ivfsstatcache /var/folders/5j/8wfq34397rjg1d0pyd53g32m0000gq/C/com.apple.DeveloperTools/26.6-17F113/Xcode/SDKStatCaches.noindex/macosx26.5-25F70-e0ccf0f438feb004bd3f7bd7c992e944.sdkstatcache -target x86_64-apple-macos10.11 -fmessage-length\\=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit\\=0 -fno-color-diagnostics -Wno-trigraphs -flto -Werror -Wno-missing-field-initializers -Wno-missing-prototypes -Wunreachable-code -Wquoted-include-in-framework-header -Wno-implicit-atomic-properties -Wno-objc-interface-ivars -Wno-arc-repeated-use-of-weak -Wimplicit-retain-self -Wnon-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-float-conversion -Wnon-literal-null-conversion -Wobjc-literal-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wdeprecated-implementations -Wno-c++11-extensions -Wno-implicit-fallthrough -isysroot /Applications/Xcode-26.6.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX26.5.sdk -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -Winvalid-offsetof -Wno-sign-conversion -Winfinite-recursion -Wmove -Wcomma -Wblock-capture-autoreleasing -Wstrict-prototypes -Wrange-loop-analysis -Wno-semicolon-before-method-body -Wreorder -Werror -Wall -Wcast-align -Wfloat-equal -Wno-ignored-qualifiers -Wsign-compare -Wsign-conversion -Wstrict-aliasing -Wswitch-enum -Wuninitialized -Wunreachable-code -Wunused-parameter -Wmissing-field-initializers -Wshadow-all -Wshorten-64-to-32 -Wconversion -Wint-conversion -Wconditional-uninitialized -Wconstant-conversion -Wbool-conversion -Wextra-semi -Wshift-sign-overflow -Wmissing-prototypes -Wnullable-to-nonnull-conversion -Wpedantic -Wdeprecated -Wunguarded-availability -Wunguarded-availability-new -Woverloaded-virtual -Wreorder -Wzero-as-null-pointer-constant -Wunused-private-field -Winconsistent-missing-destructor-override -Wall -Wcast-align -Wfloat-equal -Wno-ignored-qualifiers -Wsign-compare -Wsign-conversion -Wstrict-aliasing -Wswitch-enum -Wuninitialized -Wunreachable-code -Wunused-parameter -Wmissing-field-initializers -Wshadow-all -Wshorten-64-to-32 -Wconversion -Wint-conversion -Wconditional-uninitialized -Wconstant-conversion -Wbool-conversion -Wextra-semi -Wshift-sign-overflow -Wmissing-prototypes -Wnullable-to-nonnull-conversion -Wpedantic -Wdeprecated -Wunguarded-availability -Wunguarded-availability-new @/Users/ghrunner-2/actions-runner-2/\_work/JUCE-dev/JUCE-dev/examples/DemoRunner/Builds/MacOSX/build/DemoRunner.build/Release/DemoRunner\\ -\\ App.build/Objects-normal/x86_64/af3fcb34312c57c0f52879cdce924b91-common-args.resp -MMD -MT dependencies -MF /Users/ghrunner-2/actions-runner-2/\_work/JUCE-dev/JUCE-dev/examples/DemoRunner/Builds/MacOSX/build/DemoRunner.build/Release/DemoRunner\\ -\\ App.build/Objects-normal/x86_64/include_juce_video.d --serialize-diagnostics /Users/ghrunner-2/actions-runner-2/\_work/JUCE-dev/JUCE-dev/examples/DemoRunner/Builds/MacOSX/build/DemoRunner.build/Release/DemoRunner\\ -\\ App.build/Objects-normal/x86_64/include_juce_video.dia -c /Users/ghrunner-2/actions-runner-2/\_work/JUCE-dev/JUCE-dev/examples/DemoRunner/JuceLibraryCode/include_juce_video.mm -o /Users/ghrunner-2/actions-runner-2/\_work/JUCE-dev/JUCE-dev/examples/DemoRunner/Builds/MacOSX/build/DemoRunner.build/Release/DemoRunner\\ -\\ App.build/Objects-normal/x86_64/include_juce_video.o

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')

but it doesn’t prevent targeting 10.11.

1 Like

And then it actually runs on 10.11?

I haven’t tested running on 10.11, but a universal binary built exactly as above appears to work on 10.15.