remove qt from CONFIG for non-artifact templates
authorOswald Buddenhagen <oswald.buddenhagen@nokia.com>
Tue, 3 Apr 2012 17:27:55 +0000 (19:27 +0200)
committerOswald Buddenhagen <oswald.buddenhagen@nokia.com>
Tue, 19 Jun 2012 14:40:03 +0000 (16:40 +0200)
there is no point in adding Qt modules to SUBDIRS projects.
as QT contains core and gui by default, the operations are relatively
expensive, so skip them when they are unneeded.

Change-Id: Ibe6447ff452e403cb040fabe245d248edbda0eaa
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>
mkspecs/features/default_post.prf

index 8858e63..c56729a 100644 (file)
@@ -1,5 +1,7 @@
 contains(TEMPLATE, ".*(lib|app)"):CONFIG += have_target
 
+!have_target:!force_qt: CONFIG -= qt
+
 QT_BREAKPAD_ROOT_PATH = $$(QT_BREAKPAD_ROOT_PATH)
 !isEmpty(QT_BREAKPAD_ROOT_PATH): \   # quick test first whether requested ...
         !staticlib:!static:CONFIG(release, debug|release):have_target: \   # is it applicable?