1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-31 12:49:46 +00:00

overview-manual: Changed title for configure/compile section.

The stage of the BitBake workflow is really "Configuration, Compilation,
and Staging".  I updated the title to be such.

(From yocto-docs rev: 4aab6d001119aa8c52e09ef0f6f66694719add29)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-08 15:53:34 -07:00
committed by Richard Purdie
parent 8436b7a6a9
commit 760e435e32
@@ -1291,14 +1291,14 @@
</para> </para>
</section> </section>
<section id='configuration-and-compilation-dev-environment'> <section id='configuration-compilation-and-staging-dev-environment'>
<title>Configuration and Compilation</title> <title>Configuration, Compilation, and Staging</title>
<para> <para>
After source code is patched, BitBake executes tasks that After source code is patched, BitBake executes tasks that
configure and compile the source code. configure and compile the source code.
Once compilation occurs, the files are copied to a holding Once compilation occurs, the files are copied to a holding
area in preparation for packaging: area (staged) in preparation for packaging:
<imagedata fileref="figures/configuration-compile-autoreconf.png" align="center" width="7in" depth="5in" /> <imagedata fileref="figures/configuration-compile-autoreconf.png" align="center" width="7in" depth="5in" />
</para> </para>
@@ -1385,9 +1385,9 @@
<title>Package Splitting</title> <title>Package Splitting</title>
<para> <para>
After source code is configured and compiled, the After source code is configured, compiled, and staged, the
OpenEmbedded build system analyzes build system analyzes the results and splits the output
the results and splits the output into packages: into packages:
<imagedata fileref="figures/analysis-for-package-splitting.png" align="center" width="7in" depth="7in" /> <imagedata fileref="figures/analysis-for-package-splitting.png" align="center" width="7in" depth="7in" />
</para> </para>
@@ -1398,15 +1398,15 @@
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-packagedata'><filename>do_packagedata</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-packagedata'><filename>do_packagedata</filename></ulink>
tasks combine to analyze the files found in the tasks combine to analyze the files found in the
<ulink url='&YOCTO_DOCS_REF_URL;#var-D'><filename>D</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-D'><filename>D</filename></ulink>
directory and split them into subsets based on available directory (i.e. the staging area) and split them into
packages and files. subsets based on available packages and files.
The analyzing process involves the following as well as Analysis involves the following as well as other items:
other items: splitting out debugging symbols, looking at splitting out debugging symbols, looking at shared library
shared library dependencies between packages, and looking dependencies between packages, and looking at package
at package relationships. relationships.
The <filename>do_packagedata</filename> task creates The <filename>do_packagedata</filename> task creates
package metadata based on the analysis such that the package metadata based on the analysis such that the
OpenEmbedded build system can generate the final packages. build system can generate the final packages.
Working, staged, and intermediate results of the analysis Working, staged, and intermediate results of the analysis
and package splitting process use these areas: and package splitting process use these areas:
<itemizedlist> <itemizedlist>
@@ -1436,9 +1436,8 @@
variable defines the files that go into each package in variable defines the files that go into each package in
<ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'><filename>PACKAGES</filename></ulink>. <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'><filename>PACKAGES</filename></ulink>.
If you want details on how this is accomplished, you can If you want details on how this is accomplished, you can
look at the look at
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'><filename>package</filename></ulink> <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta/classes/package.bbclass'><filename>package.bbclass</filename></ulink>.
class.
</para> </para>
<para> <para>