summaryrefslogtreecommitdiffstats
path: root/Source/cmPolicies.cxx
diff options
context:
space:
mode:
Diffstat (limited to 'Source/cmPolicies.cxx')
-rw-r--r--Source/cmPolicies.cxx43
1 files changed, 7 insertions, 36 deletions
diff --git a/Source/cmPolicies.cxx b/Source/cmPolicies.cxx
index ffba3cb..0d35b65 100644
--- a/Source/cmPolicies.cxx
+++ b/Source/cmPolicies.cxx
@@ -359,17 +359,19 @@ cmPolicies::cmPolicies()
this->DefinePolicy(
CMP0012, "CMP0012",
"The if() command can recognize named boolean constants.",
- "In CMake versions prior to 2.6.5 the only boolean constants were 0 "
+ "In CMake versions 2.6.4 and lower the only boolean constants were 0 "
"and 1. Other boolean constants such as true, false, yes, no, "
"on, off, y, n, notfound, ignore (all case insensitive) were recognized "
- "in some cases but not all. In later versions of cmake these values are "
+ "in some cases but not all. "
+ "For example, the code \"if(TRUE)\" might have evaluated as false. "
+ "In later versions of cmake these values are "
"treated as boolean constants more consistently and should not be used "
"as variable names. "
"The OLD behavior for this policy is to allow variables to have names "
"such as true and to dereference them. "
"The NEW behavior for this policy is to treat strings like true as a "
"boolean constant.",
- 2,6,5, cmPolicies::WARN);
+ 2,8,0, cmPolicies::WARN);
this->DefinePolicy(
CMP0013, "CMP0013",
@@ -380,13 +382,13 @@ cmPolicies::cmPolicies()
"overwritten in the build tree and could lead to strange behavior. "
"CMake 2.6.4 and above explicitly detect duplicate binary directories. "
"CMake 2.6.4 always considers this case an error. "
- "In CMake 2.6.5 and above this policy determines whether or not "
+ "In CMake 2.8.0 and above this policy determines whether or not "
"the case is an error. "
"The OLD behavior for this policy is to allow duplicate binary "
"directories. "
"The NEW behavior for this policy is to disallow duplicate binary "
"directories with an error.",
- 2,6,5, cmPolicies::WARN);
+ 2,8,0, cmPolicies::WARN);
this->DefinePolicy(
CMP0014, "CMP0014",
@@ -399,37 +401,6 @@ cmPolicies::cmPolicies()
"The OLD behavior for this policy is to silently ignore the problem. "
"The NEW behavior for this policy is to report an error.",
2,8,0, cmPolicies::WARN);
-
- this->DefinePolicy(
- CMP0015, "CMP0015",
- "The set() CACHE mode and option() command make the cache value visible.",
- "In CMake 2.6 and below the CACHE mode of the set() command and the "
- "option() command did not expose the value from the named cache entry "
- "if it was already set both in the cache and as a local variable. "
- "This led to subtle differences between first and later configurations "
- "because a conflicting local variable would be overridden only when the "
- "cache value was first created. "
- "For example, the code\n"
- " set(x 1)\n"
- " set(before ${x})\n"
- " set(x 2 CACHE STRING \"X\")\n"
- " set(after ${x})\n"
- " message(STATUS \"${before},${after}\")\n"
- "would print \"1,2\" on the first run and \"1,1\" on future runs."
- "\n"
- "CMake 2.8.0 and above prefer to expose the cache value in all cases by "
- "removing the local variable definition, but this changes behavior in "
- "subtle cases when the local variable has a different value than that "
- "exposed from the cache. "
- "The example above will always print \"1,2\"."
- "\n"
- "This policy determines whether the commands should always expose the "
- "cache value. "
- "The OLD behavior for this policy is to leave conflicting local "
- "variable values untouched and hide the true cache value. "
- "The NEW behavior for this policy is to always expose the cache value.",
- 2,8,0, cmPolicies::WARN);
-
}
cmPolicies::~cmPolicies()