~oif-team/ubuntu/natty/qt4-x11/xi2.1

<td width="1">  </td><td class="postheader" valign="center"><a href="index.html"><font color="#004faf">Home</font></a> · <a href="namespaces.html"><font color="#004faf">All Namespaces</font></a> · <a href="classes.html"><font color="#004faf">All Classes</font></a> · <a href="mainclasses.html"><font color="#004faf">Main Classes</font></a> · <a href="groups.html"><font color="#004faf">Grouped Classes</font></a> · <a href="modules.html"><font color="#004faf">Modules</font></a> · <a href="functions.html"><font color="#004faf">Functions</font></a></td>

<td width="1">  </td><td class="postheader" valign="center"><a href="index.html"><font color="#004faf">Home</font></a> · <a href="classes.html"><font color="#004faf">All Classes</font></a> · <a href="functions.html"><font color="#004faf">All Functions</font></a> · <a href="overviews.html"><font color="#004faf">Overviews</font></a></td><td class="searchBar" align="right" valign="center"><form action="http://www.google.com/cse" id="cse-search-box"><div><input type="hidden" name="cx" value="000136343326384750312:dhbxnqlakyu" /><input type="hidden" name="ie" value="UTF-8" /><input type="text" name="q" size="31" /><input type="submit" name="sa" value="Search" /></div></form></td>

</tr></table><p>

[Previous: <a href="qmake-tutorial.html">qmake Tutorial</a>]

[<a href="qmake-manual.html">Contents</a>]

[Next: <a href="qmake-using.html">Using qmake</a>]

<h3>The app Template</h3>

<p>The <tt>app</tt> template tells <tt>qmake</tt> to generate a Makefile that will build an application. With this template, the type of application can be specified by adding one of the following options to the <tt>CONFIG</tt> variable definition:</p>

<thead><tr valign="top" class="qt-style"><th>Option</th><th>Description</th></tr></thead>

<tr valign="top" class="odd"><td>windows</td><td>The application is a Windows GUI application.</td></tr>

<tr valign="top" class="even"><td>console</td><td><tt>app</tt> template only: the application is a Windows console application.</td></tr>

<ul>

<li>HEADERS - A list of all the header files for the application.</li>

<li>SOURCES - A list of all the source files for the application.</li>

<li>FORMS - A list of all the .ui files (created using <tt>Qt Designer</tt>) for the application.</li>

<li>FORMS - A list of all the UI files (created using <tt>Qt Designer</tt>) for the application.</li>

<li>LEXSOURCES - A list of all the lex source files for the application.</li>

<li>YACCSOURCES - A list of all the yacc source files for the application.</li>

<li>TARGET - Name of the executable for the application. This defaults to the name of the project file. (The extension, if any, is added automatically).</li>

<li><a href="qmake-variable-reference.html#rc-file">RC_FILE</a> - Windows only: A resource file for the application.</li>

<li><a href="qmake-variable-reference.html#res-file">RES_FILE</a> - Windows only: A resource file to be linked against for the application.</li>

</ul>

<p>You only need to use the system variables that you have values for, for instance, if you don't have any extra INCLUDEPATHs then you don't need to specify any, <tt>qmake</tt> will add in the default ones needed. For instance, an example project file might look like this:</p>

<p>You only need to use the system variables that you have values for, for instance, if you do not have any extra INCLUDEPATHs then you do not need to specify any, <tt>qmake</tt> will add in the default ones needed. For instance, an example project file might look like this:</p>

<pre> TEMPLATE = app

DESTDIR = c:/helloapp

HEADERS += hello.h

<h3>The lib Template</h3>

<p>The <tt>lib</tt> template tells <tt>qmake</tt> to generate a Makefile that will build a library. When using this template, in addition to the system variables mentioned above for the <tt>app</tt> template the <tt>VERSION</tt> variable is supported. You should use these in your .pro file to specify information about the library.</p>

<p>When using the <tt>lib</tt> template, the following options can be added to the <tt>CONFIG</tt> variable to determine the type of library that is built:</p>

<thead><tr valign="top" class="qt-style"><th>Option</th><th>Description</th></tr></thead>

<tr valign="top" class="odd"><td>dll</td><td>The library is a shared library (dll).</td></tr>

<tr valign="top" class="even"><td>staticlib</td><td>The library is a static library.</td></tr>

101

<h3>Building a Qt Designer Plugin</h3>

102

<p><i>Qt Designer</i> plugins are built using a specific set of configuration settings that depend on the way Qt was configured for your system. For convenience, these settings can be enabled by adding <tt>designer</tt> to the project's <tt>CONFIG</tt> variable. For example:</p>

103

<pre> CONFIG += designer plugin</pre>

104

<p>See the <a href="examples.html#qt-designer">Qt Designer examples</a> for more examples of plugin-based projects.</p>

104

<p>See the <a href="examples-designer.html">Qt Designer Examples</a> for more examples of plugin-based projects.</p>

105

106

<h2>Building and Installing in Debug and Release Modes</h2>

107

<p>Sometimes, it is necessary to build a project in both debug and release modes. Although the <tt>CONFIG</tt> variable can hold both <tt>debug</tt> and <tt>release</tt> options, the <tt>debug</tt> option overrides the <tt>release</tt> option.</p>

139

</p>

140

141

142

143

<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>

144

145

</tr></table></div></address></body>

142

143

<td width="20%" align="center"><a href="trademarks.html">Trademarks</a></td>

144

145

146

</html>

Older »