From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/10] manual: add section about storing the configuration.
Date: Sun, 21 Oct 2012 19:34:19 +0200 [thread overview]
Message-ID: <5084321B.60701@relinux.de> (raw)
In-Reply-To: <1350776731-8467-2-git-send-email-arnout@mind.be>
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?
Just my 2 cents
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2012-10-21 17:34 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 [this message]
2012-10-23 13:05 ` Arnout Vandecappelle
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=5084321B.60701@relinux.de \
--to=sho@relinux.de \
--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.