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 --- .../dev-manual/dev-manual-common-tasks.xml | 30 +++++++--------------- documentation/dev-manual/dev-manual-qemu.xml | 4 +-- documentation/dev-manual/dev-manual-start.xml | 6 ++--- 3 files changed, 12 insertions(+), 28 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 64af8d700a..0c2e60f006 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1535,9 +1535,7 @@ Build Directory and have sourced the build environment setup script (i.e. - oe-init-build-env - or - oe-init-build-env-memres). + oe-init-build-env). Here is the basic recipetool syntax: Running recipetool -h or @@ -1718,10 +1716,8 @@ - Assuming you have sourced a build environment setup script (i.e. - &OE_INIT_FILE; - or - oe-init-build-env-memres) + Assuming you have sourced the build environment setup script (i.e. + &OE_INIT_FILE;) and you are in the Build Directory, use BitBake to process your recipe. @@ -4959,11 +4955,9 @@ - You must have sourced one of the build environment - setup scripts (i.e. - &OE_INIT_FILE; - or - oe-init-build-env-memres) + You must have sourced the build environment + setup script (i.e. + &OE_INIT_FILE;) found in the Build Directory. @@ -5052,8 +5046,6 @@ artifacts ready and available. Additionally, the environment must be set up using the &OE_INIT_FILE; - or - oe-init-build-env-memres script found in the Build Directory. @@ -6195,8 +6187,6 @@ Some notes from Cal: environment, you must launch it using BitBake. Thus, the environment must be set up using the &OE_INIT_FILE; - or - oe-init-build-env-memres script found in the Build Directory. You must also be sure of the state of your build in the @@ -7062,12 +7052,10 @@ Some notes from Cal: Aside from the *.sample configuration files, the conf-notes.txt also resides in the default meta-poky/conf directory. - The scripts that set up the build environment + The script that sets up the build environment (i.e. - &OE_INIT_FILE; - and - oe-init-build-env-memres) - use this file to display BitBake targets as part of the script + &OE_INIT_FILE;) + uses this file to display BitBake targets as part of the script output. Customizing this conf-notes.txt file is a good way to make sure your list of custom targets appears diff --git a/documentation/dev-manual/dev-manual-qemu.xml b/documentation/dev-manual/dev-manual-qemu.xml index ed4040ca60..d127c4f510 100644 --- a/documentation/dev-manual/dev-manual-qemu.xml +++ b/documentation/dev-manual/dev-manual-qemu.xml @@ -43,9 +43,7 @@ repository or you downloaded and unpacked a Yocto Project release tarball, you can source the build environment script (i.e. - &OE_INIT_FILE; - or - oe-init-build-env-memres): + &OE_INIT_FILE;): $ cd ~/poky $ source oe-init-build-env diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index bcb49fbf03..a62825122f 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -707,11 +707,9 @@ Initialize the Build Environment: - Initialize the build environment by sourcing a build + Initialize the build environment by sourcing the build environment script (i.e. - &OE_INIT_FILE; - or - oe-init-build-env-memres). + &OE_INIT_FILE;). Make Sure Your local.conf -- cgit v1.2.3-54-g00ecf