summaryrefslogtreecommitdiffstats
path: root/qmake/doc
diff options
context:
space:
mode:
authorJerome Pasion <jerome.pasion@digia.com>2013-08-09 13:58:52 +0200
committerThe Qt Project <gerrit-noreply@qt-project.org>2013-08-13 01:38:54 +0200
commit4bea83fe71fdbd9e9054929a982c999976548ca9 (patch)
tree4c222f10e300885ae0a146bd07efd9e068692e54 /qmake/doc
parent4b0dfef236c48dd6f2d629a57cf4d746c9942aeb (diff)
Doc: Fixed qmake manual's images and snippets directories.
-corrected qmake.qdocconf file to not read the manual twice -moved the snippets and images directories to make sure they are not in the src directory Task-number: QTBUG-32580 Change-Id: I7b702ce3b1c8709bbb1f473f70625083242f1a40 Reviewed-by: Martin Smith <martin.smith@digia.com> Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Diffstat (limited to 'qmake/doc')
-rw-r--r--qmake/doc/images/qmake-precompile-ui.png (renamed from qmake/doc/src/images/qmake-precompile-ui.png)bin89070 -> 89070 bytes
-rw-r--r--qmake/doc/qmake.qdocconf4
-rw-r--r--qmake/doc/snippets/code/doc_src_qmake-manual.cpp (renamed from qmake/doc/src/snippets/code/doc_src_qmake-manual.cpp)0
-rw-r--r--qmake/doc/snippets/code/doc_src_qmake-manual.pro (renamed from qmake/doc/src/snippets/code/doc_src_qmake-manual.pro)0
-rw-r--r--qmake/doc/snippets/qmake/comments.pro (renamed from qmake/doc/src/snippets/qmake/comments.pro)0
-rw-r--r--qmake/doc/snippets/qmake/configscopes.pro (renamed from qmake/doc/src/snippets/qmake/configscopes.pro)0
-rw-r--r--qmake/doc/snippets/qmake/debug_and_release.pro (renamed from qmake/doc/src/snippets/qmake/debug_and_release.pro)0
-rw-r--r--qmake/doc/snippets/qmake/delegate.h (renamed from qmake/doc/src/snippets/qmake/delegate.h)0
-rw-r--r--qmake/doc/snippets/qmake/dereferencing.pro (renamed from qmake/doc/src/snippets/qmake/dereferencing.pro)0
-rw-r--r--qmake/doc/snippets/qmake/destdir.pro (renamed from qmake/doc/src/snippets/qmake/destdir.pro)0
-rw-r--r--qmake/doc/snippets/qmake/dirname.pro (renamed from qmake/doc/src/snippets/qmake/dirname.pro)0
-rw-r--r--qmake/doc/snippets/qmake/environment.pro (renamed from qmake/doc/src/snippets/qmake/environment.pro)0
-rw-r--r--qmake/doc/snippets/qmake/functions.pro (renamed from qmake/doc/src/snippets/qmake/functions.pro)0
-rw-r--r--qmake/doc/snippets/qmake/include.pro (renamed from qmake/doc/src/snippets/qmake/include.pro)0
-rw-r--r--qmake/doc/snippets/qmake/main.cpp (renamed from qmake/doc/src/snippets/qmake/main.cpp)0
-rw-r--r--qmake/doc/snippets/qmake/model.cpp (renamed from qmake/doc/src/snippets/qmake/model.cpp)0
-rw-r--r--qmake/doc/snippets/qmake/model.h (renamed from qmake/doc/src/snippets/qmake/model.h)0
-rw-r--r--qmake/doc/snippets/qmake/other.pro (renamed from qmake/doc/src/snippets/qmake/other.pro)0
-rw-r--r--qmake/doc/snippets/qmake/paintwidget_mac.cpp (renamed from qmake/doc/src/snippets/qmake/paintwidget_mac.cpp)0
-rw-r--r--qmake/doc/snippets/qmake/paintwidget_unix.cpp (renamed from qmake/doc/src/snippets/qmake/paintwidget_unix.cpp)0
-rw-r--r--qmake/doc/snippets/qmake/paintwidget_win.cpp (renamed from qmake/doc/src/snippets/qmake/paintwidget_win.cpp)0
-rw-r--r--qmake/doc/snippets/qmake/precompile-stable.h (renamed from qmake/doc/src/snippets/qmake/precompile-stable.h)0
-rw-r--r--qmake/doc/snippets/qmake/project_location.pro (renamed from qmake/doc/src/snippets/qmake/project_location.pro)0
-rw-r--r--qmake/doc/snippets/qmake/qtconfiguration.pro (renamed from qmake/doc/src/snippets/qmake/qtconfiguration.pro)0
-rw-r--r--qmake/doc/snippets/qmake/quoting.pro (renamed from qmake/doc/src/snippets/qmake/quoting.pro)0
-rw-r--r--qmake/doc/snippets/qmake/replace.pro (renamed from qmake/doc/src/snippets/qmake/replace.pro)0
-rw-r--r--qmake/doc/snippets/qmake/replacefunction.pro (renamed from qmake/doc/src/snippets/qmake/replacefunction.pro)0
-rw-r--r--qmake/doc/snippets/qmake/scopes.pro (renamed from qmake/doc/src/snippets/qmake/scopes.pro)0
-rw-r--r--qmake/doc/snippets/qmake/shared_or_static.pro (renamed from qmake/doc/src/snippets/qmake/shared_or_static.pro)0
-rw-r--r--qmake/doc/snippets/qmake/spaces.pro (renamed from qmake/doc/src/snippets/qmake/spaces.pro)0
-rw-r--r--qmake/doc/snippets/qmake/specifications.pro (renamed from qmake/doc/src/snippets/qmake/specifications.pro)0
-rw-r--r--qmake/doc/snippets/qmake/testfunction.pro (renamed from qmake/doc/src/snippets/qmake/testfunction.pro)0
-rw-r--r--qmake/doc/snippets/qmake/variables.pro (renamed from qmake/doc/src/snippets/qmake/variables.pro)0
-rw-r--r--qmake/doc/snippets/qmake/view.h (renamed from qmake/doc/src/snippets/qmake/view.h)0
-rw-r--r--qmake/doc/src/qmake-manual.qdoc363
35 files changed, 183 insertions, 184 deletions
diff --git a/qmake/doc/src/images/qmake-precompile-ui.png b/qmake/doc/images/qmake-precompile-ui.png
index 8c7b936fee..8c7b936fee 100644
--- a/qmake/doc/src/images/qmake-precompile-ui.png
+++ b/qmake/doc/images/qmake-precompile-ui.png
Binary files differ
diff --git a/qmake/doc/qmake.qdocconf b/qmake/doc/qmake.qdocconf
index 31b4e30510..ea82e45523 100644
--- a/qmake/doc/qmake.qdocconf
+++ b/qmake/doc/qmake.qdocconf
@@ -22,8 +22,8 @@ language = Cpp
sources = src/qmake-manual.qdoc
-imagedirs = src/images
-exampledirs = src
+imagedirs = images
+exampledirs = snippets
depends += \
qtwinextras
diff --git a/qmake/doc/src/snippets/code/doc_src_qmake-manual.cpp b/qmake/doc/snippets/code/doc_src_qmake-manual.cpp
index bd63e600cd..bd63e600cd 100644
--- a/qmake/doc/src/snippets/code/doc_src_qmake-manual.cpp
+++ b/qmake/doc/snippets/code/doc_src_qmake-manual.cpp
diff --git a/qmake/doc/src/snippets/code/doc_src_qmake-manual.pro b/qmake/doc/snippets/code/doc_src_qmake-manual.pro
index 0ee4785887..0ee4785887 100644
--- a/qmake/doc/src/snippets/code/doc_src_qmake-manual.pro
+++ b/qmake/doc/snippets/code/doc_src_qmake-manual.pro
diff --git a/qmake/doc/src/snippets/qmake/comments.pro b/qmake/doc/snippets/qmake/comments.pro
index 957052c81d..957052c81d 100644
--- a/qmake/doc/src/snippets/qmake/comments.pro
+++ b/qmake/doc/snippets/qmake/comments.pro
diff --git a/qmake/doc/src/snippets/qmake/configscopes.pro b/qmake/doc/snippets/qmake/configscopes.pro
index 6ab7f7c428..6ab7f7c428 100644
--- a/qmake/doc/src/snippets/qmake/configscopes.pro
+++ b/qmake/doc/snippets/qmake/configscopes.pro
diff --git a/qmake/doc/src/snippets/qmake/debug_and_release.pro b/qmake/doc/snippets/qmake/debug_and_release.pro
index 92e8dbf76a..92e8dbf76a 100644
--- a/qmake/doc/src/snippets/qmake/debug_and_release.pro
+++ b/qmake/doc/snippets/qmake/debug_and_release.pro
diff --git a/qmake/doc/src/snippets/qmake/delegate.h b/qmake/doc/snippets/qmake/delegate.h
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/delegate.h
+++ b/qmake/doc/snippets/qmake/delegate.h
diff --git a/qmake/doc/src/snippets/qmake/dereferencing.pro b/qmake/doc/snippets/qmake/dereferencing.pro
index ff0c97995c..ff0c97995c 100644
--- a/qmake/doc/src/snippets/qmake/dereferencing.pro
+++ b/qmake/doc/snippets/qmake/dereferencing.pro
diff --git a/qmake/doc/src/snippets/qmake/destdir.pro b/qmake/doc/snippets/qmake/destdir.pro
index b2f943904a..b2f943904a 100644
--- a/qmake/doc/src/snippets/qmake/destdir.pro
+++ b/qmake/doc/snippets/qmake/destdir.pro
diff --git a/qmake/doc/src/snippets/qmake/dirname.pro b/qmake/doc/snippets/qmake/dirname.pro
index 59e1f20b3f..59e1f20b3f 100644
--- a/qmake/doc/src/snippets/qmake/dirname.pro
+++ b/qmake/doc/snippets/qmake/dirname.pro
diff --git a/qmake/doc/src/snippets/qmake/environment.pro b/qmake/doc/snippets/qmake/environment.pro
index 808bdeba47..808bdeba47 100644
--- a/qmake/doc/src/snippets/qmake/environment.pro
+++ b/qmake/doc/snippets/qmake/environment.pro
diff --git a/qmake/doc/src/snippets/qmake/functions.pro b/qmake/doc/snippets/qmake/functions.pro
index 2766120719..2766120719 100644
--- a/qmake/doc/src/snippets/qmake/functions.pro
+++ b/qmake/doc/snippets/qmake/functions.pro
diff --git a/qmake/doc/src/snippets/qmake/include.pro b/qmake/doc/snippets/qmake/include.pro
index 37e7156957..37e7156957 100644
--- a/qmake/doc/src/snippets/qmake/include.pro
+++ b/qmake/doc/snippets/qmake/include.pro
diff --git a/qmake/doc/src/snippets/qmake/main.cpp b/qmake/doc/snippets/qmake/main.cpp
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/main.cpp
+++ b/qmake/doc/snippets/qmake/main.cpp
diff --git a/qmake/doc/src/snippets/qmake/model.cpp b/qmake/doc/snippets/qmake/model.cpp
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/model.cpp
+++ b/qmake/doc/snippets/qmake/model.cpp
diff --git a/qmake/doc/src/snippets/qmake/model.h b/qmake/doc/snippets/qmake/model.h
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/model.h
+++ b/qmake/doc/snippets/qmake/model.h
diff --git a/qmake/doc/src/snippets/qmake/other.pro b/qmake/doc/snippets/qmake/other.pro
index e69de29bb2..e69de29bb2 100644
--- a/qmake/doc/src/snippets/qmake/other.pro
+++ b/qmake/doc/snippets/qmake/other.pro
diff --git a/qmake/doc/src/snippets/qmake/paintwidget_mac.cpp b/qmake/doc/snippets/qmake/paintwidget_mac.cpp
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/paintwidget_mac.cpp
+++ b/qmake/doc/snippets/qmake/paintwidget_mac.cpp
diff --git a/qmake/doc/src/snippets/qmake/paintwidget_unix.cpp b/qmake/doc/snippets/qmake/paintwidget_unix.cpp
index c39fc2cbf6..c39fc2cbf6 100644
--- a/qmake/doc/src/snippets/qmake/paintwidget_unix.cpp
+++ b/qmake/doc/snippets/qmake/paintwidget_unix.cpp
diff --git a/qmake/doc/src/snippets/qmake/paintwidget_win.cpp b/qmake/doc/snippets/qmake/paintwidget_win.cpp
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/paintwidget_win.cpp
+++ b/qmake/doc/snippets/qmake/paintwidget_win.cpp
diff --git a/qmake/doc/src/snippets/qmake/precompile-stable.h b/qmake/doc/snippets/qmake/precompile-stable.h
index eef8cef728..eef8cef728 100644
--- a/qmake/doc/src/snippets/qmake/precompile-stable.h
+++ b/qmake/doc/snippets/qmake/precompile-stable.h
diff --git a/qmake/doc/src/snippets/qmake/project_location.pro b/qmake/doc/snippets/qmake/project_location.pro
index 09d9b3d9d0..09d9b3d9d0 100644
--- a/qmake/doc/src/snippets/qmake/project_location.pro
+++ b/qmake/doc/snippets/qmake/project_location.pro
diff --git a/qmake/doc/src/snippets/qmake/qtconfiguration.pro b/qmake/doc/snippets/qmake/qtconfiguration.pro
index 55e13be352..55e13be352 100644
--- a/qmake/doc/src/snippets/qmake/qtconfiguration.pro
+++ b/qmake/doc/snippets/qmake/qtconfiguration.pro
diff --git a/qmake/doc/src/snippets/qmake/quoting.pro b/qmake/doc/snippets/qmake/quoting.pro
index 62efb2042e..62efb2042e 100644
--- a/qmake/doc/src/snippets/qmake/quoting.pro
+++ b/qmake/doc/snippets/qmake/quoting.pro
diff --git a/qmake/doc/src/snippets/qmake/replace.pro b/qmake/doc/snippets/qmake/replace.pro
index 504e01a018..504e01a018 100644
--- a/qmake/doc/src/snippets/qmake/replace.pro
+++ b/qmake/doc/snippets/qmake/replace.pro
diff --git a/qmake/doc/src/snippets/qmake/replacefunction.pro b/qmake/doc/snippets/qmake/replacefunction.pro
index 98013ba42d..98013ba42d 100644
--- a/qmake/doc/src/snippets/qmake/replacefunction.pro
+++ b/qmake/doc/snippets/qmake/replacefunction.pro
diff --git a/qmake/doc/src/snippets/qmake/scopes.pro b/qmake/doc/snippets/qmake/scopes.pro
index 63b9b3aa55..63b9b3aa55 100644
--- a/qmake/doc/src/snippets/qmake/scopes.pro
+++ b/qmake/doc/snippets/qmake/scopes.pro
diff --git a/qmake/doc/src/snippets/qmake/shared_or_static.pro b/qmake/doc/snippets/qmake/shared_or_static.pro
index 31c25ea44b..31c25ea44b 100644
--- a/qmake/doc/src/snippets/qmake/shared_or_static.pro
+++ b/qmake/doc/snippets/qmake/shared_or_static.pro
diff --git a/qmake/doc/src/snippets/qmake/spaces.pro b/qmake/doc/snippets/qmake/spaces.pro
index 614d4c553d..614d4c553d 100644
--- a/qmake/doc/src/snippets/qmake/spaces.pro
+++ b/qmake/doc/snippets/qmake/spaces.pro
diff --git a/qmake/doc/src/snippets/qmake/specifications.pro b/qmake/doc/snippets/qmake/specifications.pro
index f9a0d0a1cb..f9a0d0a1cb 100644
--- a/qmake/doc/src/snippets/qmake/specifications.pro
+++ b/qmake/doc/snippets/qmake/specifications.pro
diff --git a/qmake/doc/src/snippets/qmake/testfunction.pro b/qmake/doc/snippets/qmake/testfunction.pro
index 785ffed6be..785ffed6be 100644
--- a/qmake/doc/src/snippets/qmake/testfunction.pro
+++ b/qmake/doc/snippets/qmake/testfunction.pro
diff --git a/qmake/doc/src/snippets/qmake/variables.pro b/qmake/doc/snippets/qmake/variables.pro
index c1439ba68b..c1439ba68b 100644
--- a/qmake/doc/src/snippets/qmake/variables.pro
+++ b/qmake/doc/snippets/qmake/variables.pro
diff --git a/qmake/doc/src/snippets/qmake/view.h b/qmake/doc/snippets/qmake/view.h
index 92c7eb6a48..92c7eb6a48 100644
--- a/qmake/doc/src/snippets/qmake/view.h
+++ b/qmake/doc/snippets/qmake/view.h
diff --git a/qmake/doc/src/qmake-manual.qdoc b/qmake/doc/src/qmake-manual.qdoc
index 5f0ef59650..1f45e5021e 100644
--- a/qmake/doc/src/qmake-manual.qdoc
+++ b/qmake/doc/src/qmake-manual.qdoc
@@ -201,11 +201,11 @@
The following snippet illustrates how lists of values are assigned to
variables:
- \snippet snippets/qmake/variables.pro 0
+ \snippet qmake/variables.pro 0
The list of values in a variable is extended in the following way:
- \snippet snippets/qmake/variables.pro 1
+ \snippet 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 snippets/qmake/dereferencing.pro 0
+ \snippet 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 snippets/qmake/quoting.pro 0
+ \snippet 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 snippets/qmake/spaces.pro quoting include paths with spaces
+ \snippet 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 snippets/qmake/comments.pro 0
+ \snippet 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 snippets/qmake/include.pro 0
+ \snippet 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 snippets/qmake/scopes.pro 0
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 0
+ \snippet 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 snippets/qmake/configscopes.pro 4
- \snippet snippets/qmake/configscopes.pro 5
+ \snippet qmake/configscopes.pro 4
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 1
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 2
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 3
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 4
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 5
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 6
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 7
+ \snippet code/doc_src_qmake-manual.pro 7
*/
/*!
@@ -485,7 +485,7 @@
The syntax used to run qmake takes the following simple form:
- \snippet snippets/code/doc_src_qmake-manual.pro 8
+ \snippet code/doc_src_qmake-manual.pro 8
\section1 Operating Modes
@@ -572,7 +572,7 @@
\target MakefileMode
\section1 Makefile Mode Options
- \snippet snippets/code/doc_src_qmake-manual.pro 9
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 10
+ \snippet code/doc_src_qmake-manual.pro 10
However, some of the specified options can be omitted as they are default
values:
- \snippet snippets/code/doc_src_qmake-manual.pro 11
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 12
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 13
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 14
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 15
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 16
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 17
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 19
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 20
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 21
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 22
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 23
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 24
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 25
+ \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
@@ -1049,7 +1049,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 26
+ \snippet code/doc_src_qmake-manual.pro 26
\target DEFINES
\section1 DEFINES
@@ -1059,7 +1059,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 27
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 28
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 29
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 142
+ \snippet code/doc_src_qmake-manual.pro 142
\target DESTDIR
\section1 DESTDIR
@@ -1131,7 +1131,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 30
+ \snippet code/doc_src_qmake-manual.pro 30
\target DISTFILES
\section1 DISTFILES
@@ -1141,7 +1141,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 31
+ \snippet code/doc_src_qmake-manual.pro 31
\target DLLDESTDIR
\section1 DLLDESTDIR
@@ -1159,7 +1159,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 32
+ \snippet code/doc_src_qmake-manual.pro 32
\target GUID
\section1 GUID
@@ -1182,7 +1182,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 34
+ \snippet code/doc_src_qmake-manual.pro 34
See also \l{#SOURCES}{SOURCES}.
@@ -1201,12 +1201,12 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 35
+ \snippet code/doc_src_qmake-manual.pro 35
To specify a path containing spaces, quote the path using the technique
described in \l{Whitespace}.
- \snippet snippets/qmake/spaces.pro quoting include paths with spaces
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 36
+ \snippet code/doc_src_qmake-manual.pro 36
For more information, see \l{Installing Files}.
@@ -1247,7 +1247,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 37
+ \snippet code/doc_src_qmake-manual.pro 37
\target LIBS
\section1 LIBS
@@ -1260,18 +1260,18 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 38
+ \snippet code/doc_src_qmake-manual.pro 38
To specify a path containing spaces, quote the path using the technique
described in \l{Whitespace}.
- \snippet snippets/qmake/spaces.pro quoting library paths with spaces
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 39
+ \snippet code/doc_src_qmake-manual.pro 39
\target LITERAL_HASH
\section1 LITERAL_HASH
@@ -1282,7 +1282,7 @@
For example:
- \snippet snippets/qmake/comments.pro 1
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 40
+ \snippet code/doc_src_qmake-manual.pro 40
\target OBJECTS
\section1 OBJECTS
@@ -1327,7 +1327,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 41
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 43
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 44
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 45
+ \snippet code/doc_src_qmake-manual.pro 45
\section1 QMAKE_RPATHDIR
@@ -2131,7 +2131,7 @@
exclude the \c gui value with the "-=" operator. The following line will
result in a minimal Qt project being built:
- \snippet snippets/code/doc_src_qmake-manual.pro 47
+ \snippet code/doc_src_qmake-manual.pro 47
\section1 QTPLUGIN
@@ -2177,7 +2177,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 48
+ \snippet code/doc_src_qmake-manual.pro 48
\target REQUIRES
\section1 REQUIRES
@@ -2219,7 +2219,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 49
+ \snippet code/doc_src_qmake-manual.pro 49
See also \l{#HEADERS}{HEADERS}.
@@ -2233,7 +2233,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 50
+ \snippet 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
@@ -2244,7 +2244,7 @@
which they are specified, update the \l{#CONFIG}{CONFIG} variable to
include the \c ordered option:
- \snippet snippets/code/doc_src_qmake-manual.pro 51
+ \snippet 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:
@@ -2266,7 +2266,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 snippets/code/doc_src_qmake-manual.pro 149
+ \snippet code/doc_src_qmake-manual.pro 149
\target TARGET
\section1 TARGET
@@ -2276,7 +2276,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 52
+ \snippet 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.
@@ -2324,7 +2324,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 53
+ \snippet 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
@@ -2348,7 +2348,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 54
+ \snippet code/doc_src_qmake-manual.pro 54
\target VERSION
\section1 VERSION
@@ -2358,7 +2358,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 57
+ \snippet code/doc_src_qmake-manual.pro 57
\section1 VER_MAJ
@@ -2392,7 +2392,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 58
+ \snippet code/doc_src_qmake-manual.pro 58
\section1 _PRO_FILE_
@@ -2401,7 +2401,7 @@
For example, the following line causes the location of the project
file to be written to the console:
- \snippet snippets/qmake/project_location.pro project file
+ \snippet qmake/project_location.pro project file
\note Do not attempt to overwrite the value of this variable.
@@ -2412,7 +2412,7 @@
For example, the following line causes the location of the directory
containing the project file to be written to the console:
- \snippet snippets/qmake/project_location.pro project file directory
+ \snippet qmake/project_location.pro project file directory
\note Do not attempt to overwrite the value of this variable.
*/
@@ -2447,7 +2447,7 @@
For example, the following call returns the string
\c {"/home/johndoe/myproject/readme.txt"}:
- \snippet snippets/code/doc_src_qmake-manual.pro 159
+ \snippet code/doc_src_qmake-manual.pro 159
See also \l{clean_path(path)}{clean_path()},
\l{relative_path(filePath[, base])}{relative_path()}.
@@ -2458,7 +2458,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 59
+ \snippet code/doc_src_qmake-manual.pro 59
\section2 cat(filename[, mode])
@@ -2490,7 +2490,7 @@
Returns the directory name part of the specified file. For example:
- \snippet snippets/qmake/dirname.pro 0
+ \snippet qmake/dirname.pro 0
\section2 enumerate_vars
@@ -2505,7 +2505,7 @@
\note If you specify the string to expand literally, you need to escape the
backslashes, as illustrated by the following code snippet:
- \snippet snippets/code/doc_src_qmake-manual.pro 173
+ \snippet code/doc_src_qmake-manual.pro 173
\target findfunction
\section2 find(variablename, substr)
@@ -2513,7 +2513,7 @@
Returns all the values in \c variablename that match the regular expression
\c substr.
- \snippet snippets/code/doc_src_qmake-manual.pro 64
+ \snippet code/doc_src_qmake-manual.pro 64
MY_VAR2 will contain '-Lone -Ltwo -Lthree -Lfour -Lfive', and MY_VAR3 will
contain 'three two three'.
@@ -2524,7 +2524,7 @@
For example, the following call returns \c firstname:
- \snippet snippets/code/doc_src_qmake-manual.pro 161
+ \snippet code/doc_src_qmake-manual.pro 161
See also \l{last(variablename)}{last()}.
@@ -2550,7 +2550,7 @@
For example, the following call converts the hexadecimal number \c BAD to
\c 002989:
- \snippet snippets/code/doc_src_qmake-manual.pro 163
+ \snippet code/doc_src_qmake-manual.pro 163
\section2 fromfile(filename, variablename)
@@ -2573,7 +2573,7 @@
For example, the following call returns \c phone:
- \snippet snippets/code/doc_src_qmake-manual.pro 162
+ \snippet code/doc_src_qmake-manual.pro 162
See also \l{first(variablename)}{first()}.
@@ -2584,11 +2584,11 @@
of that variable. You can use the variable to write a loop as illustrated by
the following code snippet
- \snippet snippets/code/doc_src_qmake-manual.pro 170
+ \snippet code/doc_src_qmake-manual.pro 170
instead of:
- \snippet snippets/code/doc_src_qmake-manual.pro 171
+ \snippet code/doc_src_qmake-manual.pro 171
\section2 lower(arg1 [, arg2 ..., argn])
@@ -2634,11 +2634,11 @@
contents of the variable supplied as \c string. For example, the
code
- \snippet snippets/qmake/replace.pro 0
+ \snippet qmake/replace.pro 0
prints the message:
- \snippet snippets/code/doc_src_qmake-manual.pro 70
+ \snippet code/doc_src_qmake-manual.pro 70
\section2 sprintf(string, arguments...)
@@ -2660,7 +2660,7 @@
For example, the following call outputs \c surname:
- \snippet snippets/code/doc_src_qmake-manual.pro 167
+ \snippet code/doc_src_qmake-manual.pro 167
\section2 shadowed(path)
@@ -2698,7 +2698,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 168
+ \snippet code/doc_src_qmake-manual.pro 168
\section2 system(command[, mode])
@@ -2707,7 +2707,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 72
+ \snippet code/doc_src_qmake-manual.pro 72
See also the test variant of \l{system(command)}{system()}.
@@ -2733,7 +2733,7 @@
Returns the list of values in \c variablename with duplicate entries removed.
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 73
+ \snippet code/doc_src_qmake-manual.pro 73
\section2 upper(arg1 [, arg2 ..., argn])
@@ -2777,7 +2777,7 @@
mutually exclusive values) a second parameter can be used to specify a set
of values to consider. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 60
+ \snippet 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
@@ -2794,7 +2794,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 61
+ \snippet 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
@@ -2811,7 +2811,7 @@
only processed if the variable contains the correct number of values.
For example:
- \snippet snippets/qmake/functions.pro 2
+ \snippet qmake/functions.pro 2
\section2 debug(level, message)
@@ -2836,7 +2836,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 160
+ \snippet code/doc_src_qmake-manual.pro 160
\section2 error(string)
@@ -2846,7 +2846,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 62
+ \snippet code/doc_src_qmake-manual.pro 62
\section2 eval(string)
@@ -2856,7 +2856,7 @@
values of existing variables or create new definitions.
For example:
- \snippet snippets/qmake/functions.pro 4
+ \snippet 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.
@@ -2869,7 +2869,7 @@
succeeds if any file matches the regular expression specified.
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 63
+ \snippet code/doc_src_qmake-manual.pro 63
\note "/" should be used as a directory separator, regardless of the
platform in use.
@@ -2893,7 +2893,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 65
+ \snippet code/doc_src_qmake-manual.pro 65
\section2 greaterThan(variablename, value)
@@ -2903,7 +2903,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 164
+ \snippet 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
@@ -2911,7 +2911,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 172
+ \snippet code/doc_src_qmake-manual.pro 172
See also \l{lessThan(variablename, value)}{lessThan()}.
@@ -2921,7 +2921,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 166
+ \snippet code/doc_src_qmake-manual.pro 166
\section2 include(filename)
@@ -2933,7 +2933,7 @@
You can check whether the file was included by using this function as
the condition for a scope. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 66
+ \snippet code/doc_src_qmake-manual.pro 66
\section2 infile(filename, var, val)
@@ -2953,7 +2953,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 67
+ \snippet code/doc_src_qmake-manual.pro 67
\section2 isEqual
@@ -2966,7 +2966,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 165
+ \snippet code/doc_src_qmake-manual.pro 165
\section2 load(feature)
@@ -2985,7 +2985,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 snippets/code/doc_src_qmake-manual.pro 68
+ \snippet 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.
@@ -2996,7 +2996,7 @@
\l{Scopes}{in conjunction with a scope} to filter out
messages during builds. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 69
+ \snippet code/doc_src_qmake-manual.pro 69
\section2 mkpath(dirPath)
@@ -3019,7 +3019,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 71
+ \snippet code/doc_src_qmake-manual.pro 71
See also the replace variant of \l{system(command[, mode])}{system()}.
@@ -3035,7 +3035,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 169
+ \snippet code/doc_src_qmake-manual.pro 169
\section2 warning(string)
@@ -3059,11 +3059,11 @@
This can be useful to optionally enable or disable features. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 157
+ \snippet code/doc_src_qmake-manual.pro 157
And then, in the code:
- \snippet snippets/code/doc_src_qmake-manual.pro 158
+ \snippet code/doc_src_qmake-manual.pro 158
*/
/*!
@@ -3080,14 +3080,14 @@
property in qmake once, and query it each time qmake is invoked. You can set
a property in qmake as follows:
- \snippet snippets/code/doc_src_qmake-manual.pro 74
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 75
+ \snippet 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}.
@@ -3133,11 +3133,11 @@
For example, you can query the installation of Qt for this version of qmake with the
\c QT_INSTALL_PREFIX property:
- \snippet snippets/code/doc_src_qmake-manual.pro 77
+ \snippet code/doc_src_qmake-manual.pro 77
You can query the values of properties in a project file as follows:
- \snippet snippets/code/doc_src_qmake-manual.pro 78
+ \snippet code/doc_src_qmake-manual.pro 78
\target QMAKESPEC
\section1 QMAKESPEC
@@ -3187,7 +3187,7 @@
example, the extension used for \l moc files can be redefined with the
following assignment in a project file:
- \snippet snippets/code/doc_src_qmake-manual.pro 85
+ \snippet code/doc_src_qmake-manual.pro 85
The following variables can be used to redefine common file extensions recognized
by qmake:
@@ -3247,7 +3247,7 @@
The \c = operator assigns a value to a variable:
- \snippet snippets/code/doc_src_qmake-manual.pro 89
+ \snippet 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.
@@ -3256,7 +3256,7 @@
The \c += operator appends a new value to the list of values in a variable:
- \snippet snippets/code/doc_src_qmake-manual.pro 90
+ \snippet 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.
@@ -3265,7 +3265,7 @@
The \c -= operator removes a value from the list of values in a variable:
- \snippet snippets/code/doc_src_qmake-manual.pro 91
+ \snippet 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.
@@ -3276,7 +3276,7 @@
if it is not already present. This prevents values from being included many
times in a variable. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 92
+ \snippet 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()}
@@ -3288,7 +3288,7 @@
The \c ~= operator replaces any values that match a regular expression with
the specified value:
- \snippet snippets/code/doc_src_qmake-manual.pro 93
+ \snippet 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.
@@ -3298,7 +3298,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 snippets/code/doc_src_qmake-manual.pro 94
+ \snippet 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
@@ -3308,7 +3308,7 @@
To obtain the contents of an environment value when
qmake is run, use the \c $$(...) operator:
- \snippet snippets/qmake/environment.pro 0
+ \snippet qmake/environment.pro 0
In the above assignment, the value of the \c PWD environment variable
is read when the project file is processed.
@@ -3316,7 +3316,7 @@
To obtain the contents of an environment value at the time when the
generated Makefile is processed, use the \c $(...) operator:
- \snippet snippets/qmake/environment.pro 1
+ \snippet qmake/environment.pro 1
In the above assignment, the value of \c PWD is read immediately
when the project file is processed, but \c $(PWD) is assigned to
@@ -3328,7 +3328,7 @@
The special \c $$[...] operator can be used to access qmake properties:
- \snippet snippets/qmake/qtconfiguration.pro 0
+ \snippet qmake/qtconfiguration.pro 0
For more information, see \l{Configuring qmake}.
@@ -3337,7 +3337,7 @@
For example, a \QD plugin can be installed alongside \QD's built-in
plugins if the following declaration is made in its project file:
- \snippet snippets/code/doc_src_qmake-manual.pro 101
+ \snippet code/doc_src_qmake-manual.pro 101
\target Scopes
\section1 Scopes
@@ -3350,7 +3350,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 snippets/qmake/scopes.pro syntax
+ \snippet 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
@@ -3361,7 +3361,7 @@
A scope is written as a condition followed by a series of declarations
contained within a pair of braces. For example:
- \snippet snippets/qmake/scopes.pro 0
+ \snippet 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
@@ -3372,24 +3372,24 @@
original condition is false. For example, to process something when building
for all platforms \e except Windows, negate the scope like this:
- \snippet snippets/qmake/scopes.pro 1
+ \snippet 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 snippets/qmake/scopes.pro 2
+ \snippet 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 snippets/qmake/scopes.pro 3
+ \snippet qmake/scopes.pro 3
You may also use the \c : operator to perform single line conditional
assignments. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 95
+ \snippet 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.
@@ -3399,7 +3399,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 snippets/qmake/scopes.pro 4
+ \snippet 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
@@ -3407,7 +3407,7 @@
This allows you to write complex tests when combined with other scopes
(separated by the \c : operator as above). For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 96
+ \snippet code/doc_src_qmake-manual.pro 96
\section2 Configuration and Scopes
@@ -3416,15 +3416,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 snippets/qmake/configscopes.pro 0
+ \snippet 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 snippets/qmake/configscopes.pro 1
- \snippet snippets/qmake/configscopes.pro 2
- \snippet snippets/qmake/configscopes.pro 3
+ \snippet qmake/configscopes.pro 1
+ \snippet qmake/configscopes.pro 2
+ \snippet 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
@@ -3447,7 +3447,7 @@
following lines from a project file show the current specification in
use and test for the \c linux-g++ specification:
- \snippet snippets/qmake/specifications.pro 0
+ \snippet 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.
@@ -3462,7 +3462,7 @@
variables with a given name when it encounters an assignment to that name.
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 97
+ \snippet 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
@@ -3471,19 +3471,19 @@
You can also assign the value of a current variable to another
variable by prefixing $$ to the variable name. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 98
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 99
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 100
+ \snippet code/doc_src_qmake-manual.pro 100
\target UsingReplaceFunctions
\section1 Replace Functions
@@ -3495,7 +3495,7 @@
operator with this type of function as you would to assign contents of one
variable to another:
- \snippet snippets/qmake/functions.pro 1
+ \snippet qmake/functions.pro 1
This type of function should be used on the right-hand side of
assignments (that is, as an operand).
@@ -3503,13 +3503,13 @@
You can define your own functions for processing the contents of variables
as follows:
- \snippet snippets/code/doc_src_qmake-manual.pro 102
+ \snippet 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 snippets/qmake/replacefunction.pro 0
+ \snippet qmake/replacefunction.pro 0
\target UsingTestFunctions
\section1 Test Functions
@@ -3518,7 +3518,7 @@
used as conditions when writing scopes. These functions do not return a
value, but instead indicate \e success or \e failure:
- \snippet snippets/qmake/functions.pro 3
+ \snippet qmake/functions.pro 3
This type of function should be used in conditional expressions
only.
@@ -3527,7 +3527,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 snippets/qmake/testfunction.pro 0
+ \snippet qmake/testfunction.pro 0
*/
/*!
@@ -3584,7 +3584,7 @@
For example, consider the following assignment in a project file:
- \snippet snippets/code/doc_src_qmake-manual.pro 103
+ \snippet code/doc_src_qmake-manual.pro 103
With this addition to the \c CONFIG variable,
qmake will search the locations listed above for
@@ -3619,7 +3619,7 @@
be installed. For example, a collection of documentation files can be
described in the following way:
- \snippet snippets/code/doc_src_qmake-manual.pro 79
+ \snippet code/doc_src_qmake-manual.pro 79
The \c path member informs qmake that the files
should be installed in \c /usr/local/program/doc (the path member), and the
@@ -3630,7 +3630,7 @@
Once an install set has been fully described, you can append it to the
install list with a line like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 80
+ \snippet code/doc_src_qmake-manual.pro 80
qmake will ensure that the specified files are
copied to the installation directory. If you require more control over
@@ -3639,7 +3639,7 @@
qmake to execute a series of commands for this
install set:
- \snippet snippets/code/doc_src_qmake-manual.pro 81
+ \snippet code/doc_src_qmake-manual.pro 81
The \c unix \l{Scopes and Conditions}{scope}
ensures that these particular commands are only executed on Unix platforms.
@@ -3654,7 +3654,7 @@
will decide what needs to be copied for you. Currently, the \c target and \c dlltarget
install sets are supported. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 82
+ \snippet code/doc_src_qmake-manual.pro 82
In the above lines, qmake knows what needs to
be copied, and will handle the installation process automatically.
@@ -3670,7 +3670,7 @@
API as found in other places in qmake. Objects are defined automatically by
specifying their \e members. For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 86
+ \snippet code/doc_src_qmake-manual.pro 86
The definitions above define a qmake target called \c mytarget, containing a
Makefile target called \c{.buildfile} which in turn is generated with the
@@ -3682,7 +3682,7 @@
The final step is to use the \c QMAKE_EXTRA_TARGETS variable to instruct
qmake that this object is a target to be built:
- \snippet snippets/code/doc_src_qmake-manual.pro 87
+ \snippet code/doc_src_qmake-manual.pro 87
This is all you need to do to actually build custom targets. Of course,
you may want to tie one of these targets to the
@@ -3731,7 +3731,7 @@
It is possible to customize qmake to support new compilers and
preprocessors:
- \snippet snippets/code/doc_src_qmake-manual.pro 88
+ \snippet code/doc_src_qmake-manual.pro 88
With the above definitions, you can use a drop-in replacement for moc if one
is available. The command is executed on all arguments given to the
@@ -3833,7 +3833,7 @@
The first step is to enable dependency tracking in the library itself.
To do this you must tell qmake to save information about the library:
- \snippet snippets/code/doc_src_qmake-manual.pro 83
+ \snippet code/doc_src_qmake-manual.pro 83
This is only relevant to the \c lib template, and will be ignored for all
others. When this option is enabled, qmake will create a file ending in .prl
@@ -3846,7 +3846,7 @@
The second step in this process is to enable reading of this meta
information in the applications that use the static library:
- \snippet snippets/code/doc_src_qmake-manual.pro 84
+ \snippet code/doc_src_qmake-manual.pro 84
When this is enabled, qmake will process all
libraries linked to by the application and find their meta-information.
@@ -3906,7 +3906,7 @@
and \e static throughout your project. A typical precompiled header might
look like this:
- \snippet snippets/code/doc_src_qmake-manual.cpp 104
+ \snippet 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
@@ -3918,7 +3918,7 @@
To make your project use precompiled headers, you only need to define the
\l{PRECOMPILED_HEADER} variable in your project file:
- \snippet snippets/code/doc_src_qmake-manual.pro 105
+ \snippet 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
@@ -3931,7 +3931,7 @@
precompiled headers.
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 106
+ \snippet code/doc_src_qmake-manual.pro 106
\section1 Notes on Possible Issues
@@ -3940,7 +3940,7 @@
declarations may cause two different object files with the same name to
be generated:
- \snippet snippets/code/doc_src_qmake-manual.pro 107
+ \snippet code/doc_src_qmake-manual.pro 107
To avoid potential conflicts like these, give distinctive names to header
files that will be precompiled.
@@ -3960,7 +3960,7 @@
\section2 \c stable.h
- \snippet snippets/qmake/precompile-stable.h 0
+ \snippet qmake/precompile-stable.h 0
\omit
##Keeping the snippet in qtdoc is a workaround, because it contains code
@@ -4108,17 +4108,17 @@
Just start a new line with \c {SOURCES +=} and put hello.cpp after it.
You should have something like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 108
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 109
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 110
+ \snippet 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
@@ -4127,7 +4127,7 @@
Once you have done this, your project file should look something like
this:
- \snippet snippets/code/doc_src_qmake-manual.pro 111
+ \snippet 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
@@ -4135,24 +4135,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 snippets/code/doc_src_qmake-manual.pro 112
+ \snippet code/doc_src_qmake-manual.pro 112
The finished project file should look like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 113
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 114
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 115
+ \snippet code/doc_src_qmake-manual.pro 115
\section1 Making an Application Debuggable
@@ -4164,7 +4164,7 @@
For example:
- \snippet snippets/code/doc_src_qmake-manual.pro 116
+ \snippet 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
@@ -4184,7 +4184,7 @@
A simple scope that adds the platform-dependent file for
Windows looks like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 117
+ \snippet 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
@@ -4193,7 +4193,7 @@
When you have done that, your project file should look
something like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 118
+ \snippet code/doc_src_qmake-manual.pro 118
Use qmake as before to generate a Makefile.
@@ -4206,13 +4206,13 @@
the scope condition with the function. A check for a file called main.cpp looks
like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 119
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 120
+ \snippet 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
@@ -4231,12 +4231,12 @@
the other inside it. Put the settings to be processed inside the second
scope, like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 121
+ \snippet code/doc_src_qmake-manual.pro 121
Nested scopes can be joined together using colons, so the final
project file looks like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 122
+ \snippet 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
@@ -4309,7 +4309,7 @@
to specify any. qmake will add the necessary default values.
An example project file might look like this:
- \snippet snippets/code/doc_src_qmake-manual.pro 123
+ \snippet 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
@@ -4447,8 +4447,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 snippets/qmake/debug_and_release.pro 0
- \snippet snippets/qmake/debug_and_release.pro 1
+ \snippet qmake/debug_and_release.pro 0
+ \snippet 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
@@ -4458,23 +4458,23 @@
generate a Makefile rule to allow the project to be built in both modes.
This can be invoked in the following way:
- \snippet snippets/code/doc_src_qmake-manual.pro 124
+ \snippet 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 snippets/qmake/debug_and_release.pro 2
+ \snippet qmake/debug_and_release.pro 2
This allows the Makefile to be processed using the default rule:
- \snippet snippets/code/doc_src_qmake-manual.pro 125
+ \snippet 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 snippets/code/doc_src_qmake-manual.pro 126
+ \snippet 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
@@ -4484,11 +4484,10 @@
Note: This was originally used in the customwidgetplugin.pro file, but is
no longer needed there.
\endomit
- \snippet snippets/code/doc_src_qmake-manual.pro 127
+ \snippet 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
added to the scope to do the same for release mode. Left as it is, the
target name remains unmodified.
*/
-