diff options
author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2020-08-03 08:30:27 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-08-06 15:12:39 +0100 |
commit | 2b44ac076c7068aa0316d15fff49f02491eccb69 (patch) | |
tree | 287dd45c9853911f96c8189070d566247b068a8b /meta/classes/license.bbclass | |
parent | bb983b8f80c0dd33ae00a75b91a4cc5a10120aa9 (diff) | |
download | poky-2b44ac076c7068aa0316d15fff49f02491eccb69.tar.gz |
kernel/yocto: allow dangling KERNEL_FEATURES
KERNEL_FEATURES are explicitly checked by the kern-tools, and trigger
and error when not present. This is since the KERNEL_FEATURES are
specified by layers or BSPs as elements that are requied for correct
operation.
That being said, in order to support more kernel recipes that are using
fragments, but not necessarily the yocto kernel-cache for meta-data,
this change introduces: KERNEL_DANGLING_FEATURES_WARN_ONLY
As you'd expect, when set, missing kernel features only print a
message and warn that runtime issues may occur, but otherwise allow
the kernel configuration and build process to continue.
This was noticed/required when meta-virtualization adopted a more
generic kernel bbappend (to serve the needs of more layers in the
ecosystem), but also specifies some KERNEL_FEATURES. If layers using
a recipe derived from kernel-yocto, but not the main kernel-cache,
used meta-virtualization and error would be thrown due to missing
features. We now can both allow them to continue, and also provide
a more useful message to resolve the issue.
(From OE-Core rev: 8d44ea9fbb1ee7bec1062505a9bb1e2d7b360094)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/license.bbclass')
0 files changed, 0 insertions, 0 deletions