qmake Variable Reference

CONFIG

The CONFIG variable specifies project configuration and compiler options. The values will be recognized internally by qmake and have special meaning. They are as follows.

These CONFIG values control compilation flags:

Since the debug option overrides the release option when both are defined in the CONFIG variable, it is necessary to use the debug_and_release option if you want to allow both debug and release versions of a project to be built. In such a case, the Makefile that qmake generates includes a rule that builds both versions, and this can be invoked in the following way:

 make all

When linking a library, qmake relies on the underlying platform to know what other libraries this library links against. However, if linking statically, qmake will not get this information unless we use the following CONFIG options:

Please note that create_prl is required when

{building} a static library, while link_prl is required when

{using} a static library.

On Windows (or if Qt is configured with -debug_and_release, adding the build_all option to the CONFIG variable makes this rule the default when building the project, and installation targets will be created for both debug and release builds.

Additionally, adding debug_and_release to the CONFIG variable will cause both debug and release to be defined in the contents of CONFIG. When the project file is processed, the scopes that test for each value will be processed for both debug and release modes. The build_pass variable will be set for each of these mode, and you can test for this to perform build-specific tasks. For example:

 build_pass:CONFIG(debug, debug|release) {
     unix: TARGET = $$join(TARGET,,,_debug)
     else: TARGET = $$join(TARGET,,,d)
 }

As a result, it may be useful to define mode-specific variables, such as QMAKE_LFLAGS_RELEASE, instead of general variables, such as QMAKE_LFLAGS, where possible.

The following options define the application/library type:

These options are used to set the compiler flags:

These options define specific features on Windows only:

See qmake Platform Notes for more information on the options for embedding manifest files.

These options only have an effect on Mac OS X:

The build process for bundles is also influenced by the contents of the QMAKE_BUNDLE_DATA variable.

These options have an effect on Linux/Unix platforms:

The CONFIG variable will also be checked when resolving scopes. You may assign anything to this variable.

For example:

 CONFIG += qt console newstuff
 ...
 newstuff {
     SOURCES += new.cpp
     HEADERS += new.h
 }

 DEFINES += USE_MY_STUFF QT_DLL

 myFiles.sources = path\*.png
 DEPLOYMENT += myFiles

 myFiles.sources = path\file1.ext1 path2\file2.ext1 path3\*
 myFiles.path = \some\path\on\device
 someother.sources = C:\additional\files\*
 someother.path = \myFiles\path2
 DEPLOYMENT += myFiles someother

 DEPLOYMENT_PLUGIN += qjpeg

 DESTDIR = ../../lib

 DISTFILES += ../program.txt

 FORMS = mydialog.ui \
     mywidget.ui \
         myconfig.ui

 FORMS3 = my_uic3_dialog.ui \
      my_uic3_widget.ui \
          my_uic3_config.ui

 HEADERS = myclass.h \
           login.h \
           mainwindow.h

 INCLUDEPATH = c:/msdev/include d:/stl/include

 target.path += $$[QT_INSTALL_PLUGINS]/imageformats
 INSTALLS += target

 LEXSOURCES = lexer.l

 unix:LIBS += -L/usr/local/lib -lmath
 win32:LIBS += c:/mylibs/math.lib

 CONFIG += no_lflags_merge

 # To include a literal hash character, use the $$LITERAL_HASH variable:
 urlPieces = http://qt.nokia.com/doc/4.0/qtextdocument.html pageCount
 message($$join(urlPieces, $$LITERAL_HASH))

 unix:MOC_DIR = ../myproject/tmp
 win32:MOC_DIR = c:/myproject/tmp

 unix:OBJECTS_DIR = ../myproject/tmp
 win32:OBJECTS_DIR = c:/myproject/tmp

 app {
     # Conditional code for 'app' template here
 }

 FRAMEWORK_HEADERS.version = Versions
 FRAMEWORK_HEADERS.files = path/to/header_one.h path/to/header_two.h
 FRAMEWORK_HEADERS.path = Headers
 QMAKE_BUNDLE_DATA += FRAMEWORK_HEADERS

 QMAKE_BUNDLE_EXTENSION = .myframework

 QMAKE_RESOURCE_FLAGS += -threshold 0 -compress 9

 QMAKE_UIC = uic -L /path/to/plugin

 QT -= gui # Only the core module is used.

 unix:RCC_DIR = ../myproject/resources
 win32:RCC_DIR = c:/myproject/resources

 SOURCES = myclass.cpp \
       login.cpp \
       mainwindow.cpp

 SUBDIRS = kernel \
           tools

 CONFIG += ordered

 TEMPLATE = app
 TARGET = myapp
 SOURCES = main.cpp

 TEMPLATE = lib
 SOURCES = main.cpp
 TARGET = mylib

 unix:UI_DIR = ../myproject/ui
 win32:UI_DIR = c:/myproject/ui

 unix:UI_HEADERS_DIR = ../myproject/ui/include
 win32:UI_HEADERS_DIR = c:/myproject/ui/include

 unix:UI_SOURCES_DIR = ../myproject/ui/src
 win32:UI_SOURCES_DIR = c:/myproject/ui/src

 VERSION = 1.2.3

 YACCSOURCES = moc.y

 message($$_PRO_FILE_)

 message($$_PRO_FILE_PWD_)