diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-05-09 13:55:01 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-05-25 13:15:48 +0100 |
commit | 7090a14b0035842112d073acf7f2ed1a01fdeccf (patch) | |
tree | ca3385a0e393885e765a47c19373f93b7361a938 /conf | |
parent | 5bcd213c23da30a84baba88b775b1740e6bb77d0 (diff) | |
download | bitbake-7090a14b0035842112d073acf7f2ed1a01fdeccf.tar.gz |
cooker: Add FILE_LAYERNAME variable containing the layername for a recipe
There are times when it would be useful for code to know which layer
(or collection in old bitbake terms) it is contained within.
Add support for FILE_LAYERNAME to be set by bitbake when parsing a recipe
so that it is possible to determine this. To do it, we need to pass data
from the cooker into the recipe endpoints, since only the top level cooker
information knows about the layer structure which makes the patch a bit
painful.
The idea is that this would make layer overrides possible:
OVERRIDES .= ":layer-${FILE_LAYERNAME}"
which then opens possibilities like:
WARN_QA:append:layer-core = " patch-fuzz"
as an example where OE-Core could enable specific QA tests only for that
specific layer.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'conf')
0 files changed, 0 insertions, 0 deletions