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

ref-manual: Grammar and typo edits to "Closer Look" section. 

Patch applied from Robert P. J. Day that basically amounted to
a good review of this section.  Robert caught several typos and
small writing issues throughout the section.

(From yocto-docs rev: 559c700187f04c54352b3202fba6022eb74ac610)

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-05 10:06:18 -08:00 committed by Richard Purdie
parent 0c4b95531c
commit d47c4ea18c
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
documentation/ref-manual/closer-look.xml
View File

@ -267,7 +267,7 @@
<para> <para>
The previous section described the user configurations that The previous section described the user configurations that
define the BitBake's global behavior. define BitBake's global behavior.
This section takes a closer look at the layers the build system This section takes a closer look at the layers the build system
uses to further control the build. uses to further control the build.
These layers provide Metadata for the software, machine, and These layers provide Metadata for the software, machine, and
@ -363,7 +363,7 @@
for what you typically find in the distribution layer: for what you typically find in the distribution layer:
<itemizedlist> <itemizedlist>
<listitem><para><emphasis>classes:</emphasis> <listitem><para><emphasis>classes:</emphasis>
Class files (<filename>.bbclass</filename>) holds Class files (<filename>.bbclass</filename>) hold
common functionality that can be shared among common functionality that can be shared among
recipes in the distribution. recipes in the distribution.
When your recipes inherit a class, they take on the When your recipes inherit a class, they take on the
@ -381,7 +381,7 @@
<listitem><para><emphasis>recipes-*:</emphasis> <listitem><para><emphasis>recipes-*:</emphasis>
Recipes and append files that affect common Recipes and append files that affect common
functionality across the distribution. functionality across the distribution.
This area could include recipes and append files to This area could include recipes and append files
to add distribution-specific configuration, to add distribution-specific configuration,
initialization scripts, custom image recipes, initialization scripts, custom image recipes,
and so forth.</para></listitem> and so forth.</para></listitem>
@ -421,7 +421,7 @@
Metadata can exist for multiple formfactors, graphics Metadata can exist for multiple formfactors, graphics
support systems, and so forth. support systems, and so forth.
<note> <note>
While the figure shows several <filename>recipe-*</filename> While the figure shows several <filename>recipes-*</filename>
directories, not all these directories appear in all directories, not all these directories appear in all
BSP layers. BSP layers.
</note> </note>
@ -487,7 +487,7 @@
<para> <para>
Another area that plays a significant role in where source files Another area that plays a significant role in where source files
comes from is pointed to by the come from is pointed to by the
<link linkend='var-DL_DIR'><filename>DL_DIR</filename></link> <link linkend='var-DL_DIR'><filename>DL_DIR</filename></link>
variable. variable.
This area is a cache that can hold previously downloaded source. This area is a cache that can hold previously downloaded source.
@ -546,7 +546,7 @@
The canonical method through which to include a local project The canonical method through which to include a local project
is to use the is to use the
<link linkend='ref-classes-externalsrc'><filename>externalsrc.bbclass</filename></link> <link linkend='ref-classes-externalsrc'><filename>externalsrc.bbclass</filename></link>
class to include local project. class to include that local project.
You use either the <filename>local.conf</filename> or a You use either the <filename>local.conf</filename> or a
recipe's append file to override or set the recipe's append file to override or set the
recipe to point to the local directory on your disk to pull recipe to point to the local directory on your disk to pull
@ -704,11 +704,11 @@
</para> </para>
<para> <para>
Unpacked source source files are pointed to by the Unpacked source files are pointed to by the
<link linkend='var-S'><filename>S</filename></link> variable. <link linkend='var-S'><filename>S</filename></link> variable.
Each recipe has an area in the Build Directory where the Each recipe has an area in the Build Directory where the
unpacked source code resides. unpacked source code resides.
The name of directory for any given recipe is defined from The name of that directory for any given recipe is defined from
several different variables. several different variables.
You can see the variables that define these directories You can see the variables that define these directories
by looking at the figure: by looking at the figure:
@ -809,7 +809,7 @@
variable. variable.
For information on how this variable works within For information on how this variable works within
that class, see the that class, see the
<filename>meta/classes/autotools.bbclass</filename>. <filename>meta/classes/autotools.bbclass</filename> file.
</para></listitem> </para></listitem>
<listitem><para><emphasis><filename>do_compile</filename>:</emphasis> <listitem><para><emphasis><filename>do_compile</filename>:</emphasis>
Once a configuration task has been satisfied, BitBake Once a configuration task has been satisfied, BitBake
@ -818,8 +818,8 @@
Compilation occurs in the directory pointed to by the Compilation occurs in the directory pointed to by the
<link linkend='var-B'><filename>B</filename></link> <link linkend='var-B'><filename>B</filename></link>
variable. variable.
Realize that the <filename>B</filename> directory, by Realize that the <filename>B</filename> directory is, by
default, is the same as the default, the same as the
<link linkend='var-S'><filename>S</filename></link> <link linkend='var-S'><filename>S</filename></link>
directory.</para></listitem> directory.</para></listitem>
<listitem><para><emphasis><filename>do_install</filename>:</emphasis> <listitem><para><emphasis><filename>do_install</filename>:</emphasis>
@ -948,7 +948,7 @@
<para> <para>
During image generation, the build system attempts to run During image generation, the build system attempts to run
all post installation scripts. all post-installation scripts.
Any that fail to run on the build host are run on the Any that fail to run on the build host are run on the
target when the target system is first booted. target when the target system is first booted.
If you are using a If you are using a
@ -1052,7 +1052,7 @@
<para> <para>
The images produced by the OpenEmbedded build system The images produced by the OpenEmbedded build system
are compressed forms of the are compressed forms of the
root filesystems that are ready to boot on a target device. root filesystem that are ready to boot on a target device.
You can see from the You can see from the
<link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link> <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>
that BitBake output in part consists of images. that BitBake output in part consists of images.
@ -1062,14 +1062,14 @@
<para> <para>
For a list of example images that the Yocto Project provides, For a list of example images that the Yocto Project provides,
the see the
"<link linkend='ref-images'>Images</link>" chapter. "<link linkend='ref-images'>Images</link>" chapter.
</para> </para>
<para> <para>
Images are written out to the Images are written out to the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
inside the <filename>deploy/images/&lt;machine&gt;/</filename> inside the <filename>tmp/deploy/images/&lt;machine&gt;/</filename>
folder as shown in the figure. folder as shown in the figure.
This folder contains any files expected to be loaded on the This folder contains any files expected to be loaded on the
target device. target device.