summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/closer-look.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-09-10 12:13:25 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-12 16:50:10 +0100
commita2666193173c0eeca763f774926763e7356277f8 (patch)
treef72dc0bc8919527029a60ee67a8d71bd3033de9c /documentation/ref-manual/closer-look.xml
parentcc2626727c61025b5cf0fcc214ddb896de7bbc39 (diff)
downloadpoky-a2666193173c0eeca763f774926763e7356277f8.tar.gz
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 <richard.purdie@linuxfoundation.org> (From yocto-docs rev: c55c9a53c9b4cd1e06e6e81e32d56f9bbf5fe98c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
-rw-r--r--documentation/ref-manual/closer-look.xml13
1 files changed, 9 insertions, 4 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 8c3ceb7210..7e8d528897 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -106,7 +106,11 @@
106 configuration files. 106 configuration files.
107 These example files are used as a basis for creating actual 107 These example files are used as a basis for creating actual
108 configuration files when you source the build environment 108 configuration files when you source the build environment
109 script <filename>oe-init-build-env</filename>. 109 script
110 (i.e.
111 <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
112 or
113 <link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>).
110 </para> 114 </para>
111 115
112 <para> 116 <para>
@@ -119,14 +123,15 @@
119 and <filename>bblayers.conf</filename> configuration files. 123 and <filename>bblayers.conf</filename> configuration files.
120 These default configuration files are created only if versions 124 These default configuration files are created only if versions
121 do not already exist in the Build Directory at the time you 125 do not already exist in the Build Directory at the time you
122 source the <filename>oe-init-build-env</filename> script. 126 source the build environment setup script.
123 </para> 127 </para>
124 128
125 <para> 129 <para>
126 Because the Poky repository is fundamentally an aggregation of 130 Because the Poky repository is fundamentally an aggregation of
127 existing repositories, some users might be familiar with running 131 existing repositories, some users might be familiar with running
128 the <filename>oe-init-build-env</filename> script in the context of 132 the <filename>&OE_INIT_FILE;</filename> or
129 separate OpenEmbedded-Core and BitBake repositories rather than a 133 <filename>oe-init-build-env-memres</filename> script in the context
134 of separate OpenEmbedded-Core and BitBake repositories rather than a
130 single Poky repository. 135 single Poky repository.
131 This discussion assumes the script is executed from within a cloned 136 This discussion assumes the script is executed from within a cloned
132 or unpacked version of Poky. 137 or unpacked version of Poky.