From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Linux kernel: add support for config fragment files
Date: Tue, 10 Feb 2015 21:19:53 +0200 [thread overview]
Message-ID: <20150210191953.GA32404@tarshish> (raw)
In-Reply-To: <1423576221-24249-1-git-send-email-bos@je-eigen-domein.nl>
Hi Floris,
On Tue, Feb 10, 2015 at 02:50:21PM +0100, Floris Bos wrote:
> Adds configuration option to merge additional kernel configuration files
> to the main kernel configuration using scripts/kconfig/merge_config.sh
>
> For use-cases in which it is desired to build a custom Linux kernel based on
> the defconfig of the target device, but with a couple extra options/modules
> enabled.
>
> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
> ---
[...]
> @@ -178,6 +179,8 @@ define LINUX_CONFIGURE_CMDS
> $(INSTALL) -m 0644 $(KERNEL_SOURCE_CONFIG) $(KERNEL_ARCH_PATH)/configs/buildroot_defconfig
> $(TARGET_MAKE_ENV) $(MAKE1) $(LINUX_MAKE_FLAGS) -C $(@D) buildroot_defconfig
> rm $(KERNEL_ARCH_PATH)/configs/buildroot_defconfig
> + $(if $(LINUX_KERNEL_CONFIG_FRAGMENTS),
> + $(@D)/scripts/kconfig/merge_config.sh -m -O $(@D) $(@D)/.config $(LINUX_KERNEL_CONFIG_FRAGMENTS))
The merge_config.sh script is in the kernel since version 3.3. The -O
parameter is only supported since v3.9. How do you handle older kernels?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-02-10 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 13:50 [Buildroot] [PATCH] Linux kernel: add support for config fragment files Floris Bos
2015-02-10 19:19 ` Baruch Siach [this message]
2015-02-10 21:09 ` Floris Bos
2015-02-10 21:16 ` Baruch Siach
2015-02-14 9:01 ` Thomas Petazzoni
2015-02-14 13:47 ` Floris Bos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150210191953.GA32404@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox