From 942f915b2829ced6b719ca533c415c84e7060835 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 26 Mar 2013 10:02:36 -0700 Subject: [PATCH] ref-manual: Various edits to the "Build Overview" section. (From yocto-docs rev: ad017a31cc79b97baaa562d05aa0dab3bf45bd35) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/usingpoky.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index 0b0f02005c..14c6290945 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml @@ -30,7 +30,7 @@ The first thing you need to do is set up the OpenEmbedded build environment by sourcing the environment setup script as follows: - $ source &OE_INIT_FILE; [build_dir] + $ source &OE_INIT_FILE; [<build_dir>] @@ -38,13 +38,13 @@ The build_dir is optional and specifies the directory the OpenEmbedded build system uses for the build - the Build Directory. - If you do not specify a Build Directory it defaults to build + 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. For example, ~/build/x86 for a qemux86 target, and ~/build/arm for a qemuarm target. - See &OE_INIT_FILE; - for more information on this script. + See the "&OE_INIT_FILE;" + section for more information on this script. @@ -60,7 +60,7 @@ /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. + BusyBox. For more details about the images the OpenEmbedded build system supports, see the "Images" chapter.