qt_query_qml_module

qt_query_qml_module(
    target
    [URI uri_var]
    [VERSION version_var]
    [PLUGIN_TARGET plugin_target_var]
    [TARGET_PATH target_path_var]
    [MODULE_RESOURCE_PATH module_resource_path_var]
    [QMLDIR qmldir_var]
    [TYPEINFO typeinfo_var]
    [QML_FILES qml_files_var]
    [QML_FILES_DEPLOY_PATHS qml_files_deploy_paths_var]
    [QML_FILES_PREFIX_OVERRIDES qml_files_prefix_overrides_var]
    [RESOURCES resources_var]
    [RESOURCES_DEPLOY_PATHS resources_deploy_paths_var]
    [RESOURCES_PREFIX_OVERRIDES resources_prefix_overrides_var]
)

If versionless commands are disabled, use qt6_query_qml_module() instead. It supports the same set of arguments as this command.

This command is used to obtain information about a QML module target. That target must have previously been created by or passed to an earlier call to qt_add_qml_module(). The target cannot be an imported target.

The information provided by this command enables the caller to deploy all parts of a single QML module. The project should install the target and the associated plugin target (if the module has one and it is separate from the backing target) using the standard install(TARGETS) command. Everything else can be deployed with install(FILES).

Each of the optional arguments specifies the name of a variable in which to store the corresponding QML module property.

URI and VERSION provide the module's uri and version respectively.

PLUGIN_TARGET can be used to obtain the name of the plugin target for the QML module. Not all QML modules have a plugin, so the value returned for this option could be an empty string. If the QML module has no separate backing target, then target will be the same as the plugin target.

TARGET_PATH is the URI with dots (.) replaced by forward slashes (/). It represents the path below the base QML module installation directory where this QML module's qmldir file (and possibly others) should be deployed. The QML module installation directory serves as a QML import path where the QML engine will look for QML modules. The default base QML module installation directory used by qt_generate_deploy_qml_app_script() is qml. A project using a deployment script can use QT_DEPLOY_QML_DIR rather than hard-coding this location (also see QT_DEPLOY_PREFIX).

MODULE_RESOURCE_PATH provides the resource path under which the QML module's compiled-in files can be found. It is formed from qt_add_qml_module()'s RESOURCE_PREFIX concatenated with the module's TARGET_PATH. The queried value should not be used for deployment, but may be helpful in matching up resource paths with file system locations, if needed.

QMLDIR provides the path to the qmldir file. When deploying the QML module, this file should be copied to the target path. In a deployment script, this location can be obtained using ${QT_DEPLOY_PREFIX}/${QT_DEPLOY_QML_DIR}.

TYPEINFO provides the path to the module's typeinfo file, if it has one. It will be an empty string if the module has no typeinfo file. The typeinfo file should be deployed to the same path as the qmldir file.

QML_FILES provides a list of all files added to the QML module through one of the following methods:

• As QML_FILES arguments in qt_add_qml_module().

• As FILES arguments in qt_target_qml_sources().

All files will be recorded with absolute paths.

QML_FILES_DEPLOY_PATHS provides a list with exactly the same number of elements as QML_FILES. Each element of the QML_FILES_DEPLOY_PATHS list is the path below the target path where the corresponding element of QML_FILES should be deployed. The paths in QML_FILES_DEPLOY_PATHS include the file name, since this could be different to the file name in QML_FILES due to the use of resource aliases (see QT_RESOURCE_ALIAS).

Entries in QML_FILES_DEPLOY_PATHS can also be an empty string. Any file added using qt_target_qml_sources() with a custom PREFIX will have no deploy path, since using a custom prefix typically means the file sits outside of the QML module's target path.

QML_FILES_PREFIX_OVERRIDES provides another list with exactly the same number of elements as QML_FILES. Where a file has been added with a custom prefix as described in the preceding paragraph, its corresponding entry in the QML_FILES_PREFIX_OVERRIDES list will contain the custom prefix used. For all other files, their list entries will be an empty string.

The RESOURCES, RESOURCES_DEPLOY_PATHS, and RESOURCES_PREFIX_OVERRIDES options are analogous to those for QML_FILES discussed above. RESOURCES provides a list of all files added to the QML module as RESOURCES arguments to either qt_add_qml_module() or qt_target_qml_sources(). All paths will be absolute. The meaning and usage of RESOURCES_DEPLOY_PATHS and RESOURCES_PREFIX_OVERRIDES follows the same patterns as QML_FILES_DEPLOY_PATHS and QML_FILES_PREFIX_OVERRIDES respectively.