mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-04 04:40:56 -06:00
45fedf0e17
Do not attach a custom command to a target if it is already attached to one of the target's dependencies. The command's output will be available by the time the target needs it because the dependency containing the command will have already been built. This may break existing projects that do not properly mark non-created outputs with the `SYMBOLIC` property. Previously a chain of two custom commands whose intermediate dependency is not created would put both commands in a dependent project's Makefile even if the first command is also in its dependency's Makefile. The first command would run twice but the build would work. Now the second command needs an explicit `SYMBOLIC` mark on its input to tell CMake that it is not expected to exist. To maintain compatibility with projects that left out the mark, add a policy activating the behavior.
44 lines
1.8 KiB
ReStructuredText
44 lines
1.8 KiB
ReStructuredText
CMP0113
|
|
-------
|
|
|
|
.. versionadded:: 3.19
|
|
|
|
:ref:`Makefile Generators` do not repeat custom commands from target
|
|
dependencies.
|
|
|
|
Consider a chain of custom commands split across two dependent targets:
|
|
|
|
.. code-block:: cmake
|
|
|
|
add_custom_command(OUTPUT output-not-created
|
|
COMMAND ... DEPENDS ...)
|
|
set_property(SOURCE output-not-created PROPERTY SYMBOLIC 1)
|
|
add_custom_command(OUTPUT output-created
|
|
COMMAND ... DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/output-not-created)
|
|
add_custom_target(first DEPENDS output-not-created)
|
|
add_custom_target(second DEPENDS output-created)
|
|
add_dependencies(second first)
|
|
|
|
In CMake 3.18 and lower, the Makefile generators put a copy of both custom
|
|
commands in the Makefile for target ``second`` even though its dependency on
|
|
target ``first`` ensures that the first custom command runs before the second.
|
|
Running ``make second`` would cause the first custom command to run once in
|
|
the ``first`` target and then again in the ``second`` target.
|
|
|
|
CMake 3.19 and above prefer to not duplicate custom commands in a target that
|
|
are already generated in other targets on which the target depends (directly or
|
|
indirectly). This policy provides compatibility for projects that have not
|
|
been updated to expect the new behavior. In particular, projects that relied
|
|
on the duplicate execution or that did not properly set the :prop_sf:`SYMBOLIC`
|
|
source file property may be affected.
|
|
|
|
The ``OLD`` behavior for this policy is to duplicate custom commands in
|
|
dependent targets. The ``NEW`` behavior of this policy is to not duplicate
|
|
custom commands in dependent targets.
|
|
|
|
This policy was introduced in CMake version 3.19. Unlike many policies,
|
|
CMake version |release| does *not* warn when this policy is not set and
|
|
simply uses ``OLD`` behavior.
|
|
|
|
.. include:: DEPRECATED.txt
|