diff options
Diffstat (limited to 'doc/src/development/qmake-manual.qdoc')
| -rw-r--r-- | doc/src/development/qmake-manual.qdoc | 334 |
1 files changed, 167 insertions, 167 deletions
diff --git a/doc/src/development/qmake-manual.qdoc b/doc/src/development/qmake-manual.qdoc index b17738615..d7483d1d9 100644 --- a/doc/src/development/qmake-manual.qdoc +++ b/doc/src/development/qmake-manual.qdoc @@ -201,11 +201,11 @@ The following snippet illustrates how lists of values are assigned to variables: - \snippet doc/src/snippets/qmake/variables.pro 0 + \snippet snippets/qmake/variables.pro 0 The list of values in a variable is extended in the following way: - \snippet doc/src/snippets/qmake/variables.pro 1 + \snippet snippets/qmake/variables.pro 1 \note The first assignment only includes values that are specified on the same line as the \c HEADERS variable. The second assignment splits @@ -244,7 +244,7 @@ The contents of a variable can be read by prepending the variable name with \c $$. This can be used to assign the contents of one variable to another: - \snippet doc/src/snippets/qmake/dereferencing.pro 0 + \snippet snippets/qmake/dereferencing.pro 0 The \c $$ operator is used extensively with built-in functions that operate on strings and lists of values. For more information, see @@ -255,21 +255,21 @@ Usually, whitespace separates values in variable assignments. To specify values that contain spaces, you must enclose the values in double quotes: - \snippet doc/src/snippets/qmake/quoting.pro 0 + \snippet snippets/qmake/quoting.pro 0 The quoted text is treated as a single item in the list of values held by the variable. A similar approach is used to deal with paths that contain spaces, particularly when defining the \l{INCLUDEPATH} and \l{LIBS} variables for the Windows platform: - \snippet doc/src/snippets/qmake/spaces.pro quoting include paths with spaces + \snippet snippets/qmake/spaces.pro quoting include paths with spaces \section2 Comments You can add comments to project files. Comments begin with the \c # character and continue to the end of the same line. For example: - \snippet doc/src/snippets/qmake/comments.pro 0 + \snippet snippets/qmake/comments.pro 0 To include the \c # character in variable assignments, it is necessary to use the contents of the built-in \l{LITERAL_HASH} variable. @@ -285,12 +285,12 @@ The \c include function is most commonly used to include other project files: - \snippet doc/src/snippets/qmake/include.pro 0 + \snippet snippets/qmake/include.pro 0 Support for conditional structures is made available via \l{Scopes}{scopes} that behave like \c if statements in programming languages: - \snippet doc/src/snippets/qmake/scopes.pro 0 + \snippet snippets/qmake/scopes.pro 0 The assignments inside the braces are only made if the condition is true. In this case, the \c win32 \l{CONFIG} option must be set. This @@ -353,7 +353,7 @@ versions of a project, the Makefile that qmake generates includes a rule that builds both versions. This can be invoked in the following way: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 0 + \snippet snippets/code/doc_src_qmake-manual.pro 0 Adding the \c build_all option to the \c CONFIG variable makes this rule the default when building the project. @@ -365,8 +365,8 @@ For example, the following lines show the function as the condition in a scope to test whether only the \c opengl option is in use: - \snippet doc/src/snippets/qmake/configscopes.pro 4 - \snippet doc/src/snippets/qmake/configscopes.pro 5 + \snippet snippets/qmake/configscopes.pro 4 + \snippet snippets/qmake/configscopes.pro 5 This enables different configurations to be defined for \c release and \c debug builds. For more information, see \l{Scopes}{Using Scopes}. @@ -394,7 +394,7 @@ For example, if your application uses the Qt library and you want to build it in \c debug mode, your project file will contain the following line: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 1 + \snippet snippets/code/doc_src_qmake-manual.pro 1 \note You must use "+=", not "=", or qmake will not be able to use Qt's configuration to determine the settings @@ -409,21 +409,21 @@ extension modules. For example, we can enable the XML and network modules in the following way: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 2 + \snippet snippets/code/doc_src_qmake-manual.pro 2 \note \c QT includes the \c core and \c gui modules by default, so the above declaration \e adds the network and XML modules to this default list. The following assignment \e omits the default modules, and will lead to errors when the application's source code is being compiled: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 3 + \snippet snippets/code/doc_src_qmake-manual.pro 3 If you want to build a project \e without the \c gui module, you need to exclude it with the "-=" operator. By default, \c QT contains both \c core and \c gui, so the following line will result in a minimal Qt project being built: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 4 + \snippet snippets/code/doc_src_qmake-manual.pro 4 For a list of Qt modules that you can add to the \c QT variable, see \l{Variables#QT}{QT}. @@ -441,7 +441,7 @@ \l{http://www.freedesktop.org/wiki/Software/pkg-config}{pkg-config}, such as the D-Bus and ogg libraries, with the following lines: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 5 + \snippet snippets/code/doc_src_qmake-manual.pro 5 For more information about adding features, see \l{Adding New Configuration Features}. @@ -458,14 +458,14 @@ For example, the following lines show how a library can be specified: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 6 + \snippet snippets/code/doc_src_qmake-manual.pro 6 The paths containing header files can also be specified in a similar way using the \l{INCLUDEPATH} variable. For example, to add several paths to be searched for header files: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 7 + \snippet snippets/code/doc_src_qmake-manual.pro 7 */ /*! @@ -485,7 +485,7 @@ The syntax used to run qmake takes the following simple form: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 8 + \snippet snippets/code/doc_src_qmake-manual.pro 8 \section1 Operating Modes @@ -572,7 +572,7 @@ \target MakefileMode \section1 Makefile Mode Options - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 9 + \snippet snippets/code/doc_src_qmake-manual.pro 9 In Makefile mode, qmake will generate a Makefile that is used to build the project. Additionally, the following options may @@ -599,12 +599,12 @@ before all of the files specified. For example, the following command generates a Makefile from test.pro: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 10 + \snippet snippets/code/doc_src_qmake-manual.pro 10 However, some of the specified options can be omitted as they are default values: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 11 + \snippet snippets/code/doc_src_qmake-manual.pro 11 If you are certain you want your variables processed after the files specified, then you may pass the \c -after option. When this @@ -614,7 +614,7 @@ \target ProjectMode \section1 Project Mode Options - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 12 + \snippet snippets/code/doc_src_qmake-manual.pro 12 In project mode, qmake will generate a project file. Additionally, you may supply the following options in this mode: @@ -669,7 +669,7 @@ For example, to use qmake from a binary package to create a Makefile in a project directory, invoke the following command: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 13 + \snippet snippets/code/doc_src_qmake-manual.pro 13 \section2 Using Frameworks @@ -681,12 +681,12 @@ to the build system, and this is achieved by appending linker options to the \l{QMAKE_LFLAGS} variable, as shown in the following example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 14 + \snippet snippets/code/doc_src_qmake-manual.pro 14 The framework itself is linked in by appending the \c{-framework} options and the name of the framework to the \l{LIBS} variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 15 + \snippet snippets/code/doc_src_qmake-manual.pro 15 \section2 Creating Frameworks @@ -697,7 +697,7 @@ \l{TEMPLATE}{\c lib template} and add the \c lib_bundle option to the \l{CONFIG} variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 16 + \snippet snippets/code/doc_src_qmake-manual.pro 16 The data associated with the library is specified using the \l{QMAKE_BUNDLE_DATA} @@ -705,7 +705,7 @@ bundle, and is often used to specify a collection of header files, as in the following example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 17 + \snippet snippets/code/doc_src_qmake-manual.pro 17 You use the \c FRAMEWORK_HEADERS variable to specify the headers required by a particular framework. @@ -727,7 +727,7 @@ by running qmake to generate an Xcode project from an existing qmake project file. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 19 + \snippet snippets/code/doc_src_qmake-manual.pro 19 \note If a project is later moved on the disk, qmake must be run again to process the project file and create a new Xcode project file. @@ -778,12 +778,12 @@ This can also be set using a command line option, for example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 20 + \snippet snippets/code/doc_src_qmake-manual.pro 20 It is possible to recursively generate \c{.vcproj} files in subdirectories and a \c{.sln} file in the main directory, by typing: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 21 + \snippet snippets/code/doc_src_qmake-manual.pro 21 Each time you update the project file, you need to run qmake to generate an updated Visual Studio @@ -802,12 +802,12 @@ Removing manifest embedding for application executables can be done with the following assignment to the \l{CONFIG} variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 22 + \snippet snippets/code/doc_src_qmake-manual.pro 22 Also, the manifest embedding for DLLs can be removed with the following assignment to the \c CONFIG variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 23 + \snippet snippets/code/doc_src_qmake-manual.pro 23 This is discussed in more detail in the \l{Deploying an Application on Windows#Manifest files} @@ -916,7 +916,7 @@ qmake generates includes a rule that builds both versions, and this can be invoked in the following way: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 24 + \snippet snippets/code/doc_src_qmake-manual.pro 24 When linking a library, qmake relies on the underlying platform to know what other libraries this library links @@ -953,7 +953,7 @@ will be set for each of these modes, and you can test for this to perform build-specific tasks. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 25 + \snippet snippets/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 @@ -1049,7 +1049,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 26 + \snippet snippets/code/doc_src_qmake-manual.pro 26 \target DEFINES \section1 DEFINES @@ -1059,7 +1059,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 27 + \snippet snippets/code/doc_src_qmake-manual.pro 27 \target DEF_FILE \section1 DEF_FILE @@ -1089,7 +1089,7 @@ For example, the following definition uploads all PNG images in \c path to the directory where the build target is deployed: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 28 + \snippet snippets/code/doc_src_qmake-manual.pro 28 The default deployment target path for Windows CE is \c{%CSIDL_PROGRAM_FILES%\target}, which usually gets expanded to @@ -1101,7 +1101,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 29 + \snippet snippets/code/doc_src_qmake-manual.pro 29 \note In Windows CE all linked Qt libraries will be deployed to the path specified by \c{myFiles.path}. @@ -1122,7 +1122,7 @@ For example, the following definition uploads the jpeg imageformat plugin to the plugins directory on the Windows CE device: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 142 + \snippet snippets/code/doc_src_qmake-manual.pro 142 \target DESTDIR \section1 DESTDIR @@ -1131,7 +1131,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 30 + \snippet snippets/code/doc_src_qmake-manual.pro 30 \target DISTFILES \section1 DISTFILES @@ -1141,7 +1141,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 31 + \snippet snippets/code/doc_src_qmake-manual.pro 31 \target DLLDESTDIR \section1 DLLDESTDIR @@ -1159,7 +1159,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 32 + \snippet snippets/code/doc_src_qmake-manual.pro 32 \target GUID \section1 GUID @@ -1182,7 +1182,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 34 + \snippet snippets/code/doc_src_qmake-manual.pro 34 See also \l{#SOURCES}{SOURCES}. @@ -1201,12 +1201,12 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 35 + \snippet snippets/code/doc_src_qmake-manual.pro 35 To specify a path containing spaces, quote the path using the technique described in \l{Whitespace}. - \snippet doc/src/snippets/qmake/spaces.pro quoting include paths with spaces + \snippet snippets/qmake/spaces.pro quoting include paths with spaces \target INSTALLS \section1 INSTALLS @@ -1220,7 +1220,7 @@ build target will be installed, and the \c INSTALLS assignment adds the build target to the list of existing resources to be installed: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 36 + \snippet snippets/code/doc_src_qmake-manual.pro 36 For more information, see \l{Installing Files}. @@ -1247,7 +1247,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 37 + \snippet snippets/code/doc_src_qmake-manual.pro 37 \target LIBS \section1 LIBS @@ -1260,18 +1260,18 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 38 + \snippet snippets/code/doc_src_qmake-manual.pro 38 To specify a path containing spaces, quote the path using the technique described in \l{Whitespace}. - \snippet doc/src/snippets/qmake/spaces.pro quoting library paths with spaces + \snippet snippets/qmake/spaces.pro quoting library paths with spaces By default, the list of libraries stored in \c LIBS is reduced to a list of unique names before it is used. To change this behavior, add the \c no_lflags_merge option to the \l{CONFIG} variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 39 + \snippet snippets/code/doc_src_qmake-manual.pro 39 \target LITERAL_HASH \section1 LITERAL_HASH @@ -1282,7 +1282,7 @@ For example: - \snippet doc/src/snippets/qmake/comments.pro 1 + \snippet snippets/qmake/comments.pro 1 By using \c LITERAL_HASH in this way, the \c # character can be used to construct a URL for the \c message() function to print to the console. @@ -1310,7 +1310,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 40 + \snippet snippets/code/doc_src_qmake-manual.pro 40 \target OBJECTS \section1 OBJECTS @@ -1327,7 +1327,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 41 + \snippet snippets/code/doc_src_qmake-manual.pro 41 \target POST_TARGETDEPS \section1 POST_TARGETDEPS @@ -1416,7 +1416,7 @@ and \c path/to/header_two.h to a group containing information about the headers supplied with the framework: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 43 + \snippet snippets/code/doc_src_qmake-manual.pro 43 The last line adds the information about the headers to the collection of resources that will be installed with the library bundle. @@ -1438,7 +1438,7 @@ For example, the following definition will result in a framework with the \c{.myframework} extension: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 44 + \snippet snippets/code/doc_src_qmake-manual.pro 44 \section1 QMAKE_CC @@ -2026,7 +2026,7 @@ \c{-compress} options are used with particular values each time that \c rcc is invoked: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 45 + \snippet snippets/code/doc_src_qmake-manual.pro 45 \section1 QMAKE_RPATHDIR @@ -2130,7 +2130,7 @@ exclude the \c gui value with the "-=" operator. The following line will result in a minimal Qt project being built: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 47 + \snippet snippets/code/doc_src_qmake-manual.pro 47 \section1 QTPLUGIN @@ -2176,7 +2176,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 48 + \snippet snippets/code/doc_src_qmake-manual.pro 48 \target REQUIRES \section1 REQUIRES @@ -2218,7 +2218,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 49 + \snippet snippets/code/doc_src_qmake-manual.pro 49 See also \l{#HEADERS}{HEADERS}. @@ -2232,7 +2232,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 50 + \snippet snippets/code/doc_src_qmake-manual.pro 50 It is essential that the project file in each subdirectory has the same name as the subdirectory itself, so that qmake @@ -2243,7 +2243,7 @@ which they are specified, update the \l{#CONFIG}{CONFIG} variable to include the \c ordered option: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 51 + \snippet snippets/code/doc_src_qmake-manual.pro 51 It is possible to modify this default behavior of \c SUBDIRS by giving additional modifiers to \c SUBDIRS elements. Supported modifiers are: @@ -2265,7 +2265,7 @@ For example, define two subdirectories, both of which reside in a different directory than the \c SUBDIRS value, and one of the subdirectories must be built before the other: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 149 + \snippet snippets/code/doc_src_qmake-manual.pro 149 \target TARGET \section1 TARGET @@ -2275,7 +2275,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 52 + \snippet snippets/code/doc_src_qmake-manual.pro 52 The project file above would produce an executable named \c myapp on unix and \c{myapp.exe} on Windows. @@ -2323,7 +2323,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 53 + \snippet snippets/code/doc_src_qmake-manual.pro 53 The template can be overridden by specifying a new template type with the \c -t command line option. This overrides the template type \e after the .pro @@ -2347,7 +2347,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 54 + \snippet snippets/code/doc_src_qmake-manual.pro 54 \target VERSION \section1 VERSION @@ -2357,7 +2357,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 57 + \snippet snippets/code/doc_src_qmake-manual.pro 57 \section1 VER_MAJ @@ -2391,7 +2391,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 58 + \snippet snippets/code/doc_src_qmake-manual.pro 58 \section1 _PRO_FILE_ @@ -2400,7 +2400,7 @@ For example, the following line causes the location of the project file to be written to the console: - \snippet doc/src/snippets/qmake/project_location.pro project file + \snippet snippets/qmake/project_location.pro project file \note Do not attempt to overwrite the value of this variable. @@ -2411,7 +2411,7 @@ For example, the following line causes the location of the directory containing the project file to be written to the console: - \snippet doc/src/snippets/qmake/project_location.pro project file directory + \snippet snippets/qmake/project_location.pro project file directory \note Do not attempt to overwrite the value of this variable. */ @@ -2446,7 +2446,7 @@ For example, the following call returns the string \c {"/home/johndoe/myproject/readme.txt"}: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 159 + \snippet snippets/code/doc_src_qmake-manual.pro 159 See also \l{clean_path(path)}{clean_path()}, \l{relative_path(filePath[, base])}{relative_path()}. @@ -2457,7 +2457,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 59 + \snippet snippets/code/doc_src_qmake-manual.pro 59 \section2 cat(filename[, mode]) @@ -2489,7 +2489,7 @@ Returns the directory name part of the specified file. For example: - \snippet doc/src/snippets/qmake/dirname.pro 0 + \snippet snippets/qmake/dirname.pro 0 \section2 enumerate_vars @@ -2504,7 +2504,7 @@ \note If you specify the string to expand literally, you need to escape the backslashes, as illustrated by the following code snippet: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 173 + \snippet snippets/code/doc_src_qmake-manual.pro 173 \target findfunction \section2 find(variablename, substr) @@ -2512,7 +2512,7 @@ Returns all the values in \c variablename that match the regular expression \c substr. - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 64 + \snippet snippets/code/doc_src_qmake-manual.pro 64 MY_VAR2 will contain '-Lone -Ltwo -Lthree -Lfour -Lfive', and MY_VAR3 will contain 'three two three'. @@ -2523,7 +2523,7 @@ For example, the following call returns \c firstname: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 161 + \snippet snippets/code/doc_src_qmake-manual.pro 161 See also \l{last(variablename)}{last()}. @@ -2549,7 +2549,7 @@ For example, the following call converts the hexadecimal number \c BAD to \c 002989: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 163 + \snippet snippets/code/doc_src_qmake-manual.pro 163 \section2 fromfile(filename, variablename) @@ -2572,7 +2572,7 @@ For example, the following call returns \c phone: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 162 + \snippet snippets/code/doc_src_qmake-manual.pro 162 See also \l{first(variablename)}{first()}. @@ -2583,11 +2583,11 @@ of that variable. You can use the variable to write a loop as illustrated by the following code snippet - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 170 + \snippet snippets/code/doc_src_qmake-manual.pro 170 instead of: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 171 + \snippet snippets/code/doc_src_qmake-manual.pro 171 \section2 lower(arg1 [, arg2 ..., argn]) @@ -2633,11 +2633,11 @@ contents of the variable supplied as \c string. For example, the code - \snippet doc/src/snippets/qmake/replace.pro 0 + \snippet snippets/qmake/replace.pro 0 prints the message: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 70 + \snippet snippets/code/doc_src_qmake-manual.pro 70 \section2 sprintf(string, arguments...) @@ -2659,7 +2659,7 @@ For example, the following call outputs \c surname: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 167 + \snippet snippets/code/doc_src_qmake-manual.pro 167 \section2 shadowed(path) @@ -2697,7 +2697,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 168 + \snippet snippets/code/doc_src_qmake-manual.pro 168 \section2 system(command[, mode]) @@ -2706,7 +2706,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 72 + \snippet snippets/code/doc_src_qmake-manual.pro 72 See also the test variant of \l{system(command)}{system()}. @@ -2732,7 +2732,7 @@ Returns the list of values in \c variablename with duplicate entries removed. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 73 + \snippet snippets/code/doc_src_qmake-manual.pro 73 \section2 upper(arg1 [, arg2 ..., argn]) @@ -2776,7 +2776,7 @@ mutually exclusive values) a second parameter can be used to specify a set of values to consider. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 60 + \snippet snippets/code/doc_src_qmake-manual.pro 60 Because release is considered the active setting (for feature parsing) it will be the CONFIG used to generate the build file. In the common @@ -2791,7 +2791,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 61 + \snippet snippets/code/doc_src_qmake-manual.pro 61 The contents of the scope are only processed if the \c drivers variable contains the value \c network. If this is the case, the @@ -2808,7 +2808,7 @@ only processed if the variable contains the correct number of values. For example: - \snippet doc/src/snippets/qmake/functions.pro 2 + \snippet snippets/qmake/functions.pro 2 \section2 debug(level, message) @@ -2833,7 +2833,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 160 + \snippet snippets/code/doc_src_qmake-manual.pro 160 \section2 error(string) @@ -2843,7 +2843,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 62 + \snippet snippets/code/doc_src_qmake-manual.pro 62 \section2 eval(string) @@ -2853,7 +2853,7 @@ values of existing variables or create new definitions. For example: - \snippet doc/src/snippets/qmake/functions.pro 4 + \snippet snippets/qmake/functions.pro 4 \note Quotation marks can be used to delimit the string, and the return value can be discarded if it is not needed. @@ -2866,7 +2866,7 @@ succeeds if any file matches the regular expression specified. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 63 + \snippet snippets/code/doc_src_qmake-manual.pro 63 \note "/" should be used as a directory separator, regardless of the platform in use. @@ -2890,7 +2890,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 65 + \snippet snippets/code/doc_src_qmake-manual.pro 65 \section2 greaterThan(variablename, value) @@ -2900,7 +2900,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 164 + \snippet snippets/code/doc_src_qmake-manual.pro 164 It is impossible to compare two numbers as strings directly. As a workaround, construct temporary values with a non-numeric prefix and compare @@ -2908,7 +2908,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 172 + \snippet snippets/code/doc_src_qmake-manual.pro 172 See also \l{lessThan(variablename, value)}{lessThan()}. @@ -2918,7 +2918,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 166 + \snippet snippets/code/doc_src_qmake-manual.pro 166 \section2 include(filename) @@ -2930,7 +2930,7 @@ You can check whether the file was included by using this function as the condition for a scope. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 66 + \snippet snippets/code/doc_src_qmake-manual.pro 66 \section2 infile(filename, var, val) @@ -2950,7 +2950,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 67 + \snippet snippets/code/doc_src_qmake-manual.pro 67 \section2 isEqual @@ -2963,7 +2963,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 165 + \snippet snippets/code/doc_src_qmake-manual.pro 165 \section2 load(feature) @@ -2982,7 +2982,7 @@ Always succeeds, and displays \c string as a general message to the user. Unlike the \c error() function, this function allows processing to continue. - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 68 + \snippet snippets/code/doc_src_qmake-manual.pro 68 The above line causes "This is a message" to be written to the console. The use of quotation marks is optional, but recommended. @@ -2993,7 +2993,7 @@ \l{Scopes}{in conjunction with a scope} to filter out messages during builds. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 69 + \snippet snippets/code/doc_src_qmake-manual.pro 69 \section2 mkpath(dirPath) @@ -3016,7 +3016,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 71 + \snippet snippets/code/doc_src_qmake-manual.pro 71 See also the replace variant of \l{system(command[, mode])}{system()}. @@ -3032,7 +3032,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 169 + \snippet snippets/code/doc_src_qmake-manual.pro 169 \section2 warning(string) @@ -3056,11 +3056,11 @@ This can be useful to optionally enable or disable features. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 157 + \snippet snippets/code/doc_src_qmake-manual.pro 157 And then, in the code: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 158 + \snippet snippets/code/doc_src_qmake-manual.pro 158 */ /*! @@ -3077,14 +3077,14 @@ property in qmake once, and query it each time qmake is invoked. You can set a property in qmake as follows: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 74 + \snippet snippets/code/doc_src_qmake-manual.pro 74 The appropriate property and value should be substituted for \c PROPERTY and \c VALUE. You can retrieve this information back from qmake as follows: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 75 + \snippet snippets/code/doc_src_qmake-manual.pro 75 \note \c{qmake -query} lists built-in properties in addition to the properties that you set with \c{qmake -set PROPERTY VALUE}. @@ -3130,11 +3130,11 @@ For example, you can query the installation of Qt for this version of qmake with the \c QT_INSTALL_PREFIX property: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 77 + \snippet snippets/code/doc_src_qmake-manual.pro 77 You can query the values of properties in a project file as follows: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 78 + \snippet snippets/code/doc_src_qmake-manual.pro 78 \target QMAKESPEC \section1 QMAKESPEC @@ -3184,7 +3184,7 @@ example, the extension used for \l moc files can be redefined with the following assignment in a project file: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 85 + \snippet snippets/code/doc_src_qmake-manual.pro 85 The following variables can be used to redefine common file extensions recognized by qmake: @@ -3244,7 +3244,7 @@ The \c = operator assigns a value to a variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 89 + \snippet snippets/code/doc_src_qmake-manual.pro 89 The above line sets the \l{TARGET} variable to \c myapp. This will overwrite any values previously set for \c TARGET with \c myapp. @@ -3253,7 +3253,7 @@ The \c += operator appends a new value to the list of values in a variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 90 + \snippet snippets/code/doc_src_qmake-manual.pro 90 The above line appends \c USE_MY_STUFF to the list of pre-processor defines to be put in the generated Makefile. @@ -3262,7 +3262,7 @@ The \c -= operator removes a value from the list of values in a variable: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 91 + \snippet snippets/code/doc_src_qmake-manual.pro 91 The above line removes \c USE_MY_STUFF from the list of pre-processor defines to be put in the generated Makefile. @@ -3273,7 +3273,7 @@ if it is not already present. This prevents values from being included many times in a variable. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 92 + \snippet snippets/code/doc_src_qmake-manual.pro 92 In the above line, \c USE_MY_STUFF will only be added to the list of pre-processor defines if it is not already defined. Note that the \l{unique}{unique()} @@ -3285,7 +3285,7 @@ The \c ~= operator replaces any values that match a regular expression with the specified value: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 93 + \snippet snippets/code/doc_src_qmake-manual.pro 93 In the above line, any values in the list that start with \c QT_D or \c QT_T are replaced with \c QT. @@ -3295,7 +3295,7 @@ The \c $$ operator is used to extract the contents of a variable, and can be used to pass values between variables or supply them to functions: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 94 + \snippet snippets/code/doc_src_qmake-manual.pro 94 Variables can be used to store the contents of environment variables. These can be evaluated at the time when qmake @@ -3347,7 +3347,7 @@ Scopes consist of a condition followed by an opening brace on the same line, a sequence of commands and definitions, and a closing brace on a new line: - \snippet doc/src/snippets/qmake/scopes.pro syntax + \snippet snippets/qmake/scopes.pro syntax The opening brace \e{must be written on the same line as the condition}. Scopes may be concatenated to include more than one condition, as described @@ -3358,7 +3358,7 @@ A scope is written as a condition followed by a series of declarations contained within a pair of braces. For example: - \snippet doc/src/snippets/qmake/scopes.pro 0 + \snippet snippets/qmake/scopes.pro 0 The above code will add the \c paintwidget_win.cpp file to the sources listed in the generated Makefile when building for a Windows platform. When @@ -3369,24 +3369,24 @@ original condition is false. For example, to process something when building for all platforms \e except Windows, negate the scope like this: - \snippet doc/src/snippets/qmake/scopes.pro 1 + \snippet snippets/qmake/scopes.pro 1 Scopes can be nested to combine more than one condition. For instance, to include a particular file for a certain platform only if debugging is enabled, write the following: - \snippet doc/src/snippets/qmake/scopes.pro 2 + \snippet snippets/qmake/scopes.pro 2 To save writing many nested scopes, you can nest scopes using the \c : operator. The nested scopes in the above example can be rewritten in the following way: - \snippet doc/src/snippets/qmake/scopes.pro 3 + \snippet snippets/qmake/scopes.pro 3 You may also use the \c : operator to perform single line conditional assignments. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 95 + \snippet snippets/code/doc_src_qmake-manual.pro 95 The above line adds \c USE_MY_STUFF to the \l{DEFINES} variable only when building for the Windows platform. @@ -3396,7 +3396,7 @@ There is also the \c | operator to act like a logical OR operator, joining together a number of conditions, and requiring only one of them to be true. - \snippet doc/src/snippets/qmake/scopes.pro 4 + \snippet snippets/qmake/scopes.pro 4 You can also provide alternative declarations to those within a scope by using an \c else scope. Each \c else scope is processed if the conditions @@ -3404,7 +3404,7 @@ This allows you to write complex tests when combined with other scopes (separated by the \c : operator as above). For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 96 + \snippet snippets/code/doc_src_qmake-manual.pro 96 \section2 Configuration and Scopes @@ -3413,15 +3413,15 @@ values can be used as the condition for a scope. For example, the list of values held by \c CONFIG can be extended with the \c opengl value: - \snippet doc/src/snippets/qmake/configscopes.pro 0 + \snippet snippets/qmake/configscopes.pro 0 As a result of this operation, any scopes that test for \c opengl will be processed. We can use this feature to give the final executable an appropriate name: - \snippet doc/src/snippets/qmake/configscopes.pro 1 - \snippet doc/src/snippets/qmake/configscopes.pro 2 - \snippet doc/src/snippets/qmake/configscopes.pro 3 + \snippet snippets/qmake/configscopes.pro 1 + \snippet snippets/qmake/configscopes.pro 2 + \snippet snippets/qmake/configscopes.pro 3 This feature makes it easy to change the configuration for a project without losing all the custom settings that might be needed for a specific @@ -3444,7 +3444,7 @@ following lines from a project file show the current specification in use and test for the \c linux-g++ specification: - \snippet doc/src/snippets/qmake/specifications.pro 0 + \snippet snippets/qmake/specifications.pro 0 You can test for any other platform-compiler combination as long as a specification exists for it in the \c mkspecs directory. @@ -3459,7 +3459,7 @@ variables with a given name when it encounters an assignment to that name. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 97 + \snippet snippets/code/doc_src_qmake-manual.pro 97 There are no restricitions on what you do to your own variables, as qmake will ignore them unless it needs to evaluate them when processing @@ -3468,19 +3468,19 @@ You can also assign the value of a current variable to another variable by prefixing $$ to the variable name. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 98 + \snippet snippets/code/doc_src_qmake-manual.pro 98 Now the MY_DEFINES variable contains what is in the DEFINES variable at this point in the project file. This is also equivalent to: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 99 + \snippet snippets/code/doc_src_qmake-manual.pro 99 The second notation allows you to append the contents of the variable to another value without separating the two with a space. For example, the following will ensure that the final executable will be given a name that includes the project template being used: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 100 + \snippet snippets/code/doc_src_qmake-manual.pro 100 \target UsingReplaceFunctions \section1 Replace Functions @@ -3492,7 +3492,7 @@ operator with this type of function as you would to assign contents of one variable to another: - \snippet doc/src/snippets/qmake/functions.pro 1 + \snippet snippets/qmake/functions.pro 1 This type of function should be used on the right-hand side of assignments (that is, as an operand). @@ -3500,13 +3500,13 @@ You can define your own functions for processing the contents of variables as follows: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 102 + \snippet snippets/code/doc_src_qmake-manual.pro 102 The following example function takes a variable name as its only argument, extracts a list of values from the variable with the \l{eval(string)}{eval()} built-in function, and compiles a list of files: - \snippet doc/src/snippets/qmake/replacefunction.pro 0 + \snippet snippets/qmake/replacefunction.pro 0 \target UsingTestFunctions \section1 Test Functions @@ -3515,7 +3515,7 @@ used as conditions when writing scopes. These functions do not return a value, but instead indicate \e success or \e failure: - \snippet doc/src/snippets/qmake/functions.pro 3 + \snippet snippets/qmake/functions.pro 3 This type of function should be used in conditional expressions only. @@ -3524,7 +3524,7 @@ for scopes. The following example tests whether each file in a list exists and returns true if they all exist, or false if not: - \snippet doc/src/snippets/qmake/testfunction.pro 0 + \snippet snippets/qmake/testfunction.pro 0 */ /*! @@ -3581,7 +3581,7 @@ For example, consider the following assignment in a project file: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 103 + \snippet snippets/code/doc_src_qmake-manual.pro 103 With this addition to the \c CONFIG variable, qmake will search the locations listed above for @@ -3903,7 +3903,7 @@ and \e static throughout your project. A typical precompiled header might look like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.cpp 104 + \snippet snippets/code/doc_src_qmake-manual.cpp 104 \note A precompiled header file needs to separate C includes from C++ includes, since the precompiled header file for C files may not @@ -3915,7 +3915,7 @@ To make your project use precompiled headers, you only need to define the \l{PRECOMPILED_HEADER} variable in your project file: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 105 + \snippet snippets/code/doc_src_qmake-manual.pro 105 qmake will handle the rest, to ensure the creation and use of the precompiled header file. You do not need to @@ -3928,7 +3928,7 @@ precompiled headers. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 106 + \snippet snippets/code/doc_src_qmake-manual.pro 106 \section1 Notes on Possible Issues @@ -3937,7 +3937,7 @@ declarations may cause two different object files with the same name to be generated: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 107 + \snippet snippets/code/doc_src_qmake-manual.pro 107 To avoid potential conflicts like these, give distinctive names to header files that will be precompiled. @@ -4105,17 +4105,17 @@ Just start a new line with \c {SOURCES +=} and put hello.cpp after it. You should have something like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 108 + \snippet snippets/code/doc_src_qmake-manual.pro 108 We repeat this for each source file in the project, until we end up with the following: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 109 + \snippet snippets/code/doc_src_qmake-manual.pro 109 If you prefer to use a Make-like syntax, with all the files listed in one go you can use the newline escaping like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 110 + \snippet snippets/code/doc_src_qmake-manual.pro 110 Now that the source files are listed in the project file, the header files must be added. These are added in exactly the same way as source @@ -4124,7 +4124,7 @@ Once you have done this, your project file should look something like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 111 + \snippet snippets/code/doc_src_qmake-manual.pro 111 The target name is set automatically. It is the same as the project filename, but with the suffix appropriate for the platform. For example, if @@ -4132,24 +4132,24 @@ on Windows and \c hello on Unix. If you want to use a different name you can set it in the project file: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 112 + \snippet snippets/code/doc_src_qmake-manual.pro 112 The finished project file should look like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 113 + \snippet snippets/code/doc_src_qmake-manual.pro 113 You can now use qmake to generate a Makefile for your application. On the command line, in your project directory, type the following: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 114 + \snippet snippets/code/doc_src_qmake-manual.pro 114 Then type \c make or \c nmake depending on the compiler you use. For Visual Studio users, qmake can also generate Visual Studio project files. For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 115 + \snippet snippets/code/doc_src_qmake-manual.pro 115 \section1 Making an Application Debuggable @@ -4161,7 +4161,7 @@ For example: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 116 + \snippet snippets/code/doc_src_qmake-manual.pro 116 Use qmake as before to generate a Makefile. You will now obtain useful information about your application when running it in a debugging @@ -4181,7 +4181,7 @@ A simple scope that adds the platform-dependent file for Windows looks like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 117 + \snippet snippets/code/doc_src_qmake-manual.pro 117 When building for Windows, qmake adds \c hellowin.cpp to the list of source files. When building for any other platform, qmake simply ignores it. Now @@ -4190,7 +4190,7 @@ When you have done that, your project file should look something like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 118 + \snippet snippets/code/doc_src_qmake-manual.pro 118 Use qmake as before to generate a Makefile. @@ -4203,13 +4203,13 @@ the scope condition with the function. A check for a file called main.cpp looks like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 119 + \snippet snippets/code/doc_src_qmake-manual.pro 119 The \c{!} symbol is used to negate the test. That is, \c{exists( main.cpp )} is true if the file exists, and \c{!exists( main.cpp )} is true if the file does not exist. - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 120 + \snippet snippets/code/doc_src_qmake-manual.pro 120 Use qmake as before to generate a makefile. If you rename \c main.cpp temporarily, you will see the message and @@ -4228,12 +4228,12 @@ the other inside it. Put the settings to be processed inside the second scope, like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 121 + \snippet snippets/code/doc_src_qmake-manual.pro 121 Nested scopes can be joined together using colons, so the final project file looks like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 122 + \snippet snippets/code/doc_src_qmake-manual.pro 122 That's it! You have now completed the tutorial for qmake, and are ready to write project files for @@ -4306,7 +4306,7 @@ to specify any. qmake will add the necessary default values. An example project file might look like this: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 123 + \snippet snippets/code/doc_src_qmake-manual.pro 123 For items that are single valued, such as the template or the destination directory, we use "="; but for multi-valued items we use "+=" to \e @@ -4444,8 +4444,8 @@ To enable a project to be built in both modes, you must add the \c debug_and_release option to the \c CONFIG variable: - \snippet doc/src/snippets/qmake/debug_and_release.pro 0 - \snippet doc/src/snippets/qmake/debug_and_release.pro 1 + \snippet snippets/qmake/debug_and_release.pro 0 + \snippet snippets/qmake/debug_and_release.pro 1 The scope in the above snippet modifies the build target in each mode to ensure that the resulting targets have different names. Providing different @@ -4455,23 +4455,23 @@ generate a Makefile rule to allow the project to be built in both modes. This can be invoked in the following way: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 124 + \snippet snippets/code/doc_src_qmake-manual.pro 124 The \c build_all option can be added to the \c CONFIG variable in the project file to ensure that the project is built in both modes by default: - \snippet doc/src/snippets/qmake/debug_and_release.pro 2 + \snippet snippets/qmake/debug_and_release.pro 2 This allows the Makefile to be processed using the default rule: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 125 + \snippet snippets/code/doc_src_qmake-manual.pro 125 \section2 Installing in Both Modes The \c build_all option also ensures that both versions of the target will be installed when the installation rule is invoked: - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 126 + \snippet snippets/code/doc_src_qmake-manual.pro 126 It is possible to customize the names of the build targets depending on the target platform. For example, a library or plugin may be named using a @@ -4481,7 +4481,7 @@ Note: This was originally used in the customwidgetplugin.pro file, but is no longer needed there. \endomit - \snippet doc/src/snippets/code/doc_src_qmake-manual.pro 127 + \snippet snippets/code/doc_src_qmake-manual.pro 127 The default behavior in the above snippet is to modify the name used for the build target when building in debug mode. An \c else clause could be |