As reported by Andrea, defconfigs created with savedefconfig should specify their expansion mode as "--alldefconfig' for custom yocto recipes. To ensure that this is documented, we can add a comment in the skeleton recipe.
Reported-by: Andrea Adami <[email protected]> Signed-off-by: Bruce Ashfield <[email protected]> --- meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb index c3291064bb15..b1a0784c1b7d 100644 --- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb +++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb @@ -32,6 +32,16 @@ # patches: patches can be merged into to the source git tree itself, # added via the SRC_URI, or controlled via a BSP # configuration. +# +# defconfig: When a defconfig is provided, the linux-yocto configuration +# uses the filename as a trigger to use a 'allnoconfig' baseline +# before merging the defconfig into the build. +# +# If the defconfig file was created with make_savedefconfig, +# not all options are specified, and should be restored with their +# defaults, not set to 'n'. To properly expand a defconfig like +# this, specify: KCONFIG_MODE="--alldefconfig" in the kernel +# recipe. # # example configuration addition: # SRC_URI += "file://smp.cfg" -- 1.8.1.2 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
