summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/ref-bitbake.xml39
1 files changed, 22 insertions, 17 deletions
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml
index 3a8077007a..17f4c54b9c 100644
--- a/documentation/ref-manual/ref-bitbake.xml
+++ b/documentation/ref-manual/ref-bitbake.xml
@@ -36,9 +36,10 @@
36 </para> 36 </para>
37 37
38 <para> 38 <para>
39 The first thing BitBake does is look for the <filename>bitbake.conf</filename> file. 39 The first thing BitBake does is look for the
40 <filename>bitbake.conf</filename> file.
40 This file resides in the 41 This file resides in the
41 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> 42 <link linkend='source-directory'>Source Directory</link>
42 within the <filename>meta/conf/</filename> directory. 43 within the <filename>meta/conf/</filename> directory.
43 BitBake finds it by examining its 44 BitBake finds it by examining its
44 <link linkend='var-BBPATH'><filename>BBPATH</filename></link> environment 45 <link linkend='var-BBPATH'><filename>BBPATH</filename></link> environment
@@ -92,8 +93,8 @@
92 <filename>meta/recipes-*/</filename> directory within Poky. 93 <filename>meta/recipes-*/</filename> directory within Poky.
93 Adding extra content to <filename>BBFILES</filename> is best achieved through the use of 94 Adding extra content to <filename>BBFILES</filename> is best achieved through the use of
94 BitBake layers as described in the 95 BitBake layers as described in the
95 "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and 96 "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>"
96 Creating Layers</ulink>" section of the Yocto Project Development Manual. 97 section of the Yocto Project Development Tasks Manual.
97 </para> 98 </para>
98 99
99 <para> 100 <para>
@@ -227,13 +228,14 @@
227 228
228 <para> 229 <para>
229 Dependencies are defined through several variables. 230 Dependencies are defined through several variables.
230 You can find information about variables BitBake uses in the BitBake documentation, 231 You can find information about variables BitBake uses in the
231 which is found in the <filename>bitbake/doc/manual</filename> directory within the 232 BitBake documentation, which is found in the
232 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 233 <filename>bitbake/doc/manual</filename> directory within the
234 <link linkend='source-directory'>Source Directory</link>.
233 At a basic level, it is sufficient to know that BitBake uses the 235 At a basic level, it is sufficient to know that BitBake uses the
234 <filename><link linkend='var-DEPENDS'>DEPENDS</link></filename> and 236 <filename><link linkend='var-DEPENDS'>DEPENDS</link></filename> and
235 <filename><link linkend='var-RDEPENDS'>RDEPENDS</link></filename> variables when 237 <filename><link linkend='var-RDEPENDS'>RDEPENDS</link></filename>
236 calculating dependencies. 238 variables when calculating dependencies.
237 </para> 239 </para>
238 </section> 240 </section>
239 241
@@ -448,20 +450,23 @@ Options:
448 You can find information about the options and formats of entries for specific 450 You can find information about the options and formats of entries for specific
449 fetchers in the BitBake manual located in the 451 fetchers in the BitBake manual located in the
450 <filename>bitbake/doc/manual</filename> directory of the 452 <filename>bitbake/doc/manual</filename> directory of the
451 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 453 <link linkend='source-directory'>Source Directory</link>.
452 </para> 454 </para>
453 455
454 <para> 456 <para>
455 One useful feature for certain Source Code Manager (SCM) fetchers is the ability to 457 One useful feature for certain Source Code Manager (SCM) fetchers
456 "auto-update" when the upstream SCM changes version. 458 is the ability to "auto-update" when the upstream SCM changes
457 Since this ability requires certain functionality from the SCM, not all 459 version.
458 systems support it. 460 Since this ability requires certain functionality from the SCM,
459 Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update". 461 not all systems support it.
462 Currently Subversion, Bazaar and to a limited extent, Git support
463 the ability to "auto-update".
460 This feature works using the <filename><link linkend='var-SRCREV'>SRCREV</link></filename> 464 This feature works using the <filename><link linkend='var-SRCREV'>SRCREV</link></filename>
461 variable. 465 variable.
462 See the 466 See the
463 "<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-srcrev'>Using an External SCM</ulink>" section 467 "<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-srcrev'>Using an External SCM</ulink>"
464 in the Yocto Project Development Manual for more information. 468 section in the Yocto Project Development Tasks Manual for more
469 information.
465 </para> 470 </para>
466 471
467 </section> 472 </section>