summaryrefslogtreecommitdiffstats
path: root/Help
diff options
context:
space:
mode:
authorKyle Edwards <kyle.edwards@kitware.com>2022-07-06 15:45:02 (GMT)
committerKyle Edwards <kyle.edwards@kitware.com>2022-07-06 16:03:53 (GMT)
commit52164be69156b16ea7592b8b46820c80d9a70be9 (patch)
treee26438ce6aa017751c125aad0dbf668465d9e6ac /Help
parentad2e7f3c537dc88ea8140bab67c43d25695637f1 (diff)
downloadCMake-52164be69156b16ea7592b8b46820c80d9a70be9.zip
CMake-52164be69156b16ea7592b8b46820c80d9a70be9.tar.gz
CMake-52164be69156b16ea7592b8b46820c80d9a70be9.tar.bz2
Help: Clarify behavior of install(TARGETS) for DLLs
Fixes: #23695
Diffstat (limited to 'Help')
-rw-r--r--Help/command/install.rst12
1 files changed, 9 insertions, 3 deletions
diff --git a/Help/command/install.rst b/Help/command/install.rst
index 973aa31..54e7053 100644
--- a/Help/command/install.rst
+++ b/Help/command/install.rst
@@ -217,9 +217,7 @@ that may be installed:
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
-installation properties apply to all target types. If only one is given then
-only targets of that type will be installed (which can be used to install
-just a DLL or just an import library.)
+installation properties apply to all target types.
For regular executables, static libraries and shared libraries, the
``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
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
built-in defaults that apply when no destination is given: