diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-09-30 11:13:31 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-10-04 13:46:43 +0100 |
| commit | e0172675a0c88741f6fafa4c84a6778e0b3a8136 (patch) | |
| tree | 7b71765c718ed3150504b6b6ae5f7b6c221a5e2a /documentation/kernel-manual | |
| parent | f527e3ce70eef37ab16a704df762481887a8db31 (diff) | |
| download | poky-e0172675a0c88741f6fafa4c84a6778e0b3a8136.tar.gz | |
documentation/kernel-manual/kernel-how-to.xml: Updated build strategy
This section used the term "tree construction" somewhat out of context.
The section really focuses on what the build process and the user does
prior to compilation. I changed wording to indicate the tree is
validated to be sure that the SRC_URI point to the right stuff and
that the BSP build branch exists.
(From yocto-docs rev: e6332d5045b21354b53bbbe1203f9d52d4d97964)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-manual')
| -rw-r--r-- | documentation/kernel-manual/kernel-how-to.xml | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml index 259e8200d7..df8605ed6f 100644 --- a/documentation/kernel-manual/kernel-how-to.xml +++ b/documentation/kernel-manual/kernel-how-to.xml | |||
| @@ -140,14 +140,14 @@ | |||
| 140 | <para> | 140 | <para> |
| 141 | Once a local Git repository of the Linux Yocto kernel exists on a development system, | 141 | Once a local Git repository of the Linux Yocto kernel exists on a development system, |
| 142 | you can consider the compilation phase of kernel development - building a kernel image. | 142 | you can consider the compilation phase of kernel development - building a kernel image. |
| 143 | Some prerequisites exist that must be met before starting the compilation | 143 | Some prerequisites exist that are validated by the build process before compilation |
| 144 | phase of the kernel build system: | 144 | starts: |
| 145 | </para> | 145 | </para> |
| 146 | 146 | ||
| 147 | <itemizedlist> | 147 | <itemizedlist> |
| 148 | <listitem><para>The <filename>SRC_URI</filename> must point to the kernel Git | 148 | <listitem><para>The <filename>SRC_URI</filename> points to the kernel Git |
| 149 | repository.</para></listitem> | 149 | repository.</para></listitem> |
| 150 | <listitem><para>A BSP build branch must exist. | 150 | <listitem><para>A BSP build branch exists. |
| 151 | This branch has the following form: | 151 | This branch has the following form: |
| 152 | <literallayout class='monospaced'> | 152 | <literallayout class='monospaced'> |
| 153 | <kernel_type>/<bsp_name> | 153 | <kernel_type>/<bsp_name> |
| @@ -155,15 +155,14 @@ | |||
| 155 | </itemizedlist> | 155 | </itemizedlist> |
| 156 | 156 | ||
| 157 | <para> | 157 | <para> |
| 158 | You can typically meet these prerequisites by running the tree construction/patching phase | 158 | The Yocto Project makes sure these conditions exist before attempting compilation. |
| 159 | of the build system. | 159 | Other means, however, do exist, such as as bootstrapping a BSP, see |
| 160 | However, other means do exist. | ||
| 161 | For examples of alternate workflows such as bootstrapping a BSP, see | ||
| 162 | the "<link linkend='workflow-examples'>Workflow Examples</link>". | 160 | the "<link linkend='workflow-examples'>Workflow Examples</link>". |
| 163 | </para> | 161 | </para> |
| 164 | 162 | ||
| 165 | <para> | 163 | <para> |
| 166 | Before building a kernel, the build process configures the kernel by processing all of the | 164 | Before building a kernel, the build process verifies the tree |
| 165 | and configures the kernel by processing all of the | ||
| 167 | configuration "fragments" specified by feature descriptions in the <filename>.scc</filename> | 166 | configuration "fragments" specified by feature descriptions in the <filename>.scc</filename> |
| 168 | files. | 167 | files. |
| 169 | As the features are compiled, associated kernel configuration fragments are noted | 168 | As the features are compiled, associated kernel configuration fragments are noted |
