[bitbake-devel] Documentation: A few more tweaks to Chapter 1, BitBake User Manual.
@@ -212,11 +212,12 @@
<listitem><para>Where the source code resides and
how to fetch it</para></listitem>
<listitem><para>Whether the source code requires
- any patches</para></listitem>
+ any patches, where to find them and how to apply
<listitem><para>How to configure and compile the
<listitem><para>Where on the target machine to install the
- package or packages being compiled</para></listitem>
+ package or packages created</para></listitem>
@@ -228,7 +229,10 @@
The term "package" is also commonly used to describe recipes.
However, since the same word is used to describe packaged
output from a project, it is best to maintain a single
- descriptive term, "recipes".
+ descriptive term, "recipes". Put another way, a single
+ "recipe" file is quite capable of generating a number of
+ related but separately installable "packages"; this is
+ actually fairly common.
@@ -248,7 +252,7 @@
The main configuration file is the sample
<filename>bitbake.conf</filename> file, which is
located within the BitBake source tree
- <filename>conf</filename> directory.
+ <filename>conf/</filename> directory.
@@ -262,7 +266,7 @@
The BitBake source tree currently comes with one class metadata file
You can find this file in the
- <filename>classes</filename> directory.
+ <filename>classes/</filename> directory.
The <filename>base.bbclass</filename> class files is special since it
is always included automatically for all recipes
@@ -313,7 +317,6 @@
Append files, which are files that have the
<filename>.bbappend</filename> file extension, extend or
override information in an existing recipe file.
- recipe file.
@@ -326,8 +329,8 @@
- Information in append files overrides the information in the
- similarly-named recipe file.
+ Information in append files extends or overrides the information in the
+ underlying, similarly-named recipe file.
@@ -352,6 +355,12 @@
However, if you named the append file
<filename>busybox_1.%.bbappend</filename>, then you would have a match.
+ In the most general case, you could name the append file something as
+ simple as <filename>busybox_%.bbappend</filename> to be entirely
+ version independent.
@@ -359,7 +368,7 @@
- You can obtain BitBake several different ways:
+ You can obtain BitBake in one of several different ways:
Using Git to clone the BitBake source code repository
@@ -432,7 +441,7 @@
has been thoroughly tested for compatibility with the other
For information on how to check out a particular BitBake-based
- build system, the build system's supporting documentation.
+ build system, consult that build system's supporting documentation.