Details
-
Technical task
-
Resolution: Done
-
P2: Important
-
None
-
a25f650c317e4886007a8beb0e9f2f7e973e6e7c (qt/qtdeclarative/dev) 96fdbf597e581fe5e09e02758a4a2b0fe12add53 (qt/qtdeclarative/6.2)
Description
The proposal is to change the output name of the plugin to lower case and append '_plugin', and see what breaks.
Check what actual name we write out into the qmldir file.
Open question left is whether the default target name should be renamed to lower case as well.
One point is that we might want to be consistent in naming all our plugin targets to end with Plugin suffix, like we do for regular qt plugins.
But it's not strictly necessary for qml plugins, because our current restriction of globbing plugin Config files ending with Plugin is only there for qt plugins, not qml plugins.
Attachments
Issue Links
- relates to
-
QTBUG-95609 cmake names for qml plugins
- Closed
-
QTBUG-95141 Revise plugin target options of qt_add_qml_module
- Closed
-
QTBUG-95024 Offer CMake API to get a list of qml module artifacts for installation purposes
- Closed