From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bassem Fahmy <t_fahmy_bassem@hotmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] defconfig fragments
Date: Mon, 31 Oct 2022 18:30:22 +0100 [thread overview]
Message-ID: <20221031183022.5c51b20b@windsurf> (raw)
In-Reply-To: <SY4P282MB30149AA46B4BC3EF0C01C47FCB2F9@SY4P282MB3014.AUSP282.PROD.OUTLOOK.COM>
Hello Bassem,
On Sun, 23 Oct 2022 08:04:01 +0000
Bassem Fahmy <t_fahmy_bassem@hotmail.com> wrote:
> I understand that buildroot supports config fragments for packages (that support defconfig).
>
> But to patch the buildroot defconfig itself, the only way I could do it, is by calling
> > support/kconfig/merge_config.h xxxx_defconfig xxxx.config
>
> Is this the correct way? Is there a more standard way to patch a buildroot defconfig?
You're correct, that's the proper way of generating a Buildroot .config
from multiple fragments.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-10-31 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 8:04 [Buildroot] defconfig fragments Bassem Fahmy
2022-10-31 17:30 ` Thomas Petazzoni via buildroot [this message]
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=20221031183022.5c51b20b@windsurf \
--to=buildroot@buildroot.org \
--cc=t_fahmy_bassem@hotmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.