From 58f61cf79eb0796864c090b1ec0203760c6ec3ae Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 30 Jan 2013 13:54:59 -0600 Subject: ref-manual: new BB_DANGLINGAPPENDS_WARNONLY variable added to glossary. Fixes YOCTO #3662 New entry added. Reported-by: Robert P. J. Day (From yocto-docs rev: 73f8b28f6b6cea16cf63b99db88c961f87088fe1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 98557f0..3088123 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -120,6 +120,39 @@ + BB_DANGLINGAPPENDS_WARNONLY + + + Defines how BitBake handles situations where an append + file (.bbappend) has no + corresponding recipe file (.bb). + This condition often occurs when layers get out of sync + (e.g. oe-core bumps a + recipe version and the old recipe no longer exists and the + other layer has not been updated to the new version + of the recipe yet). + + + + The default fatal behavior is safest because it is + the sane reaction given something is out of sync. + It is important to realize when your changes are no longer + being applied. + + + + You can change the default behavior by setting this + variable to "1" in the local.conf + file in the + Build Directory + as follows: + + BB_DANGLINGAPPENDS_WARNONLY = "1" + + + + + BB_DISKMON_DIRS -- cgit v1.1