summaryrefslogtreecommitdiffstats
path: root/recipes-core/runx
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2021-06-16 23:10:36 -0400
committerBruce Ashfield <bruce.ashfield@gmail.com>2021-10-14 18:29:05 -0400
commit5c212911879753d875ba76b3ab003502c8b7f900 (patch)
tree2d442a67425225119511fc6738fb2cf29b7ec1cc /recipes-core/runx
parentfcf53f6a8c4fb67f60143955c7239f204f633dfe (diff)
downloadmeta-virtualization-5c212911879753d875ba76b3ab003502c8b7f900.tar.gz
virtualization/config: allow conditional use of yocto-cfg-fragments
To help enforce/guide consistent configuration and to avoid duplicating configuration fragments into the meta-virt layer, we leverage a native provider of the yocto-kernel-cache fragment repository. To allow support for kernels that support fragments, but don't have the yocto-kernel-cache in the kernel's SRC_URI, we create two conditional parts of the virtualization configuration. If virtualization is enabled in the distro features, the kernel version matches one of our supported ones, and the kernel inherits kernel-yocto, we add a depedency on the yocto-cfg-fragments-native recipe. That recipe will install the fragment collection to the kernel recipe's native sysroot. We can then check for the kernel-cache on the SRC_URI. If it is present, we use the feature at the standard location. If it is not present, we add the fragment from the native sysroot. While we could always use the native sysroot variant, we want to allow a kernel with a kernel-cache to be the first choice, and provide their own fragments. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-core/runx')
0 files changed, 0 insertions, 0 deletions