diff options
| author | Kai Koehne <kai.koehne@theqtcompany.com> | 2015-11-18 11:07:31 +0100 |
|---|---|---|
| committer | Kai Koehne <kai.koehne@theqtcompany.com> | 2015-11-25 08:54:49 +0000 |
| commit | 71307a0cba2e387e7e049314c2eb12c93d4ac04f (patch) | |
| tree | e42faf75bdd47a38234e4387d0b850a56a714b1d | |
| parent | c5dc385d6d4195afc331021a82b6403107565158 (diff) | |
Doc: Reformulate sentence in tutorial about explicit dependencies
Saying that you need to 'import' the dependency is unfortunate,
since import has been introduced with a very distinct meaning
(QML imports).
Change-Id: I59216cb651853eafb8169966cd6b23cee3201268
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
| -rw-r--r-- | doc/qbs.qdoc | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/qbs.qdoc b/doc/qbs.qdoc index 460833ec6..2e1af2267 100644 --- a/doc/qbs.qdoc +++ b/doc/qbs.qdoc @@ -421,8 +421,7 @@ \endcode A module can implicitly depend on other modules. For example, the \c Qt.core module depends - on \c{cpp}. But to set the properties of a module you must explicitly import - it. + on \c{cpp}. But to set the properties of a module you must make the dependency explicit. \code // THIS DOES NOT WORK |