diff options
author | Craig Scott <craig.scott@qt.io> | 2021-06-15 22:09:56 +1000 |
---|---|---|
committer | Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> | 2021-07-23 13:36:54 +0000 |
commit | f2297b2aa4d4281fe67f4278d7515362fdbedfcc (patch) | |
tree | dfac76c8b2ab65e06d04f6a7b6d00359593325aa | |
parent | 78e7b9e695bd41f97cb5b4506f02bf6c956b611b (diff) |
Add initial qml CMake API docs
This provides the overall the structure for the QML docs, but only the
qt_add_qml_module() command is fully documented. Follow-up changes
will populate the skeleton pages added here.
Remove the inline docs for qt6_add_qml_module() which were previously
embedded directly in the CMake source. This prevents having to
maintain two sets of docs and keep them in sync.
Task-number: QTBUG-82598
Task-number: QTBUG-88763
Task-number: QTBUG-89274
Change-Id: I2d6105fecf2b9e5ecfa798872b5f1ef1f830eba2
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Andrei Golubev <andrei.golubev@qt.io>
(cherry picked from commit ba252ed051dc311af001315193d0354125c423a2)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
-rw-r--r-- | src/qml/Qt6QmlMacros.cmake | 127 | ||||
-rw-r--r-- | src/qml/doc/qtqml.qdocconf | 8 | ||||
-rw-r--r-- | src/qml/doc/src/cmake/cmake-variables.qdoc | 55 | ||||
-rw-r--r-- | src/qml/doc/src/cmake/qt_add_qml_module.qdoc | 412 | ||||
-rw-r--r-- | src/qml/doc/src/cmake/qt_add_qml_plugin.qdoc | 53 | ||||
-rw-r--r-- | src/qml/doc/src/cmake/qt_import_qml_plugins.qdoc | 53 | ||||
-rw-r--r-- | src/qml/doc/src/cmake/qt_target_qml_sources.qdoc | 53 |
7 files changed, 630 insertions, 131 deletions
diff --git a/src/qml/Qt6QmlMacros.cmake b/src/qml/Qt6QmlMacros.cmake index 2ee1680993..547f099709 100644 --- a/src/qml/Qt6QmlMacros.cmake +++ b/src/qml/Qt6QmlMacros.cmake @@ -4,133 +4,6 @@ set(__qt_qml_macros_module_base_dir "${CMAKE_CURRENT_LIST_DIR}" CACHE INTERNAL "") -# Create a Qml Module. -# -# target: The name of the target to use for the qml module. If it does not -# already exist, it will be created. This is referred to as the "backing -# target" when a separate plugin is also generated (see PLUGIN_TARGET below). -# (REQUIRED) -# -# URI: Declares the module identifier of the module. The module identifier is -# the (dotted URI notation) identifier for the module, which must match the -# module's install path. (REQUIRED) -# -# VERSION: The module's version. (REQUIRED) -# -# PAST_MAJOR_VERSIONS: List of past major versions this QML module was available -# in. Ensures that the module can be imported when using these major versions. -# (OPTIONAL) -# -# TARGET_PATH: Overwrite the generated target path. By default the target path -# is generated from the URI by replacing the '.' with a '/'. However, under -# certain circumstance this may not be enough. Use this argument to provide -# a replacement. (OPTIONAL) -# -# RESOURCE_PREFIX: Resource Prefix to be used when adding resources to the -# target. This may include the qmldir file, compiled/cached *.qml files, etc. -# If not specified, a default prefix of "/" is used. (OPTIONAL) -# -# OUTPUT_DIRECTORY: Overrides the directory where the qmldir, *.qmltypes and -# plugin library will be created. Defaults to ${CMAKE_CURRENT_BINARY_DIR} if -# not specified. (OPTIONAL) -# -# STATIC, SHARED: Explicitly specify the type of library to create. At most one -# of these two options can be specified. If neither is given, then the type of -# library follows CMake's usual rules of creating a static library unless the -# BUILD_SHARED_LIBS variable is set to true. (OPTIONAL) -# -# CLASS_NAME: Provides the class name of the C++ plugin used by the module. This -# information is required for all the QML modules that depend on a C++ plugin -# for additional functionality. Qt Quick applications built with static -# linking cannot resolve the module imports without this information. -# If no CLASS_NAME is given, it defaults to the URI with non-alphanumeric -# characters converted to underscores, and "Plugin" appended. If an existing -# target is passed in as the PLUGIN_TARGET and it has a QT_PLUGIN_CLASS_NAME -# target property set, that will be used as the default CLASS_NAME instead. -# (OPTIONAL) -# -# PLUGIN_TARGET: The recommended arrangement is to have separate backing and -# plugin libraries. By default, the plugin library will be created as a second -# CMake target with the same name as ${target}, but with "plugin" appended. -# This name can be overridden with PLUGIN_TARGET. To use a single target -# instead of separate backing and plugin targets, set PLUGIN_TARGET to the -# same as ${target}. (OPTIONAL) -# -# NO_CREATE_PLUGIN_TARGET: When given, the plugin target will not be -# automatically created. Use this if the qml module will always be used by -# linking directly to the backing target and no plugin is needed at runtime. -# An executable that is set up as its own qml module is one example where this -# option is appropriate. Note also that an existing target can be specified in -# PLUGIN_TARGET, in which case it will be modified by this function rather -# than created by it. (OPTIONAL) -# -# NO_GENERATE_PLUGIN_SOURCE: A .cpp file will be created for the plugin class -# by default and automatically added to the plugin target. Use this option to -# indicate that no such .cpp file should be generated. The caller is then -# responsible for providing their own plugin class if a separate plugin will -# be created. Note that this option is independent of NO_CREATE_PLUGIN_TARGET. -# (OPTIONAL) -# -# NO_PLUGIN_OPTIONAL: The plugin is marked as optional in the qmldir file by -# default. If the plugin contains code other than just the shim plugin loader -# class, specify this option to indicate that the plugin must always be loaded -# as part of the qml module. (OPTIONAL) -# -# OUTPUT_TARGETS: In static builds, additional CMake targets can be created -# which consumers of the module will need to potentially install. -# Supply the name of an output variable, which will be set to a list of these -# targets. If installing the main target, you will also need to install these -# output targets for static builds. (OPTIONAL) -# -# DESIGNER_SUPPORTED: Specify this argument if the plugin is supported by Qt -# Quick Designer. By default, the plugin will not be supported. (OPTIONAL) -# -# TYPEINFO: Path to a file which declares a type description file for the module -# that can be read by QML tools such as Qt Creator to access information about -# the types defined by the module's plugins. You will typically need to also -# specify NO_GENERATE_QMLTYPES if using this option. When TYPEINFO is not -# specified, it will default to "${target}.qmltypes". (OPTIONAL) -# -# NO_GENERATE_QMLTYPES: Do not automatically generate the *.qmltypes file. -# See also the TYPEINFO option. (OPTIONAL) -# -# NO_GENERATE_QMLDIR: Do not automatically generate the qmldir file. (OPTIONAL) -# -# IMPORTS: List of other Qml Modules that this module imports. A version can be -# specified by appending it after a slash(/), e.g QtQuick/2.0. The minor -# version may be omitted, e.g. QtQuick/2. Alternatively "auto" may be given -# as version to forward the version the current module is being imported with, -# e.g. QtQuick/auto. (OPTIONAL) -# -# OPTIONAL_IMPORTS: List of other Qml Modules that this module may import at -# run-time. Those are not automatically imported by the QML engine when -# importing the current module, but rather serve as hints to tools like -# qmllint. Versions can be specified in the same way as for IMPORTS. -# (OPTIONAL) -# -# DEPENDENCIES: List of QML Module dependencies and their versions. The module -# and its version must be separated via a slash(/). E.g. QtQuick/2.0 -# (OPTIONAL) -# -# IMPORT_PATH: State that QML modules this one depends on may be found in the -# given import paths. (OPTIONAL) -# -# SOURCES: List of C++ sources. (OPTIONAL) -# -# QML_FILES: List of Qml files. See qt6_target_qml_sources() for more -# information on how to specify additional properties on qml files. (OPTIONAL) -# -# RESOURCES: Resources used in QML, for example images. (OPTIONAL) -# -# NO_LINT: By default, this function will create a separate ${target}_qmllint -# target if any .qml files are added to ${target} (see qt6_add_qml_sources()). -# Provide the NO_LINT option to disable this behavior. (OPTIONAL) -# -# NO_CACHEGEN: By default, this function will compile each .qml file added to -# the target and store that compiled version in the target's resources. -# Provide the NO_CACHEGEN option to disable this behavior. -# See qt6_add_qml_sources() for further details. (OPTIONAL) -# function(qt6_add_qml_module target) set(args_option STATIC diff --git a/src/qml/doc/qtqml.qdocconf b/src/qml/doc/qtqml.qdocconf index 7737ec5575..b2f2c0cb77 100644 --- a/src/qml/doc/qtqml.qdocconf +++ b/src/qml/doc/qtqml.qdocconf @@ -47,11 +47,9 @@ depends += \ qmake \ qtcmake -headerdirs += .. \ - ../../qml +headerdirs += .. -sourcedirs += .. \ - ../../qml +sourcedirs += .. exampledirs += ../../../examples/qml \ ../ \ @@ -67,3 +65,5 @@ manifestmeta.thumbnail.names += "QtQml/Chapter 4*" \ navigation.landingpage = "Qt QML" navigation.cppclassespage = "Qt QML C++ Classes" navigation.qmltypespage = "Qt QML QML Types" + +macro.versionlessNote = "If \\l{Versionless commands}{versionless commands} are disabled, use \\c{\1} instead. It supports the same set of arguments as this command." diff --git a/src/qml/doc/src/cmake/cmake-variables.qdoc b/src/qml/doc/src/cmake/cmake-variables.qdoc new file mode 100644 index 0000000000..901ce26e91 --- /dev/null +++ b/src/qml/doc/src/cmake/cmake-variables.qdoc @@ -0,0 +1,55 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! +\page cmake-variable-QT_QML_OUTPUT_DIRECTORY.html +\ingroup cmake-variables +\ingroup cmake-variables-qtqml + +\title QT_QML_OUTPUT_DIRECTORY +\target cmake-variable-QT_QML_OUTPUT_DIRECTORY + +\brief Base output directory below which QML modules will be created by default. + +The \l{qt6_add_qml_module}{qt6_add_qml_module()} command accepts an +\c OUTPUT_DIRECTORY argument which specifies where the QML module's \c qmldir +file, typeinfo file and plugin library will be created. By default, the current +binary directory (\c CMAKE_CURRENT_BINARY_DIR) is used if that argument is not +provided. When a set of QML modules are being defined, it may be convenient to +have them all generated under a common point in the build directory. If the +source directory structure doesn't match the URI structure of the QML modules, +or if you just want your QML modules to be collected under a different +location, the \c QT_QML_OUTPUT_DIRECTORY can be used. When set, the default +changes to the concatenation of \c QT_QML_OUTPUT_DIRECTORY and the QML module's +\e{target path}, which is based on the module URI. \c QT_QML_OUTPUT_DIRECTORY +will also be added to the import path of the \c qmllint and \c qmlcachegen +tooling targets, allowing them to find other QML modules under the same base +location. + +*/ + + diff --git a/src/qml/doc/src/cmake/qt_add_qml_module.qdoc b/src/qml/doc/src/cmake/qt_add_qml_module.qdoc new file mode 100644 index 0000000000..7509e2dade --- /dev/null +++ b/src/qml/doc/src/cmake/qt_add_qml_module.qdoc @@ -0,0 +1,412 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! +\page qt_add_qml_module.html +\ingroup cmake-commands-qtqml + +\title qt_add_qml_module +\target qt6_add_qml_module + +\brief Defines a QML module. + +\section1 Synopsis + +\badcode +qt_add_qml_module( + target + URI uri + VERSION version + [PAST_MAJOR_VERSIONS ...] + [STATIC | SHARED] + [PLUGIN_TARGET plugin_target] + [OUTPUT_DIRECTORY output_dir] + [RESOURCE_PREFIX resource_prefix] + [TARGET_PATH target_path] + [CLASS_NAME class_name] + [TYPEINFO typeinfo] + [IMPORTS ...] + [OPTIONAL_IMPORTS ...] + [DEPENDENCIES ...] + [IMPORT_PATH ...] + [SOURCES ...] + [QML_FILES ...] + [OUTPUT_TARGETS out_targets_var] + [DESIGNER_SUPPORTED] + [NO_PLUGIN_OPTIONAL] + [NO_CREATE_PLUGIN_TARGET] + [NO_GENERATE_PLUGIN_SOURCE] + [NO_GENERATE_QMLTYPES] + [NO_GENERATE_QMLDIR] + [NO_LINT] + [NO_CACHEGEN] +) + +\endcode + +\versionlessNote qt6_add_qml_module() + +\section1 Description + +This command defines a QML module that can consist of C++ sources, \c{.qml} +files, or both. It ensures that essential module details are provided and that +they are consistent. It also sets up and coordinates things like cached +compilation of \c{.qml} sources, resource embedding, linting checks, and +auto-generation of some key module files. + +\section2 Target Structure + +A QML module can be structured in a few different ways. The following scenarios +are the typical arrangements: + +\section3 Separate backing and plugin targets + +This is the recommended arrangement for most QML modules. All of the module's +functionality is implemented in the \e backing target, which is given as the +first command argument. C++ sources, \c{.qml} files, and resources should all +be added to the backing target. The backing target is a library that should be +installed in the same location as any other library defined by the project. + +A separate \e plugin target is associated with the QML module. It is used at +runtime to load the module dynamically when the application doesn't already +link to the backing target. The plugin target will also be a library and is +normally installed to the same directory as the module's +\l{Module Definition qmldir Files}{qmldir} file. + +The plugin target should ideally contain nothing more than a trivial +implementation of the plugin class. This allows the plugin to be designated as +optional in the \c qmldir file. Other targets can then link directly to the +backing target and the plugin will not be needed at runtime, which can improve +load-time performance. By default, a C++ source file that defines a minimal +plugin class will be automatically generated and added to the plugin target. +For cases where the QML module needs a custom plugin class implementation, the +\l{NO_GENERATE_PLUGIN_SOURCE} and usually the \l{NO_PLUGIN_OPTIONAL} options +will be needed. + +\section3 Plugin target with no backing target + +A QML module can be defined with the plugin target serving as its own backing +target. In this case, the module must be loaded dynamically at runtime and +cannot be linked to directly by other targets. To create this arrangement, +the \c PLUGIN_TARGET keyword must be used, with the \c target repeated as the +plugin target name. For example: + +\badcode +qt_add_qml_module(someTarget + PLUGIN_TARGET someTarget + ... +) +\endcode + +While this arrangement may seem marginally simpler to deploy, a separate +backing target should be preferred where possible due to the potentially better +load-time performance. + +\section3 Executable as a QML module + +An executable target can act as a backing target for a QML module. In this case, +there should be no need for a plugin library, since the QML module will always +be loaded directly as part of the application. The \c{qt_add_qml_module()} +command will detect when an executable is used as the backing target and will +automatically disable the creation of a separate plugin. Do not use any of the +options with \c{PLUGIN} in their name when using this arrangement. + + +\target qmldir-autogeneration +\section2 Auto-generating \c{qmldir} and typeinfo files + +By default, a \l{Module Definition qmldir Files}{qmldir} file and a typeinfo +file will be auto-generated for the QML module being defined. The contents of +those files are determined by the various arguments given to this command, as +well as the sources and \c{.qml} files added to the backing target. +The \l OUTPUT_DIRECTORY argument determines where the \c qmldir and typeinfo +files will be written to. If the QML module has a plugin, that plugin will also +be created in the same directory as the \c qmldir file. + +In static builds, the backing target's \c{.qml} files will be scanned during +the CMake configure run to determine the imports used by the module and set up +linking relationships. When a \c{.qml} file is added to or removed from the +module, CMake will normally re-run automatically and the relevant files will be +re-scanned, since a \c{CMakeLists.txt} file will have been modified. During the +course of development, an existing \c{.qml} file may add or remove an import or +a type. On its own, this would not cause CMake to re-run automatically, so you +should explicitly re-run CMake to force the \c qmldir file to be regenerated +and any linking relationships to be updated. + +The backing target's C++ sources are scanned at build time to generate a +typeinfo file and a C++ file to register the associated types. The generated +C++ file is automatically added to the backing target as a source. + +Projects should prefer to use the auto-generated typeinfo and \c qmldir files +where possible. They are easier to maintain and they don't suffer from the same +susceptibility to errors that hand-written files do. Nevertheless, for +situations where the project needs to provide these files itself, the +auto-generation can be disabled. The \c NO_GENERATE_QMLDIR option disables the +\c qmldir auto-generation and the \c NO_GENERATE_QMLTYPES option disables the +typeinfo and C++ type registration auto-generation. If the auto-generated +typeinfo file is acceptable, but the project wants to use a different name for +that file, it can override the default name with the \c TYPEINFO option (but +this should not typically be needed). + +\target qmlcachegen-auto +\section2 Caching compiled QML sources + +All \c{.qml}, \c{.js}, and \c{.mjs} files added to the module via the +\c QML_FILES argument will be compiled to bytecode and cached directly in the +backing target. This improves load-time performance of the module. The original +uncompiled files are also stored in the backing target's resources, as these +may still be needed in certain situations by the QML engine. + +The resource path of each file is determined by its path relative to the +current source directory (\c CMAKE_CURRENT_SOURCE_DIR). This resource path is +appended to a prefix formed by concatenating the \l{RESOURCE_PREFIX} and +\l{TARGET_PATH}. Ordinarily, the project should aim to place \c{.qml} files in +the same relative location as they would have in the resources. If the \c{.qml} +file is in a different relative directory to its desired resource path, its +location in the resources needs to be explicitly specified. This is done by +setting the \c QT_RESOURCE_ALIAS source file property, which must be set before +the \c{.qml} file is added. For example: + +\badcode +set_source_files_properties(path/to/somewhere/MyFrame.qml PROPERTIES + QT_RESOURCE_ALIAS MyFrame.qml +) + +qt_add_qml_module(someTarget + URI MyCo.Frames + RESOURCE_PREFIX /my.company.com/imports + QML_FILES + path/to/somewhere/MyFrame.qml + AnotherFrame.qml +) +\endcode + +In the above example, no \c TARGET_PATH is specified. The default based on +the \c URI will be used, which will be \c{MyCo/Frames} in this case. After +taking into account the source file properties, the two \c{.qml} files will be +found at the following resource paths: + +\list +\li \c{/my.company.com/imports/MyCo/Frames/MyFrame.qml} +\li \c{/my.company.com/imports/MyCo/Frames/AnotherFrame.qml} +\endlist + +\target qmllint-auto +\section2 Linting QML sources + +A separate linting target will be automatically created if any \c{.qml} files +are added to the module via the \c QML_FILES keyword, or by a later call to +\l{qt6_target_qml_sources}{qt_target_qml_sources()}. The name of the linting +target will be the \c target followed by \c{_qmllint}. The linting target is +not part of the default CMake \c ALL target, it is intended for developers to +execute manually on demand. + +\section1 Arguments + +The \c target specifies the name of the backing target for the QML module. +By default, it will be created as a shared library if CMake's +\c BUILD_SHARED_LIBS variable is set to true, or as a static library otherwise. +This choice can be explicitly overridden with the \c STATIC or \c SHARED +options. + +The plugin target associated with the QML module can be specified using the +\c PLUGIN_TARGET argument. The \c PLUGIN_TARGET can be the same as the backing +\c target, in which case there will be no separate backing target. +If \c PLUGIN_TARGET is not given, it defaults to \c target with \c plugin +appended. For example, a backing target called \c mymodule would have a default +plugin name of \c mymoduleplugin. The plugin target's name will be used to +populate a \c{plugin} line in the generated +\l{Module Definition qmldir Files}{qmldir} file. Therefore, you must not try to +change the plugin's output name by setting target properties like +\c OUTPUT_NAME or any of its related properties. + +The backing \c target and the plugin target (if different) will be created by +the command, unless they already exist. Projects should generally let them be +created by the command so that they are created as the appropriate target type. +If an existing \c target is passed in and it is an executable target, then no +plugin target will be created or used. + +In certain situations, the project may want to delay creating the plugin target +until after the call. The \c NO_CREATE_PLUGIN_TARGET option can be given in +that situation. The project is then expected to call +\l{qt6_add_qml_plugin}{qt_add_qml_plugin()} on the plugin target once it has +been created. + +Every QML module must define a \c URI. It should be specified in dotted URI +notation, such as \c{QtQuick.Layouts}. It must not contain anything other than +alphanumeric or dot characters. Other QML modules may use this name in +\l{qtqml-syntax-imports.html}{import statements} to import the module. The +\c URI will be used in the \c module line of the generated +\l{Module Definition qmldir Files}{qmldir} file. + +A QML module must also define a \c VERSION in the form \c{Major.Minor}, where +both \c Major and \c Minor must be integers. An additional \c{.Patch} +component may be appended, but will be ignored. A list of earlier major +versions the module provides types for can also optionally be given after the +\c PAST_MAJOR_VERSIONS keyword. +See \l{qtqml-modules-identifiedmodules.html}{Identified Modules} for further +in-depth discussion of the module URI and version numbering. + +\target RESOURCE_PREFIX +\c RESOURCE_PREFIX is intended to encapsulate a namespace for the project and +will often be the same for all QML modules that the project defines. It should +be chosen to avoid clashing with the resource prefix of anything else used by +the project or likely to be used by any other project that might consume it. +A good choice is to incorporate the domain name of the organization the project +belongs to. A common convention is to append \c{/imports} to the domain name to +form the resource prefix. For example: + +\badcode +qt_add_qml_module(someTarget + RESOURCE_PREFIX /my.company.com/imports + ... +) +\endcode + +\target TARGET_PATH +\c TARGET_PATH should represent the module-specific part of the resource path +used to refer to the module QML files. It defaults to the module's \c URI, with +dots replaced by forward slashes as path separators. It should rarely be +necessary to override this default. + +\target OUTPUT_DIRECTORY +\c OUTPUT_DIRECTORY specifies where the plugin library, \c qmldir and typeinfo +files are generated. When this keyword is not given, the default value will be +the \l TARGET_PATH appended to the value of the \l QT_QML_OUTPUT_DIRECTORY +variable. If that variable is not defined, then the output directory will be +set to \c{${CMAKE_CURRENT_BINARY_DIR}}. When the structure of the source tree +matches the structure of QML module target paths (which is highly recommended), +\l QT_QML_OUTPUT_DIRECTORY often isn't needed. The need for specifying the +\c OUTPUT_DIRECTORY keyword should be rare, but if it is used, it is likely +that the caller will also need to add to the \l IMPORT_PATH to ensure that +\l{qmllint-auto}{linting}, \l{qmlcachegen-auto}{cached compilation} of qml +sources and \l{qt6_import_qml_plugins}{automatic importing} of plugins in +static builds all work correctly. + +\target NO_GENERATE_PLUGIN_SOURCE +By default, \c{qt_add_qml_module()} will auto-generate a \c{.cpp} file that +implements the plugin class named by the \c CLASS_NAME argument. The generated +\c{.cpp} file will be automatically added to the plugin target as a source file +to be compiled. If the project wants to provide its own implementation of the +plugin class, the \c NO_GENERATE_PLUGIN_SOURCE option should be given. Where no +\c CLASS_NAME is provided, it defaults to the \c URI with dots replaced by +underscores, then \c Plugin appended. Unless the QML module has no plugin, the +class name will be recorded as a \c classname line in the generated +\l{Module Definition qmldir Files}{qmldir} file. + +\target NO_PLUGIN_OPTIONAL +If the \c NO_PLUGIN_OPTIONAL keyword is given, then the plugin is recorded in +the generated \c qmldir file as non-optional. If all of a QML module's +functionality is implemented in its backing target and the plugin target is +separate, then the plugin can be optional, which is the default and recommended +arrangement. The auto-generated plugin source file satisfies this requirement. +Where a project provides its own \c{.cpp} implementation for the plugin, that +would normally mean the \c NO_PLUGIN_OPTIONAL keyword is also needed because +the plugin will almost certainly contain functionality that the QML module +requires. + +Type registration is automatically performed for the backing target's C++ +sources that are processed by AUTOMOC. This will generate a typeinfo file in the +\l{OUTPUT_DIRECTORY}{output directory}, the file name being the \c target name +with \c{.qmltypes} appended. This file name can be changed using the +\c TYPEINFO option if desired, but this should not normally be necessary. +The file name is also recorded as a \c typeinfo entry in the generated +\l{Module Definition qmldir Files}{qmldir} file. Automatic type registration +can be disabled using the \c NO_GENERATE_QMLTYPES option, in which case no +typeinfo file will be generated, but the project will still be expected to +generate a typeinfo file and place it in the same directory as the generated +\c qmldir file. + +\c IMPORTS provides a list of other QML modules that this module imports. +A version can be specified by appending it after a slash, such as +\c{QtQuick/2.0}. The minor version may be omitted, as in \c{QtQuick/2}. +Alternatively, \c auto may be given for the version (\c{QtQuick/auto}), which +would result in the version that the current module is being imported with +being used. Each module listed here will be added as an \c{import} entry in the +generated \l{Module Definition qmldir Files}{qmldir} file. + +\c OPTIONAL_IMPORTS provides a list of other QML modules that this module +\e may import at run-time. These are not automatically imported by the QML +engine when importing the current module, but rather serve as hints to tools +like \c qmllint. Versions can be specified in the same way as for \c IMPORTS. +Each module listed here will be added as an \c{optional import} entry in the +generated \l{Module Definition qmldir Files}{qmldir} file. + +\c DEPENDENCIES provides a list of other QML modules that this module depends +on, but doesn't necessarily import. It would typically be used for dependencies +that only exist at the C++ level, such as a module registering a class to QML +which is a subclass of one defined in another module. The module version of the +dependencies must be specified along with the module name, in the same form as +used for \c IMPORTS and \c OPTIONAL_IMPORTS. Each module listed here will be +added as a \c{depends} entry in the generated +\l{Module Definition qmldir Files}{qmldir} file. + +\target IMPORT_PATH +\c IMPORT_PATH can be used to add to the search paths where other QML modules +that this one depends on can be found. The other modules must have their +\c qmldir file under their own \c TARGET_PATH below one of the search paths. + +\c SOURCES specifies a list of non-QML sources to be added to the backing +target. It is provided as a convenience and is equivalent to adding the sources +to the backing target with the built-in \c{target_sources()} CMake command. + +\c QML_FILES lists the \c{.qml}, \c{.js} and \c{.mjs} files for the module. +These will be automatically \l{qmlcachegen-auto}{compiled into bytecode} and +embedded in the backing target unless the \c NO_CACHEGEN option is given. +The uncompiled file is always stored in the embedded resources of the backing +target, even if \c NO_CACHEGEN is specified. Unless the \c NO_LINT option is +given, the uncompiled files will also be +\l{Linting QML sources}{processed by \c qmllint} via a separate custom build +target. The files will also be used to populate type information in the +generated \l{Module Definition qmldir Files}{qmldir} file. +See \l{qt6_target_qml_sources}{qt_target_qml_sources()} for further details on +the source file properties that can be set on these files or if files need to +be added to the backing target after this command has been called. + +\c RESOURCES lists any other files needed by the module, such as images +referenced from the QML code. These files will be added as compiled-in +resources under the \l RESOURCE_PREFIX. If needed, their relative location can +be controlled by setting the \c QT_RESOURCE_ALIAS source property, just as for +\c{.qml} files (see \l{qmlcachegen-auto}{Caching compiled QML sources}). + +\c NO_GENERATE_QMLDIR can be given to disable the automatic generation of the +\c qmldir file. This should normally be avoided, but for cases where the +project needs to provide its own \c qmldir file, this option can be used. + +If the backing target is a static library and that static library will be +installed, \c OUTPUT_TARGETS should be given to provide a variable in which to +store a list of additional targets that will also need to be installed. +These additional targets are generated internally by \c{qt_add_qml_module()} +and are referenced by the backing target's linking requirements as part of +ensuring that resources are set up and loaded correctly. + +The \c DESIGNER_SUPPORTED keyword should be given if the QML module supports +\l{Qt Quick Designer}. When present, the generated \c qmldir file will contain +a \c designersupported line. See \l{Module Definition qmldir Files} for how +this affects the way Quick Designer handles the plugin. + +*/ diff --git a/src/qml/doc/src/cmake/qt_add_qml_plugin.qdoc b/src/qml/doc/src/cmake/qt_add_qml_plugin.qdoc new file mode 100644 index 0000000000..01dfc3eb16 --- /dev/null +++ b/src/qml/doc/src/cmake/qt_add_qml_plugin.qdoc @@ -0,0 +1,53 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! +\page qt_add_qml_plugin.html +\ingroup cmake-commands-qtqml + +\title qt_add_qml_plugin +\target qt6_add_qml_plugin + +\brief Defines a plugin associated with a QML module. + +\section1 Synopsis + +\badcode +qt_add_qml_plugin(...) + +\endcode + +\versionlessNote qt6_add_qml_plugin() + +\section1 Description + +TBD + +\section1 Arguments + +TBD +*/ diff --git a/src/qml/doc/src/cmake/qt_import_qml_plugins.qdoc b/src/qml/doc/src/cmake/qt_import_qml_plugins.qdoc new file mode 100644 index 0000000000..b2c31123fe --- /dev/null +++ b/src/qml/doc/src/cmake/qt_import_qml_plugins.qdoc @@ -0,0 +1,53 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! +\page qt_import_qml_plugins.html +\ingroup cmake-commands-qtqml + +\title qt_import_qml_plugins +\target qt6_import_qml_plugins + +\brief Ensures QML plugins needed by a target are imported for static builds. + +\section1 Synopsis + +\badcode +qt_import_qml_plugins(...) + +\endcode + +\versionlessNote qt6_import_qml_plugins() + +\section1 Description + +TBD + +\section1 Arguments + +TBD +*/ diff --git a/src/qml/doc/src/cmake/qt_target_qml_sources.qdoc b/src/qml/doc/src/cmake/qt_target_qml_sources.qdoc new file mode 100644 index 0000000000..05770b30e0 --- /dev/null +++ b/src/qml/doc/src/cmake/qt_target_qml_sources.qdoc @@ -0,0 +1,53 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! +\page qt_target_qml_sources.html +\ingroup cmake-commands-qtqml + +\title qt_target_qml_sources +\target qt6_target_qml_sources + +\brief Add qml sources to an existing QML module target. + +\section1 Synopsis + +\badcode +qt_target_qml_sources(...) + +\endcode + +\versionlessNote qt6_target_qml_sources() + +\section1 Description + +TBD + +\section1 Arguments + +TBD +*/ |