summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-model.xml33
1 files changed, 20 insertions, 13 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 2b68fa7a1f..59c392f9db 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -186,13 +186,15 @@
186 </para></listitem> 186 </para></listitem>
187 <listitem><para><emphasis>Make recipe changes to your new BSP layer</emphasis>: Recipe 187 <listitem><para><emphasis>Make recipe changes to your new BSP layer</emphasis>: Recipe
188 changes include altering recipes (<filename>.bb</filename> files), removing 188 changes include altering recipes (<filename>.bb</filename> files), removing
189 recipes you don't use, and adding new recipes or append files 189 recipes you do not use, and adding new recipes or append files
190 (<filename>.bbappend</filename>) that you need to support your hardware. 190 (<filename>.bbappend</filename>) that you need to support your hardware.
191 </para></listitem> 191 </para></listitem>
192 <listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the 192 <listitem><para><emphasis>Prepare for the build</emphasis>: Once you have made all the
193 changes to your BSP layer, there remains a few things 193 changes to your BSP layer, there remains a few things
194 you need to do for the OpenEmbedded build system in order for it to create your image. 194 you need to do for the OpenEmbedded build system in order for it to create your image.
195 You need to get the build environment ready by sourcing an environment setup script 195 You need to get the build environment ready by sourcing an environment setup script
196 (i.e. <filename>oe-init-build-env</filename> or
197 <filename>oe-init-build-env-memres</filename>)
196 and you need to be sure two key configuration files are configured appropriately: 198 and you need to be sure two key configuration files are configured appropriately:
197 the <filename>conf/local.conf</filename> and the 199 the <filename>conf/local.conf</filename> and the
198 <filename>conf/bblayers.conf</filename> file. 200 <filename>conf/bblayers.conf</filename> file.
@@ -206,9 +208,9 @@
206 You might want to reference this information.</para></listitem> 208 You might want to reference this information.</para></listitem>
207 <listitem><para><emphasis>Build the image</emphasis>: The OpenEmbedded build system 209 <listitem><para><emphasis>Build the image</emphasis>: The OpenEmbedded build system
208 uses the BitBake tool to build images based on the type of image you want to create. 210 uses the BitBake tool to build images based on the type of image you want to create.
209 You can find more information about BitBake in the user manual, which is found in the 211 You can find more information about BitBake in the
210 <filename>bitbake/doc/manual</filename> directory of the 212 <ulink url='&YOCTO_DOCS_BB_URL;'>BitBake User Manual</ulink>.
211 <link linkend='source-directory'>Source Directory</link>.</para> 213 </para>
212 <para>The build process supports several types of images to satisfy different needs. 214 <para>The build process supports several types of images to satisfy different needs.
213 See the 215 See the
214 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter 216 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter
@@ -220,6 +222,7 @@
220 <para> 222 <para>
221 You can view a video presentation on "Building Custom Embedded Images with Yocto" 223 You can view a video presentation on "Building Custom Embedded Images with Yocto"
222 at <ulink url='http://free-electrons.com/blog/elc-2011-videos'>Free Electrons</ulink>. 224 at <ulink url='http://free-electrons.com/blog/elc-2011-videos'>Free Electrons</ulink>.
225 After going to the page, just search for "Embedded".
223 You can also find supplemental information in the 226 You can also find supplemental information in the
224 <ulink url='&YOCTO_DOCS_BSP_URL;'> 227 <ulink url='&YOCTO_DOCS_BSP_URL;'>
225 Yocto Project Board Support Package (BSP) Developer's Guide</ulink>. 228 Yocto Project Board Support Package (BSP) Developer's Guide</ulink>.
@@ -280,6 +283,9 @@
280 <listitem><para><emphasis><filename>linux-yocto-3.10</filename></emphasis> - The 283 <listitem><para><emphasis><filename>linux-yocto-3.10</filename></emphasis> - The
281 stable Yocto Project kernel to use with the Yocto Project Release 1.5. This kernel 284 stable Yocto Project kernel to use with the Yocto Project Release 1.5. This kernel
282 is based on the Linux 3.10 released kernel.</para></listitem> 285 is based on the Linux 3.10 released kernel.</para></listitem>
286 <listitem><para><emphasis><filename>linux-yocto-3.14</filename></emphasis> - The
287 stable Yocto Project kernel to use with the Yocto Project Release 1.6. This kernel
288 is based on the Linux 3.14 released kernel.</para></listitem>
283 <listitem><para><emphasis><filename>linux-yocto-dev</filename></emphasis> - A development 289 <listitem><para><emphasis><filename>linux-yocto-dev</filename></emphasis> - A development
284 kernel based on the latest upstream release candidate available.</para></listitem> 290 kernel based on the latest upstream release candidate available.</para></listitem>
285 </itemizedlist> 291 </itemizedlist>
@@ -377,7 +383,7 @@
377 </para> 383 </para>
378 384
379 <para> 385 <para>
380 Again, for additional information the Yocto Project kernel's 386 Again, for additional information on the Yocto Project kernel's
381 architecture and its branching strategy, see the 387 architecture and its branching strategy, see the
382 <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel Development Manual</ulink>. 388 <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel Development Manual</ulink>.
383 You can also reference the 389 You can also reference the
@@ -417,11 +423,12 @@
417 <link linkend='build-directory'>Build Directory</link> 423 <link linkend='build-directory'>Build Directory</link>
418 created by the 424 created by the
419 OpenEmbedded build system when you run BitBake. 425 OpenEmbedded build system when you run BitBake.
420 If you have never built the kernel you are interested in, you need to run 426 If you have never built the kernel in which you are
421 an initial build to establish local kernel source files.</para> 427 interested, you need to run an initial build to
428 establish local kernel source files.</para>
422 <para>If you are building an image for the first time, you need to get the build 429 <para>If you are building an image for the first time, you need to get the build
423 environment ready by sourcing an environment setup script 430 environment ready by sourcing an environment setup script
424 (e.g. <filename>oe-init-build-env</filename> or 431 (i.e. <filename>oe-init-build-env</filename> or
425 <filename>oe-init-build-env-memres</filename>). 432 <filename>oe-init-build-env-memres</filename>).
426 You also need to be sure two key configuration files 433 You also need to be sure two key configuration files
427 (<filename>local.conf</filename> and <filename>bblayers.conf</filename>) 434 (<filename>local.conf</filename> and <filename>bblayers.conf</filename>)
@@ -430,9 +437,9 @@
430 "<ulink url='&YOCTO_DOCS_QS_URL;#building-image'>Building an Image</ulink>" 437 "<ulink url='&YOCTO_DOCS_QS_URL;#building-image'>Building an Image</ulink>"
431 section of the Yocto Project Quick Start. 438 section of the Yocto Project Quick Start.
432 You might want to reference this information. 439 You might want to reference this information.
433 You can find more information on BitBake in the user manual, which is found in the 440 You can find more information on BitBake in the
434 <filename>bitbake/doc/manual</filename> directory of the 441 <ulink url='&YOCTO_DOCS_BB_URL;'>BitBake User Manual</ulink>.
435 Source Directory.</para> 442 </para>
436 <para>The build process supports several types of images to satisfy different needs. 443 <para>The build process supports several types of images to satisfy different needs.
437 See the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter in 444 See the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter in
438 the Yocto Project Reference Manual for information on supported images. 445 the Yocto Project Reference Manual for information on supported images.
@@ -441,7 +448,7 @@
441 applicable</emphasis>: Modifying the kernel does not always mean directly 448 applicable</emphasis>: Modifying the kernel does not always mean directly
442 changing source files. 449 changing source files.
443 However, if you have to do this, you make the changes to the files in the 450 However, if you have to do this, you make the changes to the files in the
444 Build directory.</para></listitem> 451 Build Directory.</para></listitem>
445 <listitem><para><emphasis>Make kernel configuration changes 452 <listitem><para><emphasis>Make kernel configuration changes
446 if applicable</emphasis>: 453 if applicable</emphasis>:
447 If your situation calls for changing the kernel's configuration, you can 454 If your situation calls for changing the kernel's configuration, you can
@@ -478,7 +485,7 @@
478 to run on your target hardware, which is running a kernel image created using the 485 to run on your target hardware, which is running a kernel image created using the
479 OpenEmbedded build system. 486 OpenEmbedded build system.
480 The Yocto Project provides an 487 The Yocto Project provides an
481 <ulink url='&YOCTO_DOCS_ADT_URL;#adt-intro-section'>Application Development Toolkit (ADT)</ulink> 488 <ulink url='&YOCTO_DOCS_ADT_URL;#adt-intro'>Application Development Toolkit (ADT)</ulink>
482 and stand-alone 489 and stand-alone
483 <ulink url='&YOCTO_DOCS_ADT_URL;#the-cross-development-toolchain'>cross-development toolchains</ulink> 490 <ulink url='&YOCTO_DOCS_ADT_URL;#the-cross-development-toolchain'>cross-development toolchains</ulink>
484 that facilitate quick development and integration of your application into its runtime environment. 491 that facilitate quick development and integration of your application into its runtime environment.