From 0f92dd542b65bc910caaf190b7c623aa5158c86a Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 14 Nov 2011 22:33:41 -0600 Subject: Fix native TQt3 accidental conversion to tquit --- doc/html/qmake-manual-8.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/html/qmake-manual-8.html') 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]
  • The name of a platform-compiler combination. In this case, qmake will search in the directory specified by the QTDIR environment variable.

    Note: the QMAKESPEC path will automatically be added to the INCLUDEPATH system variable.

    INSTALLS

    -

    It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this qmake 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:

    +

    It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this qmake 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:

       documentation.path = /usr/local/program/doc
       documentation.files = docs/*
    @@ -698,7 +698,7 @@ QMAKE_VERS = $$[QMAKE_VERSION]
     
  • QMAKE_EXT_H - Changes interpretation all files with these suffixes to be C header files.

    Customizing Makefile Output

    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 generator).

    -

    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:

    +

    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:

       mytarget.target = .buildfile
       mytarget.commands = touch $$mytarget.target
    -- 
    cgit v1.2.1