mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-05 21:31:08 -06:00
Merge topic 'doc-improvements'
d4d1f85297Help: Move a note about arguments and genexes into include file968224484fHelp: Drop unused `PROPERTY_GENEX` replace from `prop_tgt/INTERFACE_*` files65457e4faeHelp: Add _See Also_ sections to related CMake commandsc86ec79d07Help: Use direct refs to genexes instead of ``$<GENEX-NAME>``8c6274326dHelp: Use CMake highlighting for command synopsisc356a94512Help: Use monospaced font for a genex name in a section titlef98c8707f4Help: Use `code-block:: cmake` instead of `::` for sub-commands descriptions2ba351ca4fHelp: ``CMake`` → CMake ... Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7873
This commit is contained in:
@@ -6,4 +6,4 @@ CMAKE_DEPENDS_USE_COMPILER
|
||||
For the :ref:`Makefile Generators`, source dependencies are now, for a
|
||||
selection of compilers, generated by the compiler itself. By defining this
|
||||
variable with value ``FALSE``, you can restore the legacy behavior (i.e. using
|
||||
``CMake`` for dependencies discovery).
|
||||
CMake for dependencies discovery).
|
||||
|
||||
@@ -49,14 +49,14 @@
|
||||
* ``[/path/to/]FwName.framework/Versions/*/FwName[suffix]``
|
||||
|
||||
Note that CMake recognizes and automatically handles framework targets,
|
||||
even without using the ``$<LINK_LIBRARY:FRAMEWORK,...>`` expression.
|
||||
even without using the :genex:`$<LINK_LIBRARY:FRAMEWORK,...>` expression.
|
||||
The generator expression can still be used with a CMake target if the
|
||||
project wants to be explicit about it, but it is not required to do so.
|
||||
The linker command line may have some differences between using the
|
||||
generator expression or not, but the final result should be the same.
|
||||
On the other hand, if a file path is given, CMake will recognize some paths
|
||||
automatically, but not all cases. The project may want to use
|
||||
``$<LINK_LIBRARY:FRAMEWORK,...>`` for file paths so that the expected
|
||||
:genex:`$<LINK_LIBRARY:FRAMEWORK,...>` for file paths so that the expected
|
||||
behavior is clear.
|
||||
|
||||
.. versionadded:: 3.25
|
||||
|
||||
Reference in New Issue
Block a user