Xcode 14.1 build target

[DaveH]

Hi, I’m trying to target at least 10.9 with MacOS 13.0 SDK
It worked before, but now I’ve upgraded to Xcode 14.1 I’m getting this worrying warning.
Does anyone know if this is problem, and how do I fix it, if possible?
Thanks,
Dave

[leehu]

You’ll need to go back to using XCode 13 in order to build for anything before Monterey.
You can download a version and run it side by side with XCode 14.

Ventura and xcode14

I finally upgraded my secondary laptop to Ventura and can confirm the workaround is possible. After upgrading the OS, just rename Xcode.app to Xcode13.app, install Xcode 14 and then launch Xcode13 using the terminal. /Applications/Xcode13.app/Contents/MacOS/Xcode This leads to an “interesting” about dialog, and obviously shouldn’t be used for production builds, but otherwise it appears to work mostly fine (so far). [Screenshot 2022-11-21 at 11.33.45]

[DaveH]

@leehu Just getting it, thanks.
Oh Apple!

“10.13 to 13.0.99” is a weird message.

[eyalamir]

That warning is lying, it still works.

[DaveH]

I have no way of testing 10.9 here, sorry, but have you checked it still works?

[leehu]

I’ve had people on 10.14 messaging me saying that they can’t install a build I’ve created on XCode 14.

I had to go back and build on XCode 13.

[DaveH]

So I can’t target to old MacOS at all, and I can’t install Xcode 13 on Ventura. DOH!
So I guess I’m targeting only the latest MacOS.

Goodbye customers

I don’t really know what to do now. Apart form throw the Mac out the Window.

[daniel]

@DaveH

So I can’t target to old MacOS at all, and I can’t install Xcode 13 on Ventura.

I don’t know with which version it works, but throwing into here, that on Monterrey I could not install Xcode 12, which was required for a client project. But it was perfectly possible to copy the xip file to /Applications/XCode-12.4.app and set it via

sudo xcode-select -s /Applications/Xcode-12.4.app/Contents/Developer

You cannot use the IDE, but you can compile (we have to use QtCreator, since it is a QT project anyway.

Maybe this helps to find a workaround?

[eyalamir]

What do you get if you run:

otool -l "MyPlugin.vst3/Contents/MacOS/MyPlugin" | grep -E -A4 '(LC_VERSION_MIN_MACOSX|LC_BUILD_VERSION)' | grep -B1 sdk

?
In my tests I was able to build for 10.9 and get the correct result (for Intel machines, the minimum for ARM is 11.0).

I believe @FigBug has also tested it on older Mac OS versions.
P.S. The “official” support now is for 10.13 and above, make sure you actually see the right target in xcode and don’t let it change the mininum ‘for you’.

(In our code we target 10.13 anyway, and got 0 complaints after upgrading to Xcode 14)

[DaveH]

@daniel

sudo xcode-select -s /Applications/Xcode-12.4.app/Contents/Developer

Thanks for the help Daniel, but it didn’t work.

[DaveH]

I’m just going to go with dropping any pre-High Sierra.
Sorry customers, but it is Apple’s wish you see.

[leehu]

I get the following:
version 10.11
sdk 13.0

minos 11.0
  sdk 13.0

[Mitchco]

Also on Xcode 14.1, MacOS Monterey 12.6.

Build a VST3 that is set to target Any Mac (Apple Silicon, Intel)

Starting the build as normal:

And then towards the end of the build process, it switches to targeting just my Mac:

I had to run it a couple of times as I thought I had made a mistake (which still may be the case).

Any ideas?