diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index db6c29fdc3..1199669ab0 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -775,11 +775,11 @@ so that there are some definite steps on how to do this. I need more detail her
${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
Assuming a Yocto Project Files top-level directory named poky
- and a default Yocto Project build directory of poky/build, here
- is an example temporary package source code location for the
- v86d package:
+ and a default Yocto Project build directory of poky/build,
+ the following is the temporary package source code location for the
+ acl package:
- ~/poky/build/tmp/work/qemux86-poky-linux/v86d-01.9-r0
+ ~/poky/build/tmp/work/i586-poky-linux/acl-2.2.51-r3
@@ -789,20 +789,14 @@ so that there are some definite steps on how to do this. I need more detail her
${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
Again, assuming a Yocto Project Files top-level directory named poky
- and a default Yocto Project build directory of poky/build, here
- is an example temporary package source code location for the
- acl package that is dependent upon a MIPS-based device:
+ and a default Yocto Project build directory of poky/build, the
+ following is the temporary package source code location for the
+ acl package that is being built for a MIPS-based device:
~/poky/build/tmp/work/mips-poky-linux/acl-2.2.51-r2
-
- Be sure the package recipe sets the
- S variable to something
- other than the standard WORKDIR/PN-PV/ value.
-
-
Once you have modified the package source code, the easiest way to test your changes
is by calling the compile task as shown in the following example:
@@ -816,7 +810,13 @@ so that there are some definite steps on how to do this. I need more detail her
option forces re-execution of the specified task.
You can call other tasks this way as well.
All the modifications you make to the temporary package source code
- disappear once you -c clean for the package.
+ disappear once you -c clean or
+ -c cleanall with BitBake for the package.
+ Modifications will also disappear if you use the rm_work
+ feature as described in the
+ "Building an Image" section
+ of the Yocto Project Quick Start.
+