Doing so will likely lead to crashes at runtime if the binary is then deployed to a macOS version lower than what Qt expected to run on.įor more information about SDK-based development on macOS, see Apple's developer documentation. Note: You should not lower the deployment target beyond the default value set by Qt. To raise the deployment target with CMake:

You only need to raise the deployment target if your own code uses APIs that were added in a macOS version higher than what Qt defaults to, and you are not using checks to guard their use at runtime. Qt expresses the deployment target via the CMAKE_OSX_DEPLOYMENT_TARGET or QMAKE_MACOSX_DEPLOYMENT_TARGET variables, which by default is set to the minimum supported deployment target for Qt. If the binary is launched on a macOS version below the deployment target macOS or Qt will give an error message and the application will not run. In theory this would allow running your application on every single macOS version released, but for practical (and technical) reasons there is a lower limit to this range, known as the deployment target of your application. When the binary is run on a macOS version lower than the SDK it was built with, Qt will check at runtime whether or not a platform feature is available before utilizing it. 14.sdk Target Platformsīuilding for macOS utilizes a technique called weak linking that allows you to build your application against the headers and libraries of the latest platform SDK, while still allowing your application to be deployed to macOS versions lower than the SDK version. app /Contents /Developer /Platforms /MacOSX. OLD_XCODE_BUILD=$(/usr/libexec/PlistBuddy -c 'Print CFBundleVersion' $/Contents/Info./Applications /Xcode.

NEW_XCODE='/Applications/Xcode-14.1.0.app' # To get build number The script works by changing the build version of the old Xcode 13 to the build version of the new Xcode 14, thereby tricking the OS.īefore running the script, you need to change the OLD_XCODE and NEW_XCODE variables to the correct path. There, I found this great answer in which a script is proposed that only needs to be run once to fix the problem (allowing a regular opening of Xcode 13, e. As this problem in principle is the same problem as last year, when we wanted to run Xcode 12 on macOS Monterey, it is worth to check last year's question on the same problem.

Older xcode