sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Updates to the RDEPENDS variable entry. 

Re-wrote some stuff to be clearer.

(From yocto-docs rev: 7c8f529d099d1a234be5e5652acdbb63c9d44d42)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-06-07 15:23:04 +03:00 committed by Richard Purdie
parent d67aecffea
commit 69b36d1a06
1 changed files with 28 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
documentation/ref-manual/ref-variables.xml
View File

@ -3095,20 +3095,25 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</para> </para>
<para> <para>
The names of the variables you list with The names of the packages you list within
<filename>RDEPENDS</filename> must be the names of other <filename>RDEPENDS</filename> must be the names of other
packages as listed in the packages - they cannot be recipe names.
<note>
Although package names and recipe names usually match,
the important point here is that you are
providing package names within the
<filename>RDEPENDS</filename> variable.
</note>
For an example of the default list of packages created from
a recipe, see the
<link linkend='var-PACKAGES'><filename>PACKAGES</filename></link> <link linkend='var-PACKAGES'><filename>PACKAGES</filename></link>
variable. variable.
You should not list recipe names
(<link linkend='var-PN'><filename>PN</filename></link>).
</para> </para>
<para> <para>
Because the <filename>RDEPENDS</filename> variable applies Because the <filename>RDEPENDS</filename> variable applies
to packages being built, you should to packages being built, you should always use the variable
always attach a package name to the variable to specify the in a form with an attached package name.
particular run-time package that has the dependency.
For example, suppose you are building a development package For example, suppose you are building a development package
that depends on the <filename>perl</filename> package. that depends on the <filename>perl</filename> package.
In this case, you would use the following In this case, you would use the following
@ -3116,17 +3121,28 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<literallayout class='monospaced'> <literallayout class='monospaced'>
RDEPENDS_${PN}-dev += "perl" RDEPENDS_${PN}-dev += "perl"
</literallayout> </literallayout>
In the example, the package name In the example, the development package depends on
(<filename>${PN}-dev</filename>) must appear as it would the <filename>perl</filename> package.
in the Thus, the <filename>RDEPENDS</filename> variable has the
<filename>${PN}-dev</filename> package name as part of the
variable.
</para>
<para>
If the package with the dependency is one of the default
packages as listed in the
<filename><link linkend='var-PACKAGES'>PACKAGES</link></filename> <filename><link linkend='var-PACKAGES'>PACKAGES</link></filename>
variable, the package name you attach to the
<filename>RDEPENDS</filename> variable must appear
as it would in the <filename>PACKAGES</filename>
namespace before any renaming of the output package by namespace before any renaming of the output package by
classes like <filename>debian.bbclass</filename>. classes like <filename>debian.bbclass</filename>.
</para> </para>
<para> <para>
In many cases you do not need to explicitly add dependencies In many cases you do not need to explicitly add
to <filename>RDEPENDS</filename> since some automatic run-time dependencies using
<filename>RDEPENDS</filename> since some automatic
handling occurs: handling occurs:
<itemizedlist> <itemizedlist>
<listitem><para><emphasis><filename>shlibdeps</filename></emphasis>: If <listitem><para><emphasis><filename>shlibdeps</filename></emphasis>: If