ENH: Implemented RPATH specification support. It is documented by the command SET_TARGET_PROPERTIES.

1 files changed, 14 insertions, 1 deletions

diff --git a/Source/cmSetTargetPropertiesCommand.h b/Source/cmSetTargetPropertiesCommand.h
index 5d5b23d2eb..f4cb976a63 100644
--- a/Source/cmSetTargetPropertiesCommand.h
+++ b/Source/cmSetTargetPropertiesCommand.h
@@ -79,7 +79,20 @@ public:
         "When building or installing appropriate symlinks are created if "
         "the platform supports symlinks. "
         "The OUTPUT_NAME can be used to set an output name that is "
-        "used in place of the target name when creating executables. "
+        "used in place of the target name when creating executables.\n"
+        "There are a few properties used to specify RPATH rules. "
+        "INSTALL_RPATH is a semicolon-separated list specifying the rpath "
+        "to use in installed targets (for platforms that support it). "
+        "SKIP_BUILD_RPATH is a boolean specifying whether to skip automatic "
+        "generation of an rpath allowing the target to run from the "
+        "build tree. "
+        "BUILD_WITH_INSTALL_RPATH is a boolean specifying whether to link "
+        "the target in the build tree with the INSTALL_RPATH.  This takes "
+        "precedence over SKIP_BUILD_RPATH and avoids the need for relinking "
+        "before installation. When the target is created the values of "
+        "the variables CMAKE_INSTALL_RPATH, CMAKE_SKIP_BUILD_RPATH, and "
+        "CMAKE_BUILD_WITH_INSTALL_RPATH are used to initialize these "
+        "properties.\n"
         "PROJECT_LABEL can be used to change the name of "
         "the target in an IDE like visual studio.  VS_KEYWORD can be set "
         "to change the visual studio keyword, for example QT integration "