diff options
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
-rw-r--r-- | documentation/ref-manual/closer-look.xml | 54 |
1 files changed, 41 insertions, 13 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index eaf07d665f..27f674ae2f 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml | |||
@@ -640,7 +640,9 @@ | |||
640 | 640 | ||
641 | <para> | 641 | <para> |
642 | Package feeds are an intermediary step in the build process. | 642 | Package feeds are an intermediary step in the build process. |
643 | BitBake generates packages whose types are defined by the | 643 | The OpenEmbedded build system provides classes to generate |
644 | different package types, and you specify which classes to enable | ||
645 | through the | ||
644 | <link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link> | 646 | <link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link> |
645 | variable. | 647 | variable. |
646 | Before placing the packages into package feeds, | 648 | Before placing the packages into package feeds, |
@@ -651,22 +653,41 @@ | |||
651 | </para> | 653 | </para> |
652 | 654 | ||
653 | <para> | 655 | <para> |
654 | The package feed area resides in | 656 | The package feed area resides in the Build Directory. |
655 | <filename>tmp/deploy</filename> of the Build Directory. | 657 | The directory the build system uses to temporarily store packages |
656 | Folders are created that correspond to the package type | 658 | is determined by a combination of variables and the particular |
657 | (IPK, DEB, or RPM) created. | 659 | package manager in use. |
658 | Further organization is derived through the value of the | 660 | See the "Package Feeds" box in the illustration and note the |
659 | <link linkend='var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></link> | 661 | information to the right of that area. |
660 | variable for each package. | 662 | In particular, the following defines where package files are |
661 | For example, packages can exist for the i586 or qemux86 | 663 | kept: |
662 | architectures. | 664 | <itemizedlist> |
663 | The package files themselves reside within the appropriate | 665 | <listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>: |
664 | architecture folder. | 666 | Defined as <filename>tmp/deploy</filename> in the Build |
667 | Directory. | ||
668 | </para></listitem> | ||
669 | <listitem><para><filename>DEPLOY_DIR_*</filename>: | ||
670 | Depending on the package manager used, the package type | ||
671 | sub-folder. | ||
672 | Given RPM, IPK, or DEB packaging and tarball creation, the | ||
673 | <link linkend='var-DEPLOY_DIR_RPM'><filename>DEPLOY_DIR_RPM</filename></link>, | ||
674 | <link linkend='var-DEPLOY_DIR_IPK'><filename>DEPLOY_DIR_IPK</filename></link>, | ||
675 | <link linkend='var-DEPLOY_DIR_DEB'><filename>DEPLOY_DIR_DEB</filename></link>, | ||
676 | or | ||
677 | <link linkend='var-DEPLOY_DIR_TAR'><filename>DEPLOY_DIR_TAR</filename></link>, | ||
678 | variables are used, respectively. | ||
679 | </para></listitem> | ||
680 | <listitem><para><link linkend='var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></link>: | ||
681 | Defines architecture-specific sub-folders. | ||
682 | For example, packages could exist for the i586 or qemux86 | ||
683 | architectures. | ||
684 | </para></listitem> | ||
685 | </itemizedlist> | ||
665 | </para> | 686 | </para> |
666 | 687 | ||
667 | <para> | 688 | <para> |
668 | BitBake uses the <filename>do_package_write_*</filename> tasks to | 689 | BitBake uses the <filename>do_package_write_*</filename> tasks to |
669 | place generated packages into the package holding area (e.g. | 690 | generate packages and place them into the package holding area (e.g. |
670 | <filename>do_package_write_ipk</filename> for IPK packages). | 691 | <filename>do_package_write_ipk</filename> for IPK packages). |
671 | See the | 692 | See the |
672 | "<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_deb</filename></link>", | 693 | "<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_deb</filename></link>", |
@@ -675,6 +696,13 @@ | |||
675 | and | 696 | and |
676 | "<link linkend='ref-tasks-package_write_tar'><filename>do_package_write_tar</filename></link>" | 697 | "<link linkend='ref-tasks-package_write_tar'><filename>do_package_write_tar</filename></link>" |
677 | sections for additional information. | 698 | sections for additional information. |
699 | As an example, consider a scenario where an IPK packaging manager | ||
700 | is being used and package architecture support for both i586 | ||
701 | and qemux86 exist. | ||
702 | Packages for the i586 architecture are placed in | ||
703 | <filename>build/tmp/deploy/ipk/i586</filename>, while packages for | ||
704 | the qemux86 architecture are placed in | ||
705 | <filename>build/tmp/deploy/ipk/qemux86</filename>. | ||
678 | </para> | 706 | </para> |
679 | </section> | 707 | </section> |
680 | 708 | ||