summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/variables.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/variables.rst')
-rw-r--r--documentation/ref-manual/variables.rst18
1 files changed, 0 insertions, 18 deletions
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 5d24e80865..5c2920603f 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -361,24 +361,6 @@ system and gives an overview of their function and contents.
361 :term:`BB_CURRENTTASK` 361 :term:`BB_CURRENTTASK`
362 See :term:`bitbake:BB_CURRENTTASK` in the BitBake manual. 362 See :term:`bitbake:BB_CURRENTTASK` in the BitBake manual.
363 363
364 :term:`BB_DANGLINGAPPENDS_WARNONLY`
365 Defines how BitBake handles situations where an append file
366 (``.bbappend``) has no corresponding recipe file (``.bb``). This
367 condition often occurs when layers get out of sync (e.g. ``oe-core``
368 bumps a recipe version and the old recipe no longer exists and the
369 other layer has not been updated to the new version of the recipe
370 yet).
371
372 The default fatal behavior is safest because it is the sane reaction
373 given something is out of sync. It is important to realize when your
374 changes are no longer being applied.
375
376 You can change the default behavior by setting this variable to "1",
377 "yes", or "true" in your ``local.conf`` file, which is located in the
378 :term:`Build Directory`: Here is an example::
379
380 BB_DANGLINGAPPENDS_WARNONLY = "1"
381
382 :term:`BB_DEFAULT_TASK` 364 :term:`BB_DEFAULT_TASK`
383 See :term:`bitbake:BB_DEFAULT_TASK` in the BitBake manual. 365 See :term:`bitbake:BB_DEFAULT_TASK` in the BitBake manual.
384 366