diff options
| author | Brad King <brad.king@kitware.com> | 2021-12-20 14:40:06 (GMT) |
|---|---|---|
| committer | Kitware Robot <kwrobot@kitware.com> | 2021-12-20 14:40:19 (GMT) |
| commit | 85833461af12c03f67d86167bd71fd9b198d99f5 (patch) | |
| tree | b9e7ce6d9f56570819a444259b34e89e5060d762 | |
| parent | af9fcbd006dca8489ef22d8ed5115894be35b2ac (diff) | |
| parent | 47168b22319a1610726c00c3c8a414a330e79a8a (diff) | |
| download | CMake-85833461af12c03f67d86167bd71fd9b198d99f5.zip CMake-85833461af12c03f67d86167bd71fd9b198d99f5.tar.gz CMake-85833461af12c03f67d86167bd71fd9b198d99f5.tar.bz2 | |
Merge topic 'doc-CMP0126-OLD'
47168b2231 Help: Clarify CMP0126 OLD behavior for FORCE and INTERNAL
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6818
| -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 1b69957..a389512 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, |