mirror/CMake
1
0
Fork 0
mirror of https://github.com/Kitware/CMake.git synced 2026-03-13 12:59:55 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge topic 'patch-CMakeExpandImportedTargets'

Browse Source 
0723c36ffc CMakeExpandImportedTargets: Sync documentation

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !10822
This commit is contained in:
Brad King
2025-05-28 13:03:14 +00:00
committed by Kitware Robot
parent 479f4f5e9a 0723c36ffc
commit 2e286b3cef
1 changed files with 17 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
Modules/CMakeExpandImportedTargets.cmake
View File

@@ -16,6 +16,12 @@ CMakeExpandImportedTargets
:command:`try_compile` command and since CMake 3.2 for :command:`try_run`
command).
Load this module in a CMake project with:
.. code-block:: cmake
include(CMakeExpandImportedTargets)
.. note::
This module does not support the policy :policy:`CMP0022` ``NEW`` behavior,
@@ -23,13 +29,17 @@ CMakeExpandImportedTargets
:manual:`generator expressions <cmake-generator-expressions(7)>` cannot be
evaluated at the configuration phase.
Functions
Commands
^^^^^^^^^
This module defines the following function:
This module provides the following command:
.. command:: cmake_expand_imported_targets
Expands all imported targets in a given list of libraries to their
corresponding file paths on disk and stores the resulting list in a local
variable:
.. code-block:: cmake
cmake_expand_imported_targets(
@@ -38,19 +48,18 @@ This module defines the following function:
[CONFIGURATION <config>]
)
Expands all imported targets in a list of libraries ``<libs>...`` to their
corresponding file paths on disk and stores the resulting list in a local
variable ``<result-var>``.
The arguments are:
The options are:
``<result-var>``
Name of a CMake variable containing the resulting list of file paths.
``LIBRARIES``
``LIBRARIES <libs>...``
A :ref:`semicolon-separated list <CMake Language Lists>` of system and
imported targets. Imported targets in this list are replaced with their
corresponding library file paths, including libraries from their link
interfaces.
``CONFIGURATION``
``CONFIGURATION <config>``
If this option is given, it uses the respective build configuration
``<config>`` of the imported targets if it exists. If omitted, it defaults
to the first entry in the :variable:`CMAKE_CONFIGURATION_TYPES` variable, or