summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Maltese <michaeljosephmaltese@gmail.com>2017-02-22 12:32:13 -0800
committerMichael Maltese <michaeljosephmaltese@gmail.com>2017-02-22 13:39:09 -0800
commit1dc13019259bd62d63b9295011227029283c2ef7 (patch)
tree27cb3b9bfa061fac17cedb43b9ce93d7c0f6c5b0
parent6cbad490c2fdbd9bdc67b406b9f2dcdc21e08ddb (diff)
downloadcmake-1dc13019259bd62d63b9295011227029283c2ef7.tar.gz
Help: Clarify 'make-style' variable references in cmake-language(7)
Fixes: #16661
-rw-r--r--Help/manual/cmake-language.7.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/Help/manual/cmake-language.7.rst b/Help/manual/cmake-language.7.rst
index ba0b30fc73..27b5d30b4a 100644
--- a/Help/manual/cmake-language.7.rst
+++ b/Help/manual/cmake-language.7.rst
@@ -329,11 +329,17 @@ For example:
To support legacy CMake code, unquoted arguments may also contain
double-quoted strings (``"..."``, possibly enclosing horizontal
whitespace), and make-style variable references (``$(MAKEVAR)``).
+
Unescaped double-quotes must balance, may not appear at the
beginning of an unquoted argument, and are treated as part of the
content. For example, the unquoted arguments ``-Da="b c"``,
``-Da=$(v)``, and ``a" "b"c"d`` are each interpreted literally.
+ Make-style references are treated literally as part of the content
+ and do not undergo variable expansion. They are treated as part
+ of a single argument (rather than as separate ``$``, ``(``,
+ ``MAKEVAR``, and ``)`` arguments).
+
The above "unquoted_legacy" production represents such arguments.
We do not recommend using legacy unquoted arguments in new code.
Instead use a `Quoted Argument`_ or a `Bracket Argument`_ to