From 860acfbdaa0d0143d7c6ffd2f77e92189ea223d7 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jun 2012 11:10:39 -0700 Subject: documentation/dev-manual/dev-manual-kernel-appendix.xml: 1.1.2 variables and updates First pass at implementing the poky.ent variables. Also changed text in cases where it was not specific to the example. (From yocto-docs rev: a44657aac3a801483ea1ab3ff66fa6444438842d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-kernel-appendix.xml | 80 ++++++++++++---------- 1 file changed, 45 insertions(+), 35 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml index 06db1f91a8..80def3afdb 100644 --- a/documentation/dev-manual/dev-manual-kernel-appendix.xml +++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml @@ -1,5 +1,6 @@ +"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" +[ %poky; ] > @@ -149,14 +150,14 @@ $ git branch -a $ git tag -l - This example uses the Yocto Project 1.1.1 Release code named "edison", - which maps to the edison branch in the repository. - The following commands create and checkout the local edison + This example uses the Yocto Project &DISTRO; Release code named "&DISTRO_NAME;", + which maps to the &DISTRO_NAME; branch in the repository. + The following commands create and checkout the local &DISTRO_NAME; branch: - $ git checkout -b edison origin/edison - Branch edison set up to track remote branch edison from origin. - Switched to a new branch 'edison' + $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; + Branch &DISTRO_NAME; set up to track remote branch &DISTRO_NAME; from origin. + Switched to a new branch '&DISTRO_NAME;' @@ -244,9 +245,9 @@ If your host development system supports multi-core and multi-thread capabilities, you can uncomment these statements and set the variables to significantly shorten the full build time. - As a guideline, set BB_NUMBER_THREADS to twice the number - of cores your machine supports and set PARALLEL_MAKE to one and - a half times the number of cores your machine supports. + As a guideline, set both BB_NUMBER_THREADS and + PARALLEL_MAKE to twice the number + of cores your machine supports. The following two commands source the build environment setup script and build the default qemux86 image. @@ -411,9 +412,8 @@ build time if your host supports multi-core and multi-thread capabilities: BB_NUMBER_THREADS and PARALLEL_MAKE. If the host system has multiple cores then you can optimize build time - by setting BB_NUMBER_THREADS to twice the number of - cores and setting PARALLEL_MAKE to one and a half times the - number of cores. + by setting both these variables to twice the number of + cores. Identify Your meta-kernel-dev Layer: The BBLAYERS variable in the bblayers.conf file found in the @@ -455,15 +455,19 @@ - Before attempting to build the modified kernel, there is one more set of changes you + Before attempting to build the modified kernel, there is one more set of changes you need to make in the meta-kernel-dev layer. Because all the kernel .bbappend files are parsed during the build process regardless of whether you are using them or not, you should either comment out the COMPATIBLE_MACHINE statements in all - unused .bbappend files. - Alternatively, you can simply remove all the files + unused .bbappend files, or simply remove (or rename) all the files except the one your are using for the build - (i.e. linux-yocto_3.0.bbappend in this example). + (i.e. linux-yocto_3.0.bbappend in this example). + If you do not make one of these two adjustments, your machine will be compatible + with all the kernel recipes in the meta-kernel-dev layer. + When your machine is comapatible with all the kernel recipes, the build attempts + to build all kernels in the layer. + You could end up with build errors blocking your work. @@ -477,18 +481,21 @@ Your environment should be set up since you previously sourced the oe-init-build-env script. If it isn't, source the script again from poky. + + $ cd ~/poky + $ source oe-init-build-env + Be sure old images are cleaned out by running the - cleanall BitBake task as follows: + cleanall BitBake task as follows from your build directory: - $ cd ~/poky $ bitbake -c cleanall linux-yocto Never remove any files by hand from the tmp/deploy directory insided the local Yocto Project files build directory. Always use the BitBake cleanall task to clear out previous builds. - Build the kernel image using this command: + Next, build the kernel image using this command: $ bitbake -k core-image-minimal @@ -532,9 +539,9 @@ in "Modifying the Kernel Source Code" you should already have the Yocto Project files set up on your host machine. - If this is the case, go to then next section titled + If this is the case, go to the next section, which is titled "Examining the Default - CONFIG_SMP Behavior" and continue with the + CONFIG_SMP Behavior", and continue with the example. @@ -559,14 +566,14 @@ $ git branch -a $ git tag -l - This example uses the Yocto Project 1.1.1 Release code named "edison", - which maps to the edison branch in the repository. - The following commands create and checkout the local edison + This example uses the Yocto Project &DISTRO; Release code named "&DISTRO_NAME;", + which maps to the &DISTRO_NAME; branch in the repository. + The following commands create and checkout the local &DISTRO_NAME; branch: - $ git checkout -b edison origin/edison - Branch edison set up to track remote branch edison from origin. - Switched to a new branch 'edison' + $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; + Branch &DISTRO_NAME; set up to track remote branch &DISTRO_NAME; from origin. + Switched to a new branch '&DISTRO_NAME;' @@ -623,7 +630,7 @@
- Examining the Default <filename>CONFIG_SMP</filename> Behavior + Examining the Default  <filename>CONFIG_SMP</filename> Behavior By default, CONFIG_SMP supports single processor machines. @@ -650,7 +657,7 @@
- Changing the <filename>CONFIG_SMP</filename> Configuration Using <filename>menuconfig</filename> + Changing the  <filename>CONFIG_SMP</filename> Configuration Using  <filename>menuconfig</filename> The menuconfig tool provides an interactive method with which @@ -694,16 +701,19 @@ is updated. This is the file that the build system uses to configure the Linux Yocto kernel when it is built. - You can find and examine this file in the Yocto Project files Git repository in + You can find and examine this file in the Yocto Project Files Git repository in the build directory. - This example uses the following. - Note that this example directory is artificially split and many of the characters - in the actually filename are omitted in order to make it more - readable: + This example uses the following: ~/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.0.10+git1+d38... ...3a9ac596f7a-r3/linux-qemux86-standard-build + + The previous example directory is artificially split and many of the characters + in the actual filename are omitted in order to make it more readable. + Also, depending on the kernel you are using, the exact pathname might differ + slightly. + -- cgit v1.2.3-54-g00ecf