This is selectable at configure time:. The Qt build system does not support building unversal binaries directly. Instead, use the lipo tool to glue two Qt builds together.
On the command-line, applications can be built using 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:. Configuring with -spec macx-xcode generates an Xcode project file from project. 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. Qt does not entirely interact with the development environment for example plugins to set a file to "mocable" from within the Xcode user interface. The result of the build process is an application bundle, which is a directory structure that contains the actual application executable.
The application can be launched by double-clicking it in Finder, or by referring directly to its executable from the command line, for example, myApp. If you wish to have a command-line tool that does not use the GUI for example, moc , uic or ls , you can tell qmake to disable bundle creation from the CONFIG variable in the project file:.
In general, Qt supports building on one macOS version and deploying to earlier or later macOS versions. The recommended way is to build on the latest version and deploy to an earlier macOS version. The application can be launched by double-clicking it in Finder, or by referring directly to its executable from the command line, for example, myApp.
If you wish to have a command-line tool that does not use the GUI for example, moc , uic or ls , you can tell qmake to disable bundle creation from the CONFIG variable in the project file:. In general, Qt supports building on one macOS version and deploying to earlier or later macOS versions.
The recommended way is to build on the latest version and deploy to an earlier macOS version. The application bundle contains the application executable as well as dependencies such as the Qt libraries, plugins, translations and other resources you may need. Third party libraries like Qt are normally not installed system-wide; each application provides its own copy. A common way to distribute applications is to provide a compressed disk image.
The deployment tool, macdeployqt available from the macOS installers , can be used to create the self-contained bundles, and optionally also create a. Applications can also be distributed through the Mac App Store. Qt 5 aims to stay within the app store sandbox rules. We invite you to explore the rest of Qt. Documentation contributions included herein are the copyrights of their respective owners.
Qt and respective logos are trademarks of The Qt Company Ltd. All other trademarks are property of their respective owners.
0コメント