A list of dependencies of this rule.
(List of labels; optional)
The precise semantics of what it means for this rule to depend on
another using deps
are specific to the kind of this rule,
and the rule-specific documentation below goes into more detail.
At a minimum, though, the targets named via deps
will
appear in the *.runfiles
area of this rule, if it has
one.
Most often, a deps
dependency is used to allow one
module to use symbols defined in another module written in the
same programming language and separately compiled. Cross-language
dependencies are also permitted in many cases: for example,
a java_library
rule may depend on C++ code in
a cc_library
rule, by declaring the latter in
the deps
attribute. See the definition
of dependencies for more
information.
Almost all rules permit a deps
attribute, but where
this attribute is not allowed, this fact is documented under the
specific rule.