ac14cbf017
Revert commit v3.0.0-rc1~175^2~20 (add_dependencies: Disallow use with INTERFACE_LIBRARY, 2013-12-25). Teach our dependency analysis to transitively follow INTERFACE target utility dependencies as was done or IMPORTED targets in commit v2.8.6~127^2~1 (Allow add_dependencies() on imported targets, 2010-11-19). Extend the InterfaceLibrary test with a case to cover header generation for a header-only INTERFACE library via a custom target.
23 lines
856 B
ReStructuredText
23 lines
856 B
ReStructuredText
add_dependencies
|
|
----------------
|
|
|
|
Add a dependency between top-level targets.
|
|
|
|
::
|
|
|
|
add_dependencies(<target> [<target-dependency>]...)
|
|
|
|
Make a top-level ``<target>`` depend on other top-level targets to
|
|
ensure that they build before ``<target>`` does. A top-level target
|
|
is one created by one of the :command:`add_executable`,
|
|
:command:`add_library`, or :command:`add_custom_target` commands.
|
|
|
|
Dependencies added to an :ref:`imported target <Imported Targets>`
|
|
or an :ref:`interface library <Interface Libraries>` are followed
|
|
transitively in its place since the target itself does not build.
|
|
|
|
See the ``DEPENDS`` option of :command:`add_custom_target` and
|
|
:command:`add_custom_command` commands for adding file-level
|
|
dependencies in custom rules. See the :prop_sf:`OBJECT_DEPENDS`
|
|
source file property to add file-level dependencies to object files.
|