From d9b24ac5e7b8e9f3d8411bb7f9e8c4e603b67ff1 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 27 Mar 2013 09:19:43 -0700 Subject: [PATCH] ref-manual: Minor edits to "oe-init-build-env". (From yocto-docs rev: a15772bc73fe346ae96304f3d1d116958fee0c49) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-structure.xml | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index 0ad7b56621..f378419127 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml @@ -175,19 +175,20 @@ This script sets up the OpenEmbedded build environment. Running this script with the source command in - a shell makes changes to PATH and sets other core BitBake variables based on the - current working directory. + a shell makes changes to PATH and sets other + core BitBake variables based on the current working directory. You need to run this script before running BitBake commands. - The script uses other scripts within the scripts directory to do - the bulk of the work. + The script uses other scripts within the + scripts directory to do the bulk of the work. - By default, running this script without a Build Directory argument creates the - build directory. - If you provide a Build Directory argument when you source - the script, you direct OpenEmbedded build system to create a - Build Directory of your choice. + By default, running this script without a + Build Directory + argument creates the build directory. + If you provide a Build Directory argument when you + source the script, you direct OpenEmbedded + build system to create a Build Directory of your choice. For example, the following command creates a Build Directory named mybuilds that is outside of the Source Directory: