summaryrefslogtreecommitdiffstats
path: root/Modules/FetchContent.cmake
diff options
context:
space:
mode:
authorAlex Turbov <i.zaufi@gmail.com>2022-11-06 00:05:00 (GMT)
committerAlex Turbov <i.zaufi@gmail.com>2022-11-06 00:28:21 (GMT)
commit029210730a6b87629d937e6e5037dc2302010fc8 (patch)
tree5d00c6dcfc0e3133ff69e3a5cf7ff2a945ebaf12 /Modules/FetchContent.cmake
parent295062ef4b3ae630c2d2a19baba1da41c28ac229 (diff)
downloadCMake-029210730a6b87629d937e6e5037dc2302010fc8.zip
CMake-029210730a6b87629d937e6e5037dc2302010fc8.tar.gz
CMake-029210730a6b87629d937e6e5037dc2302010fc8.tar.bz2
Help: Use role `:program:`
When mention execitable names use Sphinx semantic role `:program` instead of ``executable`` or **executable**.
Diffstat (limited to 'Modules/FetchContent.cmake')
-rw-r--r--Modules/FetchContent.cmake2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules/FetchContent.cmake b/Modules/FetchContent.cmake
index ac3918c..9acd0db 100644
--- a/Modules/FetchContent.cmake
+++ b/Modules/FetchContent.cmake
@@ -1047,7 +1047,7 @@ directory. The :variable:`CMAKE_TOOLCHAIN_FILE` variable is not used until
the :command:`project` command is reached, at which point CMake looks for the
named toolchain file relative to the build directory. Because the tarball has
already been downloaded and unpacked by then, the toolchain file will be in
-place, even the very first time that ``cmake`` is run in the build directory.
+place, even the very first time that :program:`cmake` is run in the build directory.
Populating Content In CMake Script Mode
"""""""""""""""""""""""""""""""""""""""