Rename poky-init-build-env to oe-init-build-env

(From yocto-docs rev: 15bedcbd988300c2fdf880c5f15def50310049e2)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

3 files changed, 8 insertions, 8 deletions

diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 4cfd08f..afd3a8f 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -28,7 +28,7 @@
             Consequently, most users do not need to worry about BitBake.
             The <filename class="directory">bitbake/bin/</filename> directory is placed 
             into the PATH environment variable by the 
-            <link linkend="structure-core-script">poky-init-build-env</link> script.
+            <link linkend="structure-core-script">oe-init-build-env</link> script.
         </para>
 
         <para>
@@ -47,7 +47,7 @@
             It is also possible to place output and configuration 
             files in a directory separate from the Poky source.
             For information on separating output from the Poky source, see <link 
-            linkend='structure-core-script'>poky-init-build-env</link>.
+            linkend='structure-core-script'>oe-init-build-env</link>.
         </para>
     </section>
 
@@ -104,7 +104,7 @@
         <para>
             This directory contains various integration scripts that implement 
             extra functionality in the Poky environment (e.g. QEMU scripts).
-            The <link linkend="structure-core-script">poky-init-build-env</link> script appends this
+            The <link linkend="structure-core-script">oe-init-build-env</link> script appends this
             directory to the PATH environment variable.
         </para>
     </section>
@@ -154,7 +154,7 @@
     </section>
 
     <section id='structure-core-script'>
-        <title><filename>poky-init-build-env</filename></title>
+        <title><filename>oe-init-build-env</filename></title>
 
         <para>
             This script sets up the Poky build environment. 
@@ -168,7 +168,7 @@
         </para>
 
         <literallayout class='monospaced'>
-     $ source POKY_SRC/poky-init-build-env [BUILDDIR]
+     $ source POKY_SRC/oe-init-build-env [BUILDDIR]
         </literallayout>
 
         <para>
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index fc4fbdc..6d7b016 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -131,14 +131,14 @@
     </para>
     <para>
         <literallayout class='monospaced'>
-     $ source poky-init-build-env [build_dir]
+     $ source oe-init-build-env [build_dir]
         </literallayout>
     </para>
     <para>
         The build_dir is the dir containing all the build's object files. The default 
         build dir is poky-dir/build. A different build_dir can be used for each of the targets. 
         For example, ~/build/x86 for a qemux86 target, and ~/build/arm for a qemuarm target.
-        Please refer to <link linkend="structure-core-script">poky-init-build-env</link>
+        Please refer to <link linkend="structure-core-script">oe-init-build-env</link>
         for more detailed information.
     </para>
     <para>
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index f011f09..b9f3662 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -255,7 +255,7 @@
              <literallayout class='monospaced'>
      $ wget http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.tar.bz2
      $ tar xjf poky-bernard-5.0.tar.bz2
-     $ source poky-bernard-5.0/poky-init-build-env poky-5.0-build
+     $ source poky-bernard-5.0/oe-init-build-env poky-5.0-build
              </literallayout>
          </para>