diff options
author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-03-24 14:57:49 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-03-24 22:51:07 +0000 |
commit | 5f5595eebeb81be7e824d998228e4ef9f0bfac7d (patch) | |
tree | cece079e3a2a2fd6b0f32a84a2866322c699362c /meta/recipes-extended/net-tools | |
parent | 6cc1315b77bbdcc8f3a0d1e3132ad79ebbeeb2de (diff) | |
download | openembedded-core-5f5595eebeb81be7e824d998228e4ef9f0bfac7d.tar.gz openembedded-core-5f5595eebeb81be7e824d998228e4ef9f0bfac7d.tar.bz2 openembedded-core-5f5595eebeb81be7e824d998228e4ef9f0bfac7d.zip |
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]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/net-tools')
0 files changed, 0 insertions, 0 deletions