#CMAKE INSTALL MAN PAGES INSTALL#
Will have build errors.) If you install only the Libraries component, Namelink will be a dangling symlink, and projects that link to the library (If you don't also install the Libraries component, the In this scenario, if you choose to install only the DevelopmentĬomponent, both the headers and namelink will be installed without the Install( TARGETS mylib LIBRARY COMPONENT Libraries NAMELINK_COMPONENT Development PUBLIC_HEADER COMPONENT Development ) Subdirectory that follows the above recommendation: GNUInstallDirs, but with its headers installed to a project-specific 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 Project-specific subdirectory will need to provide a destination rather than 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: A destination can be omitted for interface and object libraries,īut they are handled differently (see the discussion of this topic toward the PUBLIC_HEADER and PRIVATE_HEADER target properties.Ī destination must always be provided for module libraries, Apple bundles andįrameworks. Public and private headers associated with the installed targets through the 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. Only targets of that type will be installed (which can be used to installįor regular executables, static libraries and shared libraries, theĭESTINATION argument is not required. Installation properties apply to all target types. To the target or file type specified in the argument. See RESOURCE for details.įor each of these arguments given, the arguments following them only apply Similar to PUBLIC_HEADER and PRIVATE_HEADER, but for Similar to PUBLIC_HEADER, but for PRIVATE_HEADER files. Into the appropriate locations inside the framework folder. Libraries on Apple platforms because the associated files are installed Rules defined by this argument are ignored for FRAMEWORK The destination specified by the PUBLIC_HEADER argument on non-Apple BUNDLEĮxecutables marked with the MACOSX_BUNDLE property are treated asĪny PUBLIC_HEADER files associated with a library are installed in Property are treated as FRAMEWORK targets on macOS. FRAMEWORKīoth static and shared libraries marked with the FRAMEWORK Object files associated with object libraries. (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). On macOS when marked as FRAMEWORK (see below). 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) There are several kinds of target Output Artifacts The TARGETS form specifies rules for installing targets from a Release configurations, do the following: For example, to set separate install paths for the Debug and This option only apply to options listed AFTER the 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, 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 kommentar(er)
