summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-07-29 15:21:05 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-13 13:18:43 +0100
commit96ce7dcedf15463ba5926a2b1fe4a25c2cb93fc0 (patch)
treea01942f95a4abffba075746b5e5739901447c899
parentef0be47efa9f42d49a80442402a8bc33dec99f6f (diff)
downloadpoky-96ce7dcedf15463ba5926a2b1fe4a25c2cb93fc0.tar.gz
ref-manual: New section on Package Feeds.
Fixes [YOCTO #2808] New section for package feeds created. Includes a new figure also. (From yocto-docs rev: 6d8b41114ebadcfb06f6064a13c4da5b47a9f73c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/ref-manual/figures/package-feeds.pngbin0 -> 26406 bytes
-rw-r--r--documentation/ref-manual/technical-details.xml52
2 files changed, 52 insertions, 0 deletions
diff --git a/documentation/ref-manual/figures/package-feeds.png b/documentation/ref-manual/figures/package-feeds.png
new file mode 100644
index 0000000000..0094f78257
--- /dev/null
+++ b/documentation/ref-manual/figures/package-feeds.png
Binary files differ
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index e355217553..a3452651c7 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -744,6 +744,58 @@
744 </para> 744 </para>
745 </section> 745 </section>
746 </section> 746 </section>
747
748 <section id="package-feeds-dev-environment">
749 <title>Package Feeds</title>
750
751 <para>
752 When the OpenEmbedded build system generates an image or an SDK,
753 it gets the packages from a package feed area located in the
754 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
755 The main
756 <link linkend='a-closer-look-at-the-yocto-project-development-environment'>Yocto Project Development Environment</link>
757 figure shows this package feeds area in the upper-right corner.
758 </para>
759
760 <para>
761 This section looks a little closer into the package feeds area used
762 by the build system.
763 Here is a more detailed look at the area:
764 <imagedata fileref="figures/package-feeds.png" align="center" width="7in" depth="6in" />
765 </para>
766
767 <para>
768 Package feeds are an intermediary step in the build process.
769 BitBake generates packages whose type is defined by the
770 <link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>
771 variable.
772 Before placing the packages into package feeds,
773 the build process validates them with generated output quality
774 assurance checks through the
775 <link linkend='ref-classes-insane'><filename>insane.bbclass</filename></link>
776 class.
777 </para>
778
779 <para>
780 The package feed area resides in
781 <filename>tmp/deploy</filename> of the Build Directory.
782 Folders are created that correspond to the package type
783 (IPK, DEB, or RPM) created.
784 Further organization is derived through the value of the
785 <link linkend='var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></link>
786 variable for each package.
787 For example, packages can exist for the i586 or qemux86
788 architectures.
789 The package files themselves reside within the appropriate
790 architecture folder.
791 </para>
792
793 <para>
794 BitBake uses the <filename>do_package_write_*</filename> task to
795 place generated packages into the package holding area (e.g.
796 <filename>do_package_write_ipk</filename> for IPK packages).
797 </para>
798 </section>
747</section> 799</section>
748 800
749<section id="cross-development-toolchain-generation"> 801<section id="cross-development-toolchain-generation">