<?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 Variable Reference</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 Variable Reference</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-reference.html" />
<link rel="next" href="qmake-function-reference.html" />
<p class="naviNextPrevious headerNavi">
<a class="prevPage" href="qmake-reference.html">qmake Reference</a>
<a class="nextPage" href="qmake-function-reference.html">qmake Function Reference</a>
</p><p/>
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#backup-registration-file-maemo">BACKUP_REGISTRATION_FILE_MAEMO</a></li>
<li class="level1"><a href="#backup-registration-file-symbian">BACKUP_REGISTRATION_FILE_SYMBIAN</a></li>
<li class="level1"><a href="#bld-inf-rules">BLD_INF_RULES</a></li>
<li class="level1"><a href="#config">CONFIG</a></li>
<li class="level1"><a href="#defines">DEFINES</a></li>
<li class="level1"><a href="#def-file">DEF_FILE</a></li>
<li class="level1"><a href="#dependpath">DEPENDPATH</a></li>
<li class="level1"><a href="#deployment">DEPLOYMENT</a></li>
<li class="level1"><a href="#deployment-plugin">DEPLOYMENT_PLUGIN</a></li>
<li class="level1"><a href="#destdir">DESTDIR</a></li>
<li class="level1"><a href="#destdir-target">DESTDIR_TARGET</a></li>
<li class="level1"><a href="#dlldestdir">DLLDESTDIR</a></li>
<li class="level1"><a href="#distfiles">DISTFILES</a></li>
<li class="level1"><a href="#dsp-template">DSP_TEMPLATE</a></li>
<li class="level1"><a href="#forms">FORMS</a></li>
<li class="level1"><a href="#forms3">FORMS3</a></li>
<li class="level1"><a href="#guid">GUID</a></li>
<li class="level1"><a href="#headers">HEADERS</a></li>
<li class="level1"><a href="#icon">ICON</a></li>
<li class="level1"><a href="#includepath">INCLUDEPATH</a></li>
<li class="level1"><a href="#installs">INSTALLS</a></li>
<li class="level1"><a href="#leximpls">LEXIMPLS</a></li>
<li class="level1"><a href="#lexobjects">LEXOBJECTS</a></li>
<li class="level1"><a href="#lexsources">LEXSOURCES</a></li>
<li class="level1"><a href="#libs">LIBS</a></li>
<li class="level1"><a href="#literal-hash">LITERAL_HASH</a></li>
<li class="level1"><a href="#makefile">MAKEFILE</a></li>
<li class="level1"><a href="#makefile-generator">MAKEFILE_GENERATOR</a></li>
<li class="level1"><a href="#mmp-rules">MMP_RULES</a></li>
<li class="level1"><a href="#moc-dir">MOC_DIR</a></li>
<li class="level1"><a href="#objects">OBJECTS</a></li>
<li class="level1"><a href="#objects-dir">OBJECTS_DIR</a></li>
<li class="level1"><a href="#objmoc">OBJMOC</a></li>
<li class="level1"><a href="#post-targetdeps">POST_TARGETDEPS</a></li>
<li class="level1"><a href="#pre-targetdeps">PRE_TARGETDEPS</a></li>
<li class="level1"><a href="#precompiled-header">PRECOMPILED_HEADER</a></li>
<li class="level1"><a href="#pwd">PWD</a></li>
<li class="level1"><a href="#out-pwd">OUT_PWD</a></li>
<li class="level1"><a href="#qmake">QMAKE</a></li>
<li class="level1"><a href="#qmakespec">QMAKESPEC</a></li>
<li class="level1"><a href="#qmake-app-flag">QMAKE_APP_FLAG</a></li>
<li class="level1"><a href="#qmake-app-or-dll">QMAKE_APP_OR_DLL</a></li>
<li class="level1"><a href="#qmake-ar-cmd">QMAKE_AR_CMD</a></li>
<li class="level1"><a href="#qmake-bundle-data">QMAKE_BUNDLE_DATA</a></li>
<li class="level1"><a href="#qmake-bundle-extension">QMAKE_BUNDLE_EXTENSION</a></li>
<li class="level1"><a href="#qmake-cc">QMAKE_CC</a></li>
<li class="level1"><a href="#qmake-cflags-debug">QMAKE_CFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-cflags-mt">QMAKE_CFLAGS_MT</a></li>
<li class="level1"><a href="#qmake-cflags-mt-dbg">QMAKE_CFLAGS_MT_DBG</a></li>
<li class="level1"><a href="#qmake-cflags-mt-dll">QMAKE_CFLAGS_MT_DLL</a></li>
<li class="level1"><a href="#qmake-cflags-mt-dlldbg">QMAKE_CFLAGS_MT_DLLDBG</a></li>
<li class="level1"><a href="#qmake-cflags-release">QMAKE_CFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-cflags-shlib">QMAKE_CFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-cflags-thread">QMAKE_CFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-cflags-warn-off">QMAKE_CFLAGS_WARN_OFF</a></li>
<li class="level1"><a href="#qmake-cflags-warn-on">QMAKE_CFLAGS_WARN_ON</a></li>
<li class="level1"><a href="#qmake-clean">QMAKE_CLEAN</a></li>
<li class="level1"><a href="#qmake-cxx">QMAKE_CXX</a></li>
<li class="level1"><a href="#qmake-cxxflags">QMAKE_CXXFLAGS</a></li>
<li class="level1"><a href="#qmake-cxxflags-debug">QMAKE_CXXFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-cxxflags-mt">QMAKE_CXXFLAGS_MT</a></li>
<li class="level1"><a href="#qmake-cxxflags-mt-dbg">QMAKE_CXXFLAGS_MT_DBG</a></li>
<li class="level1"><a href="#qmake-cxxflags-mt-dll">QMAKE_CXXFLAGS_MT_DLL</a></li>
<li class="level1"><a href="#qmake-cxxflags-mt-dlldbg">QMAKE_CXXFLAGS_MT_DLLDBG</a></li>
<li class="level1"><a href="#qmake-cxxflags-release">QMAKE_CXXFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-cxxflags-shlib">QMAKE_CXXFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-cxxflags-thread">QMAKE_CXXFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-cxxflags-warn-off">QMAKE_CXXFLAGS_WARN_OFF</a></li>
<li class="level1"><a href="#qmake-cxxflags-warn-on">QMAKE_CXXFLAGS_WARN_ON</a></li>
<li class="level1"><a href="#qmake-distclean">QMAKE_DISTCLEAN</a></li>
<li class="level1"><a href="#qmake-extension-shlib">QMAKE_EXTENSION_SHLIB</a></li>
<li class="level1"><a href="#qmake-ext-moc">QMAKE_EXT_MOC</a></li>
<li class="level1"><a href="#qmake-ext-ui">QMAKE_EXT_UI</a></li>
<li class="level1"><a href="#qmake-ext-prl">QMAKE_EXT_PRL</a></li>
<li class="level1"><a href="#qmake-ext-lex">QMAKE_EXT_LEX</a></li>
<li class="level1"><a href="#qmake-ext-yacc">QMAKE_EXT_YACC</a></li>
<li class="level1"><a href="#qmake-ext-obj">QMAKE_EXT_OBJ</a></li>
<li class="level1"><a href="#qmake-ext-cpp">QMAKE_EXT_CPP</a></li>
<li class="level1"><a href="#qmake-ext-h">QMAKE_EXT_H</a></li>
<li class="level1"><a href="#qmake-extra-compilers">QMAKE_EXTRA_COMPILERS</a></li>
<li class="level1"><a href="#qmake-extra-targets">QMAKE_EXTRA_TARGETS</a></li>
<li class="level1"><a href="#qmake-failed-requirements">QMAKE_FAILED_REQUIREMENTS</a></li>
<li class="level1"><a href="#qmake-filetags">QMAKE_FILETAGS</a></li>
<li class="level1"><a href="#qmake-framework-bundle-name">QMAKE_FRAMEWORK_BUNDLE_NAME</a></li>
<li class="level1"><a href="#qmake-framework-version">QMAKE_FRAMEWORK_VERSION</a></li>
<li class="level1"><a href="#qmake-incdir">QMAKE_INCDIR</a></li>
<li class="level1"><a href="#qmake-incdir-egl">QMAKE_INCDIR_EGL</a></li>
<li class="level1"><a href="#qmake-incdir-opengl">QMAKE_INCDIR_OPENGL</a></li>
<li class="level1"><a href="#qmake-incdir-opengl-es1-qmake-incdir-opengl-es2">QMAKE_INCDIR_OPENGL_ES1, QMAKE_INCDIR_OPENGL_ES2</a></li>
<li class="level1"><a href="#qmake-incdir-openvg">QMAKE_INCDIR_OPENVG</a></li>
<li class="level1"><a href="#qmake-incdir-qt">QMAKE_INCDIR_QT</a></li>
<li class="level1"><a href="#qmake-incdir-thread">QMAKE_INCDIR_THREAD</a></li>
<li class="level1"><a href="#qmake-incdir-x11">QMAKE_INCDIR_X11</a></li>
<li class="level1"><a href="#qmake-info-plist">QMAKE_INFO_PLIST</a></li>
<li class="level1"><a href="#qmake-lflags">QMAKE_LFLAGS</a></li>
<li class="level1"><a href="#qmake-lflags-console">QMAKE_LFLAGS_CONSOLE</a></li>
<li class="level1"><a href="#qmake-lflags-console-dll">QMAKE_LFLAGS_CONSOLE_DLL</a></li>
<li class="level1"><a href="#qmake-lflags-debug">QMAKE_LFLAGS_DEBUG</a></li>
<li class="level1"><a href="#qmake-lflags-plugin">QMAKE_LFLAGS_PLUGIN</a></li>
<li class="level1"><a href="#qmake-lflags-rpath">QMAKE_LFLAGS_RPATH</a></li>
<li class="level1"><a href="#qmake-lflags-qt-dll">QMAKE_LFLAGS_QT_DLL</a></li>
<li class="level1"><a href="#qmake-lflags-release">QMAKE_LFLAGS_RELEASE</a></li>
<li class="level1"><a href="#qmake-lflags-shapp">QMAKE_LFLAGS_SHAPP</a></li>
<li class="level1"><a href="#qmake-lflags-shlib">QMAKE_LFLAGS_SHLIB</a></li>
<li class="level1"><a href="#qmake-lflags-soname">QMAKE_LFLAGS_SONAME</a></li>
<li class="level1"><a href="#qmake-lflags-thread">QMAKE_LFLAGS_THREAD</a></li>
<li class="level1"><a href="#qmake-lflags-windows">QMAKE_LFLAGS_WINDOWS</a></li>
<li class="level1"><a href="#qmake-lflags-windows-dll">QMAKE_LFLAGS_WINDOWS_DLL</a></li>
<li class="level1"><a href="#qmake-libdir">QMAKE_LIBDIR</a></li>
<li class="level1"><a href="#qmake-libdir-flags">QMAKE_LIBDIR_FLAGS</a></li>
<li class="level1"><a href="#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a></li>
<li class="level1"><a href="#qmake-libdir-opengl">QMAKE_LIBDIR_OPENGL</a></li>
<li class="level1"><a href="#qmake-libdir-openvg">QMAKE_LIBDIR_OPENVG</a></li>
<li class="level1"><a href="#qmake-libdir-qt">QMAKE_LIBDIR_QT</a></li>
<li class="level1"><a href="#qmake-libdir-x11">QMAKE_LIBDIR_X11</a></li>
<li class="level1"><a href="#qmake-libs">QMAKE_LIBS</a></li>
<li class="level1"><a href="#qmake-libs-console">QMAKE_LIBS_CONSOLE</a></li>
<li class="level1"><a href="#qmake-libs-egl">QMAKE_LIBS_EGL</a></li>
<li class="level1"><a href="#qmake-libs-opengl">QMAKE_LIBS_OPENGL</a></li>
<li class="level1"><a href="#qmake-libs-opengl-qt">QMAKE_LIBS_OPENGL_QT</a></li>
<li class="level1"><a href="#qmake-libs-opengl-es1-qmake-libs-opengl-es2">QMAKE_LIBS_OPENGL_ES1, QMAKE_LIBS_OPENGL_ES2</a></li>
<li class="level1"><a href="#qmake-libs-openvg">QMAKE_LIBS_OPENVG</a></li>
<li class="level1"><a href="#qmake-libs-qt">QMAKE_LIBS_QT</a></li>
<li class="level1"><a href="#qmake-libs-qt-dll">QMAKE_LIBS_QT_DLL</a></li>
<li class="level1"><a href="#qmake-libs-qt-opengl">QMAKE_LIBS_QT_OPENGL</a></li>
<li class="level1"><a href="#qmake-libs-qt-thread">QMAKE_LIBS_QT_THREAD</a></li>
<li class="level1"><a href="#qmake-libs-rt">QMAKE_LIBS_RT</a></li>
<li class="level1"><a href="#qmake-libs-rtmt">QMAKE_LIBS_RTMT</a></li>
<li class="level1"><a href="#qmake-libs-thread">QMAKE_LIBS_THREAD</a></li>
<li class="level1"><a href="#qmake-libs-windows">QMAKE_LIBS_WINDOWS</a></li>
<li class="level1"><a href="#qmake-libs-x11">QMAKE_LIBS_X11</a></li>
<li class="level1"><a href="#qmake-libs-x11sm">QMAKE_LIBS_X11SM</a></li>
<li class="level1"><a href="#qmake-lib-flag">QMAKE_LIB_FLAG</a></li>
<li class="level1"><a href="#qmake-link-shlib-cmd">QMAKE_LINK_SHLIB_CMD</a></li>
<li class="level1"><a href="#qmake-ln-shlib">QMAKE_LN_SHLIB</a></li>
<li class="level1"><a href="#qmake-post-link">QMAKE_POST_LINK</a></li>
<li class="level1"><a href="#qmake-pre-link">QMAKE_PRE_LINK</a></li>
<li class="level1"><a href="#qmake-project-name">QMAKE_PROJECT_NAME</a></li>
<li class="level1"><a href="#qmake-mac-sdk">QMAKE_MAC_SDK</a></li>
<li class="level1"><a href="#qmake-macosx-deployment-target">QMAKE_MACOSX_DEPLOYMENT_TARGET</a></li>
<li class="level1"><a href="#qmake-makefile">QMAKE_MAKEFILE</a></li>
<li class="level1"><a href="#qmake-moc-src">QMAKE_MOC_SRC</a></li>
<li class="level1"><a href="#qmake-qmake">QMAKE_QMAKE</a></li>
<li class="level1"><a href="#qmake-qt-dll">QMAKE_QT_DLL</a></li>
<li class="level1"><a href="#qmake-resource-flags">QMAKE_RESOURCE_FLAGS</a></li>
<li class="level1"><a href="#qmake-rpath">QMAKE_RPATH</a></li>
<li class="level1"><a href="#qmake-rpathdir">QMAKE_RPATHDIR</a></li>
<li class="level1"><a href="#qmake-run-cc">QMAKE_RUN_CC</a></li>
<li class="level1"><a href="#qmake-run-cc-imp">QMAKE_RUN_CC_IMP</a></li>
<li class="level1"><a href="#qmake-run-cxx">QMAKE_RUN_CXX</a></li>
<li class="level1"><a href="#qmake-run-cxx-imp">QMAKE_RUN_CXX_IMP</a></li>
<li class="level1"><a href="#qmake-target">QMAKE_TARGET</a></li>
<li class="level1"><a href="#qmake-uic">QMAKE_UIC</a></li>
<li class="level1"><a href="#qt">QT</a></li>
<li class="level1"><a href="#qtplugin">QTPLUGIN</a></li>
<li class="level1"><a href="#qt-version">QT_VERSION</a></li>
<li class="level1"><a href="#qt-major-version">QT_MAJOR_VERSION</a></li>
<li class="level1"><a href="#qt-minor-version">QT_MINOR_VERSION</a></li>
<li class="level1"><a href="#qt-patch-version">QT_PATCH_VERSION</a></li>
<li class="level1"><a href="#rc-file">RC_FILE</a></li>
<li class="level1"><a href="#rcc-dir">RCC_DIR</a></li>
<li class="level1"><a href="#requires">REQUIRES</a></li>
<li class="level1"><a href="#resources">RESOURCES</a></li>
<li class="level1"><a href="#res-file">RES_FILE</a></li>
<li class="level1"><a href="#rss-rules">RSS_RULES</a></li>
<li class="level1"><a href="#s60-version">S60_VERSION</a></li>
<li class="level1"><a href="#signature-file">SIGNATURE_FILE</a></li>
<li class="level1"><a href="#sources">SOURCES</a></li>
<li class="level1"><a href="#srcmoc">SRCMOC</a></li>
<li class="level1"><a href="#subdirs">SUBDIRS</a></li>
<li class="level2"><a href="#ordered-targets-and-visual-studio-solution-files">Ordered Targets and Visual Studio Solution Files</a></li>
<li class="level1"><a href="#symbian-version">SYMBIAN_VERSION</a></li>
<li class="level1"><a href="#target">TARGET</a></li>
<li class="level1"><a href="#target-capability">TARGET.CAPABILITY</a></li>
<li class="level1"><a href="#target-epocallowdlldata">TARGET.EPOCALLOWDLLDATA</a></li>
<li class="level1"><a href="#target-epocheapsize">TARGET.EPOCHEAPSIZE</a></li>
<li class="level1"><a href="#target-epocstacksize">TARGET.EPOCSTACKSIZE</a></li>
<li class="level1"><a href="#target-sid">TARGET.SID</a></li>
<li class="level1"><a href="#target-uid2">TARGET.UID2</a></li>
<li class="level1"><a href="#target-uid3">TARGET.UID3</a></li>
<li class="level1"><a href="#target-vid">TARGET.VID</a></li>
<li class="level1"><a href="#target-ext">TARGET_EXT</a></li>
<li class="level1"><a href="#target-x">TARGET_x</a></li>
<li class="level1"><a href="#target-x-y-z">TARGET_x.y.z</a></li>
<li class="level1"><a href="#template">TEMPLATE</a></li>
<li class="level1"><a href="#translations">TRANSLATIONS</a></li>
<li class="level1"><a href="#uicimpls">UICIMPLS</a></li>
<li class="level1"><a href="#uicobjects">UICOBJECTS</a></li>
<li class="level1"><a href="#ui-dir">UI_DIR</a></li>
<li class="level1"><a href="#ui-headers-dir">UI_HEADERS_DIR</a></li>
<li class="level1"><a href="#ui-sources-dir">UI_SOURCES_DIR</a></li>
<li class="level1"><a href="#version">VERSION</a></li>
<li class="level1"><a href="#ver-maj">VER_MAJ</a></li>
<li class="level1"><a href="#ver-min">VER_MIN</a></li>
<li class="level1"><a href="#ver-pat">VER_PAT</a></li>
<li class="level1"><a href="#vpath">VPATH</a></li>
<li class="level1"><a href="#yaccimpls">YACCIMPLS</a></li>
<li class="level1"><a href="#yaccobjects">YACCOBJECTS</a></li>
<li class="level1"><a href="#yaccsources">YACCSOURCES</a></li>
<li class="level1"><a href="#pro-file">_PRO_FILE_</a></li>
<li class="level1"><a href="#pro-file-pwd">_PRO_FILE_PWD_</a></li>
</ul>
</div>
<h1 class="title">qmake Variable Reference</h1>
<span class="subtitle"></span>
<!-- $$$qmake-variable-reference.html-description -->
<div class="descr"> <a name="details"></a>
<p><tt>qmake</tt>'s fundamental behavior is influenced by variable declarations that define the build process of each project. Some of these declare resources, such as headers and source files, that are common to each platform; others are used to customize the behavior of compilers and linkers on specific platforms.</p>
<p>Platform-specific variables follow the naming pattern of the variables which they extend or modify, but include the name of the relevant platform in their name. For example, <tt>QMAKE_LIBS</tt> can be used to specify a list of libraries that a project needs to link against, and <tt>QMAKE_LIBS_X11</tt> can be used to extend or override this list.</p>
<a name="backup-registration-file-maemo"></a><a name="backup-registration-file-maemo"></a>
<h2>BACKUP_REGISTRATION_FILE_MAEMO</h2>
<p><i>This is only used on the Maemo platform.</i></p>
<p>This variable is used to specify the backup registration file to use with <tt>enable_backup</tt> <tt>CONFIG</tt> value for Maemo platform. The default value is: <tt>$$_PRO_FILE_PWD_/backup_registration/maemo/$$basename(TARGET).conf</tt>.</p>
<p>Unfortunately it is not possible to have a common registration file for Maemo like there is for Symbian, so the developer must always provide one if the platform default backup support is not sufficient.</p>
<p>For documentation about how to create backup registration files and how the device backup works in general, see: (<a href="http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Generic_Platform_Components/Using_Backup_Application">Using Backup Application</a>)</p>
<a name="backup-registration-file-symbian"></a><a name="backup-registration-file-symbian"></a>
<h2>BACKUP_REGISTRATION_FILE_SYMBIAN</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>This variable is used to specify the backup registration file to use with <tt>enable_backup</tt> <tt>CONFIG</tt> value for Symbian platform. The default value is determined as follows:</p>
<p>If a custom registration file <tt>$$_PRO_FILE_PWD_/backup_registration/symbian/backup_registration.xml</tt> exists, it is used. Otherwise, the common registration file <tt>$$[QT_INSTALL_DATA]/mkspecs/common/symbian/backup_registration.xml</tt> is used. This common registration file will define backing up of application binaries, resources, and all files under application private directory. Also note that <tt>C:/Data</tt> contents are backed up by default on Symbian devices, so no registration is needed for any files found there.</p>
<p>For documentation about how to create backup registration files and how the device backup works in general, see: (<a href="http://library.forum.nokia.com/index.jsp?topic=/S60_5th_Edition_Cpp_Developers_Library/GUID-35228542-8C95-4849-A73F-2B4F082F0C44/sdk/doc_source/guide/Connectivity-subsystem-guide/Connectivity/PC_Connectivity_How-To_Write_Backup_Aware_Software.html">How-To Write Backup-aware Software</a>)</p>
<a name="bld-inf-rules"></a><a name="bld-inf-rules"></a>
<h2>BLD_INF_RULES</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Generic <tt>bld.inf</tt> file content can be specified with <tt>BLD_INF_RULES</tt> variables. The section of <tt>bld.inf</tt> file where each rule goes is appended to <tt>BLD_INF_RULES</tt> with a dot.</p>
<p>For example:</p>
<pre class="cpp"> my_exports = \
"foo.h /epoc32/include/mylib/foo.h" \
"bar.h /epoc32/include/mylib/bar.h"
BLD_INF_RULES.prj_exports += my_exports</pre>
<p>This will add the specified statements to the <tt>prj_exports</tt> section of the generated <tt>bld.inf</tt> file.</p>
<p>It is also possible to add multiple rows in a single block. Each double quoted string will be placed on a new row in the generated <tt>bld.inf</tt> file.</p>
<p>For example:</p>
<pre class="cpp"> myextension = \
"start extension myextension" \
"$${LITERAL_HASH}if defined(WINSCW)" \
"option MYOPTION foo" \
"$${LITERAL_HASH}endif" \
"option MYOPTION bar" \
"end"
BLD_INF_RULES.prj_extensions += myextension</pre>
<p>Any rules you define will be added after automatically generated rules in each section.</p>
<p><b>Note:</b> Content specified using <tt>BLD_INF_RULES</tt> is inserted as-is into the <tt>bld.inf</tt> file, so any rules that specify host side paths may not work correctly when doing a shadow build.</p>
<a name="config"></a><a name="config"></a>
<h2>CONFIG</h2>
<p>The <tt>CONFIG</tt> variable specifies project configuration and compiler options. The values will be recognized internally by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> and have special meaning. They are as follows.</p>
<p>These <tt>CONFIG</tt> values control compilation flags:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >release</td><td >The project is to be built in release mode. This is ignored if <tt>debug</tt> is also specified.</td></tr>
<tr valign="top" class="even"><td >debug</td><td >The project is to be built in debug mode.</td></tr>
<tr valign="top" class="odd"><td >debug_and_release</td><td >The project is built in <i>both</i> debug and release modes. This can have some unexpected side effects (see below for more information).</td></tr>
<tr valign="top" class="even"><td >build_all</td><td >If <tt>debug_and_release</tt> is specified, the project is built in both debug and release modes by default.</td></tr>
<tr valign="top" class="odd"><td >ordered</td><td >When using the <tt>subdirs</tt> template, this option specifies that the directories listed should be processed in the order in which they are given.</td></tr>
<tr valign="top" class="even"><td >precompile_header</td><td >Enables support for the use of <a href="qmake-precompiledheaders.html">precompiled headers</a> in projects.</td></tr>
<tr valign="top" class="odd"><td >warn_on</td><td >The compiler should output as many warnings as possible. This is ignored if <tt>warn_off</tt> is specified.</td></tr>
<tr valign="top" class="even"><td >warn_off</td><td >The compiler should output as few warnings as possible.</td></tr>
</table>
<p>Since the <tt>debug</tt> option overrides the <tt>release</tt> option when both are defined in the <tt>CONFIG</tt> variable, it is necessary to use the <tt>debug_and_release</tt> option if you want to allow both debug and release versions of a project to be built. In such a case, the Makefile that <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> generates includes a rule that builds both versions, and this can be invoked in the following way:</p>
<pre class="cpp"> make all</pre>
<p>When linking a library, <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> relies on the underlying platform to know what other libraries this library links against. However, if linking statically, <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will not get this information unless we use the following <tt>CONFIG</tt> options:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >create_prl</td><td >This option enables <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> to track these dependencies. When this option is enabled, <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will create a file ending in <tt>.prl</tt> which will save meta-information about the library (see <a href="qmake-environment-reference.html#libdepend">Library Dependencies</a> for more info).</td></tr>
<tr valign="top" class="even"><td >link_prl</td><td >When this is enabled, <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will process all libraries linked to by the application and find their meta-information(see <a href="qmake-environment-reference.html#libdepend">Library Dependencies</a> for more info).</td></tr>
</table>
<p>Please note that <tt>create_prl</tt> is required when <i>building</i> a static library, while <tt>link_prl</tt> is required when <i>using</i> a static library.</p>
<p>On Windows (or if Qt is configured with <tt>-debug_and_release</tt>, adding the <tt>build_all</tt> option to the <tt>CONFIG</tt> variable makes this rule the default when building the project, and installation targets will be created for both debug and release builds.</p>
<p>Additionally, adding <tt>debug_and_release</tt> to the <tt>CONFIG</tt> variable will cause both <tt>debug</tt> and <tt>release</tt> to be defined in the contents of <tt>CONFIG</tt>. When the project file is processed, the <a href="qmake-advanced-usage.html#scopes">scopes</a> that test for each value will be processed for <i>both</i> debug and release modes. The <tt>build_pass</tt> variable will be set for each of these mode, and you can test for this to perform build-specific tasks. For example:</p>
<pre class="cpp"> build_pass:CONFIG(debug, debug|release) {
unix: TARGET = $$join(TARGET,,,_debug)
else: TARGET = $$join(TARGET,,,d)
}</pre>
<p>As a result, it may be useful to define mode-specific variables, such as <a href="#qmake-lflags-release">QMAKE_LFLAGS_RELEASE</a>, instead of general variables, such as <a href="#qmake-lflags">QMAKE_LFLAGS</a>, where possible.</p>
<p>The following options define the application/library type:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >qt</td><td >The target is a Qt application/library and requires the Qt library and header files. The proper include and library paths for the Qt library will automatically be added to the project. This is defined by default, and can be fine-tuned with the <tt>\l{#qt}{QT}</tt> variable.</td></tr>
<tr valign="top" class="even"><td >thread</td><td >The target is a multi-threaded application or library. The proper defines and compiler flags will automatically be added to the project.</td></tr>
<tr valign="top" class="odd"><td >x11</td><td >The target is a X11 application or library. The proper include paths and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="even"><td >windows</td><td >The target is a Win32 window application (app only). The proper include paths, compiler flags and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="odd"><td >console</td><td >The target is a Win32 console application (app only). The proper include paths, compiler flags and libraries will automatically be added to the project.</td></tr>
<tr valign="top" class="even"><td >shared</td><td rowspan="3">The target is a shared object/DLL. The proper include paths, compiler flags and libraries will automatically be added to the project. Note that <tt>dll</tt> can also be used on all platforms; a shared library file with the appropriate suffix for the target platform (dll, so, dylib) will be created.</td></tr>
<tr valign="top" class="odd"><td >dll</td><td ></td></tr>
<tr valign="top" class="even"><td >dylib</td><td ></td></tr>
<tr valign="top" class="odd"><td >static</td><td rowspan="2">The target is a static library (lib only). The proper compiler flags will automatically be added to the project.</td></tr>
<tr valign="top" class="even"><td >staticlib</td><td ></td></tr>
<tr valign="top" class="odd"><td >plugin</td><td >The target is a plugin (lib only). This enables dll as well.</td></tr>
<tr valign="top" class="even"><td >designer</td><td >The target is a plugin for <i>Qt Designer</i>.</td></tr>
<tr valign="top" class="odd"><td >uic3</td><td >Configures qmake to run uic3 on the content of <tt>FORMS3</tt> if defined; otherwise the contents of <tt>FORMS</tt> will be processed instead.</td></tr>
<tr valign="top" class="even"><td >no_lflags_merge</td><td >Ensures that the list of libraries stored in the <tt>LIBS</tt> variable is not reduced to a list of unique values before it is used.</td></tr>
<tr valign="top" class="odd"><td >resources</td><td >Configures qmake to run rcc on the content of <tt>RESOURCES</tt> if defined.</td></tr>
</table>
<p>These options are used to set the compiler flags:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >3dnow</td><td >AMD 3DNow! instruction support is enabled.</td></tr>
<tr valign="top" class="even"><td >exceptions</td><td >Exception support is enabled.</td></tr>
<tr valign="top" class="odd"><td >mmx</td><td >Intel MMX instruction support is enabled.</td></tr>
<tr valign="top" class="even"><td >rtti</td><td >RTTI support is enabled.</td></tr>
<tr valign="top" class="odd"><td >stl</td><td >STL support is enabled.</td></tr>
<tr valign="top" class="even"><td >sse</td><td >SSE support is enabled.</td></tr>
<tr valign="top" class="odd"><td >sse2</td><td >SSE2 support is enabled.</td></tr>
</table>
<p>These options define specific features on Windows only:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >flat</td><td >When using the vcapp template this will put all the source files into the source group and the header files into the header group regardless of what directory they reside in. Turning this option off will group the files within the source/header group depending on the directory they reside. This is turned on by default.</td></tr>
<tr valign="top" class="even"><td >embed_manifest_dll</td><td >Embeds a manifest file in the DLL created as part of a library project.</td></tr>
<tr valign="top" class="odd"><td >embed_manifest_exe</td><td >Embeds a manifest file in the DLL created as part of an application project.</td></tr>
<tr valign="top" class="even"><td >incremental</td><td >Used to enable or disable incremental linking in Visual C++, depending on whether this feature is enabled or disabled by default.</td></tr>
</table>
<p>See <a href="qmake-platform-notes.html#visual-studio-2005-manifest-files">qmake Platform Notes</a> for more information on the options for embedding manifest files.</p>
<p>These options only have an effect on Mac OS X:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >ppc</td><td >Builds a PowerPC binary.</td></tr>
<tr valign="top" class="even"><td >x86</td><td >Builds an i386 compatible binary.</td></tr>
<tr valign="top" class="odd"><td >app_bundle</td><td >Puts the executable into a bundle (this is the default).</td></tr>
<tr valign="top" class="even"><td >lib_bundle</td><td >Puts the library into a library bundle.</td></tr>
</table>
<p>The build process for bundles is also influenced by the contents of the <a href="#qmake-bundle-data">QMAKE_BUNDLE_DATA</a> variable.</p>
<p>These options only have an effect on the Symbian platform:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >stdbinary</td><td >Builds an Open C binary (i.e. STDDLL, STDEXE, or STDLIB, depending on the target binary type.)</td></tr>
<tr valign="top" class="even"><td >no_icon</td><td >Doesn't generate resources needed for displaying an icon for executable in application menu (app only).</td></tr>
<tr valign="top" class="odd"><td >symbian_test</td><td >Places mmp files and extension makefiles under test sections in generated bld.inf instead of their regular sections. Note that this only affects automatically generated bld.inf content; the content added via <tt>BLD_INF_RULES</tt> variable is not affected.</td></tr>
<tr valign="top" class="even"><td >localize_deployment</td><td >Makes <tt>lupdate</tt> tool add fields for application captions and package file names into generated <tt>.ts</tt> files. Qmake generates properly localized <tt>.loc</tt> and <tt>.pkg</tt> files based on available translations. Translation file name bodies must end with underscore and the language code for deployment localization to work. E.g. <tt>myapp_en.ts</tt>. <b>Note:</b> All languages supported by Qt are not supported by Symbian, so some <tt>.ts</tt> files may be ignored by qmake.</td></tr>
</table>
<p>These options only have an effect on Symbian and Maemo platforms:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >enable_backup</td><td >Generates deployment for backup registration file to enable backing up the application during device backup. See <a href="#backup-registration-file-maemo">BACKUP_REGISTRATION_FILE_MAEMO</a> and <a href="#backup-registration-file-symbian">BACKUP_REGISTRATION_FILE_SYMBIAN</a> for more information about backup.</td></tr>
</table>
<p>These options have an effect on Linux/Unix platforms:</p>
<table class="generic" width="95%">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >largefile</td><td >Includes support for large files.</td></tr>
<tr valign="top" class="even"><td >separate_debug_info</td><td >Puts debugging information for libraries in separate files.</td></tr>
</table>
<p>The <tt>CONFIG</tt> variable will also be checked when resolving scopes. You may assign anything to this variable.</p>
<p>For example:</p>
<pre class="cpp"> CONFIG += qt console newstuff
...
newstuff {
SOURCES += new.cpp
HEADERS += new.h
}</pre>
<a name="defines"></a><a name="defines"></a>
<h2>DEFINES</h2>
<p><a href="qmake-manual.html#qmake"><tt>qmake</tt></a> adds the values of this variable as compiler C preprocessor macros (-D option).</p>
<p>For example:</p>
<pre class="cpp"> DEFINES += USE_MY_STUFF QT_DLL</pre>
<a name="def-file"></a><a name="def-file"></a>
<h2>DEF_FILE</h2>
<p><i>This is only used on Windows when using the <tt>app</tt> template, and on Symbian when building a shared DLL</i>.</p>
<p>Specifies a <tt>.def</tt> file to be included in the project. On Symbian a directory may be specified instead, in which case the real files will be located under the standard Symbian directories <tt>bwins</tt> and <tt>eabi</tt>.</p>
<a name="dependpath"></a><a name="dependpath"></a>
<h2>DEPENDPATH</h2>
<p>This variable contains the list of all directories to look in to resolve dependencies. This will be used when crawling through <tt>included</tt> files.</p>
<a name="deployment"></a><a name="deployment"></a>
<h2>DEPLOYMENT</h2>
<p><i>This is only used on Windows CE and the Symbian platform.</i></p>
<p>Specifies which additional files will be deployed. Deployment means the transfer of files from the development system to the target device or emulator.</p>
<p>Files can be deployed by either creating a Visual Studio project or using the <a href="qtestlib-manual.html#using-qtestlib-remotely-on-windows-ce">cetest</a> executable.</p>
<p>For example:</p>
<pre class="cpp"> myFiles.files = path\*.png
DEPLOYMENT += myFiles</pre>
<p>This will upload all PNG images in <tt>path</tt> to the same directory your build target will be deployed to.</p>
<p>The default deployment target path for Windows CE is <tt>%CSIDL_PROGRAM_FILES%\target</tt>, which usually gets expanded to <tt>\Program Files\target</tt>. For the Symbian platform, the default target is the application private directory on the drive it is installed to.</p>
<p>It is also possible to specify multiple <tt>sources</tt> to be deployed on target <tt>paths</tt>. In addition, different variables can be used for deployment to different directories.</p>
<p>For example:</p>
<pre class="cpp"> myFiles.files = path\file1.ext1 path2\file2.ext1 path3\*
myFiles.path = \some\path\on\device
someother.files = C:\additional\files\*
someother.path = \myFiles\path2
DEPLOYMENT += myFiles someother</pre>
<p><b>Note:</b> In Windows CE all linked Qt libraries will be deployed to the path specified by <tt>myFiles.path</tt>. On Symbian platform all libraries and executables will always be deployed to the \sys\bin of the installation drive.</p>
<p>Since the Symbian platform build system automatically moves binaries to certain directories under the epoc32 directory, custom plugins, executables or dynamically loadable libraries need special handling. When deploying extra executables or dynamically loadable libraries, the target path must specify \sys\bin. For plugins, the target path must specify the location where the plugin stub will be deployed to (see the <a href="plugins-howto.html">How to Create Qt Plugins</a> document for more information about plugins). If the binary cannot be found from the indicated source path, the directory Symbian build process moves the executables to is searched, e.g. \epoc32\release\armv5\urel.</p>
<p>For example:</p>
<pre class="cpp"> customplugin.files = customimageplugin.dll
customplugin.files += c:\myplugins\othercustomimageplugin.dll
customplugin.path = imageformats
dynamiclibrary.files = mylib.dll helper.exe
dynamiclibrary.path = \sys\bin
globalplugin.files = someglobalimageplugin.dll
globalplugin.path = \resource\qt\plugins\imageformats
DEPLOYMENT += customplugin dynamiclibrary globalplugin</pre>
<p>On the Symbian platform, generic PKG file content can also be specified with this variable. You can use either <tt>pkg_prerules</tt> or <tt>pkg_postrules</tt> to pass raw data to PKG file. The strings in <tt>pkg_prerules</tt> are added before package-body and <tt>pkg_postrules</tt> after. <tt>pkg_prerules</tt> is used for defining vendor information, dependencies, custom package headers, and the like, while <tt>pkg_postrules</tt> is used for custom file deployment and embedded sis directives. The strings defined in <tt>pkg_postrules</tt> or <tt>pkg_prerules</tt> are not parsed by qmake, so they should be in a format understood by Symbian package generation tools. Please consult the Symbian platform documentation for correct syntax.</p>
<p>For example, to deploy DLL and add a new dependency:</p>
<pre class="cpp"> somelib.files = somelib.dll
somelib.path = \sys\bin
somelib.pkg_prerules = "(0x12345678), 2, 2, 0, {\"Some Package\"}" \
"(0x87654321), 1, *, * ~ 2, 2, 0, {\"Some Other Package\"}"
justdep.pkg_prerules = "(0xAAAABBBB), 0, 2, 0, {\"My Framework\"}"
DEPLOYMENT += somelib justdep</pre>
<p>Please note that <tt>pkg_prerules</tt> can also replace default statements in pkg file. If no pkg_prerules is defined, qmake makes sure that PKG file syntax is correct and it contains all mandatory statements such as:</p>
<ul>
<li>languages, for example <br /> &EN,FR</li>
<li>package-header, for example <br /> #{"MyApp-EN", "MyApp-FR"}, (0x1000001F), 1, 2, 3, TYPE=SA</li>
<li>localized and unique vendor, for example <br /> %{"Vendor-EN", ..., "Vendor-FR"} :"Unique vendor name"</li>
</ul>
<p>If you decide to override any of these statements, you need to pay attention that also other statements stay valid. For example if you override languages statement, you must override also package-header statement and all other statements which are language specific.</p>
<p><b>Note:</b> Custom deployments specified using <tt>pkg_postrules</tt> are inserted as-is into the <tt>PKG</tt> file, so any rules that specify host side paths may not work correctly when doing a shadow build.</p>
<p>On the Symbian platform, three separate PKG files are generated:</p>
<ul>
<li><app><a href="#template">_template</a>.pkg - For application SIS file. Rules suffix: <tt>.main</tt></li>
<li><app>_installer.pkg - For smart installer SIS file. Rules suffix: <tt>.installer</tt></li>
<li><app>_stub.pkg - For ROM stubs. Rules suffix: <tt>.stub</tt></li>
</ul>
<p><tt>pkg_prerules</tt> and <tt>pkg_postrules</tt> given without rules suffix will intelligently apply to each of these files, but rules can also be targeted to only one of above files by appending listed rules suffix to the variable name:</p>
<pre class="cpp"> my_note.pkg_postrules.installer = "\"myinstallnote.txt\" - \"\", FILETEXT, TEXTCONTINUE"
DEPLOYMENT += my_note</pre>
<p>On the Symbian platform, the <tt>default_deployment</tt> item specifies default platform and package dependencies. Those dependencies can be selectively disabled if alternative dependencies need to be defined - e.g. if a specific device is required to run the application or more languages need to be supported by the package file. The supported <tt>default_deployment</tt> rules that can be disabled are:</p>
<ul>
<li>pkg_depends_qt</li>
<li>pkg_depends_webkit</li>
<li>pkg_platform_dependencies</li>
</ul>
<p>For example:</p>
<pre class="cpp"> default_deployment.pkg_prerules -= pkg_platform_dependencies
my_deployment.pkg_prerules = "[0x11223344],0,0,0,{\"SomeSpecificDeviceID\"}"
DEPLOYMENT += my_deployment</pre>
<p>On the Symbian platform, a default deployment is generated for all application projects. You can modify the autogenerated default deployment via following <tt>DEPLOYMENT</tt> variable values:</p>
<ul>
<li>default_bin_deployment - Application executable</li>
<li>default_resource_deployment - Application resources, including icon</li>
<li>default_reg_deployment - Application registration file</li>
</ul>
<p>For example:</p>
<pre class="cpp"> DEPLOYMENT -= default_bin_deployment default_resource_deployment default_reg_deployment</pre>
<p>This will entirely remove the default application deployment.</p>
<p>On the Symbian platform, you can specify file specific install options with <tt>.flags</tt> modifier. Please consult the Symbian platform documentation for supported options.</p>
<p>For example:</p>
<pre class="cpp"> default_bin_deployment.flags += FILERUN RUNINSTALL
dep_note.files = install_note.txt
dep_note.flags = FILETEXT TEXTEXIT
DEPLOYMENT += dep_note</pre>
<p>This will show a message box that gives user an option to cancel the installation and then automatically runs the application after installation is complete.</p>
<p><b>Note:</b> Automatically running the applications after install may require signing the package with better than self-signed certificate, depending on the phone model. Additionally, some tools such as Runonphone may not work properly with sis packages that automatically run the application upon install.</p>
<p>On the Symbian platform, the default package name and the default name that appears in application menu is derived from the <tt>TARGET</tt> variable. Often the default is not optimal for displaying to end user. To set a better display name for these purposes, use <tt>DEPLOYMENT.display_name</tt> variable:</p>
<pre class="cpp"> DEPLOYMENT.display_name = My Qt App</pre>
<p>On the Symbian platform, you can use <tt>DEPLOYMENT.installer_header</tt> variable to generate smart installer wrapper for your application. If you specify just UID of the installer package as the value, then installer package name and version will be autogenerated:</p>
<pre class="cpp"> DEPLOYMENT.installer_header = 0x12345678</pre>
<p>If autogenerated values are not suitable, you can also specify the sis header yourself using this variable:</p>
<pre class="cpp"> DEPLOYMENT.installer_header = "$${LITERAL_HASH}{\"My Application Installer\"},(0x12345678),1,0,0"</pre>
<a name="deployment-plugin"></a><a name="deployment-plugin"></a>
<h2>DEPLOYMENT_PLUGIN</h2>
<p><i>This is only used on Windows CE and the Symbian platform.</i></p>
<p>This variable specifies the Qt plugins that will be deployed. All plugins available in Qt can be explicitly deployed to the device. See <a href="plugins-howto.html#static-plugins">Static Plugins</a> for a complete list.</p>
<p><b>Note:</b> In Windows CE, No plugins will be deployed automatically. If the application depends on plugins, these plugins have to be specified manually.</p>
<p><b>Note:</b> On the Symbian platform, all plugins supported by this variable will be deployed by default with Qt libraries, so generally using this variable is not needed.</p>
<p>For example:</p>
<pre class="cpp"> DEPLOYMENT_PLUGIN += qjpeg</pre>
<p>This will upload the jpeg imageformat plugin to the plugins directory on the Windows CE device.</p>
<a name="destdir"></a><a name="destdir"></a>
<h2>DESTDIR</h2>
<p>Specifies where to put the <a href="#target">target</a> file.</p>
<p>For example:</p>
<pre class="cpp"> DESTDIR = ../../lib</pre>
<a name="destdir-target"></a><a name="destdir-target"></a>
<h2>DESTDIR_TARGET</h2>
<p>This variable is set internally by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a>, which is basically the <tt>DESTDIR</tt> variable with the <tt>TARGET</tt> variable appened at the end. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="dlldestdir"></a><a name="dlldestdir"></a>
<h2>DLLDESTDIR</h2>
<p>Specifies where to copy the <a href="#target">target</a> dll.</p>
<a name="distfiles"></a><a name="distfiles"></a>
<h2>DISTFILES</h2>
<p>This variable contains a list of files to be included in the dist target. This feature is supported by UnixMake specs only.</p>
<p>For example:</p>
<pre class="cpp"> DISTFILES += ../program.txt</pre>
<a name="dsp-template"></a><a name="dsp-template"></a>
<h2>DSP_TEMPLATE</h2>
<p>This variable is set internally by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a>, which specifies where the dsp template file for basing generated dsp files is stored. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="forms"></a><a name="forms"></a>
<h2>FORMS</h2>
<p>This variable specifies the UI files (see <a href="designer-manual.html">Qt Designer</a>) to be processed through <tt>uic</tt> before compiling. All dependencies, headers and source files required to build these UI files will automatically be added to the project.</p>
<p>For example:</p>
<pre class="cpp"> FORMS = mydialog.ui \
mywidget.ui \
myconfig.ui</pre>
<p>If FORMS3 is defined in your project, then this variable must contain forms for uic, and not uic3. If CONFIG contains uic3, and FORMS3 is not defined, the this variable must contain only uic3 type forms.</p>
<a name="forms3"></a><a name="forms3"></a>
<h2>FORMS3</h2>
<p>This variable specifies the old style UI files to be processed through <tt>uic3</tt> before compiling, when <tt>CONFIG</tt> contains uic3. All dependencies, headers and source files required to build these UI files will automatically be added to the project.</p>
<p>For example:</p>
<pre class="cpp"> FORMS3 = my_uic3_dialog.ui \
my_uic3_widget.ui \
my_uic3_config.ui</pre>
<a name="guid"></a><a name="guid"></a>
<h2>GUID</h2>
<p>Specifies the GUID that is set inside a <tt>.vcproj</tt> file. The GUID is usually randomly determined. However, should you require a fixed GUID, it can be set using this variable.</p>
<p>This variable is specific to <tt>.vcproj</tt> files only; it is ignored otherwise.</p>
<a name="headers"></a><a name="headers"></a>
<h2>HEADERS</h2>
<p>Defines the header files for the project.</p>
<p><a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will generate dependency information (unless <tt>-nodepend</tt> is specified on the <a href="qmake-running.html#commands">command line</a>) for the specified headers. <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will also automatically detect if <tt>moc</tt> is required by the classes in these headers, and add the appropriate dependencies and files to the project for generating and linking the moc files.</p>
<p>For example:</p>
<pre class="cpp"> HEADERS = myclass.h \
login.h \
mainwindow.h</pre>
<p>See also <a href="#sources">SOURCES</a>.</p>
<a name="icon"></a><a name="icon"></a>
<h2>ICON</h2>
<p>This variable is used only in MAC and the Symbian platform to set the application icon. Please see <a href="appicon.html">the application icon documentation</a> for more information.</p>
<a name="includepath"></a><a name="includepath"></a>
<h2>INCLUDEPATH</h2>
<p>This variable specifies the #include directories which should be searched when compiling the project.</p>
<p>For example:</p>
<pre class="cpp"> INCLUDEPATH = c:/msdev/include d:/stl/include</pre>
<p>To specify a path containing spaces, quote the path using the technique mentioned in the <a href="qmake-project-files.html#whitespace">qmake Project Files</a> document.</p>
<pre class="cpp"> win32:INCLUDEPATH += "C:/mylibs/extra headers"
unix:INCLUDEPATH += "/home/user/extra headers"</pre>
<a name="installs"></a><a name="installs"></a>
<h2>INSTALLS</h2>
<p>This variable contains a list of resources that will be installed when <tt>make install</tt> or a similar installation procedure is executed. Each item in the list is typically defined with attributes that provide information about where it will be installed.</p>
<p>For example, the following <tt>target.path</tt> definition describes where the build target will be installed, and the <tt>INSTALLS</tt> assignment adds the build target to the list of existing resources to be installed:</p>
<pre class="cpp"> target.path += $$[QT_INSTALL_PLUGINS]/imageformats
INSTALLS += target</pre>
<p>Note that <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> will skip files that are executable. If you need to install executable files, you can unset the files' executable flags.</p>
<p>Note that <tt>qmake</tt> will skip files that are executable. If you need to install executable files, you can unset the files' executable flags.</p>
<a name="leximpls"></a><a name="leximpls"></a>
<h2>LEXIMPLS</h2>
<p>This variable contains a list of lex implementation files. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="lexobjects"></a><a name="lexobjects"></a>
<h2>LEXOBJECTS</h2>
<p>This variable contains the names of intermediate lex object files.The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> and rarely needs to be modified.</p>
<a name="lexsources"></a><a name="lexsources"></a>
<h2>LEXSOURCES</h2>
<p>This variable contains a list of lex source files. All dependencies, headers and source files will automatically be added to the project for building these lex files.</p>
<p>For example:</p>
<pre class="cpp"> LEXSOURCES = lexer.l</pre>
<a name="libs"></a><a name="libs"></a>
<h2>LIBS</h2>
<p>This variable contains a list of libraries to be linked into the project. You can use the Unix <tt>-l</tt> (library) and -L (library path) flags and qmake will do the correct thing with these libraries on Windows and the Symbian platform (namely this means passing the full path of the library to the linker). The only limitation to this is the library must exist, for qmake to find which directory a <tt>-l</tt> lib lives in.</p>
<p>For example:</p>
<pre class="cpp"> unix:LIBS += -L/usr/local/lib -lmath
win32:LIBS += c:/mylibs/math.lib</pre>
<p><b>Note:</b> On Windows, specifying libraries with the <tt>-l</tt> option will cause the library with the highest version number to be used. For example, <tt>math2.lib</tt> could potentially be used instead of <tt>math.lib</tt>. To avoid this ambiguity, we recommend that you explicitly specify the library to be used by including the <tt>.lib</tt> file name suffix, as in the example above.</p>
<p>To specify a path containing spaces, quote the path using the technique mentioned in the <a href="qmake-project-files.html#whitespace">qmake Project Files</a> document.</p>
<pre class="cpp"> win32:LIBS += "C:/mylibs/extra libs/extra.lib"
unix:LIBS += "-L/home/user/extra libs" -lextra</pre>
<p><b>Note:</b> On the Symbian platform, the build system makes a distinction between shared and static libraries. In most cases, qmake will figure out which library you are refering to, but in some cases you may have to specify it explicitly to get the expected behavior. This typically happens if you are building a library and using it in the same project. To specify that the library is either shared or static, add a ".dll" or ".lib" suffix, respectively, to the library name.</p>
<p>By default, the list of libraries stored in <tt>LIBS</tt> is reduced to a list of unique names before it is used. To change this behavior, add the <tt>no_lflags_merge</tt> option to the <tt>CONFIG</tt> variable:</p>
<pre class="cpp"> CONFIG += no_lflags_merge</pre>
<a name="literal-hash"></a><a name="literal-hash"></a>
<h2>LITERAL_HASH</h2>
<p>This variable is used whenever a literal hash character (<tt>#</tt>) is needed in a variable declaration, perhaps as part of a file name or in a string passed to some external application.</p>
<p>For example:</p>
<pre class="cpp"> # To include a literal hash character, use the $$LITERAL_HASH variable:
urlPieces = http://qt.nokia.com/doc/4.0/qtextdocument.html pageCount
message($$join(urlPieces, $$LITERAL_HASH))</pre>
<p>By using <tt>LITERAL_HASH</tt> in this way, the <tt>#</tt> character can be used to construct a URL for the <tt>message()</tt> function to print to the console.</p>
<a name="makefile"></a><a name="makefile"></a>
<h2>MAKEFILE</h2>
<p>This variable specifies the name of the Makefile which <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> should use when outputting the dependency information for building a project. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p><b>Note:</b> On the Symbian platform, this variable is ignored.</p>
<p><b>Note:</b> On the Symbian platform, this variable is ignored.</p>
<a name="makefile-generator"></a><a name="makefile-generator"></a>
<h2>MAKEFILE_GENERATOR</h2>
<p>This variable contains the name of the Makefile generator to use when generating a Makefile. The value of this variable is typically handled internally by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> and rarely needs to be modified.</p>
<a name="mmp-rules"></a><a name="mmp-rules"></a>
<h2>MMP_RULES</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Generic MMP file content can be specified with this variable.</p>
<p>For example:</p>
<pre class="cpp"> MMP_RULES += "DEFFILE hello.def"</pre>
<p>This will add the specified statement to the end of the generated MMP file.</p>
<p>It is also possible to add multiple rows in a single block. Each double quoted string will be placed on a new row in the generated MMP file.</p>
<p>For example:</p>
<pre class="cpp"> myBlock = \
"START RESOURCE foo.rss" \
"TARGET bar" \
"TARGETPATH private\10001234" \
"HEADER" \
"LANG 01" \
"UID 0x10002345 0x10003456" \
"END"
MMP_RULES += myBlock</pre>
<p>If you need to include a hash (<tt>#</tt>) character inside the <tt>MMP_RULES</tt> statement, it can be done with the variable <tt>LITERAL_HASH</tt> as follows:</p>
<pre class="cpp"> myIfdefBlock = \
"$${LITERAL_HASH}ifdef WINSCW" \
"DEFFILE hello_winscw.def" \
"$${LITERAL_HASH}endif"
MMP_RULES += myIfdefBlock</pre>
<p>There is also a convenience function for adding conditional rules called <tt>addMMPRules</tt>. Suppose you need certain functionality to require different library depending on architecture. This can be specified with <tt>addMMPRules</tt> as follows:</p>
<pre class="cpp"> # Set conditional libraries
LIB.MARM = "LIBRARY myarm.lib"
LIB.WINSCW = "LIBRARY mywinscw.lib"
LIB.default = "LIBRARY mydefault.lib"
# Add the conditional MMP rules
MYCONDITIONS = MARM WINSCW
MYVARIABLES = LIB
addMMPRules(MYCONDITIONS, MYVARIABLES)</pre>
<p><b>Note:</b> You should not use this variable to add MMP statements that are explicitly supported by their own variables, such as <tt>TARGET.EPOCSTACKSIZE</tt>. Doing so could result in duplicate statements in the MMP file.</p>
<p><b>Note:</b> Content specified using <tt>MMP_RULES</tt> is inserted as-is into the <tt>MMP</tt> file, so any rules that specify host side paths may not work correctly when doing a shadow build.</p>
<a name="moc-dir"></a><a name="moc-dir"></a>
<h2>MOC_DIR</h2>
<p>This variable specifies the directory where all intermediate moc files should be placed.</p>
<p>For example:</p>
<pre class="cpp"> unix:MOC_DIR = ../myproject/tmp
win32:MOC_DIR = c:/myproject/tmp</pre>
<a name="objects"></a><a name="objects"></a>
<h2>OBJECTS</h2>
<p>This variable is generated from the <a href="#sources">SOURCES</a> variable. The extension of each source file will have been replaced by .o (Unix) or .obj (Win32). The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="objects-dir"></a><a name="objects-dir"></a>
<h2>OBJECTS_DIR</h2>
<p>This variable specifies the directory where all intermediate objects should be placed.</p>
<p>For example:</p>
<pre class="cpp"> unix:OBJECTS_DIR = ../myproject/tmp
win32:OBJECTS_DIR = c:/myproject/tmp</pre>
<a name="objmoc"></a><a name="objmoc"></a>
<h2>OBJMOC</h2>
<p>This variable is set by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> if files can be found that contain the <a href="qobject.html#Q_OBJECT">Q_OBJECT</a> macro. <tt>OBJMOC</tt> contains the name of all intermediate moc object files. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="post-targetdeps"></a><a name="post-targetdeps"></a>
<h2>POST_TARGETDEPS</h2>
<p>All libraries that the <a href="#target">target</a> depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.</p>
<p>This list will go after all builtin (and <a href="#pre-targetdeps">$$PRE_TARGETDEPS</a>) dependencies.</p>
<a name="pre-targetdeps"></a><a name="pre-targetdeps"></a>
<h2>PRE_TARGETDEPS</h2>
<p>All libraries that the <a href="#target">target</a> depends on can be listed in this variable. Some backends do not support this, these include MSVC Dsp, and ProjectBuilder .pbproj files. Generally this is supported internally by these build tools, this is useful for explicitly listing dependant static libraries.</p>
<p>This list will go before all builtin dependencies.</p>
<a name="precompiled-header"></a><a name="precompiled-header"></a>
<h2>PRECOMPILED_HEADER</h2>
<p>This variable indicates the header file for creating a precompiled header file, to increase the compilation speed of a project. Precompiled headers are currently only supported on some platforms (Windows - all MSVC project types, Mac OS X - Xcode, Makefile, Unix - gcc 3.3 and up).</p>
<p>On other platforms, this variable has different meaning, as noted below.</p>
<p>This variable contains a list of header files that require some sort of pre-compilation step (such as with moc). The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="pwd"></a><a name="pwd"></a>
<h2>PWD</h2>
<p>The <tt>PWD</tt> variable specifies the full path leading to the directory containing the current file being parsed. This can be useful to refer to files within the source tree when writing project files to support shadow builds.</p>
<p>See also <a href="#pro-file-pwd">_PRO_FILE_PWD_</a>.</p>
<p><b>Note:</b> IN_PWD is an alias for PWD.</p>
<p><b>Note:</b> Function calls have no effect on the value of PWD. PWD will refer to the path of the calling file.</p>
<a name="out-pwd"></a><a name="out-pwd"></a>
<h2>OUT_PWD</h2>
<p>This variable contains the full path leading to the directory where <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> places the generated Makefile.</p>
<a name="qmake-systemvariable"></a><a name="qmake"></a>
<h2>QMAKE</h2>
<p>This variable contains the name of the <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> program itself and is placed in generated Makefiles. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmakespec-systemvariable"></a><a name="qmakespec"></a>
<h2>QMAKESPEC</h2>
<p>This variable contains the name of the <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> configuration to use when generating Makefiles. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> and rarely needs to be modified.</p>
<p>Use the <tt>QMAKESPEC</tt> environment variable to override the <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> configuration. Note that, due to the way <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> reads project files, setting the <tt>QMAKESPEC</tt> environment variable from within a project file will have no effect.</p>
<a name="qmake-app-flag"></a><a name="qmake-app-flag"></a>
<h2>QMAKE_APP_FLAG</h2>
<p>This variable is empty unless the <tt>app</tt> <a href="#template">TEMPLATE</a> is specified. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified. Use the following instead:</p>
<pre class="cpp"> app {
# Conditional code for 'app' template here
}</pre>
<a name="qmake-app-or-dll"></a><a name="qmake-app-or-dll"></a>
<h2>QMAKE_APP_OR_DLL</h2>
<p>This variable is empty unless the <tt>app</tt> or <tt>dll</tt> <a href="#template">TEMPLATE</a> is specified. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-ar-cmd"></a><a name="qmake-ar-cmd"></a>
<h2>QMAKE_AR_CMD</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains the command for invoking the program which creates, modifies and extracts archives. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-bundle-data"></a><a name="qmake-bundle-data"></a>
<h2>QMAKE_BUNDLE_DATA</h2>
<p>This variable is used to hold the data that will be installed with a library bundle, and is often used to specify a collection of header files.</p>
<p>For example, the following lines add <tt>path/to/header_one.h</tt> and <tt>path/to/header_two.h</tt> to a group containing information about the headers supplied with the framework:</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>The last line adds the information about the headers to the collection of resources that will be installed with the library bundle.</p>
<p>Library bundles are created when the <tt>lib_bundle</tt> option is added to the <a href="#config">CONFIG</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">qmake Platform Notes</a> for more information about creating library bundles.</p>
<p><i>This is used on Mac OS X only.</i></p>
<a name="qmake-bundle-extension"></a>
<h2>QMAKE_BUNDLE_EXTENSION</h2>
<p>This variable defines the extension to be used for library bundles. This allows frameworks to be created with custom extensions instead of the standard <tt>.framework</tt> directory name extension.</p>
<p>For example, the following definition will result in a framework with the <tt>.myframework</tt> extension:</p>
<pre class="cpp"> QMAKE_BUNDLE_EXTENSION = .myframework</pre>
<p><i>This is used on Mac OS X only.</i></p>
<a name="qmake-cc"></a>
<h2>QMAKE_CC</h2>
<p>This variable specifies the C compiler that will be used when building projects containing C source code. Only the file name of the compiler executable needs to be specified as long as it is on a path contained in the <tt>PATH</tt> variable when the Makefile is processed.</p>
<a name="qmake-cflags-debug"></a><a name="qmake-cflags-debug"></a>
<h2>QMAKE_CFLAGS_DEBUG</h2>
<p>This variable contains the flags for the C compiler in debug mode. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-mt"></a><a name="qmake-cflags-mt"></a>
<h2>QMAKE_CFLAGS_MT</h2>
<p>This variable contains the compiler flags for creating a multi-threaded application or when the version of Qt that you link against is a multi-threaded statically linked library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-mt-dbg"></a><a name="qmake-cflags-mt-dbg"></a>
<h2>QMAKE_CFLAGS_MT_DBG</h2>
<p>This variable contains the compiler flags for creating a debuggable multi-threaded application or when the version of Qt that you link against is a debuggable multi-threaded statically linked library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-mt-dll"></a><a name="qmake-cflags-mt-dll"></a>
<h2>QMAKE_CFLAGS_MT_DLL</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains the compiler flags for creating a multi-threaded dll or when the version of Qt that you link against is a multi-threaded dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-mt-dlldbg"></a><a name="qmake-cflags-mt-dlldbg"></a>
<h2>QMAKE_CFLAGS_MT_DLLDBG</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains the compiler flags for creating a debuggable multi-threaded dll or when the version of Qt that you link against is a debuggable multi-threaded statically linked library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-release"></a><a name="qmake-cflags-release"></a>
<h2>QMAKE_CFLAGS_RELEASE</h2>
<p>This variable contains the compiler flags for creating a non-debuggable application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-shlib"></a><a name="qmake-cflags-shlib"></a>
<h2>QMAKE_CFLAGS_SHLIB</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains the compiler flags for creating a shared library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-thread"></a><a name="qmake-cflags-thread"></a>
<h2>QMAKE_CFLAGS_THREAD</h2>
<p>This variable contains the compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-warn-off"></a><a name="qmake-cflags-warn-off"></a>
<h2>QMAKE_CFLAGS_WARN_OFF</h2>
<p>This variable is not empty if the warn_off <a href="#config">CONFIG</a> option is specified. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cflags-warn-on"></a><a name="qmake-cflags-warn-on"></a>
<h2>QMAKE_CFLAGS_WARN_ON</h2>
<p>This variable is not empty if the warn_on <a href="#config">CONFIG</a> option is specified. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-clean"></a><a name="qmake-clean"></a>
<h2>QMAKE_CLEAN</h2>
<p>This variable contains any files which are not generated files (such as moc and uic generated files) and object files that should be removed when using "make clean".</p>
<a name="qmake-cxx"></a>
<h2>QMAKE_CXX</h2>
<p>This variable specifies the C++ compiler that will be used when building projects containing C++ source code. Only the file name of the compiler executable needs to be specified as long as it is on a path contained in the <tt>PATH</tt> variable when the Makefile is processed.</p>
<a name="qmake-cxxflags"></a>
<h2>QMAKE_CXXFLAGS</h2>
<p>This variable contains the C++ compiler flags that are used when building a project. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified. The flags specific to debug and release modes can be adjusted by modifying the <tt>QMAKE_CXXFLAGS_DEBUG</tt> and <tt>QMAKE_CXXFLAGS_RELEASE</tt> variables, respectively.</p>
<p><b>Note:</b> On the Symbian platform, this variable can be used to pass architecture specific options to each compiler in the Symbian build system. For example:</p>
<pre class="cpp"> QMAKE_CXXFLAGS.CW += -O2
QMAKE_CXXFLAGS.ARMCC += -O0</pre>
<p>For more information, see <a href="qmake-platform-notes.html#compiler-specific-options">qmake Platform Notes</a>.</p>
<a name="qmake-cxxflags-debug"></a><a name="qmake-cxxflags-debug"></a>
<h2>QMAKE_CXXFLAGS_DEBUG</h2>
<p>This variable contains the C++ compiler flags for creating a debuggable application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-mt"></a><a name="qmake-cxxflags-mt"></a>
<h2>QMAKE_CXXFLAGS_MT</h2>
<p>This variable contains the C++ compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-mt-dbg"></a><a name="qmake-cxxflags-mt-dbg"></a>
<h2>QMAKE_CXXFLAGS_MT_DBG</h2>
<p>This variable contains the C++ compiler flags for creating a debuggable multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a>or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-mt-dll"></a><a name="qmake-cxxflags-mt-dll"></a>
<h2>QMAKE_CXXFLAGS_MT_DLL</h2>
<p><tt>This is used on Windows only.</tt></p>
<p>This variable contains the C++ compiler flags for creating a multi-threaded dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-mt-dlldbg"></a><a name="qmake-cxxflags-mt-dlldbg"></a>
<h2>QMAKE_CXXFLAGS_MT_DLLDBG</h2>
<p><tt>This is used on Windows only.</tt></p>
<p>This variable contains the C++ compiler flags for creating a multi-threaded debuggable dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-release"></a><a name="qmake-cxxflags-release"></a>
<h2>QMAKE_CXXFLAGS_RELEASE</h2>
<p>This variable contains the C++ compiler flags for creating an application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-shlib"></a><a name="qmake-cxxflags-shlib"></a>
<h2>QMAKE_CXXFLAGS_SHLIB</h2>
<p>This variable contains the C++ compiler flags for creating a shared library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-thread"></a><a name="qmake-cxxflags-thread"></a>
<h2>QMAKE_CXXFLAGS_THREAD</h2>
<p>This variable contains the C++ compiler flags for creating a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a>or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-warn-off"></a><a name="qmake-cxxflags-warn-off"></a>
<h2>QMAKE_CXXFLAGS_WARN_OFF</h2>
<p>This variable contains the C++ compiler flags for suppressing compiler warnings. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-cxxflags-warn-on"></a><a name="qmake-cxxflags-warn-on"></a>
<h2>QMAKE_CXXFLAGS_WARN_ON</h2>
<p>This variable contains C++ compiler flags for generating compiler warnings. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-distclean"></a><a name="qmake-distclean"></a>
<h2>QMAKE_DISTCLEAN</h2>
<p>This variable removes extra files upon the invocation of <tt>make distclean</tt>.</p>
<a name="qmake-extension-shlib"></a><a name="qmake-extension-shlib"></a>
<h2>QMAKE_EXTENSION_SHLIB</h2>
<p>This variable contains the extention for shared libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>Note that platform-specific variables that change the extension will override the contents of this variable.</p>
<a name="qmake-ext-moc"></a>
<h2>QMAKE_EXT_MOC</h2>
<p>This variable changes the extention used on included moc files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-ui"></a>
<h2>QMAKE_EXT_UI</h2>
<p>This variable changes the extention used on /e Designer UI files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-prl"></a>
<h2>QMAKE_EXT_PRL</h2>
<p>This variable changes the extention used on created PRL files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="qmake-environment-reference.html#libdepend">Library Dependencies</a>.</p>
<a name="qmake-ext-lex"></a>
<h2>QMAKE_EXT_LEX</h2>
<p>This variable changes the extention used on files given to lex.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="#lexsources">LEXSOURCES</a>.</p>
<a name="qmake-ext-yacc"></a>
<h2>QMAKE_EXT_YACC</h2>
<p>This variable changes the extention used on files given to yacc.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>, <a href="#yaccsources">YACCSOURCES</a>.</p>
<a name="qmake-ext-obj"></a>
<h2>QMAKE_EXT_OBJ</h2>
<p>This variable changes the extention used on generated object files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-cpp"></a>
<h2>QMAKE_EXT_CPP</h2>
<p>This variable changes the interpretation of all suffixes in this list of values as files of type C++ source code.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-ext-h"></a>
<h2>QMAKE_EXT_H</h2>
<p>This variable changes the interpretation of all suffixes in this list of values as files of type C header files.</p>
<p>See also <a href="qmake-environment-reference.html#extensions">File Extensions</a>.</p>
<a name="qmake-extra-compilers"></a>
<h2>QMAKE_EXTRA_COMPILERS</h2>
<p>This variable contains the extra compilers/preprocessors that have been added</p>
<p>See also <a href="qmake-environment-reference.html#customizing">Customizing Makefile Output</a></p>
<a name="qmake-extra-targets"></a>
<h2>QMAKE_EXTRA_TARGETS</h2>
<p>This variable contains the extra targets that have been added</p>
<p>See also <a href="qmake-environment-reference.html#customizing">Customizing Makefile Output</a></p>
<a name="qmake-failed-requirements"></a><a name="qmake-failed-requirements"></a>
<h2>QMAKE_FAILED_REQUIREMENTS</h2>
<p>This variable contains the list of requirements that were failed to be met when <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> was used. For example, the sql module is needed and wasn't compiled into Qt. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-filetags"></a><a name="qmake-filetags"></a>
<h2>QMAKE_FILETAGS</h2>
<p>This variable contains the file tags needed to be entered into the Makefile, such as SOURCES and HEADERS. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-framework-bundle-name"></a>
<h2>QMAKE_FRAMEWORK_BUNDLE_NAME</h2>
<p>In a framework project, this variable contains the name to be used for the framework that is built.</p>
<p>By default, this variable contains the same value as the <a href="#target">TARGET</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">qmake Platform Notes</a> for more information about creating frameworks and library bundles.</p>
<p><i>This is used on Mac OS X only.</i></p>
<a name="qmake-framework-version"></a><a name="qmake-framework-version"></a>
<h2>QMAKE_FRAMEWORK_VERSION</h2>
<p>For projects where the build target is a Mac OS X framework, this variable is used to specify the version number that will be applied to the framework that is built.</p>
<p>By default, this variable contains the same value as the <a href="#version">VERSION</a> variable.</p>
<p>See <a href="qmake-platform-notes.html#creating-frameworks">qmake Platform Notes</a> for more information about creating frameworks.</p>
<p><i>This is used on Mac OS X only.</i></p>
<a name="qmake-incdir"></a><a name="qmake-incdir"></a>
<h2>QMAKE_INCDIR</h2>
<p>This variable contains the location of all known header files to be added to INCLUDEPATH when building an application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-egl"></a><a name="qmake-incdir-egl"></a>
<h2>QMAKE_INCDIR_EGL</h2>
<p>This variable contains the location of EGL header files to be added to INCLUDEPATH when building an application with OpenGL/ES or OpenVG support. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-opengl"></a><a name="qmake-incdir-opengl"></a>
<h2>QMAKE_INCDIR_OPENGL</h2>
<p>This variable contains the location of OpenGL header files to be added to INCLUDEPATH when building an application with OpenGL support. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-opengl-es1-qmake-incdir-opengl-es2"></a>
<h2>QMAKE_INCDIR_OPENGL_ES1, QMAKE_INCDIR_OPENGL_ES2</h2>
<p>These variables contain the location of OpenGL headers files to be added to INCLUDEPATH when building an application with OpenGL ES 1 or OpenGL ES 2 support respectively.</p>
<p>The value of this variable is typically handled by l{qmake Manual#qmake}{<tt>qmake</tt>} or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-openvg"></a><a name="qmake-incdir-openvg"></a>
<h2>QMAKE_INCDIR_OPENVG</h2>
<p>This variable contains the location of OpenVG header files to be added to INCLUDEPATH when building an application with OpenVG support. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenVG implementation uses EGL then <a href="#qmake-incdir-egl">QMAKE_INCDIR_EGL</a> may also need to be set.</p>
<a name="qmake-incdir-qt"></a><a name="qmake-incdir-qt"></a>
<h2>QMAKE_INCDIR_QT</h2>
<p>This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a Qt application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-thread"></a><a name="qmake-incdir-thread"></a>
<h2>QMAKE_INCDIR_THREAD</h2>
<p>This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-incdir-x11"></a><a name="qmake-incdir-x11"></a>
<h2>QMAKE_INCDIR_X11</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains the location of X11 header file paths to be added to INCLUDEPATH when building a X11 application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-info-plist"></a><a name="qmake-info-plist"></a>
<h2>QMAKE_INFO_PLIST</h2>
<p><i>This is used on Mac OS X platforms only.</i></p>
<p>This variable contains the name of the property list file, <tt>.plist</tt>, you would like to include in your Mac OS X application bundle.</p>
<p>In the <tt>.plist</tt> file, you can define some variables, e.g., @EXECUTABLE@, which qmake will replace with the actual executable name. Other variables include <a href="#icon">@ICON@</a>, @TYPEINFO@, <a href="qmake-common-projects.html#library">@LIBRARY@</a>, and @SHORT_VERSION@.</p>
<p><b>Note:</b> Most of the time, the default <tt>Info.plist</tt> is good enough.</p>
<a name="qmake-lflags"></a>
<h2>QMAKE_LFLAGS</h2>
<p>This variable contains a general set of flags that are passed to the linker. If you need to change the flags used for a particular platform or type of project, use one of the specialized variables for that purpose instead of this variable.</p>
<a name="qmake-lflags-console"></a><a name="qmake-lflags-console"></a>
<h2>QMAKE_LFLAGS_CONSOLE</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains link flags when building console programs. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-console-dll"></a>
<h2>QMAKE_LFLAGS_CONSOLE_DLL</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains link flags when building console dlls. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-debug"></a>
<h2>QMAKE_LFLAGS_DEBUG</h2>
<p>This variable contains link flags when building debuggable applications. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-plugin"></a>
<h2>QMAKE_LFLAGS_PLUGIN</h2>
<p>This variable contains link flags when building plugins. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-rpath"></a>
<h2>QMAKE_LFLAGS_RPATH</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>Library paths in this definition are added to the executable at link time so that the added paths will be preferentially searched at runtime.</p>
<a name="qmake-lflags-qt-dll"></a>
<h2>QMAKE_LFLAGS_QT_DLL</h2>
<p>This variable contains link flags when building programs that use the Qt library built as a dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-release"></a>
<h2>QMAKE_LFLAGS_RELEASE</h2>
<p>This variable contains link flags when building applications for release. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-shapp"></a>
<h2>QMAKE_LFLAGS_SHAPP</h2>
<p>This variable contains link flags when building applications which are using the <tt>app</tt> template. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-shlib"></a>
<h2>QMAKE_LFLAGS_SHLIB</h2>
<p>This variable contains link flags when building shared libraries The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-soname"></a>
<h2>QMAKE_LFLAGS_SONAME</h2>
<p>This variable specifies the link flags to set the name of shared objects, such as .so or .dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-thread"></a>
<h2>QMAKE_LFLAGS_THREAD</h2>
<p>This variable contains link flags when building multi-threaded projects. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-windows"></a>
<h2>QMAKE_LFLAGS_WINDOWS</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains link flags when building Windows GUI projects (i.e. non-console applications). The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lflags-windows-dll"></a>
<h2>QMAKE_LFLAGS_WINDOWS_DLL</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains link flags when building Windows DLL projects. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir"></a>
<h2>QMAKE_LIBDIR</h2>
<p>This variable contains the location of all known library directories. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-flags"></a>
<h2>QMAKE_LIBDIR_FLAGS</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains the location of all library directory with -L prefixed. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-egl"></a>
<h2>QMAKE_LIBDIR_EGL</h2>
<p>This variable contains the location of the EGL library directory, when EGL is used with OpenGL/ES or OpenVG. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-opengl"></a>
<h2>QMAKE_LIBDIR_OPENGL</h2>
<p>This variable contains the location of the OpenGL library directory. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a> may also need to be set.</p>
<a name="qmake-libdir-openvg"></a>
<h2>QMAKE_LIBDIR_OPENVG</h2>
<p>This variable contains the location of the OpenVG library directory. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenVG implementation uses EGL, then <a href="#qmake-libdir-egl">QMAKE_LIBDIR_EGL</a> may also need to be set.</p>
<a name="qmake-libdir-qt"></a>
<h2>QMAKE_LIBDIR_QT</h2>
<p>This variable contains the location of the Qt library directory. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libdir-x11"></a>
<h2>QMAKE_LIBDIR_X11</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains the location of the X11 library directory. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs"></a>
<h2>QMAKE_LIBS</h2>
<p>This variable contains all project libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-console"></a>
<h2>QMAKE_LIBS_CONSOLE</h2>
<p><i>This Windows-specific variable is no longer used.</i></p>
<p>Prior to Qt 4.2, this variable was used to list the libraries that should be linked against when building a console application project on Windows. <a href="#qmake-libs-windows">QMAKE_LIBS_WINDOW</a> should now be used instead.</p>
<a name="qmake-libs-egl"></a>
<h2>QMAKE_LIBS_EGL</h2>
<p>This variable contains all EGL libraries when building Qt with OpenGL/ES or OpenVG. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified. The usual value is <tt>-lEGL</tt>.</p>
<a name="qmake-libs-opengl"></a>
<h2>QMAKE_LIBS_OPENGL</h2>
<p>This variable contains all OpenGL libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-opengl-qt"></a>
<h2>QMAKE_LIBS_OPENGL_QT</h2>
<p>This variable contains all OpenGL Qt libraries.The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-opengl-es1-qmake-libs-opengl-es2"></a>
<h2>QMAKE_LIBS_OPENGL_ES1, QMAKE_LIBS_OPENGL_ES2</h2>
<p>These variables contain all the OpenGL libraries for OpenGL ES 1 and OpenGL ES 2.</p>
<p>The value of these variables is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>If the OpenGL implementation uses EGL (most OpenGL/ES systems), then <a href="#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-openvg"></a>
<h2>QMAKE_LIBS_OPENVG</h2>
<p>This variable contains all OpenVG libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified. The usual value is <tt>-lOpenVG</tt>.</p>
<p>Some OpenVG engines are implemented on top of OpenGL. This will be detected at configure time and <a href="#qmake-libs-opengl">QMAKE_LIBS_OPENGL</a> will be implicitly added to <a href="#qmake-libs-openvg">QMAKE_LIBS_OPENVG</a> wherever the OpenVG libraries are linked.</p>
<p>If the OpenVG implementation uses EGL, then <a href="#qmake-libs-egl">QMAKE_LIBS_EGL</a> may also need to be set.</p>
<a name="qmake-libs-qt"></a>
<h2>QMAKE_LIBS_QT</h2>
<p>This variable contains all Qt libraries.The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-qt-dll"></a>
<h2>QMAKE_LIBS_QT_DLL</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains all Qt libraries when Qt is built as a dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-qt-opengl"></a>
<h2>QMAKE_LIBS_QT_OPENGL</h2>
<p>This variable contains all the libraries needed to link against if OpenGL support is turned on. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-qt-thread"></a>
<h2>QMAKE_LIBS_QT_THREAD</h2>
<p>This variable contains all the libraries needed to link against if thread support is turned on. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-rt"></a>
<h2>QMAKE_LIBS_RT</h2>
<p><i>This is used with Borland compilers only.</i></p>
<p>This variable contains the runtime library needed to link against when building an application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-rtmt"></a>
<h2>QMAKE_LIBS_RTMT</h2>
<p><i>This is used with Borland compilers only.</i></p>
<p>This variable contains the runtime library needed to link against when building a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-thread"></a>
<h2>QMAKE_LIBS_THREAD</h2>
<p><i>This is used on Unix and Symbian platforms only.</i></p>
<p>This variable contains all libraries that need to be linked against when building a multi-threaded application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-windows"></a>
<h2>QMAKE_LIBS_WINDOWS</h2>
<p><i>This is used on Windows only.</i></p>
<p>This variable contains all windows libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-x11"></a>
<h2>QMAKE_LIBS_X11</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains all X11 libraries.The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-libs-x11sm"></a>
<h2>QMAKE_LIBS_X11SM</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>This variable contains all X11 session management libraries. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-lib-flag"></a>
<h2>QMAKE_LIB_FLAG</h2>
<p>This variable is not empty if the <tt>lib</tt> template is specified. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-link-shlib-cmd"></a>
<h2>QMAKE_LINK_SHLIB_CMD</h2>
<p>This variable contains the command to execute when creating a shared library. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-ln-shlib"></a>
<h2>QMAKE_LN_SHLIB</h2>
<p>This variable contains the command to execute when creating a link to a shared library. The value of this variable is typically handled by <tt>qmake</tt> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-post-link"></a>
<h2>QMAKE_POST_LINK</h2>
<p>This variable contains the command to execute after linking the TARGET together. This variable is normally empty and therefore nothing is executed, additionally some backends will not support this - mostly only Makefile backends.</p>
<a name="qmake-pre-link"></a>
<h2>QMAKE_PRE_LINK</h2>
<p>This variable contains the command to execute before linking the TARGET together. This variable is normally empty and therefore nothing is executed, additionally some backends will not support this - mostly only Makefile backends.</p>
<a name="qmake-project-name"></a>
<h2>QMAKE_PROJECT_NAME</h2>
<p><i>This is used for Visual Studio project files only.</i></p>
<p>This variable determines the name of the project when generating project files for IDEs. The default value is the target name. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"> <tt>qmake</tt></a> and rarely needs to be modified.</p>
<a name="qmake-mac-sdk"></a>
<h2>QMAKE_MAC_SDK</h2>
<p>This variable is used on Mac OS X when building universal binaries. This process is described in more detail in the <a href="deployment-mac.html#architecture-dependencies">Deploying an Application on Mac OS X</a> document.</p>
<a name="qmake-macosx-deployment-target"></a>
<h2>QMAKE_MACOSX_DEPLOYMENT_TARGET</h2>
<p>This variable only has an effect when building on Mac OS X. On that platform, the variable will be forwarded to the MACOSX_DEPLOYMENT_TARGET environment variable, which is interpreted by the compiler or linker. For more information, see the <a href="deployment-mac.html#mac-os-x-version-dependencies">Deploying an Application on Mac OS X</a> document.</p>
<a name="qmake-makefile"></a>
<h2>QMAKE_MAKEFILE</h2>
<p>This variable contains the name of the Makefile to create. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-moc-src"></a>
<h2>QMAKE_MOC_SRC</h2>
<p>This variable contains the names of all moc source files to generate and include in the project. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-qmake"></a>
<h2>QMAKE_QMAKE</h2>
<p>This variable contains the location of qmake if it is not in the path. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-qt-dll"></a>
<h2>QMAKE_QT_DLL</h2>
<p>This variable is not empty if Qt was built as a dll. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-resource-flags"></a>
<h2>QMAKE_RESOURCE_FLAGS</h2>
<p>This variable is used to customize the list of options passed to the <a href="rcc.html#rcc">Resource Compiler</a> in each of the build rules where it is used. For example, the following line ensures that the <tt>-threshold</tt> and <tt>-compress</tt> options are used with particular values each time that <tt>rcc</tt> is invoked:</p>
<pre class="cpp"> QMAKE_RESOURCE_FLAGS += -threshold 0 -compress 9</pre>
<a name="qmake-rpath"></a>
<h2>QMAKE_RPATH</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>Is equivalent to <a href="#qmake-lflags-rpath">QMAKE_LFLAGS_RPATH</a>.</p>
<a name="qmake-rpathdir"></a>
<h2>QMAKE_RPATHDIR</h2>
<p><i>This is used on Unix platforms only.</i></p>
<p>A list of library directory paths, these paths are added to the executable at link time so that the paths will be preferentially searched at runtime.</p>
<a name="qmake-run-cc"></a>
<h2>QMAKE_RUN_CC</h2>
<p>This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cc-imp"></a>
<h2>QMAKE_RUN_CC_IMP</h2>
<p>This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cxx"></a>
<h2>QMAKE_RUN_CXX</h2>
<p>This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-run-cxx-imp"></a>
<h2>QMAKE_RUN_CXX_IMP</h2>
<p>This variable specifies the individual rule needed to build an object. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-target"></a>
<h2>QMAKE_TARGET</h2>
<p>This variable contains the name of the project target. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="qmake-uic"></a>
<h2>QMAKE_UIC</h2>
<p>This variable contains the location of uic if it is not in the path. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<p>It can be used to specify arguments to uic as well, such as additional plugin paths. For example:</p>
<pre class="cpp"> QMAKE_UIC = uic -L /path/to/plugin</pre>
<a name="qt"></a>
<h2>QT</h2>
<p>The values stored in the <tt>QT</tt> variable control which of the Qt modules are used by your project.</p>
<p>The table below shows the options that can be used with the <tt>QT</tt> variable and the features that are associated with each of them:</p>
<table class="generic">
<thead><tr class="qt-style"><th >Option</th><th >Features</th></tr></thead>
<tr valign="top" class="odd"><td >core (included by default)</td><td ><a href="qtcore.html">QtCore</a> module</td></tr>
<tr valign="top" class="even"><td >gui (included by default)</td><td ><a href="qtgui.html">QtGui</a> module</td></tr>
<tr valign="top" class="odd"><td >network</td><td ><a href="qtnetwork.html">QtNetwork</a> module</td></tr>
<tr valign="top" class="even"><td >opengl</td><td ><a href="qtopengl.html">QtOpenGL</a> module</td></tr>
<tr valign="top" class="odd"><td >phonon</td><td >Phonon Multimedia Framework</td></tr>
<tr valign="top" class="even"><td >sql</td><td ><a href="qtsql.html">QtSql</a> module</td></tr>
<tr valign="top" class="odd"><td >svg</td><td ><a href="qtsvg.html">QtSvg</a> module</td></tr>
<tr valign="top" class="even"><td >xml</td><td ><a href="qtxml.html">QtXml</a> module</td></tr>
<tr valign="top" class="odd"><td >webkit</td><td >WebKit integration</td></tr>
<tr valign="top" class="even"><td >qt3support</td><td ><a href="qt3support.html">Qt3Support</a> module</td></tr>
</table>
<p>By default, <tt>QT</tt> contains both <tt>core</tt> and <tt>gui</tt>, ensuring that standard GUI applications can be built without further configuration.</p>
<p>If you want to build a project <i>without</i> the <a href="qtgui.html">QtGui</a> module, you need to exclude the <tt>gui</tt> value with the "-=" operator; the following line will result in a minimal Qt project being built:</p>
<pre class="cpp"> QT -= gui # Only the core module is used.</pre>
<p>Note that adding the <tt>opengl</tt> option to the <tt>QT</tt> variable automatically causes the equivalent option to be added to the <tt>CONFIG</tt> variable. Therefore, for Qt applications, it is not necessary to add the <tt>opengl</tt> option to both <tt>CONFIG</tt> and <tt>QT</tt>.</p>
<a name="qtplugin"></a>
<h2>QTPLUGIN</h2>
<p>This variable contains a list of names of static plugins that are to be compiled with an application so that they are available as built-in resources.</p>
<a name="qt-version"></a><a name="qt-version"></a>
<h2>QT_VERSION</h2>
<p>This variable contains the current version of Qt.</p>
<a name="qt-major-version"></a><a name="qt-major-version"></a>
<h2>QT_MAJOR_VERSION</h2>
<p>This variable contains the current major version of Qt.</p>
<a name="qt-minor-version"></a><a name="qt-minor-version"></a>
<h2>QT_MINOR_VERSION</h2>
<p>This variable contains the current minor version of Qt.</p>
<a name="qt-patch-version"></a><a name="qt-patch-version"></a>
<h2>QT_PATCH_VERSION</h2>
<p>This variable contains the current patch version of Qt.</p>
<a name="rc-file"></a>
<h2>RC_FILE</h2>
<p>This variable contains the name of the resource file for the application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="rcc-dir"></a><a name="rcc-dir"></a>
<h2>RCC_DIR</h2>
<p>This variable specifies the directory where all intermediate resource files should be placed.</p>
<p>For example:</p>
<pre class="cpp"> unix:RCC_DIR = ../myproject/resources
win32:RCC_DIR = c:/myproject/resources</pre>
<a name="requires"></a><a name="requires"></a>
<h2>REQUIRES</h2>
<p>This is a special variable processed by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a>. If the contents of this variable do not appear in CONFIG by the time this variable is assigned, then a minimal Makefile will be generated that states what dependencies (the values assigned to REQUIRES) are missing.</p>
<p>This is mainly used in Qt's build system for building the examples.</p>
<a name="resources"></a>
<h2>RESOURCES</h2>
<p>This variable contains the name of the resource collection file (qrc) for the application. Further information about the resource collection file can be found at <a href="resources.html">The Qt Resource System</a>.</p>
<a name="res-file"></a>
<h2>RES_FILE</h2>
<p>This variable contains the name of the resource file for the application. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="rss-rules"></a><a name="rss-rules"></a>
<h2>RSS_RULES</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Generic RSS file content can be specified with this variable. The syntax is similar to <tt>MMP_RULES</tt> and <tt>BLD_INF_RULES</tt>.</p>
<p>For example:</p>
<pre class="cpp"> RSS_RULES += "hidden = KAppIsHidden;"</pre>
<p>This will add the specified statement to the end of the <tt>APP_REGISTRATION_INFO</tt> resource struct in the generated registration resource file. As an impact of this statement, the application will not be visible in application shell.</p>
<p>It is also possible to add multiple rows in a single block. Each double quoted string will be placed on a new row in the registration resource file.</p>
<p>For example:</p>
<pre class="cpp"> myrssrules = \
"hidden = KAppIsHidden;" \
"launch = KAppLaunchInBackground;" \
RSS_RULES += myrssrules</pre>
<p>This example will install the application to MyFolder in the Symbian platform application shell. In addition it will make the application to be launched in background.</p>
<p>From S60 version 5.4 onwards, you can specify <tt>graphics_memory</tt> value using <tt>RSS_RULES</tt> to specify the graphics memory quota for the application. The value is in kilobytes and defaults to 24576 (i.e. 24MB) for applications that link against <a href="qtgui.html">QtGui</a>. The default for all other applications is zero.</p>
<p>The graphics memory quota tells the operating system how much graphics memory the application is likely to need so that it can free up enough graphics memory prior to application launch. If the value is too small, it can cause random slowdowns later when the memory is freed on on-demand basis. On the other hand, too large values can delay the application launch unnecessarily.</p>
<p>For example:</p>
<pre class="cpp"> RSS_RULES += "graphics_memory=12288;"</pre>
<p>This example sets the graphics memory quota to 12MB.</p>
<p>For detailed list of possible <tt>APP_REGISTRATION_INFO</tt> statements, please refer to the Symbian platform help.</p>
<p><b>Note:</b> You should not use <tt>RSS_RULES</tt> variable to set the following RSS statements: <tt>app_file</tt>, <tt>localisable_resource_file</tt>, and <tt>localisable_resource_id</tt>.</p>
<p>These statements are internally handled by qmake.</p>
<p>There is a number of special modifiers you can attach to <tt>RSS_RULES</tt> to specify where in the application registration file the rule will be written:</p>
<table class="generic">
<thead><tr class="qt-style"><th >Modifier</th><th >Location of the rule</th></tr></thead>
<tr valign="top" class="odd"><td ><no modifier></td><td >Inside <tt>APP_REGISTRATION_INFO</tt> resource struct.</td></tr>
<tr valign="top" class="even"><td >.header</td><td >Before <tt>APP_REGISTRATION_INFO</tt> resource struct.</td></tr>
<tr valign="top" class="odd"><td >.footer</td><td >After <tt>APP_REGISTRATION_INFO</tt> resource struct.</td></tr>
<tr valign="top" class="even"><td >.service_list</td><td >Inside a <tt>SERVICE_INFO</tt> item in the <tt>service_list</tt> of <tt>APP_REGISTRATION_INFO</tt></td></tr>
<tr valign="top" class="odd"><td >.file_ownership_list</td><td >Inside a <tt>FILE_OWNERSHIP_INFO</tt> item in the <tt>file_ownership_list</tt> of <tt>APP_REGISTRATION_INFO</tt></td></tr>
<tr valign="top" class="even"><td >.datatype_list</td><td >Inside a <tt>DATATYPE</tt> item in the <tt>datatype_list</tt> of <tt>APP_REGISTRATION_INFO</tt></td></tr>
</table>
<p>For example:</p>
<pre class="cpp"> RSS_RULES.service_list += "uid = 0x12345678; datatype_list = \{\}; opaque_data = r_my_icon;"
RSS_RULES.footer +="RESOURCE CAPTION_AND_ICON_INFO r_my_icon \{ icon_file =\"$$PWD/my_icon.svg\"; \}"</pre>
<p>This example will define service information for a fictional service that requires an icon to be supplied via the <tt>opaque_data</tt> of the service information.</p>
<a name="s60-version"></a><a name="s60-version"></a>
<h2>S60_VERSION</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Contains the version number of the underlying S60 SDK; e.g. "5.0".</p>
<a name="signature-file"></a><a name="signature-file"></a>
<h2>SIGNATURE_FILE</h2>
<p><i>This is only used on Windows CE.</i></p>
<p>Specifies which signature file should be used to sign the project target.</p>
<p><b>Note:</b> This variable will overwrite the setting you have specified in configure, with the <tt>-signature</tt> option.</p>
<a name="sources"></a><a name="sources"></a>
<h2>SOURCES</h2>
<p>This variable contains the name of all source files in the project.</p>
<p>For example:</p>
<pre class="cpp"> SOURCES = myclass.cpp \
login.cpp \
mainwindow.cpp</pre>
<p>See also <a href="#headers">HEADERS</a></p>
<a name="srcmoc"></a>
<h2>SRCMOC</h2>
<p>This variable is set by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> if files can be found that contain the <a href="qobject.html#Q_OBJECT">Q_OBJECT</a> macro. <tt>SRCMOC</tt> contains the name of all the generated moc files. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="subdirs"></a><a name="subdirs"></a>
<h2>SUBDIRS</h2>
<p>This variable, when used with the <tt>subdirs</tt> <a href="#template">template</a> specifies the names of all subdirectories or project files that contain parts of the project that need to be built. Each subdirectory specified using this variable must contain its own project file.</p>
<p>It is recommended that the project file in each subdirectory has the same base name as the subdirectory itself, because that makes it possible to omit the file name. For example, if the subdirectory is called <tt>myapp</tt>, the project file in that directory should be called <tt>myapp.pro</tt>.</p>
<p>Alternatively, you can specify a relative path to a .pro file in any directory. It is strongly recommended that you specify only paths in the current project's parent directory or its subdirectories.</p>
<p>For example:</p>
<pre class="cpp"> SUBDIRS = kernel \
tools \
myapp</pre>
<p>If you need to ensure that the subdirectories are built in the order in which they are specified, update the <a href="#config">CONFIG</a> variable to include the <tt>ordered</tt> option:</p>
<pre class="cpp"> CONFIG += ordered</pre>
<p>It is possible to modify this default behavior of <tt>SUBDIRS</tt> by giving additional modifiers to <tt>SUBDIRS</tt> elements. Supported modifiers are:</p>
<table class="generic">
<thead><tr class="qt-style"><th >Modifier</th><th >Effect</th></tr></thead>
<tr valign="top" class="odd"><td >.subdir</td><td >Use the specified subdirectory instead of <tt>SUBDIRS</tt> value.</td></tr>
<tr valign="top" class="even"><td >.file</td><td >Specify the subproject <tt>pro</tt> file explicitly. Cannot be used in conjunction with <tt>.subdir</tt> modifier.</td></tr>
<tr valign="top" class="odd"><td >.condition</td><td >Specifies a <tt>bld.inf</tt> define that must be true for subproject to be built. Available only on Symbian platform.</td></tr>
<tr valign="top" class="even"><td >.depends</td><td >This subproject depends on specified subproject. Available only on platforms that use makefiles.</td></tr>
<tr valign="top" class="odd"><td >.makefile</td><td >The makefile of subproject. Available only on platforms that use makefiles.</td></tr>
<tr valign="top" class="even"><td >.target</td><td >Base string used for makefile targets related to this subproject. Available only on platforms that use makefiles.</td></tr>
</table>
<p>For example, define two subdirectories, both of which reside in a different directory than the <tt>SUBDIRS</tt> value, and one of the subdirectories must be built before the other:</p>
<pre class="cpp"> SUBDIRS += my_executable my_library
my_executable.subdir = app
my_executable.depends = my_library
my_library.subdir = lib</pre>
<p>For example, define a subdirectory that is only build for emulator builds in Qt for Symbian:</p>
<pre class="cpp"> symbian {
SUBDIRS += emulator_dll
emulator_dll.condition = WINSCW
}</pre>
<a name="ordered-targets-and-visual-studio-solution-files"></a>
<h3>Ordered Targets and Visual Studio Solution Files</h3>
<p>The <tt>ordered</tt> option is not supported for Visual Studio. The following list describes how you can get around without it--dependencies are generated automatically if:</p>
<ul>
<li>1a) There is a Lib/DLL project of which TARGET (the .lib is used and not the .dll) is used on the link line of another project in your solution (you can modify the link line with LIBS).</li>
<li>1b) There is an Exe project of which TARGET is used in a custom build-step of another project in your solution.</li>
<li>2) You don't use paths in the TARGET variable (use DESTDIR/DLLDESTDIR for that), e.g, TARGET=$(SOME_VARIABLE)/myLib, won't work.</li>
<li>3) If you have a special location for your libs, you specify the -Lmy/library/path and LIBS += mylib, instead of just using LIBS += my/library/path/mylib</li>
<li>4) The leaf projects are created before you generate the solution file. (You can use the recursive flag for qmake to do this, like "qmake -tp vc -r [yourproject.pro]"</li>
</ul>
<a name="symbian-version"></a><a name="symbian-version"></a>
<h2>SYMBIAN_VERSION</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Contains the version number of the underlying Symbian SDK; e.g. "9.2" or "Symbian3".</p>
<a name="target"></a><a name="target"></a>
<h2>TARGET</h2>
<p>This specifies the name of the target file.</p>
<p>For example:</p>
<pre class="cpp"> TEMPLATE = app
TARGET = myapp
SOURCES = main.cpp</pre>
<p>The project file above would produce an executable named <tt>myapp</tt> on unix and 'myapp.exe' on windows.</p>
<a name="target-capability"></a><a name="target-capability"></a>
<h2>TARGET.CAPABILITY</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies which platform capabilities the application should have. These include the following basic capabilities, but others are also available for signed applications.</p>
<table class="generic">
<thead><tr class="qt-style"><th >Capability</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >LocalServices</td><td >The ability to use local services running on the phone or device, including those which provide local connectivity to other devices.</td></tr>
<tr valign="top" class="even"><td >Location</td><td >Access to the service that provides information about the user's location, from GPS, phone network, or other sources.</td></tr>
<tr valign="top" class="odd"><td >NetworkServices</td><td >Use of services that access the phone network, such as dialling a phone number, sending an SMS, or other operations that result in network traffic.</td></tr>
<tr valign="top" class="even"><td >ReadUserData</td><td >Access to the user's private data, such as contact information.</td></tr>
<tr valign="top" class="odd"><td >UserEnvironment</td><td >The ability to use services that provide from the user's physical environment, such as the camera or microphone.</td></tr>
<tr valign="top" class="even"><td >WriteUserData</td><td >The ability to write or modify the user's private data.</td></tr>
</table>
<p>For more information, and a comprehensive list of capabilities, please refer to the Symbian SDK documentation or the <a href="http://wiki.forum.nokia.com/index.php/Capabilities">Symbian Capabilities</a> page of the <a href="http://wiki.forum.nokia.com/">Forum Nokia Wiki</a>.</p>
<a name="target-epocallowdlldata"></a><a name="target-epocallowdlldata"></a>
<h2>TARGET.EPOCALLOWDLLDATA</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies whether static data should be allowed in the application. Symbian disallows this by default in order to save memory. To use it, set this to 1.</p>
<a name="target-epocheapsize"></a><a name="target-epocheapsize"></a>
<h2>TARGET.EPOCHEAPSIZE</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies the minimum and maximum heap size of the application. The program will refuse to run if the minimum size is not available when it starts. For example:</p>
<pre class="cpp"> TARGET.EPOCHEAPSIZE = 10000 10000000</pre>
<a name="target-epocstacksize"></a><a name="target-epocstacksize"></a>
<h2>TARGET.EPOCSTACKSIZE</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies the maximum stack size of the application. For example:</p>
<pre class="cpp"> TARGET.EPOCSTACKSIZE = 0x8000</pre>
<a name="target-sid"></a><a name="target-sid"></a>
<h2>TARGET.SID</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies which secure identifier to use for the target application or library. For more information, see the Symbian SDK documentation.</p>
<a name="target-uid2"></a><a name="target-uid2"></a>
<h2>TARGET.UID2</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies which unique identifier 2 to use for the target application or library. If this variable is not specified, it defaults to the same value as TARGET.UID3. For more information, see the Symbian SDK documentation.</p>
<a name="target-uid3"></a><a name="target-uid3"></a>
<h2>TARGET.UID3</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies which unique identifier 3 to use for the target application or library. If this variable is not specified, a UID3 suitable for development and debugging will be generated automatically. However, applications being released should always define this variable. For more information, see the Symbian SDK documentation.</p>
<a name="target-vid"></a><a name="target-vid"></a>
<h2>TARGET.VID</h2>
<p><i>This is only used on the Symbian platform.</i></p>
<p>Specifies which vendor identifier to use for the target application or library. For more information, see the Symbian SDK documentation.</p>
<a name="target-ext"></a>
<h2>TARGET_EXT</h2>
<p>This variable specifies the target's extension. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="target-x"></a>
<h2>TARGET_x</h2>
<p>This variable specifies the target's extension with a major version number. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="target-x-y-z"></a>
<h2>TARGET_x.y.z</h2>
<p>This variable specifies the target's extension with version number. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="template"></a><a name="template"></a>
<h2>TEMPLATE</h2>
<p>This variable contains the name of the template to use when generating the project. The allowed values are:</p>
<table class="generic">
<thead><tr class="qt-style"><th >Option</th><th >Description</th></tr></thead>
<tr valign="top" class="odd"><td >app</td><td >Creates a Makefile for building applications (the default). (See <a href="qmake-common-projects.html#application">qmake Common Projects</a> for more information.)</td></tr>
<tr valign="top" class="even"><td >lib</td><td >Creates a Makefile for building libraries. (See <a href="qmake-common-projects.html#library">qmake Common Projects</a> for more information.)</td></tr>
<tr valign="top" class="odd"><td >subdirs</td><td >Creates a Makefile for building targets in subdirectories. The subdirectories are specified using the <a href="#subdirs">SUBDIRS</a> variable.</td></tr>
<tr valign="top" class="even"><td >vcapp</td><td ><i>Windows only</i> Creates an application project for Visual Studio. (See <a href="qmake-platform-notes.html#creating-visual-studio-project-files">qmake Platform Notes</a> for more information.)</td></tr>
<tr valign="top" class="odd"><td >vclib</td><td ><i>Windows only</i> Creates a library project for Visual Studio. (See <a href="qmake-platform-notes.html#creating-visual-studio-project-files">qmake Platform Notes</a> for more information.)</td></tr>
</table>
<p>For example:</p>
<pre class="cpp"> TEMPLATE = lib
SOURCES = main.cpp
TARGET = mylib</pre>
<p>The template can be overridden by specifying a new template type with the <tt>-t</tt> command line option. This overrides the template type <i>after</i> the .pro file has been processed. With .pro files that use the template type to determine how the project is built, it is necessary to declare TEMPLATE on the command line rather than use the <tt>-t</tt> option.</p>
<a name="translations"></a>
<h2>TRANSLATIONS</h2>
<p>This variable contains a list of translation (.ts) files that contain translations of the user interface text into non-native languages.</p>
<p>See the <a href="linguist-manual.html">Qt Linguist Manual</a> for more information about internationalization (i18n) and localization (l10n) with Qt.</p>
<a name="uicimpls"></a>
<h2>UICIMPLS</h2>
<p>This variable contains a list of the generated implementation files by UIC. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="uicobjects"></a>
<h2>UICOBJECTS</h2>
<p>This variable is generated from the UICIMPLS variable. The extension of each file will have been replaced by .o (Unix) or .obj (Win32). The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="ui-dir"></a><a name="ui-dir"></a>
<h2>UI_DIR</h2>
<p>This variable specifies the directory where all intermediate files from uic should be placed. This variable overrides both <a href="#ui-sources-dir">UI_SOURCES_DIR</a> and <a href="#ui-headers-dir">UI_HEADERS_DIR</a>.</p>
<p>For example:</p>
<pre class="cpp"> unix:UI_DIR = ../myproject/ui
win32:UI_DIR = c:/myproject/ui</pre>
<a name="ui-headers-dir"></a><a name="ui-headers-dir"></a>
<h2>UI_HEADERS_DIR</h2>
<p>This variable specifies the directory where all declaration files (as generated by uic) should be placed.</p>
<p>For example:</p>
<pre class="cpp"> unix:UI_HEADERS_DIR = ../myproject/ui/include
win32:UI_HEADERS_DIR = c:/myproject/ui/include</pre>
<a name="ui-sources-dir"></a><a name="ui-sources-dir"></a>
<h2>UI_SOURCES_DIR</h2>
<p>This variable specifies the directory where all implementation files (as generated by uic) should be placed.</p>
<p>For example:</p>
<pre class="cpp"> unix:UI_SOURCES_DIR = ../myproject/ui/src
win32:UI_SOURCES_DIR = c:/myproject/ui/src</pre>
<a name="version"></a><a name="version"></a>
<h2>VERSION</h2>
<p>This variable contains the version number of the application or library if either the <tt>app</tt> <a href="#template">TEMPLATE</a> or the <tt>lib</tt> <a href="#template">TEMPLATE</a> is specified.</p>
<p>For example:</p>
<pre class="cpp"> VERSION = 1.2.3</pre>
<a name="ver-maj"></a>
<h2>VER_MAJ</h2>
<p>This variable contains the major version number of the library, if the <tt>lib</tt> <a href="#template">template</a> is specified.</p>
<a name="ver-min"></a>
<h2>VER_MIN</h2>
<p>This variable contains the minor version number of the library, if the <tt>lib</tt> <a href="#template">template</a> is specified.</p>
<a name="ver-pat"></a>
<h2>VER_PAT</h2>
<p>This variable contains the patch version number of the library, if the <tt>lib</tt> <a href="#template">template</a> is specified.</p>
<a name="vpath"></a>
<h2>VPATH</h2>
<p>This variable tells <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> where to search for files it cannot open. With this you may tell <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> where it may look for things like SOURCES, and if it finds an entry in SOURCES that cannot be opened it will look through the entire VPATH list to see if it can find the file on its own.</p>
<p>See also <a href="#dependpath">DEPENDPATH</a>.</p>
<a name="yaccimpls"></a>
<h2>YACCIMPLS</h2>
<p>This variable contains a list of yacc source files. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="yaccobjects"></a>
<h2>YACCOBJECTS</h2>
<p>This variable contains a list of yacc object files. The value of this variable is typically handled by <a href="qmake-manual.html#qmake"><tt>qmake</tt></a> or <a href="#qmakespec">qmake.conf</a> and rarely needs to be modified.</p>
<a name="yaccsources"></a><a name="yaccsources"></a>
<h2>YACCSOURCES</h2>
<p>This variable contains a list of yacc source files to be included in the project. All dependencies, headers and source files will automatically be included in the project.</p>
<p>For example:</p>
<pre class="cpp"> YACCSOURCES = moc.y</pre>
<a name="pro-file"></a>
<h2>_PRO_FILE_</h2>
<p>This variable contains the path to the project file in use.</p>
<p>For example, the following line causes the location of the project file to be written to the console:</p>
<pre class="cpp"> message($$_PRO_FILE_)</pre>
<a name="pro-file-pwd"></a>
<h2>_PRO_FILE_PWD_</h2>
<p>This variable contains the path to the directory containing the project file in use.</p>
<p>For example, the following line causes the location of the directory containing the project file to be written to the console:</p>
<pre class="cpp"> message($$_PRO_FILE_PWD_)</pre>
</div>
<!-- @@@qmake-variable-reference.html -->
<p class="naviNextPrevious footerNavi">
<a class="prevPage" href="qmake-reference.html">qmake Reference</a>
<a class="nextPage" href="qmake-function-reference.html">qmake Function Reference</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>
