diff options
author | Brad King <brad.king@kitware.com> | 2022-03-22 13:49:11 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2022-03-22 15:57:48 (GMT) |
commit | 41a6b4a53ba844ef986b0bc4efe8938b97eea810 (patch) | |
tree | dfb3e49b2b54cb24865ecf15d67cc3d8ba52c55f /Help/manual | |
parent | 73337cb383a704664a47fd3fec84c8feaa303995 (diff) | |
download | CMake-41a6b4a53ba844ef986b0bc4efe8938b97eea810.zip CMake-41a6b4a53ba844ef986b0bc4efe8938b97eea810.tar.gz CMake-41a6b4a53ba844ef986b0bc4efe8938b97eea810.tar.bz2 |
INTERFACE_LINK_LIBRARIES_DIRECT: Honor link dependencies through LINK_ONLY
In commit f3ad061858 (Add usage requirements to update direct link
dependencies, 2022-01-12, v3.23.0-rc1~44^2), we evaluated the transitive
closure of `INTERFACE_LINK_LIBRARIES` as a non-linking usage requirement.
That left out `INTERFACE_LINK_LIBRARIES_DIRECT` link dependencies that
appear behind private dependencies of a static library, guarded by the
`$<LINK_ONLY:...>` generator expression. At the time, that decision was
intentional, in order to prevent arbitrary usage requirements from
leaking out of `PRIVATE` dependencies.
Since then, we've revised evaluation of `LINK_LIBRARIES` to distinguish
between collecting link dependencies and other usage requirements. Use
that information when following `INTERFACE_LINK_LIBRARIES` to collect
the matching kind of requirements from `INTERFACE_LINK_LIBRARIES_DIRECT`.
Fixes: #22496
Diffstat (limited to 'Help/manual')
0 files changed, 0 insertions, 0 deletions