diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index e7d1ca4cff..63c915ccc8 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1324,7 +1324,7 @@
${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}
- As an example, assume a Source Directory top-level folder name
+ As an example, assume a Source Directory top-level folder named
poky, a default Build Directory at
poky/build, and a
qemux86-poky-linux machine target system.
@@ -1559,9 +1559,9 @@
During the build, the do_unpack task
- unpacks the source and
+ unpacks the source with
${S}
- points to where it will be unpacked.
+ pointing to where it is unpacked.
@@ -1833,7 +1833,7 @@
For reference information on configure options specific to the
software you are building, you can consult the output of the
./configure --help command within
- ${S} or consult the upstream
+ ${S} or consult the software's upstream
documentation.
@@ -2014,13 +2014,13 @@
autotools
and
cmake
- classes, runs make install in parallel.
+ classes, runs make install in parallel.
Sometimes, a Makefile can have missing dependencies between
targets that can result in race conditions.
If you experience intermittent failures during
do_install, you might be able to work
- around them by disabling parallel make install by adding the
- following to the recipe:
+ around them by disabling parallel Makefile installs
+ by adding the following to the recipe:
PARALLEL_MAKEINST = ""
@@ -2052,15 +2052,15 @@
When you create the installation for your services, you need
- to accomplish what is normally done by "make install".
- In other words, make sure your installation puts the output
- in a layout that is similar to how they will be laid out on the
- target system.
+ to accomplish what is normally done by
+ make install.
+ In other words, make sure your installation arranges the output
+ similar to how it is arranged on the target system.
- The OpenEmbedded build system provides support for two
- different ways of starting services:
+ The OpenEmbedded build system provides support for starting
+ services two different ways:
SysVinit:
SysVinit is a system and service manager that
@@ -2083,19 +2083,19 @@
INITSCRIPT_PARAMS
variables within your recipe.Systemd:
- Systemd was designed to replace SysVinit and provide
+ Systemd was designed to replace SysVinit and to provide
enhanced management of services.
For more information on Systemd, see the Systemd
homepage at
.
To enable a service using Systemd, your recipe
- needs to inherit the systemd class.
+ needs to inherit the
+ systemd.bbclass
+ class.
See the systemd.bbclass file
located in your
- Source Directory
- in meta/classes or the
- "systemd.bbclass"
+ Source Directory.
section for more information.
@@ -2154,7 +2154,7 @@
package is included in an image.
To add a post-installation script to a package, add a
pkg_postinst_PACKAGENAME() function to
- the .bb file and use
+ the recipe file (.bb) and use
PACKAGENAME as the name of the package
you want to attach to the postinst
script.