diff options
| author | Brad King <brad.king@kitware.com> | 2009-10-27 13:07:39 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2009-10-27 13:07:39 (GMT) |
| commit | cb185d93d29d27eaafd321f657f4ba12d9beaeb8 (patch) | |
| tree | caba9c82f1ce3f68a16a577dfff0deb4eda7506a /Source/cmMakefileExecutableTargetGenerator.cxx | |
| parent | 9f43fa602d53d131adffd1a3bb8188b549a96a01 (diff) | |
| download | CMake-cb185d93d29d27eaafd321f657f4ba12d9beaeb8.zip CMake-cb185d93d29d27eaafd321f657f4ba12d9beaeb8.tar.gz CMake-cb185d93d29d27eaafd321f657f4ba12d9beaeb8.tar.bz2 | |
Fix if() command and CMP0012 OLD/NEW behavior
The commit "modified the if command to address bug 9123 some" changed
the if() command behavior with respect to named boolean constants. It
introduced policy CMP0012 to provide compatibility. However, it also
changed behavior with respect to numbers (like '2') but did not cover
the change with the policy. Also, the behavior it created for numbers
is confusing ('2' is false).
This commit teaches if() to recognize numbers again, and treats them
like the C language does in terms of boolean conversion. We also fix
the CMP0012 check to trigger in all cases where the result of boolean
coersion differs from that produced by CMake 2.6.4.
Diffstat (limited to 'Source/cmMakefileExecutableTargetGenerator.cxx')
0 files changed, 0 insertions, 0 deletions