mirror of
https://git.yoctoproject.org/poky
synced 2026-05-30 00:20:08 +00:00
ref-manual; mega-manual: Edits to further define packaging process
In response to community input where developers were attempting to
locate information on how to write packages out to a directory
other than ${DEPLOY_DIR}/<package_type>, I updated the "Package
Feeds" section, added several new DEPLOY_DIR_* variables, updated
four classes, and updated four tasks. Here are some details:
* Made changes to the "Package Feeds" section to provide more
accurate information in the package feeds directory structure
used by the build system in build/tmp. These changes included
updating the figure itself and some explanatory text.
* Updated the DEPLOY_DIR variable description.
* Added new variable descriptions for DEPLOY_DIR_DEB, DEPLOY_DIR_IPK,
DEPLOY_DIR_RPM, and DEPLOY_DIR_TAR.
* Updated the related classes: package_deb, package_ipk, package_rpm,
and package_tar.
* Updated the related tasks: do_package_write_deb, do_package_write_ipk,
do_package_write_rpm, and do_package_write_tar.
Reported-by: Trieu Nguyen <trieu.t.nguyen@intel.com>
(From yocto-docs rev: e8742267506bf9359346cfcd3965f762ed2c7d6f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
committed by
Richard Purdie
Richard Purdie
parent
a2d770b58a
commit
6192753e9d
@@ -2686,13 +2686,55 @@
|
||||
section.
|
||||
For more detail on the contents of the
|
||||
<filename>deploy</filename> directory, see the
|
||||
"<link linkend='images-dev-environment'>Images</link>" and
|
||||
"<link linkend='images-dev-environment'>Images</link>",
|
||||
"<link linkend='package-feeds-dev-environment'>Package Feeds</link>",
|
||||
and
|
||||
"<link linkend='sdk-dev-environment'>Application Development SDK</link>"
|
||||
sections.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOY_DIR_DEB'><glossterm>DEPLOY_DIR_DEB</glossterm>
|
||||
<info>
|
||||
DEPLOY_DIR_DEB[doc] = "Points to a Debian-specific area that the OpenEmbedded build system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system."
|
||||
</info>
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Points to the area that the OpenEmbedded build system uses
|
||||
to place Debian packages that are ready to be used outside
|
||||
of the build system.
|
||||
This variable applies only when
|
||||
<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>
|
||||
contains "package_deb".
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The BitBake configuration file initially defines the
|
||||
<filename>DEPLOY_DIR_DEB</filename> variable as a
|
||||
sub-folder of
|
||||
<link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
|
||||
<literallayout class='monospaced'>
|
||||
DEPLOY_DIR_DEB = "${DEPLOY_DIR}/deb"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The
|
||||
<link linkend='ref-classes-package_deb'><filename>package_deb</filename></link>
|
||||
class uses the
|
||||
<filename>DEPLOY_DIR_DEB</filename> variable to make sure
|
||||
the
|
||||
<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_deb</filename></link>
|
||||
task writes Debian packages into the appropriate folder.
|
||||
For more information on how packaging works, see the
|
||||
"<link linkend='package-feeds-dev-environment'>Package Feeds</link>"
|
||||
section.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOY_DIR_IMAGE'><glossterm>DEPLOY_DIR_IMAGE</glossterm>
|
||||
<info>
|
||||
DEPLOY_DIR_IMAGE[doc] = "Points to the area that the OpenEmbedded build system uses to place images and other associated output files that are ready to be deployed onto the target machine."
|
||||
@@ -2724,6 +2766,123 @@
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOY_DIR_IPK'><glossterm>DEPLOY_DIR_IPK</glossterm>
|
||||
<info>
|
||||
DEPLOY_DIR_IPK[doc] = "Points to a IPK-specific area that the OpenEmbedded build system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system."
|
||||
</info>
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Points to the area that the OpenEmbedded build system uses
|
||||
to place IPK packages that are ready to be used outside of
|
||||
the build system.
|
||||
This variable applies only when
|
||||
<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>
|
||||
contains "package_ipk".
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The BitBake configuration file initially defines this
|
||||
variable as a sub-folder of
|
||||
<link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
|
||||
<literallayout class='monospaced'>
|
||||
DEPLOY_DIR_IPK = "${DEPLOY_DIR}/ipk"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The
|
||||
<link linkend='ref-classes-package_ipk'><filename>package_ipk</filename></link>
|
||||
class uses the
|
||||
<filename>DEPLOY_DIR_IPK</filename> variable to make sure
|
||||
the
|
||||
<link linkend='ref-tasks-package_write_ipk'><filename>do_package_write_ipk</filename></link>
|
||||
task writes IPK packages into the appropriate folder.
|
||||
For more information on how packaging works, see the
|
||||
"<link linkend='package-feeds-dev-environment'>Package Feeds</link>"
|
||||
section.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOY_DIR_RPM'><glossterm>DEPLOY_DIR_RPM</glossterm>
|
||||
<info>
|
||||
DEPLOY_DIR_RPM[doc] = "Points to a RPM-specific area that the OpenEmbedded build system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system."
|
||||
</info>
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Points to the area that the OpenEmbedded build system uses
|
||||
to place RPM packages that are ready to be used outside
|
||||
of the build system.
|
||||
This variable applies only when
|
||||
<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>
|
||||
contains "package_rpm".
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The BitBake configuration file initially defines this
|
||||
variable as a sub-folder of
|
||||
<link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
|
||||
<literallayout class='monospaced'>
|
||||
DEPLOY_DIR_RPM = "${DEPLOY_DIR}/rpm"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The
|
||||
<link linkend='ref-classes-package_rpm'><filename>package_rpm</filename></link>
|
||||
class uses the
|
||||
<filename>DEPLOY_DIR_RPM</filename> variable to make sure
|
||||
the
|
||||
<link linkend='ref-tasks-package_write_rpm'><filename>do_package_write_rpm</filename></link>
|
||||
task writes RPM packages into the appropriate folder.
|
||||
For more information on how packaging works, see the
|
||||
"<link linkend='package-feeds-dev-environment'>Package Feeds</link>"
|
||||
section.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOY_DIR_TAR'><glossterm>DEPLOY_DIR_TAR</glossterm>
|
||||
<info>
|
||||
DEPLOY_DIR_TAR[doc] = "Points to a tarball area that the OpenEmbedded build system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system."
|
||||
</info>
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Points to the area that the OpenEmbedded build system uses
|
||||
to place tarballs that are ready to be used outside of
|
||||
the build system.
|
||||
This variable applies only when
|
||||
<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>
|
||||
contains "package_tar".
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The BitBake configuration file initially defines this
|
||||
variable as a sub-folder of
|
||||
<link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
|
||||
<literallayout class='monospaced'>
|
||||
DEPLOY_DIR_TAR = "${DEPLOY_DIR}/tar"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The
|
||||
<link linkend='ref-classes-package_tar'><filename>package_tar</filename></link>
|
||||
class uses the
|
||||
<filename>DEPLOY_DIR_TAR</filename> variable to make sure
|
||||
the
|
||||
<link linkend='ref-tasks-package_write_tar'><filename>do_package_write_tar</filename></link>
|
||||
task writes TAR packages into the appropriate folder.
|
||||
For more information on how packaging works, see the
|
||||
"<link linkend='package-feeds-dev-environment'>Package Feeds</link>"
|
||||
section.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-DEPLOYDIR'><glossterm>DEPLOYDIR</glossterm>
|
||||
<info>
|
||||
DEPLOYDIR[doc] = "For recipes that inherit the deploy class, the DEPLOYDIR points to a temporary work area for deployed files."
|
||||
|
||||
Reference in New Issue
Block a user