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 @@
- The first thing BitBake does is look for the bitbake.conf file.
+ The first thing BitBake does is look for the
+ bitbake.conf file.
This file resides in the
- Source Directory
+ Source Directory
within the meta/conf/ directory.
BitBake finds it by examining its
BBPATH environment
@@ -92,8 +93,8 @@
meta/recipes-*/ directory within Poky.
Adding extra content to BBFILES is best achieved through the use of
BitBake layers as described in the
- "Understanding and
- Creating Layers" section of the Yocto Project Development Manual.
+ "Understanding and Creating Layers"
+ section of the Yocto Project Development Tasks Manual.
@@ -227,13 +228,14 @@
Dependencies are defined through several variables.
- You can find information about variables BitBake uses in the BitBake documentation,
- which is found in the bitbake/doc/manual directory within the
- Source Directory.
+ You can find information about variables BitBake uses in the
+ BitBake documentation, which is found in the
+ bitbake/doc/manual directory within the
+ Source Directory.
At a basic level, it is sufficient to know that BitBake uses the
DEPENDS and
- RDEPENDS variables when
- calculating dependencies.
+ RDEPENDS
+ variables when calculating dependencies.
@@ -448,20 +450,23 @@ Options:
You can find information about the options and formats of entries for specific
fetchers in the BitBake manual located in the
bitbake/doc/manual directory of the
- Source Directory.
+ Source Directory.
- One useful feature for certain Source Code Manager (SCM) fetchers is the ability to
- "auto-update" when the upstream SCM changes version.
- Since this ability requires certain functionality from the SCM, not all
- systems support it.
- Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update".
+ One useful feature for certain Source Code Manager (SCM) fetchers
+ is the ability to "auto-update" when the upstream SCM changes
+ version.
+ Since this ability requires certain functionality from the SCM,
+ not all systems support it.
+ Currently Subversion, Bazaar and to a limited extent, Git support
+ the ability to "auto-update".
This feature works using the SRCREV
variable.
See the
- "Using an External SCM" section
- in the Yocto Project Development Manual for more information.
+ "Using an External SCM"
+ section in the Yocto Project Development Tasks Manual for more
+ information.