mirror of
https://git.yoctoproject.org/poky
synced 2026-05-31 00:39:46 +00:00
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>
This commit is contained in:
committed by
Richard Purdie
parent
cc2626727c
commit
a266619317
@@ -710,6 +710,28 @@ Core layer for images cannot be removed
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-BBSERVER'><glossterm>BBSERVER</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
Points to the server that runs memory-resident BitBake.
|
||||
This variable is set by the
|
||||
<link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>
|
||||
setup script and should not be hand-edited.
|
||||
The variable is only used when you employ memory-resident
|
||||
BitBake.
|
||||
The setup script exports the value as follows:
|
||||
<literallayout class='monospaced'>
|
||||
export BBSERVER=localhost:$port
|
||||
</literallayout>
|
||||
For more information on how the
|
||||
<filename>BBSERVER</filename> is used, see the
|
||||
<filename>oe-init-build-env-memres</filename> script, which
|
||||
is located in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id='var-BINCONFIG_GLOB'><glossterm>BINCONFIG_GLOB</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
@@ -762,13 +784,16 @@ Core layer for images cannot be removed
|
||||
|
||||
<glossentry id='var-BUILDDIR'><glossterm>BUILDDIR</glossterm>
|
||||
<glossdef>
|
||||
<para>Points to the location of the
|
||||
<para>
|
||||
Points to the location of the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
You can define this directory indirectly through the
|
||||
<link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
|
||||
script by passing in a Build Directory path when you run the
|
||||
script.
|
||||
If you run the script and do not provide a Build Directory
|
||||
and
|
||||
<link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>
|
||||
scripts by passing in a Build Directory path when you run
|
||||
the scripts.
|
||||
If you run the scripts and do not provide a Build Directory
|
||||
path, the <filename>BUILDDIR</filename> defaults to
|
||||
<filename>build</filename> in the current directory.
|
||||
</para>
|
||||
|
||||
Reference in New Issue
Block a user