summaryrefslogtreecommitdiffstats
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
parent093b0079ce2df52e362d0a9b7b0f0184d9de4626 (diff)
downloadpoky-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>
-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 ff19fb716a..4372769c1c 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -295,10 +295,10 @@
295 </para> 295 </para>
296 296
297 <para> 297 <para>
298 Append files files must have the same name as the corresponding recipe. 298 Append files must have the same name as the corresponding recipe.
299 For example, the append file <filename>someapp_&DISTRO;.bbappend</filename> must 299 For example, the append file <filename>someapp_&DISTRO;.bbappend</filename> must
300 apply to <filename>someapp_&DISTRO;.bb</filename>. 300 apply to <filename>someapp_&DISTRO;.bb</filename>.
301 This means the original recipe and append file names are version number specific. 301 This means the original recipe and append file names are version number-specific.
302 If the corresponding recipe is renamed to update to a newer version, the 302 If the corresponding recipe is renamed to update to a newer version, the
303 underlying <filename>.bbappend</filename> file must be renamed as well. 303 underlying <filename>.bbappend</filename> file must be renamed as well.
304 During the build process, BitBake displays an error on starting if it detects a 304 During the build process, BitBake displays an error on starting if it detects a
@@ -379,7 +379,7 @@
379 Each layer is assigned a priority value. 379 Each layer is assigned a priority value.
380 Priority values control which layer takes precedence if there are recipe files with 380 Priority values control which layer takes precedence if there are recipe files with
381 the same name in multiple layers. 381 the same name in multiple layers.
382 For these cases, the recipe file from the layer with a higher priority number taking precedence. 382 For these cases, the recipe file from the layer with a higher priority number takes precedence.
383 Priority values also affect the order in which multiple <filename>.bbappend</filename> files 383 Priority values also affect the order in which multiple <filename>.bbappend</filename> files
384 for the same recipe are applied. 384 for the same recipe are applied.
385 You can either specify the priority manually, or allow the build system to calculate it 385 You can either specify the priority manually, or allow the build system to calculate it