From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@rnout.be>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [RFC] Makefile: do defconfig with /dev/null instead of .defconfig
Date: Sat, 24 Oct 2026 23:27:04 +0200 [thread overview]
Message-ID: <at0igCDR4XVy1Qs-@windsurf> (raw)
In-Reply-To: <20261024170830.543982-1-arnout@rnout.be>
On Sat, Oct 24, 2026 at 07:08:30PM +0200, Arnout Vandecappelle via buildroot wrote:
> For `make defconfig`, we use a .defconfig file. This is inherited from
> the kernel, which has a different defconfig for each architecture. The
> kernel defconfig passes ARCH on the command line rather than in Kconfig,
> and defaults are very different for different architectures. In
> Buildroot, we don't have that, instead we have a .defconfig file which
> only has the default architecture. And it's not actually a defconfig,
> it's a very old full .config where only the first part is kept.
>
> Since we have architecture-independent defaults, and any architecture
> specific things are expressed with "depend on" and an occasional
> "default ... if ...", we don't need this infrastructure at all. We can
> simply make .defconfig an empty file - the BR2_arch choice has a default
> and that's all we need. And we don't even need an empty file, we have
> /dev/null to do that job.
>
> Use /dev/null for the "defconfig" target if no DEFCONFIG is given.
> Remove the now unnecessary .defconfig.
>
> Note that this also makes one hunk of
> support/kconfig/patches/01-kconfig-kernel-to-buildroot.patch redundant.
> Let's not do the effort of removing it now, we can remove it if it
> causes issues when updating the kconfig infrastructure.
>
> Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
Tested-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(Since this is RFC, I'm not applying right away, just voicing my
approval for this change.)
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
next prev parent reply other threads:[~2026-10-24 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 20:26 [Buildroot] [PATCH 1/4] Revert "Config.in, Makefile: add BR2_HIDE_SECONDARY_TARGET_OPTIONS" Julien Olivain via buildroot
2026-10-20 20:26 ` [Buildroot] [PATCH 2/4] Revert "arch: mark a set of target configurations as secondary" Julien Olivain via buildroot
2026-10-20 20:26 ` [Buildroot] [PATCH 3/4] utils/genrandconfig: implement secondary configurations filter Julien Olivain via buildroot
2026-10-20 20:26 ` [Buildroot] [PATCH 4/4] arch/Config.in: change default target architecture to AArch64 Julien Olivain via buildroot
2026-10-21 19:37 ` Fiona Klute via buildroot
2026-10-22 9:36 ` Arnout Vandecappelle via buildroot
2026-10-22 9:43 ` Baruch Siach via buildroot
2026-10-23 11:23 ` Julien Olivain via buildroot
2026-10-24 17:08 ` [Buildroot] [RFC] Makefile: do defconfig with /dev/null instead of .defconfig Arnout Vandecappelle via buildroot
2026-10-24 21:27 ` Thomas Petazzoni via buildroot [this message]
2026-10-25 9:13 ` Peter Seiderer via buildroot
2026-10-24 17:18 ` [Buildroot] [PATCH 4/4] arch/Config.in: change default target architecture to AArch64 Arnout Vandecappelle via buildroot
2026-10-25 20:57 ` Thomas Petazzoni via buildroot
2026-10-21 19:23 ` [Buildroot] [PATCH 1/4] Revert "Config.in, Makefile: add BR2_HIDE_SECONDARY_TARGET_OPTIONS" Thomas Petazzoni via buildroot
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=at0igCDR4XVy1Qs-@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox