From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Project configuration management
Date: Wed, 6 Apr 2016 16:52:17 +0200 [thread overview]
Message-ID: <20160406165217.07547fff@free-electrons.com> (raw)
In-Reply-To: <5702D279.3050904@mind.be>
Hello,
On Mon, 4 Apr 2016 22:45:45 +0200, Arnout Vandecappelle wrote:
> > The mechanism we typically advise in such situation is to use defconfig
> > fragments, and assemble them as needed to create the configuration you
> > feed into Buildroot. A shell script (or other) can help generating the
> > configuration fed into Buildroot from the fragments.
>
> And that shell script exists already: support/kconfig/merge_config.sh
That's not exactly the sort of script I was thinking of. I was thinking
of a more high-level, project specific script, like maybe:
genconfig -h <hwplatform> -s <softwarestack> -r <releasetype>
or anything like that, which would internally have the knowledge of
which fragments to use for which aspect (HW platform, software stack,
etc.). Of course, internally, this script can use merge_config.sh, but
having a more high-level script might help users to more easily
generate their Buildroot configuration.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-06 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 13:55 [Buildroot] Project configuration management Mateusz Słupny
2016-04-04 18:44 ` Thomas Petazzoni
2016-04-04 20:45 ` Arnout Vandecappelle
2016-04-05 11:14 ` Mateusz Słupny
2016-04-06 14:52 ` Thomas Petazzoni [this message]
2016-04-06 16:01 ` Gustavo Zacarias
2016-04-04 19:09 ` Grant Edwards
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=20160406165217.07547fff@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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