Qt.core QML Type
Provides Qt Core support. More...
Import Statement: | import QbsModules . |
Properties
- availableBuildVariants : stringList
- binPath : path
- combineMocOutput : bool
- config : stringList
- docPath : path
- enableKeywords : bool
- frameworkBuild : bool
- incPath : path
- libInfix : string
- libPath : path
- lreleaseMultiplexMode : bool
- lreleaseName : string
- mkspecPath : path
- mocFlags : stringList
- mocName : string
- namespace : string
- pluginMetaData : stringList
- pluginPath : path
- qdocEnvironment : stringList
- qdocName : string
- qmBaseName : string
- qtBuildVariant : string
- qtConfig : stringList
- resourceFileBaseName : string
- resourcePrefix : string
- resourceSourceBase : path
- staticBuild : bool
- version : string
- versionMajor : int
- versionMinor : int
- versionParts : list
- versionPatch : int
Detailed Description
All other Qt modules have a dependency on the Qt.core module, and therefore you do not need to list it in your dependencies if you depend on at least one other Qt module.
Some of the Qt.core properties only need to be defined if the respective installation of Qt was built in some unusual way, for instance by setting non-default configure
flags.
Relevant File Tags
Tag | Auto-tagged File Names | Since | Description |
---|---|---|---|
"qch" | n/a | 1.1 | This tag is attached to the output artifacts of the rule that runs the qhelpgenerator tool. |
"qdoc" | *.qdoc | 1.1 | Source files with this tag trigger a re-execution of the rule running the qdoc tool when their timestamp changes. |
"qdocconf" | *.qdocconf | 1.1 | Source files with this tag trigger a re-execution of the rule running the qdoc tool when their timestamp changes. |
"qdocconf-main" | - | 1.1 | Source files with this tag serve as inputs to the rule running the qdoc tool. |
"qdoc-output" | n/a | 1.5 | Use this tag to match all qdoc outputs, for instance in a Group using the group.fileTagsFilter property. |
"qhp" | *.qhp | 1.1 | Files with this tag serve as inputs to the rule running the qhelpgenerator tool. Such files are created by qdoc , but can also appear as source files. |
"qm" | n/a | 1.1 | This tag is attached to the output artifacts of the rule that runs the lrelease tool. |
"qrc" | *.qrc | 1.0 | Files with this tag serve as inputs to the rule running the rcc tool. |
"qt_plugin_metadata" | - | 1.0 | Source files with this tag trigger a re-execution of the rule running the moc tool when their timestamp changes. |
"qt.core.resource_data" | - | 1.7 | Source files with this tag serve as inputs to the rule creating qrc files. |
"ts" | *.ts | 1.0 | Files with this tag serve as inputs to the rule running the lrelease tool. |
Property Documentation
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
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
Whether Qt was built as a framework. This is only relevant for Darwin systems.
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: []
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"
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 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 .qm
file to be built from the .ts
files in the product.
This property is ignored if lreleaseMultiplexMode is false
.
Default: product.targetName
Specifies the type of Qt libraries to build against: "debug"
or "release"
.
Note: On some systems, it is not possible to link code built in debug mode against libraries built in release mode and vice versa.
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.
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
The Qt version.
Consists of three numbers separated by dots. For example "5.9.1".
Default: Undefined
The Qt version as a list.
For example, Qt version 5.9.1 would correspond to a value of [5, 9, 1]
.
Default: []