From 5966b44893a39847d3d590566dd488323a11ff73 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 2 Jul 2012 14:34:39 -0700 Subject: documentation/poky-ref-manual: Yocto Project scrub I have changed as many "Yocto Project" terms as possible so that better reflect reality. (From yocto-docs rev: 5f729e53b0cb653c97621e4e6598d9295d60ada5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/usingpoky.xml | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) (limited to 'documentation/poky-ref-manual/usingpoky.xml') diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index 914a0f5771..6ce36014f1 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml @@ -8,15 +8,15 @@ This chapter describes common usage for the Yocto Project. The information is introductory in nature as other manuals in the Yocto Project - provide more details on how to use the Yocto Project. + documentation set provide more details on how to use the Yocto Project.
Running a Build - You can find general information on how to build an image using the - Yocto Project in the + You can find general information on how to build an image using the OpenEmbedded build + system in the "Building an Image" section of The Yocto Project Quick Start. This section provides a summary of the build process and provides information @@ -36,7 +36,7 @@ The build_dir is optional and specifies the directory Yocto Project - uses for the build. + uses for the build - the build directory. If you do not specify a build directory it defaults to build in your current working directory. A common practice is to use a different build directory for different targets. @@ -56,11 +56,11 @@ The target is the name of the recipe you want to build. Common targets are the images in meta/recipes-core/images, - /meta/recipes-sato/images, etc. all found in the Yocto Project - files. + /meta/recipes-sato/images, etc. all found in the + source directory. Or, the target can be the name of a recipe for a specific piece of software such as busybox. - For more details about the images the Yocto Project supports, see the + For more details about the images the OpenEmbedded build system supports, see the "Reference: Images" appendix. @@ -89,7 +89,8 @@ Once an image has been built, it often needs to be installed. - The images and kernels built by the Yocto Project are placed in the build directory in + The images and kernels built by the OpenEmbedded build system are placed in the + build directory in tmp/deploy/images. For information on how to run pre-built images such as qemux86 and qemuarm, see the @@ -104,12 +105,12 @@ Debugging Build Failures - The exact method for debugging Yocto Project build failures depends on the nature of the + The exact method for debugging build failures depends on the nature of the problem and on the system's area from which the bug originates. Standard debugging practices such as comparison against the last known working version with examination of the changes and the re-application of steps to identify the one causing the problem are - valid for Yocto Project just as they are for any other system. + valid for the Yocto Project just as they are for any other system. Even though it is impossible to detail every possible potential failure, this section provides some general tips to aid in debugging. @@ -263,10 +264,10 @@ - For guidance on how logging is handled - in both Python and Bash recipes, see the + For guidance on how logging is handled in both Python and Bash recipes, see the logging.bbclass file in the - meta/classes directory of the Yocto Project files. + meta/classes folder of the + source directory.
-- cgit v1.2.3-54-g00ecf