summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-structure.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-03-27 09:01:15 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-04 14:12:53 +0100
commitdbcfb9eb1508073f1603e3cb3f89378c4ee4e373 (patch)
treeb592225f3c4a83cfc421226b9e61a1db97cdfb26 /documentation/ref-manual/ref-structure.xml
parent4277bc19fc6775f65298d108423685fe67524843 (diff)
downloadast2050-yocto-poky-dbcfb9eb1508073f1603e3cb3f89378c4ee4e373.zip
ast2050-yocto-poky-dbcfb9eb1508073f1603e3cb3f89378c4ee4e373.tar.gz
ref-manual: Minor edits to "bitbake/" section.
(From yocto-docs rev: 9d697cde9a1c5367e4529465b7c5a1443657b31b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-structure.xml')
-rw-r--r--documentation/ref-manual/ref-structure.xml8
1 files changed, 5 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index 2fa3341..e14c6b4 100644
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -33,10 +33,12 @@
<title><filename>bitbake/</filename></title>
<para>
- The <ulink url='source-directory'>Source Directory</ulink>
+ The <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
includes a copy of BitBake for ease of use.
The copy usually matches the current stable BitBake release from the BitBake project.
- BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks
+ BitBake, a
+ <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>
+ interpreter, reads the Yocto Project metadata and runs the tasks
defined by that data.
Failures are usually from the metadata and not from BitBake itself.
Consequently, most users do not need to worry about BitBake.
@@ -46,7 +48,7 @@
When you run the <filename>bitbake</filename> command, the wrapper script in
<filename>scripts/</filename> is executed to run the main BitBake executable,
which resides in the <filename>bitbake/bin/</filename> directory.
- Sourcing the <link linkend="structure-core-script">&OE_INIT_FILE;</link>
+ Sourcing the <link linkend="structure-core-script"><filename>&OE_INIT_FILE;</filename></link>
script places the <filename>scripts</filename> and <filename>bitbake/bin</filename>
directories (in that order) into the shell's <filename>PATH</filename> environment
variable.
OpenPOWER on IntegriCloud