summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-05 09:35:03 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-07 13:15:37 +0100
commitf32ee618c23650aed43fcd0f0f5914d5ba1ffbf0 (patch)
tree7c3ae306701f340d7e62d5b5d07bb84eb2be1349
parent6d5e8360cacdc8169ff3538ab9b0653f37698eda (diff)
downloadpoky-f32ee618c23650aed43fcd0f0f5914d5ba1ffbf0.tar.gz
documentation: dev-manual - added OE_INIT_FILE and went to 3.4
In the Kernel example appendix I changed some remaining 3.2 kernel strings to 3.4. Also I added the OE_INIT_FILE variable from poky.ent for use instead of the "oe-init-build-env" string. (From yocto-docs rev: 1d9d8d72d197bdd81756eed7fe1529f341de6089) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-kernel-appendix.xml32
1 files changed, 16 insertions, 16 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml
index 810919f908..387e4fdf45 100644
--- a/documentation/dev-manual/dev-manual-kernel-appendix.xml
+++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml
@@ -235,7 +235,7 @@
235 <note> 235 <note>
236 Because a full build can take hours, you should check two variables in the 236 Because a full build can take hours, you should check two variables in the
237 <filename>build</filename> directory that is created after you source the 237 <filename>build</filename> directory that is created after you source the
238 <filename>oe-init-build-env</filename> script. 238 <filename>&OE_INIT_FILE;</filename> script.
239 You can find these variables 239 You can find these variables
240 <filename>BB_NUMBER_THREADS</filename> and <filename>PARALLEL_MAKE</filename> 240 <filename>BB_NUMBER_THREADS</filename> and <filename>PARALLEL_MAKE</filename>
241 in the <filename>build/conf</filename> directory in the 241 in the <filename>build/conf</filename> directory in the
@@ -337,7 +337,7 @@
337 337
338 <para> 338 <para>
339 The file you change in this example is named <filename>calibrate.c</filename> 339 The file you change in this example is named <filename>calibrate.c</filename>
340 and is located in the <filename>my-linux-yocto-3.2-work</filename> Git repository 340 and is located in the <filename>my-linux-yocto-3.4-work</filename> Git repository
341 (the copy of the bare clone) in <filename>init</filename>. 341 (the copy of the bare clone) in <filename>init</filename>.
342 This example simply inserts several <filename>printk</filename> statements 342 This example simply inserts several <filename>printk</filename> statements
343 at the beginning of the <filename>calibrate_delay</filename> function. 343 at the beginning of the <filename>calibrate_delay</filename> function.
@@ -401,7 +401,7 @@
401 <para> 401 <para>
402 The following command pushes the changes to the bare clone: 402 The following command pushes the changes to the bare clone:
403 <literallayout class='monospaced'> 403 <literallayout class='monospaced'>
404 $ git push origin common-pc-base:standard/default/common-pc/base 404 $ git push origin standard-common-pc-base:standard/default/common-pc/base
405 </literallayout> 405 </literallayout>
406 </para> 406 </para>
407 </section> 407 </section>
@@ -461,17 +461,17 @@
461 " 461 "
462 </literallayout></para></listitem> 462 </literallayout></para></listitem>
463 <listitem><para><emphasis>Identify Your Source Files:</emphasis> In the 463 <listitem><para><emphasis>Identify Your Source Files:</emphasis> In the
464 <filename>linux-yocto_3.2.bbappend</filename> file located in the 464 <filename>linux-yocto_3.4.bbappend</filename> file located in the
465 <filename>poky-extras/meta-kernel-dev/recipes-kernel/linux</filename> 465 <filename>poky-extras/meta-kernel-dev/recipes-kernel/linux</filename>
466 directory, you need to identify the location of the 466 directory, you need to identify the location of the
467 local source code, which in this example is the bare clone named 467 local source code, which in this example is the bare clone named
468 <filename>linux-yocto-3.2.git</filename>. 468 <filename>linux-yocto-3.4.git</filename>.
469 To do this, set the <filename>KSRC_linux_yocto</filename> variable to point to your 469 To do this, set the <filename>KSRC_linux_yocto</filename> variable to point to your
470 local <filename>linux-yocto-3.2.git</filename> Git repository by adding the 470 local <filename>linux-yocto-3.4.git</filename> Git repository by adding the
471 following statement. 471 following statement.
472 Be sure to substitute your user information in the statement: 472 Be sure to substitute your user information in the statement:
473 <literallayout class='monospaced'> 473 <literallayout class='monospaced'>
474 KSRC_linux_yocto_3_2 ?= "/home/scottrif/linux-yocto-3.2.git" 474 KSRC_linux_yocto_3_2 ?= "/home/scottrif/linux-yocto-3.4.git"
475 </literallayout></para></listitem> 475 </literallayout></para></listitem>
476 </itemizedlist> 476 </itemizedlist>
477 </para> 477 </para>
@@ -484,7 +484,7 @@
484 comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all 484 comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all
485 unused <filename>.bbappend</filename> files, or simply remove (or rename) all the files 485 unused <filename>.bbappend</filename> files, or simply remove (or rename) all the files
486 except the one your are using for the build 486 except the one your are using for the build
487 (i.e. <filename>linux-yocto_3.2.bbappend</filename> in this example).</para> 487 (i.e. <filename>linux-yocto_3.4.bbappend</filename> in this example).</para>
488 <para>If you do not make one of these two adjustments, your machine will be compatible 488 <para>If you do not make one of these two adjustments, your machine will be compatible
489 with all the kernel recipes in the <filename>meta-kernel-dev</filename> layer. 489 with all the kernel recipes in the <filename>meta-kernel-dev</filename> layer.
490 When your machine is comapatible with all the kernel recipes, the build attempts 490 When your machine is comapatible with all the kernel recipes, the build attempts
@@ -501,11 +501,11 @@
501 Do the following: 501 Do the following:
502 <orderedlist> 502 <orderedlist>
503 <listitem><para>Your environment should be set up since you previously sourced 503 <listitem><para>Your environment should be set up since you previously sourced
504 the <filename>oe-init-build-env</filename> script. 504 the <filename>&OE_INIT_FILE;</filename> script.
505 If it isn't, source the script again from <filename>poky</filename>. 505 If it isn't, source the script again from <filename>poky</filename>.
506 <literallayout class='monospaced'> 506 <literallayout class='monospaced'>
507 $ cd ~/poky 507 $ cd ~/poky
508 $ source oe-init-build-env 508 $ source &OE_INIT_FILE;
509 </literallayout> 509 </literallayout>
510 </para></listitem> 510 </para></listitem>
511 <listitem><para>Be sure old images are cleaned out by running the 511 <listitem><para>Be sure old images are cleaned out by running the
@@ -605,7 +605,7 @@
605 <note> 605 <note>
606 Because a full build can take hours, you should check two variables in the 606 Because a full build can take hours, you should check two variables in the
607 <filename>build</filename> directory that is created after you source the 607 <filename>build</filename> directory that is created after you source the
608 <filename>oe-init-build-env</filename> script. 608 <filename>&OE_INIT_FILE;</filename> script.
609 You can find these variables 609 You can find these variables
610 <filename>BB_NUMBER_THREADS</filename> and <filename>PARALLEL_MAKE</filename> 610 <filename>BB_NUMBER_THREADS</filename> and <filename>PARALLEL_MAKE</filename>
611 in the <filename>build/conf</filename> directory in the 611 in the <filename>build/conf</filename> directory in the
@@ -623,7 +623,7 @@
623 If necessary, the script creates the build directory: 623 If necessary, the script creates the build directory:
624 <literallayout class='monospaced'> 624 <literallayout class='monospaced'>
625 $ cd ~/poky 625 $ cd ~/poky
626 $ source oe-init-build-env 626 $ source &OE_INIT_FILE;
627 627
628 ### Shell environment set up for builds. ### 628 ### Shell environment set up for builds. ###
629 629
@@ -699,19 +699,19 @@
699 The <filename>menuconfig</filename> tool provides an interactive method with which 699 The <filename>menuconfig</filename> tool provides an interactive method with which
700 to set kernel configurations. 700 to set kernel configurations.
701 You need to run <filename>menuconfig</filename> inside the Yocto BitBake environment. 701 You need to run <filename>menuconfig</filename> inside the Yocto BitBake environment.
702 Thus, the environment must be set up using the <filename>oe-init-build-env</filename> 702 Thus, the environment must be set up using the <filename>&OE_INIT_FILE;</filename>
703 script found in the build directory. 703 script found in the build directory.
704 If you have not sourced this script do so with the following commands: 704 If you have not sourced this script do so with the following commands:
705 <literallayout class='monospaced'> 705 <literallayout class='monospaced'>
706 $ cd ~/poky 706 $ cd ~/poky
707 $ source oe-init-build-env 707 $ source &OE_INIT_FILE;
708 </literallayout> 708 </literallayout>
709 </para> 709 </para>
710 710
711 <para> 711 <para>
712 After setting up the environment to run <filename>menuconfig</filename>, you are ready 712 After setting up the environment to run <filename>menuconfig</filename>, you are ready
713 to use the tool to interactively change the kernel configuration. 713 to use the tool to interactively change the kernel configuration.
714 In this example, we are basing our changes on the <filename>linux-yocto-3.2</filename> 714 In this example, we are basing our changes on the <filename>linux-yocto-3.4</filename>
715 kernel. 715 kernel.
716 The OpenEmbedded build system recognizes this kernel as 716 The OpenEmbedded build system recognizes this kernel as
717 <filename>linux-yocto</filename>. 717 <filename>linux-yocto</filename>.
@@ -742,7 +742,7 @@
742 You can find and examine this file in the build directory. 742 You can find and examine this file in the build directory.
743 This example uses the following: 743 This example uses the following:
744 <literallayout class='monospaced'> 744 <literallayout class='monospaced'>
745 ~/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.2.11+git1+84f... 745 ~/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f...
746 ...656ed30-r1/linux-qemux86-standard-build 746 ...656ed30-r1/linux-qemux86-standard-build
747 </literallayout> 747 </literallayout>
748 <note> 748 <note>