mirror of
https://github.com/Kitware/CMake.git
synced 2026-02-26 10:48:38 -06:00
Merge topic 'help-syntax-highlighting'
93f3f65516Help: Revise docs of modules AddFileDependencies..CheckFunctionExistsfc7ee1ca45Help: Override pygments CMakeLexer to support <..> and [..]74b3eacdc7Help: Use appropriate list types in FindPkgConfig Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2468
This commit is contained in:
@@ -5,8 +5,8 @@ Execute one or more child processes.
|
||||
|
||||
.. code-block:: cmake
|
||||
|
||||
execute_process(COMMAND <cmd1> [args1...]]
|
||||
[COMMAND <cmd2> [args2...] [...]]
|
||||
execute_process(COMMAND <cmd1> [<arguments>]
|
||||
[COMMAND <cmd2> [<arguments>]]...
|
||||
[WORKING_DIRECTORY <directory>]
|
||||
[TIMEOUT <seconds>]
|
||||
[RESULT_VARIABLE <variable>]
|
||||
|
||||
@@ -206,9 +206,10 @@ enclosed content, such as `Escape Sequences`_ or `Variable References`_,
|
||||
is performed. A bracket argument is always given to the command
|
||||
invocation as exactly one argument.
|
||||
|
||||
For example:
|
||||
.. No code-block syntax highlighting in the following example
|
||||
(long string literal not supported by our cmake.py)
|
||||
|
||||
.. code-block:: cmake
|
||||
For example::
|
||||
|
||||
message([=[
|
||||
This is the first line in a bracket argument with bracket length 1.
|
||||
@@ -253,9 +254,10 @@ closing quotes. Both `Escape Sequences`_ and `Variable References`_
|
||||
are evaluated. A quoted argument is always given to the command
|
||||
invocation as exactly one argument.
|
||||
|
||||
For example:
|
||||
.. No code-block syntax highlighting in the following example
|
||||
(escape \" not supported by our cmake.py)
|
||||
|
||||
::
|
||||
For example::
|
||||
|
||||
message("This is a quoted argument containing multiple lines.
|
||||
This is always one argument even though it contains a ; character.
|
||||
@@ -264,11 +266,12 @@ For example:
|
||||
It does end in an unescaped double quote.
|
||||
")
|
||||
|
||||
.. No code-block syntax highlighting in the following example
|
||||
(for conformity with the two above examples)
|
||||
|
||||
The final ``\`` on any line ending in an odd number of backslashes
|
||||
is treated as a line continuation and ignored along with the
|
||||
immediately following newline character. For example:
|
||||
|
||||
.. code-block:: cmake
|
||||
immediately following newline character. For example::
|
||||
|
||||
message("\
|
||||
This is the first line of a quoted argument. \
|
||||
|
||||
@@ -3,14 +3,14 @@ CMP0049
|
||||
|
||||
Do not expand variables in target source entries.
|
||||
|
||||
CMake 2.8.12 and lower performed and extra layer of variable expansion
|
||||
when evaluating source file names:
|
||||
|
||||
.. code-block:: cmake
|
||||
CMake 2.8.12 and lower performed an extra layer of variable expansion
|
||||
when evaluating source file names::
|
||||
|
||||
set(a_source foo.c)
|
||||
add_executable(foo \${a_source})
|
||||
|
||||
.. note: no cmake highlighting since this syntax is deprecated
|
||||
|
||||
This was undocumented behavior.
|
||||
|
||||
The OLD behavior for this policy is to expand such variables when processing
|
||||
|
||||
Reference in New Issue
Block a user