<p>See the HelpDemo example in the TQt distribution for a demonstration on how to use <em>TQt Assistant</em> with profiles for your own applications.</p>
<p>When distributing <em>TQt Assistant</em> with your application, you will also need to copy the icon files from the <tt>QTDIR/tools/assistant/images</tt> directory so that <em>TQt Assistant</em> finds its icons.</p>
<p>When distributing <em>TQt Assistant</em> with your application, you will also need to copy the icon files from the <tt>TQTDIR/tools/assistant/images</tt> directory so that <em>TQt Assistant</em> finds its icons.</p>
<p>We do <em>not</em> include the <tt>creditformbase.ui</tt> file since this file will be read at runtime, as we'll see shortly. We must include the <tt>tqui</tt> library since the functionality we require is not part of the standard TQt library.</p>
<aname="1"></a><p> There is one of these per application. At application startup time it
reads the font definition file from <tt>$QTDIR/etc/fonts/fontdir</tt> (or <tt>/usr/local/etc/qt-embedded/fonts/fontdir</tt> if QTDIR is undefined). It
reads the font definition file from <tt>$TQTDIR/etc/fonts/fontdir</tt> (or <tt>/usr/local/etc/qt-embedded/fonts/fontdir</tt> if TQTDIR is undefined). It
keeps track of all font information and maintains a cache of rendered
fonts. It also creates the font factories: TQFontManager::TQFontManager
is the place to add constructors for new factories. It provides a
@ -52,7 +52,7 @@ the <a href="activentqt.html#ActiveTQt">ActiveTQt</a> Framework to develop plugi
<aname="2"></a><p><oltype=1>
<li> Download the
<ahref="http://home.netscape.com/comprod/development_partners/plugin_api/index.html">Plugin SDK from Netscape</a>, and copy the following files from there to
<li><p>QTDIR <br> This must be set to where TQt is (or will be) installed. For example, <em>c:\qt</em> and <em>\local\qt</em></p>
</ul><p>Once the environment variables are set go into the qmake directory, <em>$QTDIR/qmake</em>, e.g. <em>C:\qt\qmake</em>. Now run <em>make</em> or <em>nmake</em> depending on your compiler.</p>
<li><p>TQTDIR <br> This must be set to where TQt is (or will be) installed. For example, <em>c:\qt</em> and <em>\local\qt</em></p>
</ul><p>Once the environment variables are set go into the qmake directory, <em>$TQTDIR/qmake</em>, e.g. <em>C:\qt\qmake</em>. Now run <em>make</em> or <em>nmake</em> depending on your compiler.</p>
<p>When the make has completed, <em>qmake</em> is ready for use.</p>
<!-- eof -->
<palign="right">[<ahref="qmake-manual-1.html">Prev: Introduction to qmake</a>] [<ahref="qmake-manual.html">Home</a>] [<ahref="qmake-manual-3.html">Next: The 10 minute guide to using qmake</a>]</p>
<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 <em>qmake</em> or <ahref="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p>
<p>This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a TQt application. The value of this variable is typically handled by <em>qmake</em> or <ahref="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p>
<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 <em>qmake</em> or <ahref="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p>
@ -430,7 +430,7 @@ app {
<p>This variable contains the list of all directories to look in to resolve dependencies. This will be used when crawling through 'included' files.</p>
<h5><aname="4-2-63"></a>QMAKE_LIBDIR_OPENGL</h5>
<p>This variable contains the location of the OpenGL library directory.The value of this variable is typically handled by <em>qmake</em> or <ahref="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p>
<h5><aname="4-2-64"></a>QMAKE_LIBDIR_QT</h5>
<h5><aname="4-2-64"></a>QMAKE_LIBDIR_TQT</h5>
<p>This variable contains the location of the TQt library directory.The value of this variable is typically handled by <em>qmake</em> or <ahref="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p>
<h5><aname="4-2-65"></a>QMAKE_LIBDIR_X11</h5>
<p><em>This is used on Unix platforms only</em></p>
@ -571,7 +571,7 @@ OPTIONS = standard custom
<p>This function will test if <em>file</em> exists. If the file exists, then it will succeed; otherwise it will fail. You can specify a regular expression in file and it will succeed if any file matches the regular expression specified.</p>
<p>For example:</p>
<pre>
exists( $(QTDIR)/lib/libtqt-mt* ) {
exists( $(TQTDIR)/lib/libtqt-mt* ) {
message( "Configuring for multi-threaded TQt..." )
CONFIG += thread
}
@ -645,7 +645,7 @@ QMAKE_VERS = $$[QMAKE_VERSION]
<p><em>qmake</em> requires a platform and compiler description file which contains many default values used to generate appropriate makefiles. The standard TQt distribution comes with many of these files, located in the 'mkspecs' subdirectory of the TQt installation.</p>
<p>The QMAKESPEC environment variable can contain any of the following:</p>
<ul><li><p>A complete path to a directory containing a qmake.conf file. In this case <em>qmake</em> will open the qmake.conf file from within that directory. If the file does not exist, <em>qmake</em> will exit with an error.</p>
<li><p>The name of a platform-compiler combination. In this case, <em>qmake</em> will search in the directory specified by the QTDIR environment variable.</p>
<li><p>The name of a platform-compiler combination. In this case, <em>qmake</em> will search in the directory specified by the TQTDIR environment variable.</p>
</ul><p>Note: the QMAKESPEC path will automatically be added to the <ahref="qmake-manual-8.html#INCLUDEPATH">INCLUDEPATH</a> system variable.</p>
<p>It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this <em>qmake</em> has introduce the concept of an install set. The notation for this is quite simple, first you fill in an "object" in qmake for example:</p>
