dev-manual, kernel-dev: Provides some cross-reference to "clean" stuff.

I scrubbed the manual set for appropriate places to reference into the
do_clean* type tasks.  Found and added several occurrences.

(From yocto-docs rev: 01594823b1d556bc70e928af1838039cc15a816d)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2014-06-16 11:45:19 +03:00
committed by Richard Purdie
parent cf0be8389c
commit ac6bdb4d41
3 changed files with 39 additions and 14 deletions

View File

@@ -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 <filename>do_fetch</filename> task for the recipe.
You can avoid triggering this task by not issuing BitBake's
<filename>cleanall</filename>, <filename>cleansstate</filename>,
or forced <filename>fetch</filename> commands.
trigger the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-fetch'><filename>do_fetch</filename></ulink>
task for the recipe.
You can avoid triggering this task by not using BitBake to
run the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-cleanall'><filename>cleanall</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-cleansstate'><filename>cleansstate</filename></ulink>,
or forced
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-fetch'><filename>fetch</filename></ulink>
commands.
Also, do not modify the recipe itself while working
with temporary changes or BitBake might run the
<filename>fetch</filename> command depending on the