From: Vladimir Oltean <olteanv@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to make two defconfig simultaneously
Date: Thu, 9 Apr 2020 15:16:36 +0300 [thread overview]
Message-ID: <CA+h21hpmV55Nh7HUA5WZ3QKU+yCPsnoLOVuNge8VyMbbK6EtHg@mail.gmail.com> (raw)
In-Reply-To: <20200409133434.20276005@windsurf.home>
Hi Thomas,
On Thu, 9 Apr 2020 at 14:34, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> On Thu, 9 Apr 2020 08:13:52 +0000
> Jerry Huang <jerry.huang@nxp.com> wrote:
>
> > Hi, all guys,
> > Is there any mechanism to make two defconfig simultaneously ?
> > For example:
> > "make xxx_defcofnig yyy_defconfig"
>
> It is not clear what you want to achieve. Do you want to build
> xxx_defconfig and yyy_defconfig as two separate configurations and two
> separate builds ?
>
> Or do you want to combine them together because each describes only one
> part of the overall system ?
>
> Thomas
> --
> 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.
Thanks,
-Vladimir
next prev parent reply other threads:[~2020-04-09 12:16 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 [this message]
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 ` [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=CA+h21hpmV55Nh7HUA5WZ3QKU+yCPsnoLOVuNge8VyMbbK6EtHg@mail.gmail.com \
--to=olteanv@gmail.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.