diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index 951468d46c..8e41031702 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -81,7 +81,7 @@ do_install() {
Applications that use autotools such as autoconf and
automake require a recipe that has a source archive listed in
SRC_URI and
- also inherits autotools, which instructs BitBake to use the
+ also inherits autotools, which instructs BitBake to use the
autotools.bbclass file, which contains the definitions of all the steps
needed to build an autotooled application.
The result of the build is automatically packaged.
@@ -114,7 +114,7 @@ inherit autotools gettext
Applications that use GNU make also require a recipe that has
the source archive listed in SRC_URI.
- You do not need to add a do_compile step since by default BitBake
+ You do not need to add a "do_compile" step since by default BitBake
starts the make command to compile the application.
If you need additional make options you should store them in the
EXTRA_OEMAKE variable.
@@ -209,8 +209,8 @@ FILES_sxpm = "${bindir}/sxpm"
Post Install Scripts
- To add a post-installation script to a package, add a pkg_postinst_PACKAGENAME()
- function to the .bb file and use
+ To add a post-installation script to a package, add a pkg_postinst_PACKAGENAME()
+ function to the .bb file and use
PACKAGENAME as the name of the package you want to attach to the
postinst script.
Normally PN can be used, which
@@ -298,8 +298,8 @@ IMAGE_INSTALL += "strace"
For complex custom images, the best approach is to create a custom task package
that is used to build the image or images.
- A good example of a tasks package is meta/recipes-sato/tasks/task-poky.bb
- .
+ A good example of a tasks package is
+ meta/recipes-sato/tasks/task-poky.bb.
The PACKAGES
variable lists the task packages to build along with the complementary
-dbg and -dev packages.
@@ -494,7 +494,7 @@ COMPATIBLE_MACHINE = '(qemux86|qemumips)'
Adding a Formfactor Configuration File
A formfactor configuration file provides information about the
- target hardware on which Poky is running, and information that Poky cannot
+ target hardware on which Poky is running and information that Poky cannot
obtain from other sources such as the kernel.
Some examples of information contained in a formfactor configuration file include
framebuffer orientation, whether or not the system has a keyboard,
@@ -505,7 +505,7 @@ COMPATIBLE_MACHINE = '(qemux86|qemumips)'
Reasonable defaults are used in most cases, but if customization is
necessary you need to create a machconfig file
under meta/packages/formfactor/files/MACHINENAME/,
- where MACHINENAME is the name for which this information
+ where MACHINENAME is the name for which this information
applies.
For information about the settings available and the defaults, see
meta/packages/formfactor/files/config.
@@ -674,7 +674,7 @@ BBFILE_PRIORITY_emenlow = "6"
variables allowing moves to be made towards generating checksums and allowing
use of the dependency information in other parts of bitbake.
- Signed-off-by: Richard Purdie rpurdie@linux.intel.com
+ Signed-off-by: Richard Purdie richard.purdie@linuxfoundation.org
@@ -714,7 +714,7 @@ BBFILE_PRIORITY_emenlow = "6"
Usually, version increases occur only to packages.
However, if for some reason PV changes but does not increase, you can increase the
PE variable (Package Epoch).
- The PE variable defaults to '0'.
+ The PE variable defaults to "0".
Version numbering strives to follow the
@@ -823,7 +823,8 @@ BBFILE_PRIORITY_emenlow = "6"
For a standard recipe not related to
MACHINE the location is
tmp/work/PACKAGE_ARCH-poky-TARGET_OS/PN-PV-PR/.
- For target device-dependent packages you should use the MACHINE variable instead of
+ For target device-dependent packages you should use the MACHINE
+ variable instead of
PACKAGE_ARCH
in the directory name.
@@ -864,19 +865,19 @@ BBFILE_PRIORITY_emenlow = "6"
into the new patch file:
-quilt new NAME-OF-PATCH.patch
+ quilt new NAME-OF-PATCH.patch
After notifying quilt, add all modified files into that patch:
-quilt add file1 file2 file3
+ quilt add file1 file2 file3
You can now start editing.
Once you are done editing, you need to use quilt to generate the final patch that
will contain all your modifications.
-quilt refresh
+ quilt refresh
You can find the resulting patch file in the