sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/dev-manual: model changes and updated figure 

Edits to the dev-manual-model.xml chapter for general improvements.
Also had to update the figure that shows the kernel development flow.

(From yocto-docs rev: 2aacccb03d167eac74a1b45c39a9edac160efc7f)

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 2011-09-20 10:26:58 -07:00 committed by Richard Purdie
parent 1017d2aec8
commit 5b58674c6b
2 changed files with 93 additions and 88 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

181
documentation/dev-manual/dev-manual-model.xml
View File

@ -9,16 +9,22 @@
Many development models exist for which you can use the Yocto Project. Many development models exist for which you can use the Yocto Project.
However, for the purposes of this manual we are going to focus on two common ones: However, for the purposes of this manual we are going to focus on two common ones:
System Development and User Application Development. System Development and User Application Development.
System Development covers Board Support Package (BSP) development and kernel modification. System Development covers Board Support Package (BSP) development and kernel modification
or configuration.
User Application Development covers development of applications that you intend to run on some User Application Development covers development of applications that you intend to run on some
target hardware. target hardware.
</para> </para>
<para> <para>
This chapter presents overviews of both system and application models. This chapter presents overviews of both system and application models.
If you want to reference specific examples of these development models, If you want to examine specific examples of the system development models,
see <xref linkend='dev-manual-bsp-appendix'>BSP Development Example</xref> and see the "<link linkend='dev-manual-bsp-appendix'>BSP Development Example</link>"
<xref linkend='dev-manual-kernel-appendix'>Kernel Modification Example</xref>. appendix and the
"<link linkend='dev-manual-kernel-appendix'>Kernel Modification Example</link>" appendix.
For a user-space application development example that uses the Eclipse IDE,
see the
<ulink url='http://www.yoctoproject.org/docs/1.1/adt-manual/adt-manual.html'>
The Yocto Project Application Development Toolkit (ADT) User's Guide</ulink>.
</para> </para>
<section id='system-development-model'> <section id='system-development-model'>
@ -27,7 +33,7 @@
<para> <para>
System development involves modification or creation of an image that you want to run on System development involves modification or creation of an image that you want to run on
a specific hardware target. a specific hardware target.
Usually when you want to create an image that runs on embedded hardware the image does Usually, when you want to create an image that runs on embedded hardware, the image does
not require the same amount of features that a full-fledged Linux distribution provides. not require the same amount of features that a full-fledged Linux distribution provides.
Thus, you can create a much smaller image that is designed to just use the hardware Thus, you can create a much smaller image that is designed to just use the hardware
features for your particular hardware. features for your particular hardware.
@ -35,33 +41,33 @@
<para> <para>
To help you understand how system development works in the Yocto Project, this section To help you understand how system development works in the Yocto Project, this section
covers two types of image development: BSP creation and kernel modification covers two types of image development: BSP creation and kernel modification or
(see <xref linkend='kernel-spot'></xref>). configuration.
</para> </para>
<section id='developing-a-board-support-package-bsp'> <section id='developing-a-board-support-package-bsp'>
<title>Developing a Board Support Package (BSP)</title> <title>Developing a Board Support Package (BSP)</title>
<para> <para>
A BSP is a package of recipes that when applied during a build results in A BSP is a package of recipes that, when applied, during a build results in
an image you can run on a particular board. an image you can run on a particular board.
Thus, the package, when compiled into the new image, supports the operation of the board. Thus, the package, when compiled into the new image, supports the operation of the board.
</para> </para>
<note> <note>
For a brief list of terms used when describing the development process in the Yocto Project, For a brief list of terms used when describing the development process in the Yocto Project,
see <xref linkend='yocto-project-terms'>Yocto Project Terms</xref> in this manual. see the "<link linkend='yocto-project-terms'>Yocto Project Terms</link>" section.
</note> </note>
<para> <para>
The remainder of this section presents the basic steps to create a BSP basing it on an The remainder of this section presents the basic steps to create a BSP basing it on an
existing BSP that ships with the Yocto Project. existing BSP that ships with the Yocto Project.
You can reference <xref linkend='dev-manual-bsp-appendix'>BSP Development Example</xref> You can reference the "<link linkend='dev-manual-bsp-appendix'>BSP Development Example</link>"
for a detailed example that uses the Crown Bay BSP as a base BSP from which to start. appendix for a detailed example that uses the Crown Bay BSP as a base BSP from which to start.
</para> </para>
<para> <para>
This illustration and the following list summarizes the BSP creation general workflow. The following illustration and list summarize the BSP creation general workflow.
</para> </para>
<para> <para>
@ -71,37 +77,38 @@
<para> <para>
<orderedlist> <orderedlist>
<listitem><para><emphasis>Set up your host development system to support <listitem><para><emphasis>Set up your host development system to support
development using the Yocto Project</emphasis>: See development using the Yocto Project</emphasis>: See the
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#the-linux-distro'> "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#the-linux-distro'>The Linux Distributions</ulink>" and the
The Linux Distributions</ulink> section and "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>The Packages</ulink>" sections both
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>
The Packages</ulink> section both
in the Yocto Project Quick Start for requirements.</para></listitem> in the Yocto Project Quick Start for requirements.</para></listitem>
<listitem><para><emphasis>Establish a local copy of the Yocto Project files on your <listitem><para><emphasis>Establish a local copy of the Yocto Project files on your
system</emphasis>: You need to have the Yocto Project files available on your host system. system</emphasis>: You need to have the Yocto Project files available on your host system.
Having the Yocto Project files on your system gives you access to the build Having the Yocto Project files on your system gives you access to the build
process and tools you need. process and tools you need.
For information on how to get these files, see the For information on how to get these files, see the
<xref linkend='getting-setup'>Getting Setup</xref> section in this manual.</para></listitem> "<link linkend='getting-setup'>Getting Setup</link>" section.</para></listitem>
<listitem><para><emphasis>Establish a local copy of the base BSP files</emphasis>: Having <listitem><para><emphasis>Establish a local copy of the base BSP files</emphasis>: Having
the BSP files on your system gives you access to the build the BSP files on your system gives you access to the build
process and tools you need. process and tools you need for creating a BSP.
For information on how to get these files, see For information on how to get these files, see the
<xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual.</para></listitem> "<link linkend='getting-setup'>Getting Setup</link>" section.</para></listitem>
<listitem><para><emphasis>Choose a Yocto Project-supported BSP as your base BSP</emphasis>: <listitem><para><emphasis>Choose a Yocto Project-supported BSP as your base BSP</emphasis>:
The Yocto Project ships with several BSPs that support various hardware. The Yocto Project ships with several BSPs that support various hardware.
It is best to base your new BSP on an existing BSP rather than create all the It is best to base your new BSP on an existing BSP rather than create all the
recipes and configuration files from scratch. recipes and configuration files from scratch.
While it is possible to create everything from scratch, basing your new BSP While it is possible to create everything from scratch, basing your new BSP
on something that is close is much easier. on something that is close is much easier.
Or, at a minimum, it gives you some structure with which to start.</para> Or, at a minimum, leveraging off an existing BSP
gives you some structure with which to start.</para>
<para>At this point you need to understand your target hardware well enough to determine which <para>At this point you need to understand your target hardware well enough to determine which
existing BSP it most closely matches. existing BSP it most closely matches.
Things to consider are your hardware’s on-board features such as CPU type and graphics support. Things to consider are your hardware’s on-board features, such as CPU type and graphics support.
You should look at the README files for supported BSPs to get an idea of which one You should look at the README files for supported BSPs to get an idea of which one
you could use. you could use.
A generic Atom-based BSP to consider is the Crown Bay that does not support A generic <trademark class='registered'>Intel</trademark>
the Intel® Embedded Media Graphics Driver (EMGD). <trademark class='trade'>Atom</trademark>-based BSP to consider is the
Crown Bay that does not support the <trademark class='registered'>Intel</trademark>
Embedded Media Graphics Driver (EMGD).
The remainder of this example uses that base BSP.</para> The remainder of this example uses that base BSP.</para>
<para>To see the supported BSPs, go to the Yocto Project <para>To see the supported BSPs, go to the Yocto Project
<ulink url='http://www.yoctoproject.org/download'>download page</ulink> and click <ulink url='http://www.yoctoproject.org/download'>download page</ulink> and click
@ -110,35 +117,34 @@
isolating and storing work for a given piece of hardware. isolating and storing work for a given piece of hardware.
A layer is really just a location or area in which you place the recipes for your BSP. A layer is really just a location or area in which you place the recipes for your BSP.
In fact, a BSP is, in itself, a special type of layer. In fact, a BSP is, in itself, a special type of layer.
Consider an application as another example that illustrates a layer. Another example that illustrates a layer is an application.
Suppose you are creating an application that has library or other dependencies in Suppose you are creating an application that has library or other dependencies in
order for it to compile and run. order for it to compile and run.
The layer, in this case, would be where all the recipes that define those dependencies The layer, in this case, would be where all the recipes that define those dependencies
are kept. The key point for a layer is that it is an isolated area that contains are kept.
The key point for a layer is that it is an isolated area that contains
all the relevant information for the project that the Yocto Project build all the relevant information for the project that the Yocto Project build
system knows about.</para> system knows about.</para>
<note>The Yocto Project supports four BSPs that are part of the <note>The Yocto Project supports four BSPs that are part of the
Yocto Project release: <filename>atom-pc</filename>, <filename>beagleboard</filename>, Yocto Project release: <filename>atom-pc</filename>, <filename>beagleboard</filename>,
<filename>mpc8315e</filename>, and <filename>routerstationpro</filename>. <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>.
The recipes and configurations for these four BSPs are located and dispersed The recipes and configurations for these four BSPs are located and dispersed
within local Yocto Project files. within the local Yocto Project files.
Consequently, they are not totally isolated in the spirit of layers unless you think Consequently, they are not totally isolated in the spirit of layers unless you think
of <filename>meta-yocto</filename> as a layer itself. of <filename>meta-yocto</filename> as a layer itself.
On the other hand, BSP layers for Crown Bay, Emenlow, Jasper Forest, On the other hand, BSP layers for Crown Bay, Emenlow, Jasper Forest,
N450, and Sugar Bay are isolated.</note> N450, and Sugar Bay are isolated.</note>
<para>When you set up a layer for a new BSP you should follow a standard layout. <para>When you set up a layer for a new BSP, you should follow a standard layout.
This layout is described in the This layout is described in the section
<ulink url='http://www.yoctoproject.org/docs/1.1/bsp-guide/bsp-guide.html#bsp-filelayout'> "<ulink url='http://www.yoctoproject.org/docs/1.1/bsp-guide/bsp-guide.html#bsp-filelayout'>Example Filesystem Layout</ulink>" section of the Board Support Package (BSP) Development Guide.
Example Filesystem Layout</ulink> section of the Board Support Package (BSP) Development In the standard layout, you will notice a suggested structure for recipes and
Guide.
In the standard layout you will notice a suggested structure for recipes and
configuration information. configuration information.
You can see the standard layout for the Crown Bay BSP in this example by examining the You can see the standard layout for the Crown Bay BSP in this example by examining the
directory structure of the <filename>meta-crownbay</filename> layer inside the directory structure of the <filename>meta-crownbay</filename> layer inside the
local Yocto Project files.</para></listitem> local Yocto Project files.</para></listitem>
<listitem><para><emphasis>Make configuration changes to your new BSP <listitem><para><emphasis>Make configuration changes to your new BSP
layer</emphasis>: The standard BSP layer structure organizes the files you need to edit in layer</emphasis>: The standard BSP layer structure organizes the files you need to edit in
<filename>conf</filename> and several <filename>recipes-*</filename> within the <filename>conf</filename> and several <filename>recipes-*</filename> directories within the
BSP layer. BSP layer.
Configuration changes identify where your new layer is on the local system Configuration changes identify where your new layer is on the local system
and identify which kernel you are going to use. and identify which kernel you are going to use.
@ -148,22 +154,20 @@
recipes you don't use, and adding new recipes that you need to support your hardware. recipes you don't use, and adding new recipes that you need to support your hardware.
</para></listitem> </para></listitem>
<listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the <listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the
changes to your BSP layer there remains a few things changes to your BSP layer, there remains a few things
you need to do for the Yocto Project build system in order for it to create your image. you need to do for the Yocto Project build system in order for it to create your image.
You need to get the build environment ready by sourcing an environment setup script You need to get the build environment ready by sourcing an environment setup script
and you need to be sure two key configuration files are configured appropriately.</para> and you need to be sure two key configuration files are configured appropriately.</para>
<para>The entire process for building an image is overviewed in the <para>The entire process for building an image is overviewed in the section
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'> "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" section of the Yocto Project Quick Start.
Building an Image</ulink> section of the Yocto Project Quick Start.
You might want to reference this information.</para></listitem> You might want to reference this information.</para></listitem>
<listitem><para><emphasis>Build the image</emphasis>: The Yocto Project uses the BitBake <listitem><para><emphasis>Build the image</emphasis>: The Yocto Project uses the BitBake
tool to build images based on the type of image you want to create. tool to build images based on the type of image you want to create.
You can find more information on BitBake You can find more information on BitBake
<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para> <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
<para>The build process supports several types of images to satisfy different needs. <para>The build process supports several types of images to satisfy different needs.
See See the
<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'> "<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in the
Reference: Images</ulink> in the
<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'> <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
Yocto Project Reference Manual</ulink>for information on supported images.</para></listitem> Yocto Project Reference Manual</ulink>for information on supported images.</para></listitem>
</orderedlist> </orderedlist>
@ -175,9 +179,9 @@
You can also find supplemental information in You can also find supplemental information in
<ulink url='http://yoctoproject.org/docs/1.1/bsp-guide/bsp-guide.html'> <ulink url='http://yoctoproject.org/docs/1.1/bsp-guide/bsp-guide.html'>
The Board Support Package (BSP) Development Guide</ulink>. The Board Support Package (BSP) Development Guide</ulink>.
Finally, there is wiki page write up of the example located Finally, there is wiki page write up of the example also located
<ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'> <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'>
here</ulink> you might find helpful. here</ulink> that you might find helpful.
</para> </para>
</section> </section>
@ -198,7 +202,8 @@
For a complete discussion of the kernel, see For a complete discussion of the kernel, see
<ulink url='http://www.yoctoproject.org/docs/1.1/kernel-manual/kernel-manual.html'> <ulink url='http://www.yoctoproject.org/docs/1.1/kernel-manual/kernel-manual.html'>
The Yocto Project Kernel Architecture and Use Manual</ulink>. The Yocto Project Kernel Architecture and Use Manual</ulink>.
You can reference <xref linkend='dev-manual-kernel-appendix'>Kernel Modification Example</xref> You can reference the appendix
"<link linkend='dev-manual-kernel-appendix'>Kernel Modification Example</link>"
for a detailed example that changes the configuration of a kernel. for a detailed example that changes the configuration of a kernel.
</para> </para>
@ -210,6 +215,7 @@
of files that contain kernel patches. of files that contain kernel patches.
The Yocto Project, however, employs mechanisims, that in a sense, result in a kernel source The Yocto Project, however, employs mechanisims, that in a sense, result in a kernel source
generator. generator.
By the end of this section, this analogy will become clearer.
</para> </para>
<para> <para>
@ -365,17 +371,14 @@
<orderedlist> <orderedlist>
<listitem><para><emphasis>Set up your host development system to support <listitem><para><emphasis>Set up your host development system to support
development using the Yocto Project</emphasis>: See development using the Yocto Project</emphasis>: See
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#the-linux-distro'> "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#the-linux-distro'>The Linux Distributions</ulink>" and
The Linux Distributions</ulink> section and "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>The Packages</ulink>" sections both
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>
The Packages</ulink> section both
in the Yocto Project Quick Start for requirements.</para></listitem> in the Yocto Project Quick Start for requirements.</para></listitem>
<listitem><para><emphasis>Establish a local copy of the Yocto Project files on your <listitem><para><emphasis>Establish a local copy of the Yocto Project files on your
system</emphasis>: Having the Yocto Project files on your system gives you access to system</emphasis>: Having the Yocto Project files on your system gives you access to
the build process and tools you need. the build process and tools you need.
For information on how to get these files, see the bulleted item For information on how to get these files, see the bulleted item
<link linkend='local-yp-release'>Yocto Project Release</link> in "<link linkend='local-yp-release'>Yocto Project Release</link>" earlier in this manual.
<xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual.
</para></listitem> </para></listitem>
<listitem><para><emphasis>Set up the <filename>poky-extras</filename> Git <listitem><para><emphasis>Set up the <filename>poky-extras</filename> Git
repository</emphasis>: This repository is the area for your configuration repository</emphasis>: This repository is the area for your configuration
@ -384,85 +387,87 @@
It is good practice to set this repository up inside the local Yocto It is good practice to set this repository up inside the local Yocto
Project files Git repository. Project files Git repository.
For information on how to get these files, see the bulleted item For information on how to get these files, see the bulleted item
<link linkend='poky-extras-repo'>The "<link linkend='poky-extras-repo'>The <filename>poky-extras</filename> Git Repository</link>"
<filename>poky-extras</filename> Git Repository</link> in earlier in this manual.</para></listitem>
<xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual.
</para></listitem>
<listitem><para><emphasis>Establish a local copy of the Linux Yocto kernel files on your <listitem><para><emphasis>Establish a local copy of the Linux Yocto kernel files on your
system</emphasis>: In order to make modifications to the kernel you need two things: system</emphasis>: In order to make modifications to the kernel you need two things:
a bare clone of the Linux Yocto kernel you are modifying and a copy of that a bare clone of the Linux Yocto kernel you are modifying and
bare clone. a copy of that bare clone.
The bare clone is required by the build process and is the area to which you The bare clone is required by the build process and is the area to which you
push your kernel source changes. push your kernel source changes (pulling does not work with bare clones).
The copy of the bare clone is a local Git repository that contains all the kernel's The copy of the bare clone is a local Git repository that contains all the kernel's
source files. source files.
You make your changes to the files in this copy of the bare clone. You make your changes to the files in this copy of the bare clone.
For information on how to set these two items up, see the bulleted item For information on how to set these two items up, see the bulleted item
<link linkend='local-kernel-files'>Linux Yocto Kernel</link> in "<link linkend='local-kernel-files'>Linux Yocto Kernel</link>"
<xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual. earlier in this manual.</para></listitem>
</para></listitem>
<listitem><para><emphasis>Make changes to the kernel source code if <listitem><para><emphasis>Make changes to the kernel source code if
applicable</emphasis>: Modifying the kernel does not always mean directly applicable</emphasis>: Modifying the kernel does not always mean directly
changing source files. changing source files.
However, if you have to do this then you make the changes in the local However, if you have to do this, you make the changes in the local
Git repository you set up to hold the source files (i.e. the copy of the Git repository you set up to hold the source files (i.e. the copy of the
bare clone). bare clone).
Once the changes are made you need to use Git commands to commit the changes Once the changes are made, you need to use Git commands to commit the changes
and then push them to the bare clone.</para></listitem> and then push them to the bare clone.</para></listitem>
<listitem><para><emphasis>Make kernel configuration changes <listitem><para><emphasis>Make kernel configuration changes
to your local kernel layer if applicable</emphasis>: to your local kernel layer if applicable</emphasis>:
If your situation calls for changing the kernel's configuration you can If your situation calls for changing the kernel's configuration, you can
use <filename>menuconfig</filename> use <filename>menuconfig</filename>
to enable and disable kernel configurations. to enable and disable kernel configurations.
Using <filename>menuconfig</filename> allows you to develop and test the Using <filename>menuconfig</filename> allows you to interactively develop and test the
configuration changes you are making to the kernel.</para></listitem> configuration changes you are making to the kernel.
When saved, changes using <filename>menuconfig</filename> update the kernel's
<filename>.config</filename>.
As an alternative method to changing the kernel's configuration, you can simply
edit the <filename>.config</filename> found in the Yocto Project build
directory at <filename>tmp/sysroots/&lt;machine-name&gt;/kernel</filename>
directly.</para></listitem>
<listitem><para><emphasis>Add new kernel recipes if applicable</emphasis>: The standard <listitem><para><emphasis>Add new kernel recipes if applicable</emphasis>: The standard
layer structure organizes recipe files inside the layer structure organizes recipe files inside the
<filename>meta-kernel-dev</filename> layer that is within the <filename>meta-kernel-dev</filename> layer that is within the
<filename>poky-extras</filename> Git repository. <filename>poky-extras</filename> Git repository.
If you need to add new kernel recipes you add them within this layer. If you need to add new kernel recipes, you add them within this layer.
Also within this area you will find the <filename>.bbappend</filename> Also within this area, you will find the <filename>.bbappend</filename>
file that appends information to the kernel's recipe file used during the file that appends information to the kernel's recipe file used during the
build. build.
</para></listitem> </para></listitem>
<listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the <listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the
changes to your kernel (configurations, source code changes, recipe additions, changes to your kernel (configurations, source code changes, recipe additions,
or recipe changes) there remains a few things or recipe changes), there remains a few things
you need to do for the Yocto Project build system in order for it to create your image. you need to do in order for the Yocto Project build system to create your image.
If you have not done so you need to get the build environment ready by sourcing If you have not done so, you need to get the build environment ready by sourcing
the environment setup script described earlier. the environment setup script described earlier.
You also need to be sure two key configuration files You also need to be sure two key configuration files
(<filename>local.conf</filename> and <filename>bblayers.conf</filename>) (<filename>local.conf</filename> and <filename>bblayers.conf</filename>)
are configured appropriately.</para> are configured appropriately.</para>
<para>The entire process for building an image is overviewed in the <para>The entire process for building an image is overviewed in the
<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'> "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" section of the Yocto Project Quick Start.
Building an Image</ulink> section of the Yocto Project Quick Start.
You might want to reference this information. You might want to reference this information.
Also, you should look at the detailed examples found in the appendices at Also, you should look at the detailed examples found in the appendices at
end of this manual.</para></listitem> at the end of this manual.</para></listitem>
<listitem><para><emphasis>Build the image</emphasis>: The Yocto Project uses the BitBake <listitem><para><emphasis>Build the image</emphasis>: The Yocto Project
build system Poky uses the BitBake
tool to build images based on the type of image you want to create. tool to build images based on the type of image you want to create.
You can find more information on BitBake You can find more information on BitBake
<ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para> <ulink url='http://bitbake.berlios.de/manual/'>here</ulink>.</para>
<para>The build process supports several types of images to satisfy different needs. <para>The build process supports several types of images to satisfy different needs.
See See the appendix
<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'> "<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" in the
Reference: Images</ulink> in the
<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'> <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'>
Yocto Project Reference Manual</ulink> for information on supported Yocto Project Reference Manual</ulink> for information on supported
images.</para></listitem> images.</para></listitem>
<listitem><para><emphasis>Make your configuration changes available <listitem><para><emphasis>Make your configuration changes available
in the kernel layer</emphasis>: Up to this point all the configuration changes to the in the kernel layer</emphasis>: Up to this point, all the configuration changes to the
kernel have been done and tested iteratively. kernel have been done and tested iteratively.
Once they are tested and ready to go you can move them into the kernel layer, Once they are tested and ready to go, you can move them into the kernel layer,
which allows you to distribute the layer. which allows you to distribute the layer.</para></listitem>
[WRITER'S NOTE: Not sure if the layer is meta-kernel-dev or if it would be <listitem><para><emphasis>If applicable, share your in-tree changes</emphasis>:
a new layer copied from the work done there.]</para></listitem> If the changes you made
<listitem><para><emphasis>Push your configuration and recipe changes upstream to the are suited for all Linux Yocto users, you might want to push the changes to a
linux Yocto Git repository (in-tree changes)</emphasis>: If the changes you made contribution area for the Linux Yocto Git repository.
are suited for all Linux Yocto users you might want to push the changes up into Once the changes are pushed, you can request that they
the Linux Yocto Git repository so that they become part of the kernel tree be pulled into the master branch of the kernel tree.
and available to everyone using the kernel.</para></listitem> Doing so makes them available to everyone using the kernel.</para></listitem>
</orderedlist> </orderedlist>
</para> </para>
</section> </section>

BIN
documentation/dev-manual/figures/kernel-dev-flow.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 61 KiB

After

Width:  |  Height:  |  Size: 60 KiB