![]() ![]() The following example shows a static libraryīeing installed to the default destination provided by This allows package maintainers to control the install destination by setting Path that begins with the appropriate GNUInstallDirs variable. Projects must specify a DESTINATION, it is recommended that they use a To make packages compliant with distribution filesystem layout policies, if Instead of being able to rely on the above (see next example below). Otherwise, they must provide a DESTINATION Project-specific subdirectory may prefer using file sets with appropriate Projects wishing to follow the common practice of installing headers into a The following table shows the target types with their associated variables andīuilt-in defaults that apply when no destination is given: If both RUNTIME and ARCHIVEĭestinations are specified, then both components are installed to their If either a RUNTIME or ARCHIVEĭestination is specified, the component is installed to that destination, and Object libraries, but they are handled differently (see the discussion of thisįor shared libraries on DLL platforms, if neither RUNTIME nor ARCHIVEĭestinations are specified, both the RUNTIME and ARCHIVE components are A destination can be omitted for interface and A destination must always be provided for module libraries,Īpple bundles and frameworks. Targets through the PUBLIC_HEADER and PRIVATE_HEADER Sets, and the public and private headers associated with the installed For these target types, whenĭESTINATION is omitted, a default destination will be taken from theĪppropriate variable from GNUInstallDirs, or set to a built-inĭefault value if that variable is not defined. To suppress installing these files (for use in generic code).įor regular executables, static libraries and shared libraries, theĭESTINATION argument is not required. Modules are placed directly in the destination as no directory structure isĭerived from the names of the modules. Type CXX_MODULES will be installed to the given DESTINATION. (except on macOS when marked as MACOSX_BUNDLE, see BUNDLE below) ĭLLs (on all Windows-based systems including Cygwin note that theĪccompanying import libraries are of kind ARCHIVE).Īny module files from C++ modules from PUBLIC sources in a file set of On macOS when marked as FRAMEWORK (see below). On macOS, the linker import file created for shared libraries withĮNABLE_EXPORTS enabled (except when marked as FRAMEWORK, On AIX, the linker import file created for executables with (on all Windows-based systems including Cygwin they have extension (except on macOS when marked as FRAMEWORK, see below) Output Artifacts of the specified artifact kind: ARCHIVE ![]() Output Artifacts that do not have a dedicated group specified 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. ![]() Specify an installation component name with which the install rule If an install(TARGETS)Ĭonfigurations is accumulated for each kind of artifact. Specify a list of build configurations for which the install rule Is accumulated for each kind of artifact. Uses arguments, a separate list of permissions If this option is used multiple times in a single call, its list 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, In particular, there is no need to make paths absolute by prependingĬMAKE_INSTALL_PREFIX this prefix is used by default if Generators, it is preferable to use relative paths throughout. If an absolute path (with a leading slash or drive letter) is givenĪs absolute paths are not supported by cpack installer Mechanism explained in the CMAKE_INSTALL_PREFIX variable The prefix can be relocated at install time using the DESTDIR If a relative path is given it is interpreted relative to the value Specify the directory on disk to which a file will be installed.Īrguments can be relative or absolute paths. Multiple signatures are covered here but they are valid only for Installation options for files and targets. There are multiple signatures for this command. Changed in version 3.22: The environment variable CMAKE_INSTALL_MODE can override the ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |