From a19f575cde39917e4632dab1e813d84402f95937 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 11 Jun 2014 10:46:05 +0300 Subject: dev-manual, kernel-dev, ref-manual: Updated task name usage. There was inconsistency on how we refer to a task name throughout the YP manual set. The proper way is "do_". Some occurrences did not include the "do_" prefix. These have been fixed. (From yocto-docs rev: b32821bb0d3e6de7bca68b25c662a023526a10c4) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'documentation/dev-manual/dev-manual-model.xml') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 4fd4c4e1e3..59e19a2bae 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -1773,8 +1773,10 @@ Make your changes in the temporary source code to the files you added to the patch. Test Your Changes: - Once you have modified the source code, the easiest way to test your changes - is by calling the compile task as shown in the following example: + Once you have modified the source code, the easiest way to + your changes is by calling the + do_compile task as shown in the + following example: $ bitbake -c compile -f <name_of_package> @@ -1870,8 +1872,10 @@ Edit the Files: Make your changes to the temporary source code. Test Your Changes: - Once you have modified the source code, the easiest way to test your changes - is by calling the compile task as shown in the following example: + Once you have modified the source code, the easiest way + to test your changes is by calling the + do_compile task as shown in the + following example: $ bitbake -c compile -f <name_of_package> -- cgit v1.2.3-54-g00ecf