diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-14 22:33:41 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-14 22:33:41 -0600 |
| commit | 0f92dd542b65bc910caaf190b7c623aa5158c86a (patch) | |
| tree | 120ab7e08fa0ffc354ef58d100f79a33c92aa6e6 /doc/html/qmake-manual-8.html | |
| parent | d796c9dd933ab96ec83b9a634feedd5d32e1ba3f (diff) | |
| download | tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.tar.gz tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.zip | |
Fix native TQt3 accidental conversion to tquit
Diffstat (limited to 'doc/html/qmake-manual-8.html')
| -rw-r--r-- | doc/html/qmake-manual-8.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/qmake-manual-8.html b/doc/html/qmake-manual-8.html index 19e875d4d..e21c9779a 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -648,7 +648,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <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> </ul><p>Note: the QMAKESPEC path will automatically be added to the <a href="qmake-manual-8.html#INCLUDEPATH">INCLUDEPATH</a> system variable.</p> <a name="INSTALLS"></a><h4><a name="7-2"></a>INSTALLS</h4> -<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 tquite simple, first you fill in an "object" in qmake for example:</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> <pre> documentation.path = /usr/local/program/doc documentation.files = docs/* @@ -698,7 +698,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <li><p>QMAKE_EXT_H - Changes interpretation all files with these suffixes to be C header files.</p> </ul><a name="Customizing"></a><h4><a name="7-6"></a>Customizing Makefile Output</h4> <p>qmake often tries to be all things to all build tools, this is often less than ideal when you really need to run special platform dependent commands. This can be achieved with specific instructions to the different qmake backends (currently this is only supported by the UNIX <a href="qmake-manual-8.html#MAKEFILE_GENERATOR">generator</a>).</p> -<p>The interfaces to customizing the Makefile are done through "objects" as in other places in qmake. The notation for this is tquite simple, first you fill in an "object" in qmake for example:</p> +<p>The interfaces to customizing the Makefile are done through "objects" as in other places in qmake. The notation for this is quite simple, first you fill in an "object" in qmake for example:</p> <pre> mytarget.target = .buildfile mytarget.commands = touch $$mytarget.target |