Architecturesīy default, Qt will build for the architecture of your development machine - either x86_64 if you're on an Intel Mac, or arm64 if you are on an Apple Silicon Mac. This technique allows Apple to ensure that binaries built long before the new SDK and operating system was released will still continue to run without regressions on new macOS releases.īuilding against an older SDK is a last-resort solution, and should only be applied if your application has no other ways of working around the problem. One caveat to using the latest Xcode version and SDK to build your application is that macOS's system frameworks will sometimes decide whether or not to enable behavior changes based on the SDK you built your application with.įor example, when dark-mode was introduced in macOS 10.14 Mojave, macOS would only treat applications built against the 10.14 SDK as supporting dark-mode, and would leave applications built against earlier SDKs with the default light mode look. 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. Note you should stop getting the error: xcrun: error: unable to load libxcrun (dlopen(/Library/Developer/CommandLineTools/usr/lib/libxcrun.dylib, 0x0005): tried: '/Library/Developer/CommandLineTools/usr/lib/libxcrun.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/lib/libxcrun.dylib' (no such file))./Applications /Xcode. For me ~13mins.Īfter that your issues with P圜harm, git, brew and likely other tools will be resolved. Then agree to it and it should download after a couple of minutes. Then install the command line tools (CLT) again: xcode-select -install Output xcode-select: error: unable to get active developer directory, use `sudo xcode-select -switch path/to/Xcode.app` to set one (or see `man xcode-select`) So do ( source): sudo rm -rf /Library/Developer/CommandLineToolsĬheck it uninstalled, you should get an output as follows: xcode-select -p What I suggest is to uninstall the command line tools (CLT) and re-install them the official way. Homebrew Ruby: 2.3.3 => /System/Library/Frameworks/amework/Versions/2.3/usr/bin/ruby CLT is now installed and homebrew is detecting it just fine.īrew Config now: HOMEBREW_VERSION: 1.5.14 I downloaded the CLT as a pkg from the apple developer website ( ) and installed it the old fashioned way. Leaving it here if anyone else has the same problem in the future:ĭoing xcode-select -install showed everything as being installed correctly but I just couldn't confirm that anywhere. found a solution which I should have tried a lot earlier in all honesty. Okay, After a full day of attempts, re-installing homebrew and all.

Xcode select install high sierra