Browse Source

Help: Clarify CMP0126 OLD behavior for FORCE and INTERNAL

Fixes: #23022
Craig Scott 3 years ago
parent
commit
47168b2231
1 changed files with 3 additions and 0 deletions
  1. 3 0
      Help/policy/CMP0126.rst

+ 3 - 0
Help/policy/CMP0126.rst

@@ -14,6 +14,9 @@ current scope in the following situations:
   This can occur when the variable was set on the command line using a form
   like ``cmake -DMYVAR=blah`` instead of ``cmake -DMYVAR:STRING=blah``.
 
+* The ``FORCE`` or ``INTERNAL`` keywords were used when setting the cache
+  variable.
+
 Note that the ``NEW`` behavior has an important difference to the similar
 ``NEW`` behavior of policy :policy:`CMP0077`.  The :command:`set(CACHE)`
 command always sets the cache variable if it did not exist previously,