ref-manual: Applied review changes to the DEPENDS variable.

Updated the note with some formatting and grammar changes.

Fixes [YOCTO #9933]

(From yocto-docs rev: afef28ae894c313f85ddbaeef8b0abbc2700ba2c)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-07-16 11:52:37 -07:00 committed by Richard Purdie
parent bdf9003cfb
commit 451334a841
1 changed files with 17 additions and 11 deletions

View File

@ -2806,23 +2806,29 @@
<filename>DEPENDS</filename> does not make
sense.
Use "foo" instead, as this will put files
from all the packages that make up "foo" -
including those from "foo-dev" - into the
sysroot.
from all the packages that make up
<filename>foo</filename>, which includes
those from <filename>foo-dev</filename>, into
the sysroot.
</para></listitem>
<listitem><para>
Counter intuitively,
Counterintuitively,
<filename>DEPENDS</filename> is often necessary
even for recipes that install precompiled
components.
For example, if "libfoo" is a precompiled
library that links against "libbar", then
linking against "libfoo" requires both "libfoo"
and "libbar" to be available in the sysroot.
For example, if <filename>libfoo</filename>
is a precompiled library that links against
<filename>libbar</filename>, then
linking against <filename>libfoo</filename>
requires both <filename>libfoo</filename>
and <filename>libbar</filename> to be available
in the sysroot.
Without a <filename>DEPENDS</filename> from the
recipe that installs "libfoo" to the recipe
that installs "libbar", other recipes might
fail to link against "libfoo".
recipe that installs <filename>libfoo</filename>
to the recipe that installs
<filename>libbar</filename>, other recipes might
fail to link against
<filename>libfoo</filename>.
</para></listitem>
</itemizedlist>
</note>