From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/10] manual: add section about storing the configuration.
Date: Tue, 23 Oct 2012 15:05:52 +0200 [thread overview]
Message-ID: <50869630.6020703@mind.be> (raw)
In-Reply-To: <5084321B.60701@relinux.de>
On 21/10/12 19:34, Stephan Hoffmann wrote:
> Am 21.10.2012 01:45, schrieb Arnout Vandecappelle (Essensium/Mind):
>> +Once you have a known working configuration, run +make
>> +savedefconfig+. This will generate a minimal +defconfig+ file at the
>> +root of the Buildroot source tree. Move this file into the +configs/+
>> +directory, and rename it +<boardname>_defconfig+.
> Hello all,
>
> so we will end with a nice tree of hopefully many
> board/<manufacturer>/<boardname> folders containig special settings for
> each board, most likely at least a kernel config file. I don't expect
> that too many boards will do without other settings but those in
> buildroot's defconfig. And we will have many<boardname>_defconfig files
> in the configs folder.
>
> Wouldn't it make more sense to move buildroot's<boardname>_defconfig
> files to the respective board folder, so that everything would be
> together in one place?
I fully agree, but I think we should first get these clean-ups committed
before considering that.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-10-23 13:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 23:45 [Buildroot] [PATCH 00/10] Various simplifications of the buildroot configuration Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 01/10] manual: add section about storing the configuration Arnout Vandecappelle
2012-10-21 15:05 ` Samuel Martin
2012-10-21 18:20 ` Thomas Petazzoni
2012-10-23 13:03 ` Arnout Vandecappelle
2012-10-21 17:34 ` Stephan Hoffmann
2012-10-23 13:05 ` Arnout Vandecappelle [this message]
2012-10-20 23:45 ` [Buildroot] [PATCH 02/10] target/generic: add filesystem overlay option Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 03/10] ctng: add ctng-update-config target Arnout Vandecappelle
2012-10-21 15:06 ` Samuel Martin
2012-10-23 13:09 ` Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 04/10] busybox: busybox-update-config should depend on busybox-configure Arnout Vandecappelle
2012-10-21 15:07 ` Samuel Martin
2012-10-23 13:15 ` Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 05/10] at91bootstrap3: add -update-config target Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 06/10] Add update-all-config target Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 07/10] busybox: update-all-config shouldn't update default busybox config Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 08/10] crosstool-ng: " Arnout Vandecappelle
2012-10-21 15:07 ` Samuel Martin
2012-10-23 13:16 ` Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 09/10] uClibc: update-all-config shouldn't update default uClibc config Arnout Vandecappelle
2012-10-20 23:45 ` [Buildroot] [PATCH 10/10] Make savedefconfig save to a configured file Arnout Vandecappelle
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=50869630.6020703@mind.be \
--to=arnout@mind.be \
--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