If you want to keep things simple by only having a few files to deploy, then you must build everything statically. A future version of this document may include more information for using Xcode in the deployment process. While it is possible to use Xcode for this, Xcode has changed enough between each version that it makes it difficult to document it perfectly for each version. We will only concern ourselves with command-line tools here. Please refer to the X11 deployment documentation for information about how to deploy these 'bundle-less' applications. This will tell qmake not to put the executable inside a bundle. You probably don't want to run it in a bundle: Add this to your application's. More information about bundles is available on Apple's Developer Website.Ī Qt command line application on Mac OS X works similar to a command line application on Unix and Windows. This is specific to Mac OS X and beyond the scope of this document. As a programmer you can access bundle information in your own code. One primary advantage is that, since it is a single entity, it allows for drag-and-drop installation. The bundle provides many advantages to the user. A bundle for an application typcially contains the executable and all the resources it needs. A bundle is a directory structure that appears as a single entity when viewed in the Finder. On the Mac, a GUI application must be built and run from a bundle.

Deploying Phonon Applications on Mac OS X.Linking the Application to Qt as Frameworks.

Linking the Application to the Static Version of Qt.

We will demonstrate the procedures in terms of deploying the Plug & Paint application that is provided in Qt's examples directory. This documentation will describe how to create a bundle, and how to make sure that the application will find the resources it needs at run-time. Starting with version 4.5, Qt now includes a deployment tool that automates the prodecures described in this document.

Buidling static 5 qt for mac