Target Platform | Architecture | Build Environment |
---|---|---|
macOS 10.13, 10.14, 10.15 | x86_64 and x86_64h | Xcode 11 (10.15 SDK) |
xcode-select
tool.xcrun
command can then be used to find a particular tool in the toolchain.QMAKE_MACOSX_DEPLOYMENT_TARGET
qmake variable, which has a default value set via the makespec for macOS. You should not need to change this default, but if needed you can increase it in your project file:QMAKE_APPLE_DEVICE_ARCHS
qmake
variable. This is selectable at configure time:QMAKE_APPLE_DEVICE_ARCHS
can also be specified as a space-delimited list in order to build for multiple architectures simultaneously:qmake
and make
. Optionally, qmake
can generate project files for Xcode with -spec macx-xcode
. If you are using the binary package, qmake
generates Xcode projects by default; use -spec macx-gcc
to generate makefiles. For example:-spec macx-xcode
generates an Xcode project file from project.pro. With qmake you do not have to worry about rules for Qt's preprocessors (moc and uic) since qmake automatically handles them and ensures that everything necessary is linked into your application.myApp.app/Contents/MacOS/myApp
.moc
, uic
or ls
, you can tell qmake to disable bundle creation from the CONFIG
variable in the project file:macdeployqt
(available from the macOS installers), can be used to create the self-contained bundles, and optionally also create a .dmg archive. Applications can also be distributed through the Mac App Store. Qt 5 aims to stay within the app store sandbox rules. macdeployqt (bin/macdeployqt) can be used as a starting point for app store deployment.