Help: Clarify preset-specific macros

Closes: #26030
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
This commit is contained in:
Cristian Le
2024-06-06 09:37:43 +02:00
committed by Brad King
parent c370593f2e
commit 1ea780ea7c
2 changed files with 9 additions and 3 deletions

View File

@@ -150,8 +150,9 @@ include files from anywhere.
Starting from version ``7``, the ``include`` field supports
`macro expansion`_, but only ``$penv{}`` macro expansion. Starting from version
``9``, other macro expansions are also available, except for preset specific
ones (e.g. ``presetName``), and ``$env{}``.
``9``, other macro expansions are also available, except for ``$env{}`` and
preset-specific macros, i.e., those derived from the fields inside a preset's
definition like ``presetName``.
Configure Preset
^^^^^^^^^^^^^^^^
@@ -1217,11 +1218,15 @@ Recognized macros include:
``${presetName}``
Name specified in the preset's ``name`` field.
This is a preset-specific macro.
``${generator}``
Generator specified in the preset's ``generator`` field. For build and
test presets, this will evaluate to the generator specified by
``configurePreset``.
This is a preset-specific macro.
``${hostSystemName}``
The name of the host operating system. Contains the same value as
:variable:`CMAKE_HOST_SYSTEM_NAME`. This is allowed in preset files

View File

@@ -15,7 +15,8 @@ Presets
* :manual:`cmake-presets(7)` files now support schema version ``9``.
``include`` fields now expand all macros except ``$env{}`` and
preset-specific macros.
preset-specific macros, i.e., those derived from the fields
inside a preset's definition.
File-Based API
--------------