Help: XCFrameworks and stubs are supported on all Apple, not just macOS

This commit is contained in:
Craig Scott
2023-12-09 16:14:53 +11:00
parent 6ac50df591
commit 01735badee
4 changed files with 14 additions and 18 deletions

View File

@@ -68,9 +68,9 @@ Each ``<item>`` may be:
.. 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.
The library file may point to a ``.xcframework`` folder on Apple platforms.
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

View File

@@ -35,8 +35,8 @@ the property instead for backward compatibility reasons.
See below for alternative initialization behavior for shared library targets.
.. versionadded:: 3.27
On Apple platforms, to link with a shared library (either a bare library or a
framework), a linker import file can be used instead of the actual shared
To link with a shared library on macOS, or to a shared framework on any Apple
platform, a linker import file can be used instead of the actual shared
library. These linker import files are also known as text-based stubs, and
they have a ``.tbd`` file extension.

View File

@@ -10,10 +10,10 @@ This property may be set:
On AIX, to an import file (e.g. ``.imp``) created for executables that
export symbols (see the :prop_tgt:`ENABLE_EXPORTS` target property).
* .. versionadded:: 3.27
On macOS platforms, to an import file (e.g. ``.tbd``) created for shared
libraries (see the :prop_tgt:`ENABLE_EXPORTS` target property).
For frameworks this is the location of the ``.tbd`` file symlink just
inside the framework folder.
On Apple platforms, to an import file (e.g. ``.tbd``) created for shared
libraries or frameworks (see the :prop_tgt:`ENABLE_EXPORTS` target
property). For frameworks, this is the location of the ``.tbd`` file
symlink just inside the framework folder.
* .. versionadded:: 3.28
On non-DLL platforms, to the location of a shared library.
When set without also specifying an :prop_tgt:`IMPORTED_LOCATION`,

View File

@@ -17,14 +17,10 @@ non-imported targets.
.. versionadded:: 3.28
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.
For ordinary frameworks on Apple platforms, this may be the location of the
``.framework`` folder itself. For XCFrameworks, it may be the location of
the ``.xcframework`` folder, in which case 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
@@ -38,5 +34,5 @@ selected and its :prop_tgt:`IMPORTED_LOCATION_<CONFIG>` value used.
To get the location of an imported target read one of the :prop_tgt:`LOCATION`
or ``LOCATION_<CONFIG>`` properties.
For platforms with import libraries (e.g. Windows, AIX or macOS) see also
For platforms with import libraries (e.g. Windows, AIX or Apple) see also
:prop_tgt:`IMPORTED_IMPLIB`.