Remove use of qt_internal_module_info from qt_internal_add_plugin
Plugin targets don't fit the requirements of the module but use the function associated to the module. The purpose of using qt_internal_module_info is to get the path to the top-level include directory. So there is no point in breaking the encapsulation rules to get a well-known directory. Change-Id: If3d2a31d4ec186929e3d662a79a1ae9eac988d1a Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
This commit is contained in:
parent
1e8b085f8c
commit
ae70011377
@ -23,8 +23,6 @@ endmacro()
|
||||
# A CMake target is created with the given target. The TYPE parameter is needed to place the
|
||||
# plugin into the correct plugins/ sub-directory.
|
||||
function(qt_internal_add_plugin target)
|
||||
qt_internal_module_info(module "${target}")
|
||||
|
||||
qt_internal_set_qt_known_plugins("${QT_KNOWN_PLUGINS}" "${target}")
|
||||
|
||||
_qt_internal_get_add_plugin_keywords(
|
||||
@ -230,7 +228,7 @@ function(qt_internal_add_plugin target)
|
||||
"${CMAKE_CURRENT_SOURCE_DIR}"
|
||||
"${CMAKE_CURRENT_BINARY_DIR}"
|
||||
# For the syncqt headers
|
||||
"$<BUILD_INTERFACE:${module_repo_include_dir}>"
|
||||
"$<BUILD_INTERFACE:${QT_BUILD_DIR}/include>"
|
||||
${arg_INCLUDE_DIRECTORIES}
|
||||
)
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user