![]() ![]() NAMELINK_SKIP option installs the library and the NAMELINK_ONLY On platforms where versioned shared librariesĭo not have namelinks or when a library is not versioned the The NAMELINK_SKIP optionĬauses installation of library files other than the namelink when a Namelink when a library target is installed. The NAMELINK_ONLY option causes installation of only the Is a “namelink” allowing linkers to find the library when given Where lib.so.1 is the soname of the library and lib.so On some platforms a versioned shared library See documentation of theĮither NAMELINK_ONLY or NAMELINK_SKIP may be specified as a Rulesĭefined by these arguments are ignored on Apple platforms because theĪssociated files are installed into the appropriate locations inside Shared library target’s associated files on non-Apple platforms. The PRIVATE_HEADER, PUBLIC_HEADER, and RESOURCE argumentsĬause subsequent properties to be applied to installing a FRAMEWORK Installed (which can be used to install just a DLL or just an import If only one is given then only targets of that type will be If none is given the installation properties apply to all target The ARCHIVE, LIBRARY, RUNTIME, OBJECTS, and FRAMEWORKĪrguments change the type of target to which the subsequent propertiesĪpply. Libraries are always treated as OBJECTS targets. Part of a shared library is treated as a RUNTIME target and theĬorresponding import library is treated as an ARCHIVE target.Īll Windows-based systems including Cygwin are DLL platforms. Targets, except that those marked with the FRAMEWORK property are Module libraries are always treated as LIBRARY targets.įor non-DLL platforms shared libraries are treated as LIBRARY Static libraries are treated as ARCHIVE targets,Įxcept that those marked with the FRAMEWORK property are treated ![]() Those marked with the MACOSX_BUNDLE property are treated as BUNDLE ![]() Executables are treated as RUNTIME targets, except that There are six kinds of target files that may be installed:ĪRCHIVE, LIBRARY, RUNTIME, OBJECTS, FRAMEWORK, andīUNDLE. The TARGETS form specifies rules for installing targets from a OPTIONAL Specify that it is not an error if the file to be installed doesĬommand signatures that install files may print messages during Renaming is allowed only when a single file is Installed as part of a component-specific installation RENAME Specify a name for an installed file that may be different from the EXCLUDE_FROM_ALL Specify that the file is excluded from a full installation and only The default component name may be controlled with theĬMAKE_INSTALL_DEFAULT_COMPONENT_NAME variable. If COMPONENT is not provided a default component “Unspecified” isĬreated. During a full installationĪll components are installed unless marked with EXCLUDE_FROM_ALL. The given component name will be executed. DuringĬomponent-specific installation only install rules associated with Is associated, such as “runtime” or “development”. COMPONENT Specify an installation component name with which the install rule CONFIGURATIONS Specify a list of build configurations for which the install ruleĪpplies (Debug, Release, etc.). Not make sense on certain platforms are ignored on those platforms. GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE, OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ, PERMISSIONS Specify permissions for installed files. Mechanism explained in the CMAKE_INSTALL_PREFIX variableĭocumentation. The prefix can be relocated at install time using the DESTDIR Relative to the value of the CMAKE_INSTALL_PREFIX variable. If a relative path is given it is interpreted If a full path (with a leading slash or drive letter) is given The common options are: DESTINATION Specify the directory on disk to which a file will be installed. Multiple signatures are covered here but they are valid only for Installation options for files and targets. There are multiple signatures for this command. Specified by calls to this command within a source directory areĮxecuted in order during installation. This command generates installation rules for a project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |