diff options
| author | Alexandru Croitor <alexandru.croitor@qt.io> | 2025-02-13 16:33:59 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2025-02-13 19:33:41 (GMT) |
| commit | 2b314e9009aa8578cdd33a843c9e9f3ca8a57354 (patch) | |
| tree | 669dffa3ede8376caa3f467d45766bf728799c28 /Tests/RunCMake/FindPython/Python2Module.cmake | |
| parent | 3f2386db2b9e8490b8249234d7235e23b56ce237 (diff) | |
| download | CMake-2b314e9009aa8578cdd33a843c9e9f3ca8a57354.zip CMake-2b314e9009aa8578cdd33a843c9e9f3ca8a57354.tar.gz CMake-2b314e9009aa8578cdd33a843c9e9f3ca8a57354.tar.bz2 | |
Autogen: Fix missing autogen dependencies if a target is linked twice
Autogen contains code to forward dependencies from an origin target
to its associated <origin>_autogen target. This code also contains a
check to skip forwarding a dependency if it does not appear in the
dependency graph for all configured build types.
This is done by counting the number of times a dependency appears in
the graph for each configured build type.
Unfortunately the code did not account for the case when a dependency
appears more than once in the link graph for a single build type. This
means that for a single-config build, if the same dependency is linked
twice, the dependency will be skipped altogether.
This can lead to build errors in a project where a hypothetical App
target depends on a Lib target, and thus expects App_autogen to depend
on Lib_autogen and any of its dependencies, but the latter is skipped.
Fix this by incrementing the count of a target in the dependency graph
only once per build type.
Fixes: #26700
Diffstat (limited to 'Tests/RunCMake/FindPython/Python2Module.cmake')
0 files changed, 0 insertions, 0 deletions
