summaryrefslogtreecommitdiffstats
path: root/meta/classes/crosssdk.bbclass
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2015-03-24 14:57:49 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-25 12:39:46 +0000
commit4dbe239ff4e9dbe0216a554a806d41537c82cfb4 (patch)
tree025d11e576265e4eb841f6bfc9279578af50914a /meta/classes/crosssdk.bbclass
parentdf6d275d749d181f94102997efed80ae464455d7 (diff)
downloadpoky-4dbe239ff4e9dbe0216a554a806d41537c82cfb4.tar.gz
kernel-yocto: allow in-tree defconfigs
In a similar manner to the kernel itself, which does the following to bring a defconfig into the configuration: defconfig: $(obj)/conf ifeq ($(KBUILD_DEFCONFIG),) $< --defconfig $(Kconfig) else @echo "*** Default configuration is based on '$(KBUILD_DEFCONFIG)'" $(Q)$< --defconfig=arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG) $(Kconfig) endif We do the same with the linux-yocto configuration processing. If a defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it from the source tree, into a common location and normalized "defconfig" name, where the rest of the process will include and incorporate it into the configuration process. If the fetcher has already placed a defconfig in WORKDIR (from the SRC_URI), we don't overwrite it, but instead warn the user that SRC_URI defconfigs take precedence. [YOCTO: #7474] (From OE-Core rev: 5f5595eebeb81be7e824d998228e4ef9f0bfac7d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/crosssdk.bbclass')
0 files changed, 0 insertions, 0 deletions