dilim/CMake
1
0
Fork 0
mirror of https://github.com/Kitware/CMake.git synced 2026-08-07 16:20:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Tutorial: Move multi-config install note to the first exercise

Browse Source 
The context is needed when running all exercises in this step.

Revise both this note and its mirror for `ctest` in Step 7 to
cross-reference the relevant flags.
This commit is contained in:
Tyler Yankee
2026-05-14 18:14:43 -04:00
parent 653356bed0
commit 4b093ae12e
2 changed files with 12 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
Help/guide/tutorial/Installation Commands and Concepts.rst
View File

@@ -187,6 +187,14 @@ No special configuration is needed, configure and build as usual.
We can verify the installation is correct with :option:`cmake --install`.
.. note::
As with CTest, when using a multi-config generator such as Visual Studio, it
will be necessary to specify a configuration like ``Debug`` or ``Release``
using :option:`cmake --install --config <cmake--install --config>`.
This is true whenever using a multi-config generator, and won't be called out
specifically in future commands.
.. code-block:: console
cmake --install build --prefix install
@@ -352,15 +360,6 @@ The build command is sufficient to reconfigure the project.
We can verify the installation is correct with :option:`cmake --install`.
.. note::
As with CTest, when using multi-config generator, eg Visual Studio, it will be
necessary to specify a configuration with
``cmake --install --config <config> <remaining flags>``, where
``<config>`` is a value like ``Debug`` or ``Release``. This is true whenever
using a multi-config generator, and won't be called out specifically in
future commands.
.. code-block:: console
cmake --install build --prefix install

9
Help/guide/tutorial/Testing and CTest.rst
View File

@@ -117,11 +117,10 @@ Verify all the tests pass with CTest.
.. note::
If using a multi-config generator, eg Visual Studio, it will be necessary to
specify a configuration with ``ctest -C <config> <remaining flags>``, where
``<config>`` is a value like ``Debug`` or ``Release``. This is true whenever
using a multi-config generator, and won't be called out specifically in
future commands.
When using a multi-config generator such as Visual Studio, it
will be necessary to specify a configuration like ``Debug`` or ``Release``
using :option:`ctest -C`. This is true whenever using a multi-config
generator, and won't be called out specifically in future commands.
.. code-block:: console