diff options
author | Joerg Bornemann <joerg.bornemann@qt.io> | 2021-07-06 18:24:11 +0200 |
---|---|---|
committer | Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> | 2021-07-06 20:02:57 +0000 |
commit | 3bb9dc32df973faeb2bd2c44c4c9883e0da493ba (patch) | |
tree | bbf07f20ca9c9e0a5f77de892752738d953911c7 /dependencies.yaml | |
parent | 546e6846eb641aa943aaca6ce0e650222c455482 (diff) | |
download | qtsvg-3bb9dc32df973faeb2bd2c44c4c9883e0da493ba.tar.gz |
CMake: Don't give plugins PUBLIC usage requirements
The pro2cmake.py conversion script faithfully reproduced the .pro files
for the plugins, which specified the libraries as public. But in CMake,
the implications of this are that public usage requirements should then
be propagated to consumers. We don't expect any consumers, since a
plugin is created as a MODULE library in CMake, so for Windows we don't
even have an import library to link with. The only exception to this is
for static builds where plugins are created as STATIC libraries
instead, but only in certain controlled situations do we then link to
plugins. Even then, usage requirements are not expected to propagate to
the consumers, so these relationships should always be specified as
private.
Task-number: QTBUG-90819
Change-Id: Ifa2d76d6bff7b29d746455aa070a77cbd06879f0
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit 80dd9dffbc7c7fa2c20954fcd23084f65120b83a)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Diffstat (limited to 'dependencies.yaml')
0 files changed, 0 insertions, 0 deletions