c2efb3efcd
Revise docs for all "Scripting Commands", except four find_XXX that use a macro suite of their own. * Take full advantage of the improved syntax highlighting. * Make consequential use of <..> placeholders. * Clarify things here and there in the text. Specific improvements to some command docs: * "math": Correct description of novel hexadecimal capability. * "if", "foreach", "while": Provide link to "endif" etc * "foreach", "while": Mention "break" and "continue". * "foreach": Simplify explanation of ``RANGE`` and ``IN`` signatures; advise against negative arguments or reverse ranges (compare issue #18461) * "endif", "endfunction" etc: Explain that the argument is optional and maintained for compatibility only
25 lines
726 B
ReStructuredText
25 lines
726 B
ReStructuredText
mark_as_advanced
|
|
----------------
|
|
|
|
Mark cmake cached variables as advanced.
|
|
|
|
.. code-block:: cmake
|
|
|
|
mark_as_advanced([CLEAR|FORCE] <var1> ...)
|
|
|
|
Sets the advanced/non-advanced state of the named
|
|
cached variables.
|
|
|
|
An advanced variable will not be displayed in any
|
|
of the cmake GUIs unless the ``show advanced`` option is on.
|
|
In script mode, the advanced/non-advanced state has no effect.
|
|
|
|
If the keyword ``CLEAR`` is given
|
|
then advanced variables are changed back to unadvanced.
|
|
If the keyword ``FORCE`` is given
|
|
then the variables are made advanced.
|
|
If neither ``FORCE`` nor ``CLEAR`` is specified,
|
|
new values will be marked as advanced, but if a
|
|
variable already has an advanced/non-advanced state,
|
|
it will not be changed.
|