diff options
author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2020-08-27 16:04:47 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-08-28 07:06:44 +0100 |
commit | 09f4db415fb6a1398e9e9b359630043c833f6118 (patch) | |
tree | b5977fd642047c733439dc68e870d7b18af8e1d7 /meta/recipes-extended/newt | |
parent | 86142dad13935a0d9af4a4177e05ff5c39003db7 (diff) | |
download | openembedded-core-09f4db415fb6a1398e9e9b359630043c833f6118.tar.gz |
kernel-yocto: checksum all modifications to available kernel fragments directories
This is based on the patch from Zhaolong Zhang <zhangzl2013@126.com>
[kernel-yocto: checksum indirect cfg and scc files]
While the recommended manner to share/reuse feature fragments is to
maintain them in a kernel-meta repository and track the changes via the
standard SRCREV fetcher mechanism, that method is not always practical
for small sets of features or for quick testing of changes.
These other flows use .scc files on the SRC_URI. It has been noted that
config fragments or other features indirectly included by those .scc
files will not trigger the kernel meta-data to be re-run and hence a
build can continue with stale data (or not be triggered at all).
To solve this issue, we can collect the directories that are searchable
via FILESEXTRAPATHS and add them to the do_kernel_metadata task
checksum.
This allows modifications, additions and removals from the potential
kernel feature directories to trigger a re-execution of the meta data
task.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/newt')
0 files changed, 0 insertions, 0 deletions