mirror/CMake
1
0
Fork 0
mirror of https://github.com/Kitware/CMake.git synced 2026-05-04 05:10:10 -05:00
Code Issues Packages Projects Releases Wiki Activity

Help: Clarify behavior of install(TARGETS) for DLLs

Browse Source 
Fixes: #23695
This commit is contained in:
Kyle Edwards
2022-07-06 11:45:02 -04:00
parent ad2e7f3c53
commit 52164be691
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Help/command/install.rst
+9 -3
View File
@@ -217,9 +217,7 @@ that may be installed:
For each of these arguments given, the arguments following them only apply For each of these arguments given, the arguments following them only apply
to the target or file type specified in the argument. If none is given, the to the target or file type specified in the argument. If none is given, the
installation properties apply to all target types. If only one is given then installation properties apply to all target types.
only targets of that type will be installed (which can be used to install
just a DLL or just an import library.)
For regular executables, static libraries and shared libraries, the For regular executables, static libraries and shared libraries, the
``DESTINATION`` argument is not required. For these target types, when ``DESTINATION`` argument is not required. For these target types, when
@@ -233,6 +231,14 @@ Apple bundles and frameworks. A destination can be omitted for interface and
object libraries, but they are handled differently (see the discussion of this object libraries, but they are handled differently (see the discussion of this
topic toward the end of this section). topic toward the end of this section).
For shared libraries on DLL platforms, if neither ``RUNTIME`` nor ``ARCHIVE``
destinations are specified, both the ``RUNTIME`` and ``ARCHIVE`` components are
installed to their default destinations. If either a ``RUNTIME`` or ``ARCHIVE``
destination is specified, the component is installed to that destination, and
the other component is not installed. If both ``RUNTIME`` and ``ARCHIVE``
destinations are specified, then both components are installed to their
respective destinations.
The following table shows the target types with their associated variables and The following table shows the target types with their associated variables and
built-in defaults that apply when no destination is given: built-in defaults that apply when no destination is given: