summaryrefslogtreecommitdiffstats
path: root/mkspecs
diff options
context:
space:
mode:
authorHarald Fernengel <harald.fernengel@nokia.com>2011-11-11 11:21:52 +0100
committerQt by Nokia <qt-info@nokia.com>2011-11-11 12:24:48 +0100
commit6a25a86d375b03805686e82dbe9e9974f92bf5dd (patch)
tree7ec42355f5f9b917cb1bfe25ca4f0fb529c72365 /mkspecs
parent999196e3369417969d4a561710d68c8bb1786c47 (diff)
Add a -force-asserts option to configure
We have the following scenario: Either you build a release package without asserts, or a debug package with asserts. However, in embedded development, we need asserts also in release packages. This flag allows you to build a release package, but Q_ASSERTs still fire. Change-Id: Icd1dd4dd63c3cafecf515b40741263d902ad42d1 Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'mkspecs')
-rw-r--r--mkspecs/features/qt.prf1
1 files changed, 1 insertions, 0 deletions
diff --git a/mkspecs/features/qt.prf b/mkspecs/features/qt.prf
index 39d7a4b8a8..d288930eaf 100644
--- a/mkspecs/features/qt.prf
+++ b/mkspecs/features/qt.prf
@@ -18,6 +18,7 @@ win32 {
!isEmpty(QMAKESPEC_ORIGINAL):INCLUDEPATH += $$QMAKESPEC_ORIGINAL
}
CONFIG(release, debug|release):DEFINES += QT_NO_DEBUG
+contains(QT_CONFIG, force_asserts):DEFINES += QT_FORCE_ASSERTS
no_keywords:DEFINES += QT_NO_KEYWORDS
plugin { #Qt plugins
static:DEFINES += QT_STATICPLUGIN