diff options
Diffstat (limited to 'doc/reference/modules/qt-modules.qdoc')
| -rw-r--r-- | doc/reference/modules/qt-modules.qdoc | 18 |
1 files changed, 2 insertions, 16 deletions
diff --git a/doc/reference/modules/qt-modules.qdoc b/doc/reference/modules/qt-modules.qdoc index 87e738b67..e3fee3c72 100644 --- a/doc/reference/modules/qt-modules.qdoc +++ b/doc/reference/modules/qt-modules.qdoc @@ -35,6 +35,8 @@ The \c{Qt.*} modules contain properties and rules for Qt. + Qt modules are generated by the \l[QML]{Qt} module provider. + \section1 Creating Dependencies to Qt Modules The Qt modules are grouped using the prefix \c Qt. If your product depends @@ -54,22 +56,6 @@ The Qt modules that have properties and relevant file tags are described in separate topics. - \section1 Qt-specific Module Provider Properties - - Looking up a Qt installation happens via a \l{Module Providers}{module provider}. - By default, if a dependency to a Qt module is encountered, \QBS collects all Qt installations - it can find. This lookup happens by searching for \c qmake executables in the \c PATH - environment variable. Alternatively, you can explicitly tell \QBS which Qt - installations it should consider by setting the \c Qt.qmakeFilePaths - \l{Parameterizing Module Providers}{module provider property}. In that case, - the environment will be ignored. For instance, with the following Linux command line, - \QBS will build the project against a custom Qt instead of the standard one in \c{/usr/bin}: - \code - $ qbs moduleProviders.Qt.qmakeFilePaths:/opt/myqt/bin/qmake - \endcode - You can also set the module provider property in a profile. The simplest way to do - this is via the \l setup-qt tool. - \section1 List of Submodules \table |