From 444597f44edb0dcaf048c115997e10b31fc13222 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 11 Nov 2010 13:44:17 -0800 Subject: Poky Reference Manual: Task wording made consistent I am using "xxxxxx" task as the way to call out a specific task in the text. Previously a mix of xxxxxx and the "xxxxxx" methods were being used. Signed-off-by: Scott Rifenbark --- documentation/poky-ref-manual/usingpoky.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation/poky-ref-manual/usingpoky.xml') diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index fa08699129..79e9dfbf9c 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml @@ -195,7 +195,7 @@ Task Failures The log file for shell tasks is available in ${WORKDIR}/temp/log.do_taskname.pid. - For example, the compile task of busybox 1.01 on the ARM spitz machine might be + For example, the "compile" task of busybox 1.01 on the ARM spitz machine might be tmp/work/armv5te-poky-linux-gnueabi/busybox-1.01/temp/log.do_compile.1234. To see what bitbake runs to generate that log, look at the corresponding run.do_taskname.pid file located in the same directory. @@ -241,12 +241,12 @@ This sequence first builds matchbox-desktop and then recompiles it. The last command reruns all tasks, basically the packaging tasks, after the compile. - Bitbake recognizes that the compile task was rerun and therefore understands that the other + Bitbake recognizes that the "compile" task was rerun and therefore understands that the other tasks also need to be run again. - You can view a list of tasks in a given package by running the listtasks task. + You can view a list of tasks in a given package by running the "listtasks" task. For example: $ bitbake matchbox-desktop -c -- cgit v1.2.3-54-g00ecf