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

dev manual: Minor tweaks to first part of ch 5, dev-manual. 

given the length of chapter 5 in the dev manual, i'm going to do
this in bite-size pieces.

(From yocto-docs rev: 3db48a0be170a02e5042fe65253c65b5245c6b89)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Robert P. J. Day 2013-11-11 11:02:57 -08:00 committed by Richard Purdie
parent 3736d5c8e4
commit 30bebff0dc
1 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -10,7 +10,7 @@
adding new software packages, extending or customizing images, adding new software packages, extending or customizing images,
porting work to new hardware (adding a new machine), and so forth. porting work to new hardware (adding a new machine), and so forth.
You will find the procedures documented here occur often in the You will find the procedures documented here occur often in the
develop cycle using the Yocto Project. development cycle using the Yocto Project.
</para> </para>
<section id="understanding-and-creating-layers"> <section id="understanding-and-creating-layers">
@ -31,7 +31,7 @@
To illustrate how layers are used to keep things modular, consider To illustrate how layers are used to keep things modular, consider
machine customizations. machine customizations.
These types of customizations typically reside in a special layer, These types of customizations typically reside in a special layer,
rather than a general layer, called a Board Specific Package (BSP) rather than a general layer, called a Board Support Package (BSP)
Layer. Layer.
Furthermore, the machine customizations should be isolated from Furthermore, the machine customizations should be isolated from
recipes and Metadata that support a new GUI environment, recipes and Metadata that support a new GUI environment,
@ -60,11 +60,12 @@
You can easily identify layers that ship with a You can easily identify layers that ship with a
Yocto Project release in the Source Directory by their Yocto Project release in the Source Directory by their
folder names. folder names.
Folders that are layers begin with the string Folders that represent layers typically have names that begin with
<filename>meta</filename>. the string <filename>meta-</filename>.
<note> <note>
It is not a requirement that a layer begins with the It is not a requirement that a layer name begin with the
string <filename>meta</filename>. prefix <filename>meta-</filename>, but it's a commonly accepted
standard in the Yocto Project community.
</note> </note>
For example, when you set up the Source Directory structure, For example, when you set up the Source Directory structure,
you will see several layers: you will see several layers:
@ -72,14 +73,14 @@
<filename>meta-skeleton</filename>, <filename>meta-skeleton</filename>,
<filename>meta-yocto</filename>, and <filename>meta-yocto</filename>, and
<filename>meta-yocto-bsp</filename>. <filename>meta-yocto-bsp</filename>.
Each of these folders is a layer. Each of these folders represents a distinct layer.
</para> </para>
<para> <para>
Furthermore, if you set up a local copy of the Furthermore, if you set up a local copy of the
<filename>meta-intel</filename> Git repository <filename>meta-intel</filename> Git repository
and then explore the folder of that general layer, and then explore the folder of that general layer,
you will discover many BSP layers inside. you will discover many Intel-specific BSP layers inside.
For more information on BSP layers, see the For more information on BSP layers, see the
"<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>"
section in the Yocto Project Board Support Package (BSP) section in the Yocto Project Board Support Package (BSP)
@ -252,8 +253,8 @@
configuration. configuration.
In other words, do not copy an entire recipe into your In other words, do not copy an entire recipe into your
layer and then modify it. layer and then modify it.
Use <filename>.bbappend</filename> files to override the Rather, use <filename>.bbappend</filename> files to override the
parts of the recipe you need to modify. only those parts of the original recipe you need to modify.
</para> </para>
</section> </section>
@ -275,6 +276,9 @@
the layer to which it originally belongs. the layer to which it originally belongs.
If this is the case, you need to address that deficiency If this is the case, you need to address that deficiency
instead of overlaying the include file. instead of overlaying the include file.
</para>
<para>
For example, consider how support plug-ins for the Qt 4 For example, consider how support plug-ins for the Qt 4
database are configured. database are configured.
The Source Directory does not have MySQL or PostgreSQL. The Source Directory does not have MySQL or PostgreSQL.
@ -496,7 +500,7 @@
number-specific. number-specific.
If the corresponding recipe is renamed to update to a newer If the corresponding recipe is renamed to update to a newer
version, the corresponding <filename>.bbappend</filename> file must version, the corresponding <filename>.bbappend</filename> file must
be renamed as well. be renamed (and possibly updated) as well.
During the build process, BitBake displays an error on starting During the build process, BitBake displays an error on starting
if it detects a <filename>.bbappend</filename> file that does if it detects a <filename>.bbappend</filename> file that does
not have a corresponding recipe with a matching name. not have a corresponding recipe with a matching name.