2022-07-05 11:26:52 +00:00
|
|
|
# Copyright (C) 2022 The Qt Company Ltd.
|
2022-08-19 13:21:34 +00:00
|
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
2022-07-05 11:26:52 +00:00
|
|
|
|
2022-12-08 13:56:15 +00:00
|
|
|
#! [0]
|
CMake: Create plugin initializers for static user plugins
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 91c65dd80cdd2de666448c14202c0c63718152b6
As a result of the implementation change, cleanup example projects
to ensure that they build successfully (the important part is
specifying the CLASS_NAME).
Only plugandpaint works properly with both shared and static Qt
builds.
echoplugin works with a shared Qt build, but not a static one due to
some assumptions in the C++ code about shared plugins.
styleplugin doesn't seem to work properly neither with shared Qt
builds nor static Qt builds, at least on macOS. But it builds fine.
For some reason even if the plugin is found, the style is not applied.
Amends 4caac1feea025b0ad496141e8f16ab88c04c2caa
Pick-to: 6.2
Task-number: QTBUG-80863
Task-number: QTBUG-92933
Change-Id: I6f631cda9566229b7a63992b23d7d7fa50303eeb
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2021-08-19 09:42:12 +00:00
|
|
|
qt_add_plugin(simplestyleplugin
|
|
|
|
|
CLASS_NAME SimpleStylePlugin
|
2019-06-04 15:08:47 +00:00
|
|
|
simplestyle.cpp simplestyle.h
|
|
|
|
|
simplestyleplugin.cpp simplestyleplugin.h
|
2019-03-20 12:41:37 +00:00
|
|
|
)
|
2022-12-08 13:56:15 +00:00
|
|
|
#! [0]
|
2021-12-08 16:25:35 +00:00
|
|
|
|
2022-12-08 13:56:15 +00:00
|
|
|
if(QT_FEATURE_debug AND APPLE)
|
|
|
|
|
set_property(simplestyleplugin
|
|
|
|
|
APPEND_STRING PROPERTY OUTPUT_NAME "_debug")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
get_target_property(is_bundle styleplugin MACOSX_BUNDLE)
|
|
|
|
|
if(APPLE AND is_bundle)
|
|
|
|
|
#! [1]
|
|
|
|
|
set_target_properties(simplestyleplugin PROPERTIES
|
|
|
|
|
LIBRARY_OUTPUT_DIRECTORY "$<TARGET_BUNDLE_CONTENT_DIR:styleplugin>/PlugIns/styles"
|
|
|
|
|
)
|
|
|
|
|
#! [1]
|
|
|
|
|
else()
|
|
|
|
|
#! [2]
|
|
|
|
|
set_target_properties(simplestyleplugin PROPERTIES
|
|
|
|
|
LIBRARY_OUTPUT_DIRECTORY "$<TARGET_FILE_DIR:styleplugin>/styles"
|
|
|
|
|
)
|
|
|
|
|
#! [2]
|
|
|
|
|
endif()
|
2021-12-08 16:25:35 +00:00
|
|
|
|
CMake: Create plugin initializers for static user plugins
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 91c65dd80cdd2de666448c14202c0c63718152b6
As a result of the implementation change, cleanup example projects
to ensure that they build successfully (the important part is
specifying the CLASS_NAME).
Only plugandpaint works properly with both shared and static Qt
builds.
echoplugin works with a shared Qt build, but not a static one due to
some assumptions in the C++ code about shared plugins.
styleplugin doesn't seem to work properly neither with shared Qt
builds nor static Qt builds, at least on macOS. But it builds fine.
For some reason even if the plugin is found, the style is not applied.
Amends 4caac1feea025b0ad496141e8f16ab88c04c2caa
Pick-to: 6.2
Task-number: QTBUG-80863
Task-number: QTBUG-92933
Change-Id: I6f631cda9566229b7a63992b23d7d7fa50303eeb
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2021-08-19 09:42:12 +00:00
|
|
|
target_link_libraries(simplestyleplugin PRIVATE
|
2022-11-14 13:49:32 +00:00
|
|
|
Qt6::Core
|
|
|
|
|
Qt6::Gui
|
|
|
|
|
Qt6::Widgets
|
2020-02-04 07:15:50 +00:00
|
|
|
)
|
2019-03-20 12:41:37 +00:00
|
|
|
|
2020-02-04 07:15:50 +00:00
|
|
|
install(TARGETS simplestyleplugin
|
|
|
|
|
RUNTIME DESTINATION "${INSTALL_EXAMPLEDIR}"
|
|
|
|
|
LIBRARY DESTINATION "${INSTALL_EXAMPLEDIR}"
|
|
|
|
|
)
|
