bitbake: bitbake-user-manual: Updated the [noexec] and [nostamp] flag descriptions

Fixes [YOCTO #10401]

Added some wording to clarify that setting these flags to "1"
causes the desired action.  Also, provided a cautionary note
about tasks depending on any [nostamp] task causes the task
to always be executed and could cause unnecessary rebuild time.

(Bitbake rev: b6a4a6147b9e455cc1fec37553fb577f187a2d73)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-10-10 12:49:06 -07:00 committed by Richard Purdie
parent 1d4031a4df
commit ce70355260
1 changed files with 13 additions and 4 deletions

View File

@ -1833,14 +1833,23 @@
exclusion.
</para></listitem>
<listitem><para><emphasis><filename>[noexec]</filename>:</emphasis>
Marks the tasks as being empty and no execution required.
The <filename>[noexec]</filename> flag can be used to set up
When set to "1", marks the task as being empty, with
no execution required.
You can use the <filename>[noexec]</filename> flag to set up
tasks as dependency placeholders, or to disable tasks defined
elsewhere that are not needed in a particular recipe.
</para></listitem>
<listitem><para><emphasis><filename>[nostamp]</filename>:</emphasis>
Tells BitBake to not generate a stamp file for a task,
which implies the task should always be executed.
When set to "1", tells BitBake to not generate a stamp
file for a task, which implies the task should always
be executed.
<note><title>Caution</title>
Any task that depends (possibly indirectly) on a
<filename>[nostamp]</filename> task will always be
executed as well.
This can cause unnecessary rebuilding if you are
not careful.
</note>
</para></listitem>
<listitem><para><emphasis><filename>[postfuncs]</filename>:</emphasis>
List of functions to call after the completion of the task.