There are five kinds of target files that may be installed: ARCHIVE, LIBRARY, RUNTIME, FRAMEWORK, and BUNDLE. ) The TARGETS form specifies rules for installing targets from a project. installing Targets install ( TARGETS targets. Use the CMAKE_INSTALL_MESSAGE variable to control which messages are printed. Command signatures that install files may print messages during installation. OPTIONAL Specify that it is not an error if the file to be installed does not exist. Renaming is allowed only when a single file is installed by the command. RENAME Specify a name for an installed file that may be different from the original file. The default component name may be controlled with the CMAKE_INSTALL_DEFAULT_COMPONENT_NAME variable. If COMPONENT is not provided a default component “Unspecified” is created. During a full installation all components are installed. During component-specific installation only install rules associated with the given component name will be executed. COMPONENT Specify an installation component name with which the install rule is associated, such as “runtime” or “development”. CONFIGURATIONS Specify a list of build configurations for which the install rule applies (Debug, Release, etc.). Permissions that do not make sense on certain platforms are ignored on those platforms.

Valid permissions are OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ, GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE, WORLD_EXECUTE, SETUID, and SETGID. PERMISSIONS Specify permissions for installed files. The prefix can be relocated at install time using the DESTDIR mechanism explained above. If a relative path is given it is interpreted relative to the value of the CMAKE_INSTALL_PREFIX variable. If a full path (with a leading slash or drive letter) is given it is used directly. The common options are: DESTINATION Specify the directory on disk to which a file will be installed. Options common to multiple signatures are covered here but they are valid only for signatures that specify them. Some of them define installation options for files and targets. There are multiple signatures for this command. Rules specified by calls to this command within a source directory are executed in order during installation.The order across directories is not defined. This command generates installation rules for a project. WARNING: DESTDIR may not be used on Windows because installation prefix usually contains a drive letter like in C:/Program Files which cannot be prepended with some other prefix. usr/local prepended with the DESTDIR value which finally gives /home/john/usr/local. Which will install the concerned software using the installation prefix, e.g.

Cmake install prefix