diff options
| author | Craig Scott <craig.scott@crascit.com> | 2021-12-20 21:24:50 +1100 |
|---|---|---|
| committer | Craig Scott <craig.scott@crascit.com> | 2021-12-20 21:24:50 +1100 |
| commit | 47168b22319a1610726c00c3c8a414a330e79a8a (patch) | |
| tree | 6c77a4175ee36aa382067f21ef9ba54ec06e3dfc /Help/policy | |
| parent | 6b5c836252f897a79d7293a951ab79fd1755f16b (diff) | |
| download | cmake-47168b22319a1610726c00c3c8a414a330e79a8a.tar.gz | |
Help: Clarify CMP0126 OLD behavior for FORCE and INTERNAL
Fixes: #23022
Diffstat (limited to 'Help/policy')
| -rw-r--r-- | Help/policy/CMP0126.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Help/policy/CMP0126.rst b/Help/policy/CMP0126.rst index 1b6995762d..a389512994 100644 --- a/Help/policy/CMP0126.rst +++ b/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, |