summaryrefslogtreecommitdiffstats
path: root/tqtinterface/qt4/qmake/book/qmake-advanced.leaf
diff options
context:
space:
mode:
Diffstat (limited to 'tqtinterface/qt4/qmake/book/qmake-advanced.leaf')
-rw-r--r--tqtinterface/qt4/qmake/book/qmake-advanced.leaf20
1 files changed, 10 insertions, 10 deletions
diff --git a/tqtinterface/qt4/qmake/book/qmake-advanced.leaf b/tqtinterface/qt4/qmake/book/qmake-advanced.leaf
index ab94a46..d1b8c4b 100644
--- a/tqtinterface/qt4/qmake/book/qmake-advanced.leaf
+++ b/tqtinterface/qt4/qmake/book/qmake-advanced.leaf
@@ -64,7 +64,7 @@ is not already defined.
\section2 The '~=' operator
-This operator tqreplaces any values that match the regexp with the
+This operator replaces any values that match the regexp with the
specified value. It is used like this:
\code
@@ -193,7 +193,7 @@ variable by prefixing $$ to the variable name. For example:
MY_DEFINES = $$DEFINES
\endcode
-Now the MY_DEFINES variable tqcontains what is in the DEFINES variable at
+Now the MY_DEFINES variable contains what is in the DEFINES variable at
this point in the project file. This is also equivalent to:
\code
@@ -204,7 +204,7 @@ The second notation allows you to adjoin the variable expansion to another
value without separating by space. \e qmake will allow a variable to
contain anything (including $(VALUE), which will be placed directly into
the Makefile, and allow it to expand as appropriate, usually an environment
-variable). However, if you require an environment variable to be tqreplaced
+variable). However, if you require an environment variable to be replaced
immediately then you may use the $$() notation. For example:
\code
@@ -235,7 +235,7 @@ list. If the value of \e variablename is not long this will return an empty
string. \e variablename is the only required field, if not specified
position will default to the first value in the list (0).
-\section2 tqfind( variablename, substr )
+\section2 find( variablename, substr )
This will place all the values in \e variablename that match \e substr. \e
substr may be a regular expression as well, and will be matched
@@ -244,11 +244,11 @@ accordingly.
\code
MY_VAR = one two three four
MY_VAR2 = $$join(MY_VAR, " -L", -L) -Lfive
- MY_VAR3 = $$member(MY_VAR, 2) $$tqfind(MY_VAR, t.*)
+ MY_VAR3 = $$member(MY_VAR, 2) $$find(MY_VAR, t.*)
\endcode
MY_VAR2 will contain '-Lone -Ltwo -Lthree -Lfour -Lfive', and MYVAR3 will
-tqcontains 'three two three'.
+contains 'three two three'.
\section2 system( program_and_args )
@@ -258,7 +258,7 @@ platform for example.
\code
UNAME = $$system(uname -s)
- tqcontains( UNAME, [lL]inux ):message( This looks like Linux ($$UNAME) to me )
+ contains( UNAME, [lL]inux ):message( This looks like Linux ($$UNAME) to me )
\endcode
\section1 Test Functions
@@ -268,14 +268,14 @@ tests. These tests may be used in place of scopes (as described above), in
some cases it is more usefull to use the test function by itself ignoring
its test value.
-\section2 tqcontains( variablename, value )
+\section2 contains( variablename, value )
If \e value is in the list of values stored in the variable called \e
variablename, then the settings inside the scope will be processed.
For example:
\code
- tqcontains( CONFIG, thread ) {
+ contains( CONFIG, thread ) {
DEFINES += QT_THREAD_SUPPORT
}
\endcode
@@ -396,6 +396,6 @@ headers.
\section2 infile( filename, var, val )
This function will succeed if the file \e filename (when parsed
-by qmake itself) tqcontains the variable \e var with a value of
+by qmake itself) contains the variable \e var with a value of
\e val. You may also not pass in a third argument (\e val) and the
function will only test if \e var has been assigned to in the file.