diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-09-13 14:32:05 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-09-22 12:20:44 +0100 |
commit | 25bea918aaccdd8561681923f36cb3ca359fdb25 (patch) | |
tree | 7ffe9007de5f2833706b1f691008dddfcd96cd33 /documentation/ref-manual/closer-look.xml | |
parent | 72c73e67ca38d5024f93644806a657726edc27d7 (diff) | |
download | ast2050-yocto-poky-25bea918aaccdd8561681923f36cb3ca359fdb25.zip ast2050-yocto-poky-25bea918aaccdd8561681923f36cb3ca359fdb25.tar.gz |
ref-manual: Edits to the "Image Generation" section
Fixes [YOCTO #2808]
Did a self-edit here to try and straighten out how I am mapping
the variables to the actual figure.
(From yocto-docs rev: 82e94d8a8221bbf2eb5feb19a6642907b4ff490b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
-rw-r--r-- | documentation/ref-manual/closer-look.xml | 123 |
1 files changed, 59 insertions, 64 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index a690544..5a7d111 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -601,6 +601,58 @@ </section> </section> + <section id="package-feeds-dev-environment"> + <title>Package Feeds</title> + + <para> + When the OpenEmbedded build system generates an image or an SDK, + it gets the packages from a package feed area located in the + <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. + The + <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link> + shows this package feeds area in the upper-right corner. + </para> + + <para> + This section looks a little closer into the package feeds area used + by the build system. + Here is a more detailed look at the area: + <imagedata fileref="figures/package-feeds.png" align="center" width="7in" depth="6in" /> + </para> + + <para> + Package feeds are an intermediary step in the build process. + BitBake generates packages whose type is defined by the + <link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link> + variable. + Before placing the packages into package feeds, + the build process validates them with generated output quality + assurance checks through the + <link linkend='ref-classes-insane'><filename>insane.bbclass</filename></link> + class. + </para> + + <para> + The package feed area resides in + <filename>tmp/deploy</filename> of the Build Directory. + Folders are created that correspond to the package type + (IPK, DEB, or RPM) created. + Further organization is derived through the value of the + <link linkend='var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></link> + variable for each package. + For example, packages can exist for the i586 or qemux86 + architectures. + The package files themselves reside within the appropriate + architecture folder. + </para> + + <para> + BitBake uses the <filename>do_package_write_*</filename> task to + place generated packages into the package holding area (e.g. + <filename>do_package_write_ipk</filename> for IPK packages). + </para> + </section> + <section id='bitbake-dev-environment'> <title>BitBake</title> @@ -844,12 +896,15 @@ <para> The image generation process consists of several stages and depends on many variables. - The <filename>do_rootfs</filename> uses these key variables + The <filename>do_rootfs</filename> task uses these key variables to help create the list of packages to actually install: <itemizedlist> <listitem><para><link linkend='var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></link>: Lists out the base set of packages to install from the Package Feeds area.</para></listitem> + <listitem><para><link linkend='var-PACKAGE_EXCLUDE'><filename>PACKAGE_EXCLUDE</filename></link>: + Specifies packages that should not be installed. + </para></listitem> <listitem><para><link linkend='var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></link>: Specifies features to include in the image. These features map to additional packages for @@ -858,20 +913,12 @@ Specifies the package manager to use and consequently helps determine where to locate packages within the Package Feeds area.</para></listitem> - <listitem><para><link linkend='var-PACKAGE_EXCLUDE'><filename>PACKAGE_EXCLUDE</filename></link>: - Specifies packages that should not be installed. - </para></listitem> + <listitem><para><link linkend='var-IMAGE_LINGUAS'><filename>IMAGE_LINGUAS</filename></link>: + Determines the language for which packages are being + installed.</para></listitem> </itemizedlist> </para> - <para> - In addition to the previously mentioned variables, the image - generation process uses - <link linkend='var-IMAGE_LINGUAS'><filename>IMAGE_LINGUAS</filename></link> - to determine what language for which packages are being - installed. - </para> - <para> Part of the image generation process includes compressing the root filesystem image. @@ -923,58 +970,6 @@ </section> </section> - <section id="package-feeds-dev-environment"> - <title>Package Feeds</title> - - <para> - When the OpenEmbedded build system generates an image or an SDK, - it gets the packages from a package feed area located in the - <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. - The - <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link> - shows this package feeds area in the upper-right corner. - </para> - - <para> - This section looks a little closer into the package feeds area used - by the build system. - Here is a more detailed look at the area: - <imagedata fileref="figures/package-feeds.png" align="center" width="7in" depth="6in" /> - </para> - - <para> - Package feeds are an intermediary step in the build process. - BitBake generates packages whose type is defined by the - <link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link> - variable. - Before placing the packages into package feeds, - the build process validates them with generated output quality - assurance checks through the - <link linkend='ref-classes-insane'><filename>insane.bbclass</filename></link> - class. - </para> - - <para> - The package feed area resides in - <filename>tmp/deploy</filename> of the Build Directory. - Folders are created that correspond to the package type - (IPK, DEB, or RPM) created. - Further organization is derived through the value of the - <link linkend='var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></link> - variable for each package. - For example, packages can exist for the i586 or qemux86 - architectures. - The package files themselves reside within the appropriate - architecture folder. - </para> - - <para> - BitBake uses the <filename>do_package_write_*</filename> task to - place generated packages into the package holding area (e.g. - <filename>do_package_write_ipk</filename> for IPK packages). - </para> - </section> - <section id='images-dev-environment'> <title>Images</title> |