mirror/CMake
1
0
Fork 0
mirror of https://github.com/Kitware/CMake.git synced 2026-04-20 13:22:22 -05:00
Code Issues Packages Projects Releases Wiki Activity

Help: add and make references to generators consistent

Browse Source
This commit is contained in:
Ben Boeckel
2025-06-12 20:22:26 +02:00
parent b44bc8d1a5
commit b634998727
31 changed files with 80 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Help/command/add_custom_command.rst
View File

@@ -282,7 +282,7 @@ The options are:
``MAIN_DEPENDENCY``
Specify the primary input source file to the command. This is
treated just like any value given to the ``DEPENDS`` option
but also suggests to Visual Studio generators where to hang
but also suggests to :ref:`Visual Studio Generators` where to hang
the custom command. Each source file may have at most one command
specifying it as its main dependency. A compile command (i.e. for a
library or an executable) counts as an implicit main dependency which

6
Help/command/add_library.rst
View File

@@ -120,9 +120,9 @@ may contain only sources that compile, header files, and other files
that would not affect linking of a normal library (e.g. ``.txt``).
They may contain custom commands generating such sources, but not
``PRE_BUILD``, ``PRE_LINK``, or ``POST_BUILD`` commands. Some native build
systems (such as Xcode) may not like targets that have only object files, so
consider adding at least one real source file to any target that references
:genex:`$\<TARGET_OBJECTS:objlib\> <TARGET_OBJECTS>`.
systems (such as :generator:`Xcode`) may not like targets that have only
object files, so consider adding at least one real source file to any target
that references :genex:`$\<TARGET_OBJECTS:objlib\> <TARGET_OBJECTS>`.
.. versionadded:: 3.12
Object libraries can be linked to with :command:`target_link_libraries`.

4
Help/command/link_directories.rst
View File

@@ -40,8 +40,8 @@ The command will apply only to targets created after it is called.
generally be used directly in calls to :command:`target_link_libraries`.
Situations where a library search path may be needed include:
- Project generators like Xcode where the user can switch target
architecture at build time, but a full path to a library cannot
- Project generators like :generator:`Xcode` where the user can switch
target architecture at build time, but a full path to a library cannot
be used because it only provides one architecture (i.e. it is not
a universal binary).
- Libraries may themselves have other private library dependencies

4
Help/command/target_link_directories.rst
View File

@@ -46,8 +46,8 @@ property instead of being appended.
generally be used directly in calls to :command:`target_link_libraries`.
Situations where a library search path may be needed include:
- Project generators like Xcode where the user can switch target
architecture at build time, but a full path to a library cannot
- Project generators like :generator:`Xcode` where the user can switch
target architecture at build time, but a full path to a library cannot
be used because it only provides one architecture (i.e. it is not
a universal binary).
- Libraries may themselves have other private library dependencies