Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Adding in support for custom configurations
Date: Tue, 19 Apr 2016 09:22:55 +0200	[thread overview]
Message-ID: <20160419092255.4ebd2291@free-electrons.com> (raw)
In-Reply-To: <57157458.7080802@mind.be>

Hello,

On Tue, 19 Apr 2016 01:57:12 +0200, Arnout Vandecappelle wrote:

> >> >I think the only reasonable solution to this is to really allow
> >> >multiple BR2_EXTERNAL directories. A patch series doing this was
> >> >proposed by Yann E. Morin a while ago, but due to the fairly
> >> >significant additional complexity, it hasn't been merged so far.
> > Has there been any previous discussion about allowing sub-directories
> > under 'configs'?  The Linux kernel tree allows both
> > $(ARCH)/configs/*_defconfig and $(ARCH)/configs/*/*_defconfig .  Coupled
> > with Steve's proposal for us to use symlinks, we could create
> > $(BR2_EXTERNAL)/configs/custom as a symlink to
> > $(BR2_EXTERNAL)/custom/configs and have a solution as well.
> 
>   If that doesn't add too much complexity (and I can't imagine it does), it 
> could definitely be a good solution. Especially if that allows us to kill the 
> idea of a multi-layered-without-calling-it-layers BR2_EXTERNAL :-)

Our configs/ directory is also growing, so we could think of using
sub-directories to organize the configurations per-vendor, or to
separate the minimal configs from the demo ones, or something.

Or we could move the configs next to the board/ related files they
correspond. Hm, wait, that's what we used to do 5+ years ago :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-19  7:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 15:40 [Buildroot] [PATCH] Adding in support for custom configurations Patrick Williams
2016-04-16  1:06 ` Steve Calfee
2016-04-17 20:31 ` Thomas Petazzoni
2016-04-18 16:25   ` Patrick Williams
2016-04-18 17:07     ` Steve Calfee
2016-04-18 17:14       ` Patrick Williams
2016-04-18 17:37         ` Steve Calfee
2016-04-18 20:59           ` Patrick Williams
2016-04-18 19:15     ` Thomas Petazzoni
2016-04-18 21:44       ` Patrick Williams
2016-04-18 23:57         ` Arnout Vandecappelle
2016-04-19  7:22           ` Thomas Petazzoni [this message]
2016-05-12  2:12 ` [Buildroot] [PATCH] Support nested config directories Patrick Williams
2016-05-12 13:55   ` Thomas Petazzoni

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=20160419092255.4ebd2291@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