summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Komissarov <abbapoh@gmail.com>2023-04-20 01:33:42 +0300
committerIvan Komissarov <ABBAPOH@gmail.com>2023-04-22 12:57:58 +0000
commitc9ecd28c79e2464fcd05678dbbdc5fd0639fd219 (patch)
tree47da2f20efbae9772ab07a10ea2e67dcf69ea7f9
parent43f173106ee30e07c951f2b13e04a9160b2edaad (diff)
downloadqbs-c9ecd28c79e2464fcd05678dbbdc5fd0639fd219.tar.gz
doc: fix intro
Change-Id: I403a5a8f7716c88ed7c36d610cb1762e78be3e14 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
-rw-r--r--doc/qbs.qdoc20
1 files changed, 5 insertions, 15 deletions
diff --git a/doc/qbs.qdoc b/doc/qbs.qdoc
index 45d6dfc91..29f4266de 100644
--- a/doc/qbs.qdoc
+++ b/doc/qbs.qdoc
@@ -1207,27 +1207,17 @@
}
\endcode
- A module can implicitly depend on other modules. For example, the
- \l{Qt.core} module depends on the \l{cpp} module. However, to set the
- properties of a module, you must make the dependency explicit.
+ A module can depend on other modules. For example, the
+ \l{Qt.core} module depends on the \l{cpp} module. The module dependencies are transitive,
+ i.e. in a Product, all dependent modules are accessible:
\code
- // THIS DOES NOT WORK
Application {
name: "helloworld"
files: ["main.cpp"]
Depends { name: "Qt.core" }
- cpp.optimization: "ludicrousSpeed"
- // ERROR! We do not know about "cpp" here,
- // though "Qt.core" depends on "cpp".
- }
-
- // THIS WORKS
- Application {
- name: "helloworld"
- files: ["main.cpp"]
- Depends { name: "Qt.core" }
- Depends { name: "cpp" }
+ // the "cpp" module is available since
+ // "Qt.core" depends on "cpp".
cpp.optimization: "ludicrousSpeed"
}
\endcode