From b103ff6ba7a91d5bc83816f300b95361de8e700f Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 21 Sep 2017 09:36:46 -0700 Subject: documentation: Purged "oe-init-build-env-memres" from docs Fixes [YOCTO #11968] Purged all occurrences of the "oe-init-build-env-memres" script from the YP documentation set. Occurrences in a lot of places. The BBSERVER variable was also impacted and had to have the definition updated. (From yocto-docs rev: 274b05108d1bc53df20c11ab2efa15363bce23da) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 56 +++++++++++++----------------- 1 file changed, 25 insertions(+), 31 deletions(-) (limited to 'documentation/ref-manual/ref-variables.xml') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index e34cfbcffb..8b1ca83938 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -1299,29 +1299,29 @@ BBSERVER - BBSERVER[doc] = "Points to the server that runs memory-resident BitBake." + BBSERVER[doc] = "Points to the BitBake remote server." - Points to the server that runs memory-resident BitBake. - This variable is set by the - oe-init-build-env-memres - 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: + If defined in the BitBake environment, + BBSERVER points to the BitBake + remote server. + + + + Use the following format to export the variable to the + BitBake environment: - export BBSERVER=localhost:$port + export BBSERVER=localhost:$port" - For more information on how the - BBSERVER is used, see the - oe-init-build-env-memres script, which - is located in the - Source Directory. + By default, BBSERVER also appears in + BB_HASHBASE_WHITELIST. + Consequently, BBSERVER is excluded + from checksum and dependency data. @@ -1736,11 +1736,9 @@ Build Directory. You can define this directory indirectly through the &OE_INIT_FILE; - and - oe-init-build-env-memres - 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 + 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 path, the BUILDDIR defaults to build in the current directory. @@ -6626,7 +6624,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" recipe in the Source Directory for an example initramfs recipe. - To select this sample recipe as the one bulit + To select this sample recipe as the one built to provide the initramfs image, set INITRAMFS_IMAGE to "core-image-minimal-initramfs". @@ -9026,19 +9024,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The directory from which the top-level build environment setup script is sourced. - The Yocto Project makes two top-level build environment - setup scripts available: - &OE_INIT_FILE; - and - oe-init-build-env-memres. - When you run one of these scripts, the + The Yocto Project provides a top-level build environment + setup script: + &OE_INIT_FILE;. + When you run this script, the OEROOT variable resolves to the directory that contains the script. For additional information on how this variable is used, - see the initialization scripts. + see the initialization script. @@ -15089,10 +15085,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The top-level Build Directory. BitBake automatically sets this variable when you - initialize your build environment using either - &OE_INIT_FILE; - or - oe-init-build-env-memres. + initialize your build environment using + &OE_INIT_FILE;. -- cgit v1.2.3-54-g00ecf