diff options
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
| -rw-r--r-- | documentation/poky-ref-manual/usingpoky.xml | 27 |
1 files changed, 14 insertions, 13 deletions
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 @@ <para> 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. </para> <section id='usingpoky-build'> <title>Running a Build</title> <para> - 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 "<ulink url='&YOCTO_DOCS_QS_URL;#building-image'>Building an Image</ulink>" section of The Yocto Project Quick Start. This section provides a summary of the build process and provides information @@ -36,7 +36,7 @@ <para> The <filename>build_dir</filename> is optional and specifies the directory Yocto Project - uses for the build. + uses for the build - the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>. If you do not specify a build directory it defaults to <filename>build</filename> in your current working directory. A common practice is to use a different build directory for different targets. @@ -56,11 +56,11 @@ <para> The <filename>target</filename> is the name of the recipe you want to build. Common targets are the images in <filename>meta/recipes-core/images</filename>, - <filename>/meta/recipes-sato/images</filename>, etc. all found in the Yocto Project - files. + <filename>/meta/recipes-sato/images</filename>, etc. all found in the + <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. Or, the target can be the name of a recipe for a specific piece of software such as <application>busybox</application>. - 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 "<link linkend="ref-images">Reference: Images</link>" appendix. </para> @@ -89,7 +89,8 @@ <para> 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 + <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> in <filename class="directory">tmp/deploy/images</filename>. For information on how to run pre-built images such as <filename>qemux86</filename> and <filename>qemuarm</filename>, see the @@ -104,12 +105,12 @@ <title>Debugging Build Failures</title> <para> - 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. </para> @@ -263,10 +264,10 @@ </para> <para> - 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 <filename>logging.bbclass</filename> file in the - <filename>meta/classes</filename> directory of the Yocto Project files. + <filename>meta/classes</filename> folder of the + <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. </para> <section id='logging-with-python'> |