From 1a95d4a0701b87ae3674239a01aabe38a0123585 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 13 Oct 2016 15:00:23 -0700 Subject: 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 Signed-off-by: Richard Purdie --- bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml') 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 @@ Finally, after all the setscene tasks have executed, BitBake calls the function listed in - BB_SETSCENE_VERIFY_FUNCTION + BB_SETSCENE_VERIFY_FUNCTION2 with the list of tasks BitBake thinks has been "covered". The metadata can then ensure that this list is correct and can inform BitBake that it wants specific tasks to be run regardless -- cgit v1.2.3-54-g00ecf