From 9eecdc7ab7141e6bbd3289ed0172e942e20ace05 Mon Sep 17 00:00:00 2001 From: "FeRD (Frank Dana)" Date: Fri, 1 Sep 2023 21:23:34 +1000 Subject: Help: Use signature directive for cmake_policy() --- Help/command/cmake_policy.rst | 29 +++++++++++++++-------------- 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/Help/command/cmake_policy.rst b/Help/command/cmake_policy.rst index d7880bc..dff6c3c 100644 --- a/Help/command/cmake_policy.rst +++ b/Help/command/cmake_policy.rst @@ -24,9 +24,8 @@ The ``cmake_policy`` command is used to set policies to ``OLD`` or ``NEW`` behavior. While setting policies individually is supported, we encourage projects to set policies based on CMake versions: -.. code-block:: cmake - - cmake_policy(VERSION [...]) +.. signature:: cmake_policy(VERSION [...]) + :target: VERSION .. versionadded:: 3.12 The optional ```` version. @@ -57,10 +56,8 @@ command implicitly calls ``cmake_policy(VERSION)`` too. Setting Policies Explicitly ^^^^^^^^^^^^^^^^^^^^^^^^^^^ -.. code-block:: cmake - - cmake_policy(SET CMP NEW) - cmake_policy(SET CMP OLD) +.. signature:: cmake_policy(SET CMP NEW|OLD) + :target: SET Tell CMake to use the ``OLD`` or ``NEW`` behavior for a given policy. Projects depending on the old behavior of a given policy may silence a @@ -73,9 +70,8 @@ policy state to ``NEW``. Checking Policy Settings ^^^^^^^^^^^^^^^^^^^^^^^^ -.. code-block:: cmake - - cmake_policy(GET CMP ) +.. signature:: cmake_policy(GET CMP ) + :target: GET Check whether a given policy is set to ``OLD`` or ``NEW`` behavior. The output ```` value will be ``OLD`` or ``NEW`` if the @@ -94,15 +90,20 @@ except when invoked with the ``NO_POLICY_SCOPE`` option The ``cmake_policy`` command provides an interface to manage custom entries on the policy stack: -.. code-block:: cmake +.. signature:: cmake_policy(PUSH) + :target: PUSH + + Create a new entry on the policy stack. + +.. signature:: cmake_policy(POP) + :target: POP - cmake_policy(PUSH) - cmake_policy(POP) + Remove the last policy stack entry created with ``cmake_policy(PUSH)``. Each ``PUSH`` must have a matching ``POP`` to erase any changes. This is useful to make temporary changes to policy settings. Calls to the :command:`cmake_minimum_required(VERSION)`, -``cmake_policy(VERSION)``, or ``cmake_policy(SET)`` commands +:command:`cmake_policy(VERSION)`, or :command:`cmake_policy(SET)` commands influence only the current top of the policy stack. .. versionadded:: 3.25 -- cgit v0.12