summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-08-21 15:10:09 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-26 11:06:30 +0100
commitbf91da6c0a7fcd081a4cd70a70f0a545382dc7da (patch)
treea6890094d65150b5cc0e25825367713c7b38de91 /documentation
parent88705462726892a19dbb3d15a900e6cb04490a3b (diff)
downloadast2050-yocto-poky-bf91da6c0a7fcd081a4cd70a70f0a545382dc7da.zip
ast2050-yocto-poky-bf91da6c0a7fcd081a4cd70a70f0a545382dc7da.tar.gz
ref-manual, mega-manual: new section on config/compile for expanded build
Fixes [YOCTO #2808] Added a new section on configuration and compilation for the expanded discussion for the build process. This involved a new figure that had to be added to both the ref-manual and mega-manual figures directories. (From yocto-docs rev: 9ba90c79990b79226d6e95e4a01ddedeccb94b35) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/mega-manual/figures/configuration-compile-autoreconf.pngbin0 -> 48116 bytes
-rw-r--r--documentation/ref-manual/figures/configuration-compile-autoreconf.pngbin0 -> 48116 bytes
-rw-r--r--documentation/ref-manual/technical-details.xml59
3 files changed, 59 insertions, 0 deletions
diff --git a/documentation/mega-manual/figures/configuration-compile-autoreconf.png b/documentation/mega-manual/figures/configuration-compile-autoreconf.png
new file mode 100644
index 0000000..596a894
--- /dev/null
+++ b/documentation/mega-manual/figures/configuration-compile-autoreconf.png
Binary files differ
diff --git a/documentation/ref-manual/figures/configuration-compile-autoreconf.png b/documentation/ref-manual/figures/configuration-compile-autoreconf.png
new file mode 100644
index 0000000..596a894
--- /dev/null
+++ b/documentation/ref-manual/figures/configuration-compile-autoreconf.png
Binary files differ
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 5ee2615..2607661 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1066,6 +1066,65 @@
section.
</para>
</section>
+
+ <section id='configuration-and-compilation-dev-environment'>
+ <title>Configuration and Compilation</title>
+
+ <para>
+ After source code is patched, BitBake executes tasks that
+ configure and compile the source code:
+ <imagedata fileref="figures/configuration-compile-autoreconf.png" align="center" width="7in" depth="5in" />
+ </para>
+
+ <para>
+ This step in the build process consists of three tasks:
+ <itemizedlist>
+ <listitem><para><emphasis><filename>do_configure</filename>:</emphasis>
+ This task configures the source by enabling and
+ disabling any build-time and configuration options for
+ the software being built.
+ Configurations can come from the recipe itself as well
+ as from an inherited class.
+ Additionally, the software itself might configure itself
+ depending on the target for which it is being built.
+ </para>
+
+ <para>The configurations handled by the
+ <filename>do_configure</filename> task are specific
+ to source code configuration for the source code
+ being built by the recipe.</para>
+
+ <para>If you are using
+ <link linkend='ref-classes-autotools'><filename>autotools.bbclass</filename></link>,
+ you can add additional configuration options by using
+ the <link linkend='var-EXTRA_OECONF'><filename>EXTRA_OECONF</filename></link>
+ variable.
+ For information on how this variable works within
+ that class, see the
+ <filename>meta/classes/autotools.bbclass</filename>.
+ </para></listitem>
+ <listitem><para><emphasis><filename>do_compile</filename>:</emphasis>
+ Once a configuration task has been satisfied, BitBake
+ compiles the source using the
+ <filename>do_compile</filename> task.
+ Compilation occurs in the directory pointed to by the
+ <link linkend='var-B'><filename>B</filename></link>
+ variable.
+ Realize that the <filename>B</filename> directory, by
+ default, is the same as the
+ <link linkend='var-S'><filename>S</filename></link>
+ directory.</para></listitem>
+ <listitem><para><emphasis><filename>do_install</filename>:</emphasis>
+ Once compilation is done, BitBake executes the
+ <filename>do_install</filename> task.
+ This task copies files from the <filename>B</filename>
+ directory and places them in a holding area pointed to
+ by the
+ <link linkend='var-D'><filename>D</filename></link>
+ variable.</para></listitem>
+ </itemizedlist>
+ </para>
+ </section>
</section>
</section>
OpenPOWER on IntegriCloud