Bruce Ashfield fcf53f6a8c yocto-cfg-fragments: introduce native provider of configuration fragments ... To allow the use of the yocto configuration fragments in scenarios where a kernel inherits kernel-yocto or has a custom fragment implementation, but doesn't directly include the yocto-kernel-cache in the kernel SRC_URI, we introduce a native provider of the fragments. This fragment provider is independent of a kernel tree and when added as a dependency to a recipe, the fragments will be placed in: recipe-sysroot-native/kcfg/ These can then be referenced on the SRC_URI or in KERNEL_FEEATURES by using '../recipe-sysroot-native/kcfg' as the relative path to the .scc or .cfg file. In the future, this won't be required as kernel-yocto will always check the native sysroot for fragments, and fragments will always be referenced by relative path from the base of the kernel-cache. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>		2021-10-13 22:45:55 -04:00
..
dtc	python3-dtc: update BSD License to more specific BSD-2-Clause	2021-09-16 18:01:55 -04:00
linux	yocto-cfg-fragments: introduce native provider of configuration fragments	2021-10-13 22:45:55 -04:00
lopper	global: overrides conversion pass 2	2021-08-02 17:18:08 -04:00