summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-02-01 15:31:38 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:24:01 +0000
commitcf10be36c1d9d37a8cec93a1e509b3049a9b4c5b (patch)
treeee7d9e49d735199a3a02da281d461497994b9374 /documentation
parent093b0079ce2df52e362d0a9b7b0f0184d9de4626 (diff)
downloadast2050-yocto-poky-cf10be36c1d9d37a8cec93a1e509b3049a9b4c5b.zip
ast2050-yocto-poky-cf10be36c1d9d37a8cec93a1e509b3049a9b4c5b.tar.gz
dev-manual: three typos fixed.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 3272f0d51e3d09f4ffd96b7322f66ffd878d3714) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index ff19fb7..4372769 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -295,10 +295,10 @@
</para>
<para>
- Append files files must have the same name as the corresponding recipe.
+ Append files must have the same name as the corresponding recipe.
For example, the append file <filename>someapp_&DISTRO;.bbappend</filename> must
apply to <filename>someapp_&DISTRO;.bb</filename>.
- This means the original recipe and append file names are version number specific.
+ This means the original recipe and append file names are version number-specific.
If the corresponding recipe is renamed to update to a newer version, the
underlying <filename>.bbappend</filename> file must be renamed as well.
During the build process, BitBake displays an error on starting if it detects a
@@ -379,7 +379,7 @@
Each layer is assigned a priority value.
Priority values control which layer takes precedence if there are recipe files with
the same name in multiple layers.
- For these cases, the recipe file from the layer with a higher priority number taking precedence.
+ For these cases, the recipe file from the layer with a higher priority number takes precedence.
Priority values also affect the order in which multiple <filename>.bbappend</filename> files
for the same recipe are applied.
You can either specify the priority manually, or allow the build system to calculate it
OpenPOWER on IntegriCloud