From bd3df791214e81bd3d4e5e4dac7aaf2f78048fb9 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 9 May 2018 11:43:48 -0700 Subject: overview-manual: Updated text for Image and SDK generation. General improvements to both sections. (From yocto-docs rev: 977fdeaf1258613c3dfc41d78c8125fdba9b2a24) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../overview-manual/overview-manual-concepts.xml | 70 ++++++++++++---------- 1 file changed, 37 insertions(+), 33 deletions(-) (limited to 'documentation/overview-manual/overview-manual-concepts.xml') diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml index 4797878312..2a3d62c32a 100644 --- a/documentation/overview-manual/overview-manual-concepts.xml +++ b/documentation/overview-manual/overview-manual-concepts.xml @@ -1507,9 +1507,9 @@ Once packages are split and stored in the Package Feeds - area, the OpenEmbedded build system uses BitBake to - generate the root filesystem image: - + area, the build system uses BitBake to generate the root + filesystem image: + @@ -1524,12 +1524,13 @@ IMAGE_INSTALL: - Lists out the base set of packages to install from - the Package Feeds area. + Lists out the base set of packages from which to + install from the Package Feeds area. PACKAGE_EXCLUDE: - Specifies packages that should not be installed. + Specifies packages that should not be installed + into the image. IMAGE_FEATURES: @@ -1539,9 +1540,9 @@ PACKAGE_CLASSES: - Specifies the package backend to use and - consequently helps determine where to locate - packages within the Package Feeds area. + Specifies the package backend (e.g. RPM, DEB, or + IPK) to use and consequently helps determine where + to locate packages within the Package Feeds area. IMAGE_LINGUAS: @@ -1550,8 +1551,8 @@ PACKAGE_INSTALL: - The final list of packages passed to the package manager - for installation into the image. + The final list of packages passed to the package + manager for installation into the image. @@ -1574,15 +1575,15 @@ enabled for the target, the package manager's data files are deleted from the root filesystem. As part of the final stage of package installation, - postinstall scripts that are part of the packages are run. - Any scripts that fail to run - on the build host are run on the target when the target - system is first booted. + post installation scripts that are part of the packages + are run. + Any scripts 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 read-only root filesystem, - all the post installation scripts must succeed during the - package installation phase since the root filesystem is - read-only. + all the post installation scripts must succeed on the + build host during the package installation phase since the + root filesystem on the target is read-only. @@ -1606,7 +1607,7 @@ - Optimizing processes run across the image include + Optimizing processes that are run across the image include mklibs, prelink, and any other post-processing commands as defined by the ROOTFS_POSTPROCESS_COMMAND @@ -1627,12 +1628,11 @@ IMAGE_PREPROCESS_COMMAND variable. This variable specifies a list of functions to call before - the OpenEmbedded build system creates the final image - output files. + the build system creates the final image output files. - The OpenEmbedded build system dynamically creates + The build system dynamically creates do_image_* tasks as needed, based on the image types specified in the IMAGE_FSTYPES @@ -1671,11 +1671,10 @@ IMAGE_POSTPROCESS_COMMAND variable. The variable specifies a list of functions to call once the - OpenEmbedded build system has created the final image - output files. + build system has created the final image output files. The entire image generation process is run under - Pseudo. + Pseudo. Running under Pseudo ensures that the files in the root filesystem have correct ownership. @@ -1687,9 +1686,12 @@ The OpenEmbedded build system uses BitBake to generate the - Software Development Kit (SDK) installer script for both - the standard and extensible SDKs: - + Software Development Kit (SDK) installer scripts for both + the standard SDK and the extensible SDK (eSDK): + + + + For more information on the cross-development toolchain generation, see the @@ -1701,7 +1703,7 @@ task, see the "Building an SDK Installer" section in the Yocto Project Application Development - and the Extensible Software Development Kit (SDK) + and the Extensible Software Development Kit (eSDK) manual. @@ -1709,10 +1711,12 @@ Like image generation, the SDK script process consists of several stages and depends on many variables. - The do_populate_sdk and - do_populate_sdk_ext tasks use these - key variables to help create the list of packages to - actually install. + The + do_populate_sdk + and + do_populate_sdk_ext + tasks use these key variables to help create the list of + packages to actually install. For information on the variables listed in the figure, see the "Application Development SDK" -- cgit v1.2.3-54-g00ecf