From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to make two defconfig simultaneously
Date: Thu, 9 Apr 2020 15:18:45 +0200 [thread overview]
Message-ID: <20200409151845.7635fea8@windsurf.home> (raw)
In-Reply-To: <CA+h21hr+Ct3COWUv7ZfiHnwfWRb0GVw_A268qEG6WZD-VMyv7g@mail.gmail.com>
On Thu, 9 Apr 2020 15:45:35 +0300
Vladimir Oltean <olteanv@gmail.com> wrote:
> Ok, this answers the 'how to merge them' portion of the question.
> Are there guidelines for where defconfig fragments _can_ be stored,
> how they should be structured, named, what they can contain? All the
> files that I see in the configs/ folder are simple defconfigs.
They can be stored wherever you want, and there are no particular
guidelines on how they should be structured. Each project will have its
own constraints. What matters is that Buildroot takes as input a single
.config file: how this .config file is produced is not relevant to
Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-09 13:18 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
2020-04-09 12:45 ` Vladimir Oltean
2020-04-09 13:03 ` [Buildroot] [EXT] " Jerry Huang
2020-04-09 13:18 ` Thomas Petazzoni [this message]
2020-04-09 12:59 ` 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=20200409151845.7635fea8@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 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.