Qt.core

The build variants that this Qt installation offers.

Default: Set by setup-qt.

The path in which Qt tools such as qmake, moc, and so on are located.

Default: Undefined

Whether the C++ sources created by moc are combined into a single C++ file per product. For projects where many header files are to be handled by moc, this can speed up compilation considerably. However, side effects may occur as a result of merging translation units.

Default: cpp.combineCxxSources

Corresponds to the default value of qmake's CONFIG variable.

Default: []

Corresponds to cmake's QT_DISABLED_PUBLIC_FEATURES variable.

The path in which the Qt documentation is located.

Default: Undefined

Whether the Qt resource compiler is run in a two-pass fashion that supports the creation of big resources.

Default: false

Set this property to false if you do not want Qt to define the symbols signals, slots, and emit. This can be necessary if your project interacts with code that also defines such symbols.

Default: true

Corresponds to cmake's QT_ENABLED_PUBLIC_FEATURES variable.

Whether Qt was built as a framework. This is only relevant for Darwin systems.

Default: Undefined

If this property is enabled, a JSON file tagged as "qt.core.metatypes" will potentially be generated from metatype information collected by moc.

Default: Undefined

This property was introduced in Qbs 1.16.

The directory where tools that generate headers (such as moc or uic) put resulting files.

Normally, you don't need to change this property. The one use-case is when there are several files with the same file name in the Product. The file name produced by moc is based only on the source file's base file name (without the directory path) which leads to a conflict in the mentioned case. You can resolve the conflict by setting this property to a non-default value for one of the files. For example:

QtApplication {
    files: ["my_cool_header.h", "main.cpp"]
    Group {
        name: "legacy"
        files: "legacy/my_cool_header.h"
        Qt.core.generatedHeadersDir: "qt.legacy.headers"
    }
}

Default: product.buildDirectory + "/qt.headers"

The base path of the Qt headers.

Default: Undefined

The library infix can be set at Qt build time to change the name of Qt's libraries.

For example, if the infix is "Test", on Unix systems, the Qt Core library will be in a file called libQt5CoreTest.so instead of the default libQt5Core.so.

Default: []

The path in which the Qt libraries are located.

Default: Undefined

If this property is true, lrelease will merge all .ts files into one .qm file. Otherwise, one .qm file will be created for each .ts file.

Default: false

The base name of the lrelease tool. Set this if your system uses a name such as "lrelease-qt4".

Default: "lrelease"

The directory to install the metatypes file into. If this property is empty or undefined, the metatypes file will not be installed. If the generateMetaTypesFile property is not true, then this property has no effect.

Default: Undefined

This property was introduced in Qbs 1.16.

The path in which the Qt mkspecs are located.

Default: Undefined

A list of additional flags to moc.

You will rarely need to set this property.

Default: []

The base name of the moc tool.

Set this if your system uses a name such as "moc-qt4".

Default: "moc"

The Qt namespace that can be set at build time via the configure script.

By default, Qt is not built in a namespace.

Default: Undefined

A list of additional plugin metadata.

The elements of the list are key-value pairs separated by the = character.

A possible use case is to set the plugin URI when building a static QML plugin:

Qt.core.pluginMetaData: ["uri=thePlugin"]

Default: []

The path in which the Qt plugins are located.

Default: Undefined

The environment for calls to qdoc. Typically, you will need to set some variables here when running qdoc to build your project documentation.

Default: Undefined

The base name of the qdoc tool.

Default: "qdoc3" for Qt 4, "qdoc" otherwise.

The directory name where the qdoc tool writes its output.

Default: product.buildDirectory + "/qdoc_html"

The base name of the .qm file to be built from the .ts files in the product.

This property is ignored if lreleaseMultiplexMode is false.

Default: product.targetName

The directory name where to put the .qm file to be built.

Default: product.destinationDirectory

Specifies the type of Qt libraries to build against: "debug" or "release".

Default: The build variant of the code linking against Qt. If Qt does not offer that build variant, the build variant offered by Qt is chosen instead.

Corresponds to the default value of qmake's QT_CONFIG variable.

Default: []

For files tagged as qt.core.resource_data, this property determines the base name of the generated .qrc file.

If this property needs to be changed, it must be set in the corresponding product rather than in a Group.

Default: product.targetName

For files tagged as qt.core.resource_data, this property determines the prefix under which they will be available in the generated .qrc file.

Default: "/"

For files tagged as qt.core.resource_data, this property determines which part of their path will end up in the generated .qrc file. If this property is set to undefined, only the file name is used.

Default: Undefined

Whether Qt was built statically.

Default: Undefined

This property provides the absolute path to the directory where the Qt translation files (.qm) are installed.

Default: Undefined

This property was introduced in Qt 2.5.

Whether to add Qt.core.libPath to cpp.rpaths.

Default: true on Linux, false everywhere else.

The Qt version.

Consists of three numbers separated by dots. For example "5.9.1".

Default: Undefined

The Qt major version.

Default: versionParts[0]

The Qt minor version.

Default: versionParts[1]

The Qt version as a list.

For example, Qt version 5.9.1 would correspond to a value of [5, 9, 1].

Default: []

The Qt patch level.

Default: versionParts[2]