mirror of
https://github.com/Kitware/CMake.git
synced 2025-10-14 02:08:27 +08:00
Merge topic 'doc-EXCLUDE_FROM_ALL'
e262123fee
Help: Clarify the effect of EXCLUDE_FROM_ALL on target installationa09195e7bf
Help: Rename 'artefact' to 'artifact' in target_precompile_headers Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4840
This commit is contained in:
@@ -93,7 +93,7 @@ Reusing Precompile Headers
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The command also supports a second signature which can be used to specify that
|
||||
one target re-uses a precompiled header file artefact from another target
|
||||
one target re-uses a precompiled header file artifact from another target
|
||||
instead of generating its own:
|
||||
|
||||
.. code-block:: cmake
|
||||
|
@@ -13,9 +13,9 @@ included in the "all" target of its ancestor directories unless the
|
||||
|
||||
With ``EXCLUDE_FROM_ALL`` set to false or not set at all, the target
|
||||
will be brought up to date as part of doing a ``make install`` or its
|
||||
equivalent for the CMake generator being used. If a target has
|
||||
``EXCLUDE_FROM_ALL`` set to true, then any attempt to install that
|
||||
target has undefined behavior. Note that such a target can still safely
|
||||
be listed in an :command:`install(TARGETS)` command as long as the install
|
||||
components the target belongs to are not part of the set of components
|
||||
that anything tries to install.
|
||||
equivalent for the CMake generator being used.
|
||||
|
||||
If a target has ``EXCLUDE_FROM_ALL`` set to true, it may still be listed
|
||||
in an :command:`install(TARGETS)` command, but the user is responsible for
|
||||
ensuring that the target's build artifacts are not missing or outdated when
|
||||
an install is performed.
|
||||
|
Reference in New Issue
Block a user