summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/ref-bitbake.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-07-02 14:34:39 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-07-03 14:55:03 +0100
commit5966b44893a39847d3d590566dd488323a11ff73 (patch)
tree4cc4c8a6fd8403ea0d9708eb9c449d1e0b8eded2 /documentation/poky-ref-manual/ref-bitbake.xml
parent7064538309121c23323d442db6c9f0b11c8d6431 (diff)
downloadpoky-5966b44893a39847d3d590566dd488323a11ff73.tar.gz
documentation/poky-ref-manual: Yocto Project scrub
I have changed as many "Yocto Project" terms as possible so that better reflect reality. (From yocto-docs rev: 5f729e53b0cb653c97621e4e6598d9295d60ada5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/ref-bitbake.xml')
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml15
1 files changed, 9 insertions, 6 deletions
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index 523caf7090..81a8934e6a 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -7,7 +7,8 @@
7 <title>Reference: BitBake</title> 7 <title>Reference: BitBake</title>
8 8
9 <para> 9 <para>
10 BitBake is a program written in Python that interprets the metadata that makes up the Yocto Project. 10 BitBake is a program written in Python that interprets the metadata used by the Yocto Project.
11 The OpenEmbedded build system uses BitBake.
11 At some point, developers wonder what actually happens when you enter: 12 At some point, developers wonder what actually happens when you enter:
12 <literallayout class='monospaced'> 13 <literallayout class='monospaced'>
13 $ bitbake core-image-sato 14 $ bitbake core-image-sato
@@ -34,20 +35,22 @@
34 35
35 <para> 36 <para>
36 The first thing BitBake does is look for the <filename>bitbake.conf</filename> file. 37 The first thing BitBake does is look for the <filename>bitbake.conf</filename> file.
37 The Yocto Project keeps this file in the Yocto Project file's <filename>meta/conf/</filename> 38 This file resides in the
38 directory. 39 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>
39 BitBake finds it by examining its <filename>BBPATH</filename> environment 40 within the <filename>meta/conf/</filename> directory.
41 BitBake finds it by examining its
42 <link linkend='var-BBPATH'><filename>BBPATH</filename></link> environment
40 variable and looking for the <filename>meta/conf/</filename> 43 variable and looking for the <filename>meta/conf/</filename>
41 directory. 44 directory.
42 </para> 45 </para>
43 46
44 <para> 47 <para>
45 In the Yocto Project, <filename>bitbake.conf</filename> lists other configuration 48 The <filename>bitbake.conf</filename> file lists other configuration
46 files to include from a <filename>conf/</filename> 49 files to include from a <filename>conf/</filename>
47 directory below the directories listed in <filename>BBPATH</filename>. 50 directory below the directories listed in <filename>BBPATH</filename>.
48 In general, the most important configuration file from a user's perspective 51 In general, the most important configuration file from a user's perspective
49 is <filename>local.conf</filename>, which contains a user's customized 52 is <filename>local.conf</filename>, which contains a user's customized
50 settings for the Yocto Project build environment. 53 settings for the OpenEmbedded build environment.
51 Other notable configuration files are the distribution 54 Other notable configuration files are the distribution
52 configuration file (set by the 55 configuration file (set by the
53 <filename><link linkend='var-DISTRO'>DISTRO</link></filename> variable) 56 <filename><link linkend='var-DISTRO'>DISTRO</link></filename> variable)