qiurui
/
qtdeclarative
mirror of https://github.com/qt/qtdeclarative.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Point out that STATIC QML plugins require direct linking 

In qt_add_qml_module documentation we never mention targets using the
STATIC QML plugins need to link to corresponding QML plugins. Add
couple words in addition to the Q_IMPORT_QML_PLUGIN note.

Task-number: QTBUG-114688
Change-Id: I2e484250ea9d06dc8824aea23a7c4c106f01884f
Reviewed-by: Amir Masoud Abdol <amir.abdol@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 42b0cb7cca)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Alexey Edelev 2023-08-23 16:40:39 +02:00 committed by Qt Cherry-pick Bot
parent 7a4bc6c10b
commit 67d845a027
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/qml/doc/src/cmake/qt_add_qml_module.qdoc
View File

@ -112,9 +112,13 @@ 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.
The \c STATIC QML modules also generate the static QML plugins if
\c NO_PLUGIN is not specified. Targets that import such \c STATIC QML modules
also need to explicitly link to corresponding QML plugins.
\note
When using static linking, it might be necessary to use
\c Q_IMPORT_QML_PLUGIN to ensure that the QML plugin is correctly linked.
\l {Q_IMPORT_QML_PLUGIN} to ensure that the QML plugin is correctly linked.
\section3 Plugin target with no backing target