]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
ref-manual: Added new variable entry for BULIDDIR.
authorScott Rifenbark <scott.m.rifenbark@intel.com>
Wed, 27 Mar 2013 20:53:01 +0000 (13:53 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 4 Apr 2013 13:13:36 +0000 (14:13 +0100)
Ross Burton suggested this might be good to have so I added
it.  The changes include the entry itself and a link to it
from the beginning of the "Classes" chapter where it is
talked about.

Reported-by: Ross Burton <ross.burton@intel.com>
(From yocto-docs rev: 5b0263fa5e01706ccb815db51b8f1b7f86275721)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation/ref-manual/ref-classes.xml
documentation/ref-manual/ref-variables.xml

index 9cc7ad134a2b777e02d0f45ec498be79eca4c5ca..529f89c3d8c87b29aabf68f8f999e5fd24703747 100644 (file)
@@ -15,7 +15,8 @@
     in a <filename>classes/</filename> directory beneath the
     <filename>meta*/</filename> directory found in the
     <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
-    Class files can also be pointed to by <filename>BUILDDIR</filename>
+    Class files can also be pointed to by
+    <link linkend='var-BUILDDIR'><filename>BUILDDIR</filename></link>
     (e.g. <filename>build/</filename>)in the same way as
     <filename>.conf</filename> files in the <filename>conf</filename> directory.
     Class files are searched for in <link linkend='var-BBPATH'><filename>BBPATH</filename></link>
index 204046fc1409cc731f4954554539674535498faa..c433110f2b0fe42405805dc0e5958ca41fa4e5ed 100644 (file)
@@ -556,6 +556,20 @@ Core layer for images cannot be removed
             </glossdef>
         </glossentry>
 
+        <glossentry id='var-BUILDDIR'><glossterm>BUILDDIR</glossterm>
+            <glossdef>
+                <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 pass a Build Directory
+                    path, the <filename>BUILDDIR</filename> defaults to
+                    <filename>build</filename> in the current directory.
+                </para>
+            </glossdef>
+        </glossentry>
     </glossdiv>
 
     <glossdiv id='var-glossary-c'><title>C</title>