From a2666193173c0eeca763f774926763e7356277f8 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 10 Sep 2013 12:13:25 -0700 Subject: documentation: Added the memory-resident BitBake feature The main changes are captured in a new section devoted to the oe-init-build-env-memres script within the ref-structure.xml file and in the variables.xml file in a BBSERVER variable entry in the glossary. All other changes were necessary to integrate the new functionality into areas where running the setup script are discussed. Before this feature, there was a single setup script (oe-init-build-env). Consequently, wordings and such were designed exclusively for this single method. With the introduction of a second possible method to initialize the build environment, tweaks to many sections were needed. Beside the wording tweaks, appropriate cross-referencing was also needed. All these changes cover the integration of the new feature. Reported-by: Richard Purdie (From yocto-docs rev: c55c9a53c9b4cd1e06e6e81e32d56f9bbf5fe98c) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/faq.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'documentation/ref-manual/faq.xml') diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 71fb03aedb..69b679bbf7 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -682,9 +682,11 @@ Yes - you can easily do this. When you use BitBake to build an image, all the build output - goes into the directory created when you source the + goes into the directory created when you run the + build environment setup script (i.e. &OE_INIT_FILE; - setup script. + or + oe-init-build-env-memres). By default, this Build Directory is named build but can be named anything you want. -- cgit v1.2.3-54-g00ecf