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

dev-manual: Added -ptest to list of complementarty packages 

Added the '-ptest' complementary package to the list of packages,
which included '-dev' and '-dbg' when using inherit packagegroup.
Robert P. J. Day pointed out the code in the OE packagegroup.bbclass
class that showed these three packages all together.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 92bbbbe77b5694eb9e11789c6c425be8c47399c9)

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-10-22 08:58:21 -07:00 committed by Richard Purdie
parent c65cb4348b
commit 52a9ca562e
1 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -917,23 +917,29 @@
<title>Customizing Images Using Custom Package Groups</title>
<para>
For complex custom images, the best approach is to create a custom package group recipe
that is used to build the image or images.
For complex custom images, the best approach is to create a
custom package group recipe that is used to build the image or
images.
A good example of a package group recipe is
<filename>meta/recipes-core/packagegroups/packagegroup-core-boot.bb</filename>.
The
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
variable lists the package group packages you wish to produce. <filename>inherit packagegroup</filename>
sets appropriate default values and automatically adds <filename>-dev</filename>
and <filename>-dbg</filename> complementary
packages for every package specified in <filename>PACKAGES</filename>.
variable lists the package group packages you wish to produce.
<filename>inherit packagegroup</filename> sets appropriate
default values and automatically adds <filename>-dev</filename>,
<filename>-dbg</filename>, and <filename>-ptest</filename>
complementary packages for every package specified in
<filename>PACKAGES</filename>.
Note that the inherit line should be towards
the top of the recipe, certainly before you set <filename>PACKAGES</filename>.
For each package you specify in <filename>PACKAGES</filename>, you can use
the top of the recipe, certainly before you set
<filename>PACKAGES</filename>.
For each package you specify in <filename>PACKAGES</filename>,
you can use
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-RDEPENDS'>RDEPENDS</ulink></filename>
and
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS'>RRECOMMENDS</ulink></filename>
entries to provide a list of packages the parent task package should contain.
entries to provide a list of packages the parent task package
should contain.
Following is an example:
<literallayout class='monospaced'>
DESCRIPTION = "My Custom Package Groups"