diff options
Diffstat (limited to 'qmake/doc/src/qmake-manual.qdoc')
| -rw-r--r-- | qmake/doc/src/qmake-manual.qdoc | 60 |
1 files changed, 26 insertions, 34 deletions
diff --git a/qmake/doc/src/qmake-manual.qdoc b/qmake/doc/src/qmake-manual.qdoc index 58e3ecec71..7ffdd9da0c 100644 --- a/qmake/doc/src/qmake-manual.qdoc +++ b/qmake/doc/src/qmake-manual.qdoc @@ -913,15 +913,34 @@ By default, support is disabled. \endtable - Since the \c debug option overrides the \c release option when both are - defined in the \c CONFIG variable, it is necessary to use the - \c 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: + When you use the \c debug_and_release option (which is the default under + Windows), the project will be processed three times: one time to produce + a "meta" Makefile, and two more times to produce a Makefile.Debug and a + Makefile.Release. + + During the latter passes, \c build_pass and the respective \c debug or + \c release option is appended to \c CONFIG. This makes it possible to + perform build-specific tasks. For example: + + \snippet code/doc_src_qmake-manual.pro 25 + + As an alternative to manually writing build type conditionals, some + variables offer build-specific variants, for example + \l{#QMAKE_LFLAGS_RELEASE}{QMAKE_LFLAGS_RELEASE} in addition to the general + \l{#QMAKE_LFLAGS}{QMAKE_LFLAGS}. These should be used when available. + + The meta Makefile makes the sub-builds invokable via the \c debug and + \c release targets, and a combined build via the \c all target. + When the \c build_all \c CONFIG option is used, the combined build is + the default. Otherwise, the last specified \c CONFIG option from the set + (\c debug, \c release) determines the default. In this case, you can + explicitly invoke the \c all target to build both configurations at once: \snippet code/doc_src_qmake-manual.pro 24 + \note The details are slightly different when producing Visual Studio + and Xcode projects. + When linking a library, qmake relies on the underlying platform to know what other libraries this library links against. However, if linking statically, qmake @@ -945,24 +964,6 @@ static library, while \c link_prl is required when \e {using} a static library. - On Windows (or if Qt is configured with \c{-debug-and-release}), add the - \c build_all option to the \c CONFIG variable to build all build - configurations by default. - - Additionally, adding \c debug_and_release to the \c CONFIG variable will - cause both \c debug and \c release to be defined in the contents of - \c CONFIG. When the project file is processed, the - \l{Scopes}{scopes} that test for each value will be - processed for \e both debug and release modes. The \c{build_pass} variable - will be set for each of these modes, and you can test for this to perform - build-specific tasks. For example: - - \snippet code/doc_src_qmake-manual.pro 25 - - As a result, it may be useful to define mode-specific variables, such as - \l{#QMAKE_LFLAGS_RELEASE}{QMAKE_LFLAGS_RELEASE}, instead of general - variables, such as \l{#QMAKE_LFLAGS}{QMAKE_LFLAGS}, where possible. - The following options define the application or library type: \table @@ -971,9 +972,6 @@ library and header files. The proper include and library paths for the Qt library will automatically be added to the project. This is defined by default, and can be fine-tuned with the \c{\l{#qt}{QT}} variable. - \row \li thread \li The target is a multi-threaded application or library. The - proper defines and compiler flags will automatically be added to - the project. This value is set by default. \row \li x11 \li The target is a X11 application or library. The proper include paths and libraries will automatically be added to the project. @@ -1002,8 +1000,6 @@ \row \li designer \li The target is a plugin for \QD. \row \li no_lflags_merge \li Ensures that the list of libraries stored in the \c LIBS variable is not reduced to a list of unique values before it is used. - \row \li resources \li Configures qmake to run rcc on the content of \c RESOURCES - if defined. \endtable These options define specific features on Windows only: @@ -1019,8 +1015,6 @@ as part of a library project. \row \li embed_manifest_exe \li Embeds a manifest file in the DLL created as part of an application project. - \row \li incremental \li Used to enable or disable incremental linking in Visual - C++, depending on whether this feature is enabled or disabled by default. \endtable See \l{Platform Notes#Visual Studio Manifest Files}{Platform Notes} @@ -1030,8 +1024,6 @@ \table \header \li Option \li Description - \row \li ppc \li Builds a PowerPC binary. - \row \li x86 \li Builds an i386 compatible binary. \row \li app_bundle \li Puts the executable into a bundle (this is the default). \row \li lib_bundle \li Puts the library into a library bundle. \endtable @@ -4527,7 +4519,7 @@ Sometimes, it is necessary to build a project in both debug and release modes. Although the \l{CONFIG} variable can hold both \c debug and \c release - options, the \c debug option overrides the \c release option. + options, only the option that is specified last is applied. \section2 Building in Both Modes |