Qt

Module provider that generates Qt modules. More...

Properties

Detailed Description

Looking up a Qt installation happens via a 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 qmake executables in the PATH environment variable. Alternatively, you can explicitly tell Qbs which Qt installations it should consider by setting the qmakeFilePaths 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 /usr/bin:

$ qbs moduleProviders.Qt.qmakeFilePaths:/opt/myqt/bin/qmake

You can also set the module provider property in a profile. The simplest way to do this is via the setup-qt tool. For examples of how to use this tool, see the Managing Qt Versions section.

This provider is activated automatically when encountering a dependency on the Qt module and the qbsModuleProviders property is undefined:

CppApplication {
    Depends { name: "Qt.core" }
    files: "main.cpp"
}

Alternatively, you can activate this provider explicitly via the qbsModuleProviders property:

CppApplication {
    Depends { name: "Qt.core" }
    files: "main.cpp"
    qbsModuleProviders: "Qt"
}

Property Documentation

qmakeFilePaths : stringList

List of paths to qmake executables.

Default: undefined


© 2018 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.