macOS: Add support for linking against .xcframework folders

Issue: #21752
This commit is contained in:
Kyle Edwards
2023-05-17 13:50:32 -04:00
parent 93ed53790c
commit 7050ac56a1
94 changed files with 828 additions and 6 deletions
+6
View File
@@ -66,6 +66,12 @@ Each ``<item>`` may be:
:ref:`usage requirement <Target Usage Requirements>`. This has the same
effect as passing the framework directory as an include directory.
.. versionadded:: 3.28
The library file may point to a ``.xcframework`` folder on macOS. If it
does, the target will get the selected library's ``Headers`` directory as
a usage requirement.
.. versionadded:: 3.8
On :ref:`Visual Studio Generators` for VS 2010 and above, library files
ending in ``.targets`` will be treated as MSBuild targets files and
+6
View File
@@ -20,6 +20,12 @@ non-imported targets.
For frameworks on macOS, this may be the location of the framework folder
itself.
.. versionadded:: 3.28
This may be the location of a ``.xcframework`` folder on macOS. If it is,
any target that links against it will get the selected library's ``Headers``
directory as a usage requirement.
The ``IMPORTED_LOCATION`` target property may be overridden for a
given configuration ``<CONFIG>`` by the configuration-specific
:prop_tgt:`IMPORTED_LOCATION_<CONFIG>` target property. Furthermore,
@@ -0,0 +1,7 @@
xcframework-target-link-libraries
---------------------------------
* Targets may now link against an ``.xcframework`` folder in
:command:`target_link_libraries`.
* The :prop_tgt:`IMPORTED_LOCATION` property of a target may now be an
``.xcframework`` folder.