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 2/6] Remove the BOARD/LOCAL feature
Date: Thu, 17 Sep 2009 07:43:42 +0200	[thread overview]
Message-ID: <20090917074342.7ea13dd0@surf> (raw)
In-Reply-To: <d6cda7730909161521k54dbdcfaud53cca89589dffe6@mail.gmail.com>

Le Wed, 16 Sep 2009 19:21:54 -0300,
Thiago A. Corr?a <thiago.correa@gmail.com> a ?crit :

> Exporting a variable all the time is a bit anoying, but one could
> always create a script to do that.

Well, you can also do :

 make BUILDROOT_EXTERNAL_BOARDS=/path/to menuconfig
 make BUILDROOT_EXTERNAL_BOARDS=/path/to

but I find it even more annoying.

The issue is that it is not possible to store this information in the
configuration, since depending on this value we must change some
Config.in file, which has to be done *before* we run the configuration
system.

> Looks good. It would be nice to add BUILDROOT_EXTERNAL_BOARDS to the
> find command at the %_defconfig rule, so things like this would work:
> make mycustomboard_defconfig

Well, it's already done by the patch (and works). Since a symbolic link
to the BUILDROOT_EXTERNAL_BOARDS directory is added in target/device/,
I just added the -L option to find and it is able to find the defconfig
of the external boards. See the patch for the one-liner
implementation :-)

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-09-17  5:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 21:07 [Buildroot] [pull request] Buildroot cleanup, v2 Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 1/6] Remove the "project" feature Thomas Petazzoni
2009-09-17 16:17   ` Bernhard Reutner-Fischer
2009-09-17 17:30     ` Thomas Petazzoni
2009-09-19 15:26     ` Peter Korsgaard
2009-09-19 15:15   ` Peter Korsgaard
2009-09-16 21:07 ` [Buildroot] [PATCH 2/6] Remove the BOARD/LOCAL feature Thomas Petazzoni
2009-09-16 22:00   ` Thiago A. Corrêa
2009-09-16 22:08     ` Thomas Petazzoni
2009-09-16 22:21       ` Thiago A. Corrêa
2009-09-17  5:43         ` Thomas Petazzoni [this message]
2009-09-17 12:02           ` Peter Korsgaard
2009-09-16 21:07 ` [Buildroot] [PATCH 3/6] By default, put the output in an output/ directory Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 4/6] Remove BR2_TOPDIR_PREFIX and BR2_TOPDIR_SUFFIX Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 5/6] Rename the output directories Thomas Petazzoni
2009-09-16 21:07 ` [Buildroot] [PATCH 6/6] documentation: update after major changes Thomas Petazzoni
2009-09-19 15:27 ` [Buildroot] [pull request] Buildroot cleanup, v2 Peter Korsgaard
2009-09-20  9:08   ` Thomas Petazzoni
2009-09-21  2:37     ` Steve Calfee
2009-09-22 22:16 ` H Hartley Sweeten
2009-09-22 22:38   ` Thomas Petazzoni
2009-09-22 22:56     ` H Hartley Sweeten
2009-09-22 23:13       ` 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=20090917074342.7ea13dd0@surf \
    --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