and are ideal for experimentation using Yocto Project.
For information on the image types you can build using the OpenEmbedded build system,
see the
- "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" appendix in
+ "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter in
The Yocto Project Reference Manual.
</para>
It also allows you to perform post-mortem style analysis of program crashes.
GDB is available as a package within the Yocto Project and by default is
installed in sdk images.
- See the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" appendix
+ See the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" appendix
in the Yocto Project Reference Manual for a description of these images.
You can find information on GDB at <ulink url="http://sourceware.org/gdb/"/>.
</para>
<ulink url='&BITBAKE_DOCS_URL;'>here</ulink>.</para>
<para>The build process supports several types of images to satisfy different needs.
See the
- "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" appendix
- in The Yocto Project Reference Manual for information on
+ "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter
+ in the Yocto Project Reference Manual for information on
supported images.</para></listitem>
</orderedlist>
</para>
You can find more information on BitBake
<ulink url='&BITBAKE_DOCS_URL;'>here</ulink>.</para>
<para>The build process supports several types of images to satisfy different needs.
- See the appendix
- "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" in
- The Yocto Project Reference Manual for information on supported images.</para></listitem>
+ See the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter in
+ the Yocto Project Reference Manual for information on supported images.</para></listitem>
<listitem><para><emphasis>Make your configuration changes available
in the kernel layer</emphasis>: Up to this point, all the configuration changes to the
kernel have been done and tested iteratively.
Images are the binary output that run on specific hardware and for specific
use cases.
For a list of the supported image types that the Yocto Project provides, see the
- "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>"
- appendix in The Yocto Project Reference Manual.</para></listitem>
+ "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>"
+ chapter in the Yocto Project Reference Manual.</para></listitem>
<listitem><para id='layer'><emphasis>Layer:</emphasis> A collection of recipes representing the core,
a BSP, or an application stack.
For a discussion on BSP Layers, see the
<para>
Another option you have to get started is to use pre-built binaries.
The Yocto Project provides many types of binaries with each release.
- See the <ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>
- section for descriptions of the types of binaries that ship with a Yocto Project
+ See the <ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>
+ chapter in the Yocto Project Reference Manual
+ for descriptions of the types of binaries that ship with a Yocto Project
release.
</para>
<link linkend='ref-classes'>Classes</link>:</emphasis>
This chapter describes the classes used in the Yocto Project.</para></listitem>
<listitem><para><emphasis>
- <link linkend='ref-images'>Reference: Images</link>:</emphasis>
- This appendix describes the standard images that the Yocto Project supports.
+ <link linkend='ref-images'>Images</link>:</emphasis>
+ This chapter describes the standard images that the Yocto Project supports.
</para></listitem>
<listitem><para><emphasis>
- <link linkend='ref-features'>Reference: Features</link>:</emphasis>
- This appendix describes mechanisms for creating distribution, machine, and image
+ <link linkend='ref-features'>Features</link>:</emphasis>
+ This chapter describes mechanisms for creating distribution, machine, and image
features during the build process using the OpenEmbedded build system.</para></listitem>
<listitem><para><emphasis>
<link linkend='ref-variables-glos'>Reference: Variables Glossary</link>:</emphasis>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
-<appendix id='ref-features'>
+<chapter id='ref-features'>
<title>Reference: Features</title>
<para>
</itemizedlist>
</para>
</section>
-</appendix>
+</chapter>
<!--
vim: expandtab tw=80 ts=4 spell spelllang=en_gb
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
-<appendix id='ref-images'>
- <title>Reference: Images</title>
+<chapter id='ref-images'>
+ <title>Images</title>
<para>
The OpenEmbedded build process supports several types of images to satisfy different needs.
"live" to <filename>IMAGE_FSTYPES</filename> within the <filename>local.conf</filename>
file or wherever appropriate and then build the desired image as normal.
</tip>
-</appendix>
+</chapter>
<!--
vim: expandtab tw=80 ts=4
-->
Typically, you configure this variable in image recipes.
Note that you can add extra features to the image by using the
<filename><link linkend='var-EXTRA_IMAGE_FEATURES'>EXTRA_IMAGE_FEATURES</link></filename> variable.
- See the "<link linkend="ref-features-image">Reference: Images</link>" section for the
+ See the "<link linkend="ref-features-image">Images</link>" chapter for the
list of features present in images built by the OpenEmbedded build system.</para>
</glossdef>
</glossentry>
Or, the target can be the name of a recipe for a specific piece of software such as
<application>busybox</application>.
For more details about the images the OpenEmbedded build system supports, see the
- "<link linkend="ref-images">Reference: Images</link>" appendix.
+ "<link linkend="ref-images">Images</link>" chapter.
</para>
<note>
Building an image without GNU Public License Version 3 (GPLv3) components is
only supported for minimal and base images.
- See the "<link linkend='ref-images'>Reference: Images</link>" appendix for more information.
+ See the "<link linkend='ref-images'>Images</link>" chapter for more information.
</note>
</section>
Where:
<<emphasis>profile</emphasis>> is the filesystem image's profile:
lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk.
- For information on these types of image profiles, see
- <ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink> in the Yocto Project Reference Manual.
+ For information on these types of image profiles, see the
+ "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter
+ in the Yocto Project Reference Manual.
<<emphasis>arch</emphasis>> is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm.