3c1125d9fe
Previously we only created object library static plugin initializers for Qt plugins only, not user-project plugins. The reason was that if a user tried to install the plugin target via an export set, CMake would error out saying that the _init library is not part of the same export set. Introduce an OUTPUT_TARGETS option that would allow projects to get the name of the generated _init target, so they can install it if needed. This was already done for qt6_add_qml_module, so we just introduce the same option for qt6_add_plugin. Now user static plugins will have an _init target created, which will be propagated to consumers whenever the consumers link against the plugin itself. We also need an internal option to disable this propagation, because it's handled a bit differently for Qt plugins which can be linked either via finalizers or via usage requirements. Amends |
||
---|---|---|
.. | ||
aggregate | ||
corelib | ||
dbus | ||
embedded | ||
gui | ||
network | ||
opengl | ||
qmake | ||
qpa | ||
qtconcurrent | ||
qtestlib | ||
sql | ||
vulkan | ||
widgets | ||
xml | ||
CMakeLists.txt | ||
examples.pro | ||
README |
Qt is supplied with a number of example applications that have been written to provide developers with examples of the Qt API in use, highlight good programming practice, and showcase features found in each of Qt's core technologies. Documentation for examples can be found in the Examples section of the Qt documentation.