From d47c4ea18c685d7fafdf6788a311f46a5a836ee1 Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Tue, 5 Nov 2013 10:06:18 -0800 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/closer-look.xml | 30 ++++++++++++------------ 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index 25c03e0a52..4883981985 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -267,7 +267,7 @@ 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 uses to further control the build. These layers provide Metadata for the software, machine, and @@ -363,7 +363,7 @@ for what you typically find in the distribution layer: classes: - Class files (.bbclass) holds + Class files (.bbclass) hold common functionality that can be shared among recipes in the distribution. When your recipes inherit a class, they take on the @@ -381,7 +381,7 @@ recipes-*: Recipes and append files that affect common 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, initialization scripts, custom image recipes, and so forth. @@ -421,7 +421,7 @@ Metadata can exist for multiple formfactors, graphics support systems, and so forth. - While the figure shows several recipe-* + While the figure shows several recipes-* directories, not all these directories appear in all BSP layers. @@ -487,7 +487,7 @@ 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 DL_DIR variable. 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 is to use the externalsrc.bbclass - class to include local project. + class to include that local project. You use either the local.conf or a recipe's append file to override or set the recipe to point to the local directory on your disk to pull @@ -704,11 +704,11 @@ - Unpacked source source files are pointed to by the + Unpacked source files are pointed to by the S variable. Each recipe has an area in the Build Directory where the 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. You can see the variables that define these directories by looking at the figure: @@ -809,7 +809,7 @@ variable. For information on how this variable works within that class, see the - meta/classes/autotools.bbclass. + meta/classes/autotools.bbclass file. do_compile: Once a configuration task has been satisfied, BitBake @@ -818,8 +818,8 @@ Compilation occurs in the directory pointed to by the B variable. - Realize that the B directory, by - default, is the same as the + Realize that the B directory is, by + default, the same as the S directory. do_install: @@ -948,7 +948,7 @@ 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 target when the target system is first booted. If you are using a @@ -1052,7 +1052,7 @@ The images produced by the OpenEmbedded build system 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 general Yocto Project Development Environment figure that BitBake output in part consists of images. @@ -1062,14 +1062,14 @@ For a list of example images that the Yocto Project provides, - the + see the "Images" chapter. Images are written out to the Build Directory - inside the deploy/images/<machine>/ + inside the tmp/deploy/images/<machine>/ folder as shown in the figure. This folder contains any files expected to be loaded on the target device.