From 2b51188de67f16423da2b0c0b3859b8900de6828 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 22 Oct 2012 13:16:49 -0700 Subject: documentation: dev-manual - Final changes before 1.3 lockdown. Made minor changes as needed due to some new sections, links, and capitalization standards. (From yocto-docs rev: bc966e5a78dadd14ecf1896a36e40a9b256bae77) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 35 ++++++++++++++------------- 1 file changed, 18 insertions(+), 17 deletions(-) (limited to 'documentation/dev-manual/dev-manual-model.xml') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 4452d2a4e2..c14c524aa5 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -236,7 +236,7 @@ "Patching the Kernel" section for an example that changes the source code of the kernel. For information on how to configure the kernel, see the - "Configuring the Kernel section. + "Configuring the Kernel" section.
@@ -347,7 +347,8 @@ What happens during the build? When you build the kernel on your development system, all files needed for the build are taken from the source repositories pointed to by the - SRC_URI variable and gathered in a temporary work area + SRC_URI variable + and gathered in a temporary work area where they are subsequently used to create the unique kernel. Thus, in a sense, the process constructs a local source tree specific to your kernel to generate the new kernel image - a source generator if you will. @@ -394,8 +395,8 @@ "The Packages" sections both in the Yocto Project Quick Start for requirements. Establish a local copy of project files on your - system: Having the source - directory on your system gives you access to the build process and tools + system: Having the Source + Directory on your system gives you access to the build process and tools you need. For information on how to get these files, see the bulleted item "Yocto Project Release" earlier in this manual. @@ -439,7 +440,7 @@ .config. Try to resist the temptation of directly editing the .config file found in the - build directory at + Build Directory at tmp/sysroots/<machine-name>/kernel. Doing so, can produce unexpected results when the OpenEmbedded build system regenerates the configuration file. @@ -986,10 +987,10 @@ Build System Derived Toolchain: Select this mode if the cross-toolchain has been installed and built - as part of the build directory. + as part of the Build Directory. When you select Build system derived toolchain, you are using the toolchain bundled - inside the build directory. + inside the Build Directory. @@ -1008,9 +1009,9 @@ However, doing so is discouraged. If you are using a system-derived toolchain, the path you provide for the Toolchain Root Location - field is the build directory. + field is the Build Directory. See the "Using - BitBake and the build directory" section in the Yocto Project Application + BitBake and the Build Directory" section in the Yocto Project Application Developer's Guide for information on how to install the toolchain into the build directory. Specify the Sysroot Location: @@ -1053,7 +1054,7 @@ directory. and specify any custom options. If you selected Build system derived toolchain, the target kernel you built will be located in the - build directory in tmp/deploy/images directory. + Build Directory in tmp/deploy/images directory. If you selected Standalone pre-built toolchain, the pre-built image you downloaded is located in the directory you specified when you downloaded the image. @@ -1409,7 +1410,7 @@ directory. Select your Yocto Bitbake Commander project. Select Project -> Launch HOB. - Enter the build directory where you want to put your final images. + Enter the Build Directory where you want to put your final images. Click OK to launch Hob. Use Hob to customize and build your own images. For information on Hob, see the @@ -1480,7 +1481,7 @@ directory. to figure out your solution. After you have initially built the package, you can iteratively tweak the source code, which is located in the - build directory, and then + Build Directory, and then you can force a re-compile and quickly test your altered code. Once you settle on a solution, you can then preserve your changes in the form of patches. @@ -1494,7 +1495,7 @@ directory. During a build, the unpacked temporary source code used by recipes - to build packages is available in the build directory as + to build packages is available in the Build Directory as defined by the S variable. Below is the default value for the S variable as defined in the @@ -1528,7 +1529,7 @@ directory. Let's look at an example without variables. Assuming a top-level Source Directory named poky - and a default build directory of poky/build, + and a default Build Directory of poky/build, the following is the work directory for the acl recipe that creates the acl package: @@ -1543,7 +1544,7 @@ directory. ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} Again, assuming top-level Source Directory named poky - and a default build directory of poky/build, the + and a default Build Directory of poky/build, the following are the work and temporary source directories, respectively, for the acl package that is being built for a MIPS-based device: @@ -1591,7 +1592,7 @@ directory. Find the Source Code: The temporary source code used by the OpenEmbedded build system is kept in the - build directory. + Build Directory. See the "Finding the Temporary Source Code" section to learn how to locate the directory that has the temporary source code for a @@ -1689,7 +1690,7 @@ directory. Find the Source Code: The temporary source code used by the OpenEmbedded build system is kept in the - build directory. + Build Directory. See the "Finding the Temporary Source Code" section to learn how to locate the directory that has the temporary source code for a -- cgit v1.2.3-54-g00ecf