ENH: Created new install script generation framework. The INSTALL command creates the generators which are later used by cmLocalGenerator to create the cmake_install.cmake files. A new target installation interface is provided by the INSTALL command which fixes several problems with the INSTALL_TARGETS command. See bug#2691. Bugs 1481 and 1695 are addressed by these changes.

1 files changed, 23 insertions, 13 deletions

diff --git a/Source/cmSetTargetPropertiesCommand.h b/Source/cmSetTargetPropertiesCommand.h
index c24ec76..e3afd76 100644
--- a/Source/cmSetTargetPropertiesCommand.h
+++ b/Source/cmSetTargetPropertiesCommand.h
@@ -58,17 +58,25 @@ public:
         "Set properties on a target. The syntax for the command is to "
         "list all the files you want "
         "to change, and then provide the values you want to set next.  "
-        "Properties that cmake knows about are PREFIX and SUFFIX for UNIX "
-        "systems and libraries.   CMake also knows about LINK_FLAGS, which "
-        "can be used to add extra flags to the link step of a target. "
+        "You can use any prop value pair you want and "
+        "extract it later with the GET_TARGET_PROPERTY command.\n"
+        "Properties that affect the name of a target's output file are "
+        "as follows.  "
+        "The PREFIX and SUFFIX properties override the default target name "
+        "prefix (such as \"lib\") and suffix (such as \".so\"). "
+        "IMPORT_PREFIX and IMPORT_SUFFIX are the equivalent properties for "
+        "the import library corresponding to a DLL "
+        "(for SHARED library targets).  "
+        "OUTPUT_NAME sets the real name of a target when it is built and "
+        "can be used to help create two targets of the same name even though "
+        "CMake requires unique logical target names.\n"
+        "The LINK_FLAGS property can be used to add extra flags to the "
+        "link step of a target. "
         "DEFINE_SYMBOL sets the name of the preprocessor symbol defined when "
         "compiling sources in a shared library. "
         "If not set here then it is set to target_EXPORTS by default "
         "(with some substitutions if the target is not a valid C "
-        "identifier). "
-        "PRE_INSTALL_SCRIPT specifies a CMake script that is run "
-        "prior to installing the target. POST_INSTALL_SCRIPT specifies "
-        "a CMake script that is run after target is installed. "
+        "identifier).\n"
         "For shared libraries VERSION and SOVERSION can be used to specify "
         "the build version and api version respectively. When building or "
         "installing appropriate symlinks are created if the platform "
@@ -77,9 +85,7 @@ public:
         "the same version number. "
         "For executables VERSION can be used to specify the build version. "
         "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.\n"
+        "the platform supports symlinks.\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). "
@@ -96,9 +102,13 @@ public:
         "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 "
-        "works better if this is set to Qt4VSv1.0. "
-        "You can use any prop value pair you want and "
-        "extract it later with the GET_TARGET_PROPERTY command.";
+        "works better if this is set to Qt4VSv1.0.\n"
+        "The PRE_INSTALL_SCRIPT and POST_INSTALL_SCRIPT properties are the "
+        "old way to specify CMake scripts to run before and after "
+        "installing a target.  They are used only when the old "
+        "INSTALL_TARGETS command is used to install the target.  Use the "
+        "INSTALL command instead."
+        ;
     }
   
   cmTypeMacro(cmSetTargetPropertiesCommand, cmCommand);