RPATH: Docs use inline code markup for RPATH

This commit is contained in:
Robert Maynard authored and Brad King committed 2026-11-03 09:52:46 -05:00
1 parent defb221446
commit 2d4a6a6fbd
2 files changed
+13 -13

No files matched your search

+6 -6
View File
@@ -1,18 +1,18 @@
CMAKE_SKIP_BUILD_RPATH
----------------------
Do not include RPATHs in the build tree.
Do not include ``RPATHs`` in the build tree.
Normally CMake uses the build tree for the RPATH when building
executables etc on systems that use RPATH. When the software is
Normally CMake uses the build tree for the ``RPATH`` when building
executables etc on systems that use ``RPATH``. When the software is
installed the executables etc are relinked by CMake to have the
install RPATH. If this variable is set to ``TRUE`` then the software is
always built with no RPATH.
install ``RPATH``. If this variable is set to ``TRUE`` then the software
is always built with no ``RPATH``.
This is used to initialize the :prop_tgt:`SKIP_BUILD_RPATH` target property
for all targets. For more information on RPATH handling see
the :prop_tgt:`INSTALL_RPATH` and :prop_tgt:`BUILD_RPATH` target properties.
See also the :variable:`CMAKE_SKIP_INSTALL_RPATH` variable.
To omit RPATH in both the build and install steps, use
To omit ``RPATH`` in both the build and install steps, use
:variable:`CMAKE_SKIP_RPATH` instead.
+7 -7
View File
@@ -1,18 +1,18 @@
CMAKE_SKIP_INSTALL_RPATH
------------------------
Do not include RPATHs in the install tree.
Do not include ``RPATHs`` in the install tree.
Normally CMake uses the build tree for the RPATH when building
executables etc on systems that use RPATH. When the software is
Normally CMake uses the build tree for the ``RPATH`` when building
executables etc on systems that use ``RPATH``. When the software is
installed the executables etc are relinked by CMake to have the
install RPATH. If this variable is set to true then the software is
always installed without RPATH, even if RPATH is enabled when
install ``RPATH``. If this variable is set to true then the software is
always installed without ``RPATH``, even if ``RPATH`` is enabled when
building. This can be useful for example to allow running tests from
the build directory with RPATH enabled before the installation step.
the build directory with ``RPATH`` enabled before the installation step.
See also the :variable:`CMAKE_SKIP_BUILD_RPATH` variable.
To omit RPATH in both the build and install steps, use
To omit ``RPATH`` in both the build and install steps, use
:variable:`CMAKE_SKIP_RPATH` instead.
For more information on RPATH handling see the :prop_tgt:`INSTALL_RPATH`