From a830bf10b7d4ed2c83ffe68c0b22d7c4ba9860b0 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Thu, 1 Mar 2012 13:24:30 -0600 Subject: Rename additional global TQt functions --- doc/html/qmake-manual-4.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/html/qmake-manual-4.html') diff --git a/doc/html/qmake-manual-4.html b/doc/html/qmake-manual-4.html index 1577835..1036729 100644 --- a/doc/html/qmake-manual-4.html +++ b/doc/html/qmake-manual-4.html @@ -135,7 +135,7 @@ body { background: #ffffff; color: black; }

Use qmake as before to generate a makefile. If you rename main.cpp temporarily, you will see the message and qmake will stop processing.

Checking for more than one condition

-

Suppose you use Windows and you want to be able to see the qDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put console on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows and when debug is already on the CONFIG line. This requires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:

+

Suppose you use Windows and you want to be able to see the tqDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put console on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows and when debug is already on the CONFIG line. This requires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:

     win32 {
         debug {
-- 
cgit v1.2.3