diff options
author | Shane Parris <shane.lee.parris@gmail.com> | 2020-02-10 22:26:28 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2020-02-11 13:45:35 (GMT) |
commit | 818ec34bddf3c5f838d3a3087d00e3a94e62cba4 (patch) | |
tree | e83ccdfa8b38998cdfe831848ae244e7d7a2a616 /Source/cmConditionEvaluator.cxx | |
parent | b620dc566de2b2f4c115c027151c34d3e08e255c (diff) | |
download | CMake-818ec34bddf3c5f838d3a3087d00e3a94e62cba4.zip CMake-818ec34bddf3c5f838d3a3087d00e3a94e62cba4.tar.gz CMake-818ec34bddf3c5f838d3a3087d00e3a94e62cba4.tar.bz2 |
file: GLOB_RECURSE VerifyGlobs.cmake should have CMP0009 set to new
In certain cases, rebuilds with CMake using the CONFIGURE_DEPENDS flag
with GLOB_RECURSE could result in a reconfigure loop due to CMP0009 not
being propogated to the generated VerifyGlobs.cmake script.
During the inital configuration phase, RecurseThroughSymlinksOn() is
called for recursive glob operations either by having the CMP0009 status
not set to NEW or by explicitly providing the FOLLOW_SYMLINKS flag. At
the end when the VerifyGlobs script is created, the FOLLOW_SYMLINKS flag
is written according to the final resolved form through a call to
GetRecurseThroughSymlinks(). Thus, setting CMP0009 to NEW in the
generated file is safe and allows correct behavior whether or not the
end user sets the policy status to NEW or OLD.
Diffstat (limited to 'Source/cmConditionEvaluator.cxx')
0 files changed, 0 insertions, 0 deletions