linux-yocto-custom: provide defconfig guidance

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 <andrea.adami@gmail.com>
(From OE-Core rev: 2c41a28c9a9772531dcfc7079604ff2441c71f8f)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Bruce Ashfield 2014-04-28 12:09:33 -04:00 committed by Richard Purdie
parent ee4f09a850
commit 70b11e54ff
1 changed files with 10 additions and 0 deletions

View File

@ -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"