summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-10-13 15:00:23 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-10-13 23:29:25 +0100
commit1a95d4a0701b87ae3674239a01aabe38a0123585 (patch)
treef428093d006d8097f8036dc2dcc5e0422cbecac9 /bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
parent19d39be99bddcc72d012710438f6ec636e9f2945 (diff)
downloadpoky-1a95d4a0701b87ae3674239a01aabe38a0123585.tar.gz
bitbake: bitbake-user-manual: Changed BB_SETSCENE_VERIFY_FUNCTION name
The BB_SETSCENE_VERIFY_FUNCTION variable has effectively changed to BB_SETSCENE_VERIFY_FUNCTION2. I changed the three areas in the book. Basically a name change. (Bitbake rev: 41d9cd41d40b04746c82b4a940dca47df02514fc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
index ec75893e15..e4cc422ea4 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
@@ -916,7 +916,7 @@
916 <para> 916 <para>
917 Finally, after all the setscene tasks have executed, BitBake calls the 917 Finally, after all the setscene tasks have executed, BitBake calls the
918 function listed in 918 function listed in
919 <link linkend='var-BB_SETSCENE_VERIFY_FUNCTION'><filename>BB_SETSCENE_VERIFY_FUNCTION</filename></link> 919 <link linkend='var-BB_SETSCENE_VERIFY_FUNCTION2'><filename>BB_SETSCENE_VERIFY_FUNCTION2</filename></link>
920 with the list of tasks BitBake thinks has been "covered". 920 with the list of tasks BitBake thinks has been "covered".
921 The metadata can then ensure that this list is correct and can 921 The metadata can then ensure that this list is correct and can
922 inform BitBake that it wants specific tasks to be run regardless 922 inform BitBake that it wants specific tasks to be run regardless