Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to make two defconfig simultaneously
Date: Thu, 9 Apr 2020 14:25:07 +0200	[thread overview]
Message-ID: <20200409142507.5de703f4@windsurf.home> (raw)
In-Reply-To: <CA+h21hpmV55Nh7HUA5WZ3QKU+yCPsnoLOVuNge8VyMbbK6EtHg@mail.gmail.com>

On Thu, 9 Apr 2020 15:16:36 +0300
Vladimir Oltean <olteanv@gmail.com> wrote:

> > Thomas Petazzoni, CTO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com  
> 
> I would assume the question is about merging a defconfig with multiple
> fragments.

Then:

$ ./support/kconfig/merge_config.sh fragment1 fragment2

see also
https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf slides
43 and 44.

However, I would recommend to *not* store fragments under configs/ with
a _defconfig suffix, as this is normally used for complete defconfigs,
not fragments.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-09 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  8:13 [Buildroot] how to make two defconfig simultaneously Jerry Huang
2020-04-09 11:34 ` Thomas Petazzoni
2020-04-09 12:16   ` Vladimir Oltean
2020-04-09 12:25     ` Thomas Petazzoni [this message]
2020-04-09 12:45       ` Vladimir Oltean
2020-04-09 13:03         ` [Buildroot] [EXT] " Jerry Huang
2020-04-09 13:18         ` [Buildroot] " Thomas Petazzoni
2020-04-09 12:59     ` [Buildroot] [EXT] " Jerry Huang

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=20200409142507.5de703f4@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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