summaryrefslogtreecommitdiffstats
path: root/Tests/FindPython/Python2Module
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2024-04-11 17:37:46 (GMT)
committerBrad King <brad.king@kitware.com>2024-04-11 22:35:40 (GMT)
commitc94cfe92eb579b07ab7a9bbb66d98090ec6fe840 (patch)
treec783b90c706b39003675487eb027c31afdb718e5 /Tests/FindPython/Python2Module
parent061f7a6b9756bafa2d3d2f0ce86b6abd2b2e4598 (diff)
downloadCMake-c94cfe92eb579b07ab7a9bbb66d98090ec6fe840.zip
CMake-c94cfe92eb579b07ab7a9bbb66d98090ec6fe840.tar.gz
CMake-c94cfe92eb579b07ab7a9bbb66d98090ec6fe840.tar.bz2
GenEx: Fix COMPATIBLE_INTERFACE_ evaluation outside usage requirements
In commit ff6c401309 (cmTarget: Add interface for compatible numeric properties, 2013-10-22, v3.0.0-rc1~460^2) the condition dagCheckerParent && !dagCheckerParent->EvaluatingLinkLibraries() was written that way to avoid a nullptr dereference, but is actually meant to say "is not evaluating link libraries". That can also be true when there is no `dagCheckerParent`, such as when evaluating a generator expression outside of usage requirements, e.g., for `add_custom_target`. The original commit tried to account for that by duplicating the implementation in another code path, but that did not work in all cases. Fix the condition, remove the duplication, and enable tests for the now-working cases.
Diffstat (limited to 'Tests/FindPython/Python2Module')
0 files changed, 0 insertions, 0 deletions