LayerIndex/Checker/Usual Issues

From Openembedded.org
Revision as of 10:33, 1 June 2021 by Dl9pf (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Usual issues that lead to yocto-check-layer failing:

a) The layer does change recipes just by being present

  • this means that usually a .bbappend has a change which is not conditional or in other ways inactive until enabled by the user
    • Patterns that can be used for this are:
      • _append_someoverride - to activate the layer, an override needs to be added
        • e.g. FILESEXTRAPATHS_prepend_rpi , SRC_URI_append_rpi , RDEPENDS_${PN}_append_rpi with the override _rpi being defined for the various pi boards
      • FOO_ENABLE = "1" and ${@bb.utils.contains('FOO_ENABLE', '1', 'case_yes', 'case_no', d)}
        • e.g. require ${@bb.utils.contains('FOO_ENABLE', '1', 'foo_bar.inc', , d)}

b) append files to layers that are not a hard requirement

c) The layer is missing either LAYERSERIES_COMPAT or LAYERDEPENDS

d) The layer has been restructured, the folders registered with the layerindex are no longer there - resubmit and note what entry should be replaced !