diff --git a/documentation/mega-manual/figures/image-generation.png b/documentation/mega-manual/figures/image-generation.png
index ae82e5a118..45aad7c7a8 100644
Binary files a/documentation/mega-manual/figures/image-generation.png and b/documentation/mega-manual/figures/image-generation.png differ
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 5a7d111890..0a6c56c048 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -106,7 +106,7 @@
configuration files.
These example files are used as a basis for creating actual
configuration files when you source the build environment
- script
+ script
(i.e.
&OE_INIT_FILE;
or
@@ -129,8 +129,8 @@
Because the Poky repository is fundamentally an aggregation of
existing repositories, some users might be familiar with running
- the &OE_INIT_FILE; or
- oe-init-build-env-memres script in the context
+ the &OE_INIT_FILE; or
+ oe-init-build-env-memres script in the context
of separate OpenEmbedded-Core and BitBake repositories rather than a
single Poky repository.
This discussion assumes the script is executed from within a cloned
@@ -297,7 +297,7 @@
The following figure shows an expanded representation of the
Metadata, Machine Configuration, and Policy Configuration input
- (layers) boxes of the
+ (layers) boxes of the
general Yocto Project Development Environment figure:
@@ -452,7 +452,7 @@
In order for the OpenEmbedded build system to create an image or
any target, it must be able to access source files.
- The
+ The
general Yocto Project Development Environment figure
represents source files using the "Upstream Project Releases",
"Local Projects", and "SCMs (optional)" boxes.
@@ -608,7 +608,7 @@
When the OpenEmbedded build system generates an image or an SDK,
it gets the packages from a package feed area located in the
Build Directory.
- The
+ The
general Yocto Project Development Environment figure
shows this package feeds area in the upper-right corner.
@@ -887,84 +887,80 @@
Image Generation
- Once packages are split and stored in the Package Feeds area,
- the OpenEmbedded build system uses BitBake to generate the
+ Once packages are split and stored in the Package Feeds area,
+ the OpenEmbedded build system uses BitBake to generate the
root filesystem image:
- The image generation process consists of several stages and
+ The image generation process consists of several stages and
depends on many variables.
The do_rootfs task uses these key variables
to help create the list of packages to actually install:
IMAGE_INSTALL:
- Lists out the base set of packages to install from
- the Package Feeds area.
+ Lists out the base set of packages to install from
+ the Package Feeds area.PACKAGE_EXCLUDE:
Specifies packages that should not be installed.
-
+ IMAGE_FEATURES:
- Specifies features to include in the image.
- These features map to additional packages for
+ Specifies features to include in the image.
+ Most of these features map to additional packages for
installation.PACKAGE_CLASSES:
- Specifies the package manager to use and consequently
- helps determine where to locate packages within the
- Package Feeds area.
+ Specifies the package backend to use and consequently
+ helps determine where to locate packages within the
+ Package Feeds area.
IMAGE_LINGUAS:
- Determines the language for which packages are being
- installed.
+ Determines the language(s) for which additional
+ language support packages are installed.
+
- Part of the image generation process includes compressing the
- root filesystem image.
- Compression is accomplished through several optimization
+ The process runs all of the post installation scripts, and
+ any that fail to run on the build host will be run on the
+ target when the target system is first booted.
+ If you are using a read-only root filesystem, all the post
+ installation scripts must succeed during the package
+ installation phase since the root filesystem cannot be
+ written into.
+
+
+
+ During Optimization, optimizing processes are run across
+ the image.
+ These processes include mklibs and
+ prelink.
+ The mklibs optimizes the size of the
+ libraries.
+ A prelink process optimizes the dynamic
+ linking of shared libraries to reduce start up time of the
+ executables.
+
+
+
+ Part of the image generation process includes compressing the
+ root filesystem image.
+ Compression is accomplished through several optimization
routines designed to reduce the overall size of the image.
-
- The process runs as many post installation scripts as possible.
- Any scripts that cannot be run are run when the system is
- first booted.
- If you are using a read-only root filesystem, all the post
- installation scripts are run during the package installation
- phase since the root filesystem cannot be written into.
-
-
-
- During the Prelink phase, optimization processes are run across
- the image.
- These processes include mklibs and
- prelink.
- The mklibs optimizes the size of the
- libraries.
- The prelink process optimizes the dynamic
- linking of shared libraries to reduce start up time of the
- executables.
- See the
- IMAGE_POSTPROCESS_COMMAND
- and
- ROOTFS_POSTPROCESS_COMMAND
- variables for additional information.
-
-
After the root filesystem has been constructed, the image
- generation process turns everything into an image file or
- a set of image files.
- we need to turn into an image file or set of image files.
- The formats used for the root filesystem depend on the
+ generation process turns everything into an image file or
+ a set of image files.
+ The formats used for the root filesystem depend on the
IMAGE_FSTYPES
variable.
The entire image generation process is run under Pseudo.
- Running under Pseudo ensures that the files in the root
+ Running under Pseudo ensures that the files in the root
filesystem have correct ownership.
@@ -977,7 +973,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.
- You can see from the
+ You can see from the
general Yocto Project Development Environment figure
that BitBake output in part consists of images.
This section is going to look more closely at this output:
@@ -1049,7 +1045,7 @@
Application Development SDK
- In the
+ In the
general Yocto Project Development Environment figure,
the output labeled "Application Development SDK" represents an
SDK.
diff --git a/documentation/ref-manual/figures/image-generation.png b/documentation/ref-manual/figures/image-generation.png
index ae82e5a118..45aad7c7a8 100644
Binary files a/documentation/ref-manual/figures/image-generation.png and b/documentation/ref-manual/figures/image-generation.png differ