diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 10c3711b9a..a5cefe499f 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3920,17 +3920,30 @@
Clean up:
- Be sure to clean the shared state out by running the
- cleansstate BitBake task as follows from your Build Directory:
+ Be sure to clean the shared state out by using BitBake
+ to run from within the Build Directory the
+ do_cleansstate
+ task as follows:
$ bitbake -c cleansstate linux-yocto
- Never remove any files by hand from the tmp/deploy
- directory inside the
- Build Directory.
- Always use the various BitBake clean tasks to clear out previous
- build artifacts.
-
+
+
+ Never remove any files by hand from the
+ tmp/deploy
+ directory inside the
+ Build Directory.
+ Always use the various BitBake clean tasks to
+ clear out previous build artifacts.
+ For information on the clean tasks, see the
+ "do_clean",
+ "do_cleanall",
+ and
+ "do_cleansstate"
+ sections all in the Yocto Project Reference
+ Manual.
+
+ Build the image:
Next, build the kernel image using this command:
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 59e19a2bae..bd24905ad7 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -1785,8 +1785,14 @@
If you find problems with your code, you can just keep editing and
re-testing iteratively until things work as expected.
All the modifications you make to the temporary source code
- disappear once you -c clean or
- -c cleanall with BitBake for the package.
+ disappear once you run the
+ do_clean
+ or
+ do_cleanall
+ tasks using BitBake (i.e.
+ bitbake -c clean <name_of_package>
+ and
+ bitbake -c cleanall <name_of_package>).
Modifications will also disappear if you use the rm_work
feature as described in the
"Building an Image"
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 31ffa5c83c..3ab21e7077 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -445,10 +445,16 @@
You can edit the sources as you would any other Linux source
tree.
However, keep in mind that you will lose changes if you
- trigger the do_fetch task for the recipe.
- You can avoid triggering this task by not issuing BitBake's
- cleanall, cleansstate,
- or forced fetch commands.
+ trigger the
+ do_fetch
+ task for the recipe.
+ You can avoid triggering this task by not using BitBake to
+ run the
+ cleanall,
+ cleansstate,
+ or forced
+ fetch
+ commands.
Also, do not modify the recipe itself while working
with temporary changes or BitBake might run the
fetch command depending on the