<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- qmake-manual.qdoc -->
<title>Qt 4.8: qmake Platform Notes</title>
<link rel="stylesheet" type="text/css" href="style/style.css" />
<script src="scripts/jquery.js" type="text/javascript"></script>
<script src="scripts/functions.js" type="text/javascript"></script>
<link rel="stylesheet" type="text/css" href="style/superfish.css" />
<link rel="stylesheet" type="text/css" href="style/narrow.css" />
<!--[if IE]>
<meta name="MSSmartTagsPreventParsing" content="true">
<meta http-equiv="imagetoolbar" content="no">
<![endif]-->
<!--[if lt IE 7]>
<link rel="stylesheet" type="text/css" href="style/style_ie6.css">
<![endif]-->
<!--[if IE 7]>
<link rel="stylesheet" type="text/css" href="style/style_ie7.css">
<![endif]-->
<!--[if IE 8]>
<link rel="stylesheet" type="text/css" href="style/style_ie8.css">
<![endif]-->
<script src="scripts/superfish.js" type="text/javascript"></script>
<script src="scripts/narrow.js" type="text/javascript"></script>
</head>
<body class="" onload="CheckEmptyAndLoadList();">
<div class="header" id="qtdocheader">
<div class="content">
<div id="nav-logo">
<a href="index.html">Home</a></div>
<a href="index.html" class="qtref"><span>Qt Reference Documentation</span></a>
<div id="narrowsearch"></div>
<div id="nav-topright">
<ul>
<li class="nav-topright-home"><a href="http://qt.digia.com/">Qt HOME</a></li>
<li class="nav-topright-dev"><a href="http://qt-project.org/">DEV</a></li>
<li class="nav-topright-doc nav-topright-doc-active"><a href="http://qt-project.org/doc/">
DOC</a></li>
<li class="nav-topright-blog"><a href="http://blog.qt.digia.com/">BLOG</a></li>
</ul>
</div>
<div id="shortCut">
<ul>
<li class="shortCut-topleft-inactive"><span><a href="index.html">Qt 4.8</a></span></li>
<li class="shortCut-topleft-active"><a href="http://qt-project.org/doc/">ALL VERSIONS </a></li>
</ul>
</div>
<ul class="sf-menu" id="narrowmenu">
<li><a href="#">API Lookup</a>
<ul>
<li><a href="classes.html">Class index</a></li>
<li><a href="functions.html">Function index</a></li>
<li><a href="modules.html">Modules</a></li>
<li><a href="namespaces.html">Namespaces</a></li>
<li><a href="qtglobal.html">Global Declarations</a></li>
<li><a href="qdeclarativeelements.html">QML elements</a></li>
</ul>
</li>
<li><a href="#">Qt Topics</a>
<ul>
<li><a href="qt-basic-concepts.html">Programming with Qt</a></li>
<li><a href="qtquick.html">Device UIs & Qt Quick</a></li>
<li><a href="qt-gui-concepts.html">UI Design with Qt</a></li>
<li><a href="supported-platforms.html">Supported Platforms</a></li>
<li><a href="technology-apis.html">Qt and Key Technologies</a></li>
<li><a href="best-practices.html">How-To's and Best Practices</a></li>
</ul>
</li>
<li><a href="#">Examples</a>
<ul>
<li><a href="all-examples.html">Examples</a></li>
<li><a href="tutorials.html">Tutorials</a></li>
<li><a href="demos.html">Demos</a></li>
<li><a href="qdeclarativeexamples.html">QML Examples</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div class="wrapper">
<div class="hd">
<span></span>
</div>
<div class="bd group">
<div class="sidebar">
<div class="searchlabel">
Search index:</div>
<div class="search" id="sidebarsearch">
<form id="qtdocsearch" action="" onsubmit="return false;">
<fieldset>
<input type="text" name="searchstring" id="pageType" value="" />
<div id="resultdialog">
<a href="#" id="resultclose">Close</a>
<p id="resultlinks" class="all"><a href="#" id="showallresults">All</a> | <a href="#" id="showapiresults">API</a> | <a href="#" id="showarticleresults">Articles</a> | <a href="#" id="showexampleresults">Examples</a></p>
<p id="searchcount" class="all"><span id="resultcount"></span><span id="apicount"></span><span id="articlecount"></span><span id="examplecount"></span> results:</p>
<ul id="resultlist" class="all">
</ul>
</div>
</fieldset>
</form>
</div>
<div class="box first bottombar" id="lookup">
<h2 title="API Lookup"><span></span>
API Lookup</h2>
<div id="list001" class="list">
<ul id="ul001" >
<li class="defaultLink"><a href="classes.html">Class index</a></li>
<li class="defaultLink"><a href="functions.html">Function index</a></li>
<li class="defaultLink"><a href="modules.html">Modules</a></li>
<li class="defaultLink"><a href="namespaces.html">Namespaces</a></li>
<li class="defaultLink"><a href="qtglobal.html">Global Declarations</a></li>
<li class="defaultLink"><a href="qdeclarativeelements.html">QML elements</a></li>
</ul>
</div>
</div>
<div class="box bottombar" id="topics">
<h2 title="Qt Topics"><span></span>
Qt Topics</h2>
<div id="list002" class="list">
<ul id="ul002" >
<li class="defaultLink"><a href="qt-basic-concepts.html">Programming with Qt</a></li>
<li class="defaultLink"><a href="qtquick.html">Device UIs & Qt Quick</a></li>
<li class="defaultLink"><a href="qt-gui-concepts.html">UI Design with Qt</a></li>
<li class="defaultLink"><a href="supported-platforms.html">Supported Platforms</a></li>
<li class="defaultLink"><a href="technology-apis.html">Qt and Key Technologies</a></li>
<li class="defaultLink"><a href="best-practices.html">How-To's and Best Practices</a></li>
</ul>
</div>
</div>
<div class="box" id="examples">
<h2 title="Examples"><span></span>
Examples</h2>
<div id="list003" class="list">
<ul id="ul003">
<li class="defaultLink"><a href="all-examples.html">Examples</a></li>
<li class="defaultLink"><a href="tutorials.html">Tutorials</a></li>
<li class="defaultLink"><a href="demos.html">Demos</a></li>
<li class="defaultLink"><a href="qdeclarativeexamples.html">QML Examples</a></li>
</ul>
</div>
</div>
</div>
<div class="wrap">
<div class="toolbar">
<div class="breadcrumb toolblock">
<ul>
<li class="first"><a href="index.html">Home</a></li>
<!-- Breadcrumbs go here -->
<li>qmake Platform Notes</li>
</ul>
</div>
<div class="toolbuttons toolblock">
<ul>
<li id="smallA" class="t_button">A</li>
<li id="medA" class="t_button active">A</li>
<li id="bigA" class="t_button">A</li>
<li id="print" class="t_button"><a href="javascript:this.print();">
<span>Print</span></a></li>
</ul>
</div>
</div>
<div class="content mainContent">
<link rel="prev" href="qmake-running.html" />
<link rel="next" href="qmake-advanced-usage.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="qmake-running.html">Running qmake</a>
<a class="nextPage" href="qmake-advanced-usage.html">qmake Advanced Usage</a>
</p><p/>
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#mac-os-x">Mac OS X</a></li>
<li class="level2"><a href="#source-and-binary-packages">Source and Binary Packages</a></li>
<li class="level2"><a href="#using-frameworks">Using Frameworks</a></li>
<li class="level2"><a href="#creating-frameworks">Creating Frameworks</a></li>
<li class="level2"><a href="#creating-universal-binaries">Creating Universal Binaries</a></li>
<li class="level2"><a href="#creating-and-moving-xcode-projects">Creating and Moving Xcode Projects</a></li>
<li class="level2"><a href="#on-supporting-two-build-targets-simultaneously">On supporting two build targets simultaneously</a></li>
<li class="level1"><a href="#windows">Windows</a></li>
<li class="level2"><a href="#creating-visual-studio-project-files">Creating Visual Studio Project Files</a></li>
<li class="level2"><a href="#visual-studio-2005-manifest-files">Visual Studio 2005 Manifest Files</a></li>
<li class="level1"><a href="#symbian-platform">Symbian Platform</a></li>
<li class="level2"><a href="#handling-of-static-data">Handling of Static Data</a></li>
<li class="level2"><a href="#stack-and-heap-size">Stack and Heap Size</a></li>
<li class="level2"><a href="#compiler-specific-options">Compiler-Specific Options</a></li>
<li class="level2"><a href="#unique-identifiers">Unique Identifiers</a></li>
<li class="level2"><a href="#capabilities">Capabilities</a></li>
</ul>
</div>
<h1 class="title">qmake Platform Notes</h1>
<span class="subtitle"></span>
<!-- $$$qmake-platform-notes.html-description -->
<div class="descr"> <a name="details"></a>
<p>Many cross-platform projects can be handled by the <tt>qmake</tt>'s basic configuration features. On some platforms, it is sometimes useful, or even necessary, to take advantage of platform-specific features. <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> knows about many of these features, and these can be accessed via specific variables that only have an effect on the platforms where they are relevant.</p>
<a name="mac-os-x"></a>
<h2>Mac OS X</h2>
<p>Features specific to this platform include support for creating universal binaries, frameworks and bundles.</p>
<a name="source-and-binary-packages"></a>
<h3>Source and Binary Packages</h3>
<p>The version of <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> supplied in source packages is configured slightly differently to that supplied in binary packages in that it uses a different feature specification. Where the source package typically uses the <tt>macx-g++</tt> specification, the binary package is typically configured to use the <tt>macx-xcode</tt> specification.</p>
<p>Users of each package can override this configuration by invoking <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> with the <tt>-spec</tt> option (see <a href="qmake-running.html">Running qmake</a> for more information). This makes it possible, for example, to use <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> from a binary package to create a Makefile in a project directory with the following command line invocation:</p>
<pre class="cpp"> qmake -spec macx-g++</pre>
<a name="using-frameworks"></a>
<h3>Using Frameworks</h3>
<p><a href="qmake-manual.html#qmake"><tt>qmake</tt></a> is able to automatically generate build rules for linking against frameworks in the standard framework directory on Mac OS X, located at <tt>/Library/Frameworks/</tt>.</p>
<p>Directories other than the standard framework directory need to be specified to the build system, and this is achieved by appending linker options to the <a href="qmake-variable-reference.html#qmake-lflags">QMAKE_LFLAGS</a> variable, as shown in the following example:</p>
<pre class="cpp"> QMAKE_LFLAGS += -F/path/to/framework/directory/</pre>
<p>The framework itself is linked in by appending the <tt>-framework</tt> options and the name of the framework to the <a href="qmake-variable-reference.html#libs">LIBS</a> variable:</p>
<pre class="cpp"> LIBS += -framework TheFramework</pre>
<a name="creating-frameworks"></a>
<h3>Creating Frameworks</h3>
<p>Any given library project can be configured so that the resulting library file is placed in a <a href="http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WhatAreFrameworks.html">framework</a>, ready for deployment. To do this, set up the project to use the <a href="qmake-variable-reference.html#template"><tt>lib</tt> template</a> and add the <tt>lib_bundle</tt> option to the <a href="qmake-variable-reference.html#config">CONFIG</a> variable:</p>
<pre class="cpp"> TEMPLATE = lib
CONFIG += lib_bundle</pre>
<p>The data associated with the library is specified using the <a href="qmake-variable-reference.html#qmake-bundle-data">QMAKE_BUNDLE_DATA</a> variable. This holds items that will be installed with a library bundle, and is often used to specify a collection of header files, as in the following example:</p>
<pre class="cpp"> FRAMEWORK_HEADERS.version = Versions
FRAMEWORK_HEADERS.files = path/to/header_one.h path/to/header_two.h
FRAMEWORK_HEADERS.path = Headers
QMAKE_BUNDLE_DATA += FRAMEWORK_HEADERS</pre>
<p>Here, the <tt>FRAMEWORK_HEADERS</tt> variable is a user-defined variable that is used to define the headers required to use a particular framework. Appending it to the <tt>QMAKE_BUNDLE_DATA</tt> variable ensures that the information about these headers are added to the collection of resources that will be installed with the library bundle. Also, the framework's name and version are specified by <a href="qmake-variable-reference.html#qmake-framework-bundle-name">QMAKE_FRAMEWORK_BUNDLE_NAME</a> and <a href="qmake-variable-reference.html#qmake-framework-version">QMAKE_FRAMEWORK_VERSION</a> variables. By default, the values used for these are obtained from the <a href="qmake-variable-reference.html#target">TARGET</a> and <a href="qmake-variable-reference.html#version">VERSION</a> variables.</p>
<p>See <a href="deployment-mac.html">Deploying an Application on Mac OS X</a> for more information about deploying applications and libraries.</p>
<a name="creating-universal-binaries"></a>
<h3>Creating Universal Binaries</h3>
<p>To create a universal binary for your application, you need to be using a version of Qt that has been configured with the <tt>-universal</tt> option.</p>
<p>The architectures to be supported in the binary are specified with the <a href="qmake-variable-reference.html#config">CONFIG</a> variable. For example, the following assignment causes <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> to generate build rules to create a universal binary for both PowerPC and x86 architectures:</p>
<pre class="cpp"> CONFIG += x86 ppc</pre>
<p>Additionally, developers using a PowerPC-based platform need to set the <a href="qmake-variable-reference.html#qmake-mac-sdk">QMAKE_MAC_SDK</a> variable. This process is discussed in more detail in the <a href="deployment-mac.html#architecture-dependencies">deployment guide for Mac OS X</a>.</p>
<a name="creating-and-moving-xcode-projects"></a>
<h3>Creating and Moving Xcode Projects</h3>
<p>Developers on Mac OS X can take advantage of <tt>qmake</tt>'s support for Xcode project files, as described in <a href="qtmac-as-native.html#development-tools">Qt is Mac OS X Native</a>, by running <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> to generate an Xcode project from an existing <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> project files. For example:</p>
<pre class="cpp"> qmake -spec macx-xcode project.pro</pre>
<p>Note that, if a project is later moved on the disk, <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> must be run again to process the project file and create a new Xcode project file.</p>
<a name="on-supporting-two-build-targets-simultaneously"></a>
<h3>On supporting two build targets simultaneously</h3>
<p>Implementing this is currently not feasible, because the <a href="deployment-mac.html#xcode">XCode</a> concept of Active Build Configurations is conceptually different from the qmake idea of build targets.</p>
<p>The <a href="deployment-mac.html#xcode">XCode</a> Active Build Configurations settings are for modifying xcode configurations, compiler flags and similar build options. Unlike Visual Studio, <a href="deployment-mac.html#xcode">XCode</a> does not allow for the selection of specific library files based on whether debug or release build configurations are selected. The qmake debug and release settings control which library files are linked to the executable.</p>
<p>It is currently not possible to set files in <a href="deployment-mac.html#xcode">XCode</a> configuration settings from the qmake generated xcode project file. The way the libraries are linked in the "Frameworks & Libraries" phase in the <a href="deployment-mac.html#xcode">XCode</a> build system.</p>
<p>Furthermore, the selected "Active Build Configuration" is stored in a .pbxuser file, which is generated by xcode on first load, not created by qmake.</p>
<a name="windows"></a>
<h2>Windows</h2>
<p>Features specific to this platform include support for creating Visual Studio project files and handling manifest files when deploying Qt applications developed using Visual Studio 2005.</p>
<a name="creating-visual-studio-project-files"></a>
<h3>Creating Visual Studio Project Files</h3>
<p>Developers using Visual Studio to write Qt applications can use the Visual Studio integration facilities provided with the Qt Commercial Edition and do not need to worry about how project dependencies are managed.</p>
<p>However, some developers may need to import an existing <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> project into Visual Studio. <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> is able to take a project file and create a Visual Studio project that contains all the necessary information required by the development environment. This is achieved by setting the <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> <a href="qmake-variable-reference.html#template">project template</a> to either <tt>vcapp</tt> (for application projects) or <tt>vclib</tt> (for library projects).</p>
<p>This can also be set using a command line option, for example:</p>
<pre class="cpp"> qmake -tp vc</pre>
<p>It is possible to recursively generate <tt>.vcproj</tt> files in subdirectories and a <tt>.sln</tt> file in the main directory, by typing:</p>
<pre class="cpp"> qmake -tp vc -r</pre>
<p>Each time you update the project file, you need to run <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> to generate an updated Visual Studio project.</p>
<p><b>Note:</b> If you are using the Visual Studio Add-in, you can import <tt>.pro</tt> files via the <b>Qt->Import from .pro file</b> menu item.</p>
<a name="visual-studio-2005-manifest-files"></a>
<h3>Visual Studio 2005 Manifest Files</h3>
<p>When deploying Qt applications built using Visual Studio 2005, it is necessary to ensure that the manifest file, created when the application was linked, is handled correctly. This is handled automatically for projects that generate DLLs.</p>
<p>Removing manifest embedding for application executables can be done with the following assignment to the <a href="qmake-variable-reference.html#config">CONFIG</a> variable:</p>
<pre class="cpp"> CONFIG -= embed_manifest_exe</pre>
<p>Also, the manifest embedding for DLLs can be removed with the following assignment to the <a href="qmake-variable-reference.html#config">CONFIG</a> variable:</p>
<pre class="cpp"> CONFIG -= embed_manifest_dll</pre>
<p>This is discussed in more detail in the <a href="deployment-windows.html#visual-studio-2005-onwards">deployment guide for Windows</a>.</p>
<a name="symbian-platform"></a>
<h2>Symbian Platform</h2>
<p>Features specific to this platform include handling of static data, capabilities, stack and heap size, compiler specific options, and unique identifiers for the application or library.</p>
<a name="handling-of-static-data"></a>
<h3>Handling of Static Data</h3>
<p>If the application uses any static data, the build system needs to be informed about it. This is because Symbian tries to save memory if no static data is in use.</p>
<p>To specify that static data support is desired, add this to the project file:</p>
<pre class="cpp"> TARGET.EPOCALLOWDLLDATA = 1</pre>
<p>The default value is zero.</p>
<a name="stack-and-heap-size"></a>
<h3>Stack and Heap Size</h3>
<p>The Symbian platform uses predefined sizes for stacks and heaps. If an application exceeds either limit, it may crash or fail to complete its task. Crashes that seem to have no reason can often be traced back to insufficient stack and/or heap sizes.</p>
<p>The stack size has a maximum value, whereas the heap size has a minimum and a maximum value, all specified in bytes. The minimum value prevents the application from starting if that amount of memory is not available. The minimum and maximum values are separated by a space. For example:</p>
<pre class="cpp"> TARGET.EPOCHEAPSIZE = 10000 10000000
TARGET.EPOCSTACKSIZE = 0x8000</pre>
<p>The default values depend on the version of the Symbian SDK you're using, however, the Qt toolchain sets this to the maximum possible value and this should not be changed.</p>
<a name="compiler-specific-options"></a>
<h3>Compiler-Specific Options</h3>
<p>General compiler options can as usual be set using <tt>QMAKE_CFLAGS</tt> and <tt>QMAKE_CXXFLAGS</tt>. In order to set specific compiler options, <tt>QMAKE_CFLAGS.<compiler></tt> and <tt>QMAKE_CXXFLAGS.<compiler></tt> can be used. <tt><compiler></tt> can be either <tt>CW</tt> for the WINSCW architecture (emulator), or <tt>ARMCC</tt> for the ARMv5 architecture (hardware), or <tt>GCCE</tt> for the ARMv5 architecture (hardware).</p>
<p>Here is an example:</p>
<pre class="cpp"> QMAKE_CXXFLAGS.CW += -O2
QMAKE_CXXFLAGS.ARMCC += -O0</pre>
<a name="unique-identifiers"></a>
<h3>Unique Identifiers</h3>
<p>Symbian applications may have unique identifiers attached to them. Here is how to define them in a project file:</p>
<p>There are four available types of IDs supported: <tt>UID2</tt>, <tt>UID3</tt>, <tt>SID</tt>, and <tt>VID</tt>. They are specified like this:</p>
<pre class="cpp"> TARGET.UID2 = 0x00000001
TARGET.UID3 = 0x00000002
TARGET.SID = 0x00000003
TARGET.VID = 0x00000004</pre>
<p>If <tt>SID</tt> is not specified, it defaults to the same value as <tt>UID3</tt>. If <tt>UID3</tt> is not specified, qmake will automatically generate a <tt>UID3</tt> suitable for development and debugging. This value should be manually specified for applications that are to be released. See the <a href="http://www.symbiansigned.com">Symbian Signed</a> Web site for information about obtaining an official UID. Both <tt>SID</tt> and <tt>VID</tt> default to empty values.</p>
<p>There exists one UID1 too, but this should not be touched by any application.</p>
<p>The UID2 has a specific value for different types of files; e.g. apps/exes are always 0x100039CE. The toolchain will set this for value for the most common file types like, EXE/APP and shared library DLL.</p>
<p>For more information about unique identifiers and their meaning for Symbian applications, please refer to the <a href="http://wiki.forum.nokia.com/index.php/UID_Q&As_(Symbian_Signed)">UID Q&As (Symbian Signed)</a> page in the <a href="http://wiki.forum.nokia.com/">Forum Nokia Wiki</a> for more information.</p>
<a name="capabilities"></a>
<h3>Capabilities</h3>
<p>Capabilities define extra privileges for the application, such as the ability to list all files on the file system. Capabilities are defined in the project file like this:</p>
<pre class="cpp"> TARGET.CAPABILITY += AllFiles</pre>
<p>It is also possible to specify which capabilities <i>not</i> to have, by first specifying <tt>ALL</tt> and then list the unwanted capabilities with a minus in front of them, like this:</p>
<pre class="cpp"> TARGET.CAPABILITY = ALL -TCB -DRM -AllFiles</pre>
<p>For more information about capabilities, please refer to the Symbian SDK documentation.</p>
</div>
<!-- @@@qmake-platform-notes.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="qmake-running.html">Running qmake</a>
<a class="nextPage" href="qmake-advanced-usage.html">qmake Advanced Usage</a>
</p>
</div>
</div>
</div>
<div class="ft">
<span></span>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2015 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.</p>
<br />
<p>
The documentation provided herein is licensed under the terms of the
<a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation
License version 1.3</a> as published by the Free Software Foundation.</p>
<p>
Documentation sources may be obtained from <a href="http://www.qt-project.org">
www.qt-project.org</a>.</p>
<br />
<p>
Qt and respective logos are trademarks of The Qt Company Ltd
in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. <a title="Privacy Policy"
href="http://en.gitorious.org/privacy_policy/">Privacy Policy</a></p>
</div>
<script src="scripts/functions.js" type="text/javascript"></script>
</body>
</html>
