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] add some simple "config & build" board shortcuts
Date: Thu, 18 Nov 2010 11:59:10 +0100	[thread overview]
Message-ID: <20101118115910.5261e8af@surf> (raw)
In-Reply-To: <1290075996-31465-1-git-send-email-vapier@gentoo.org>

On Thu, 18 Nov 2010 05:26:36 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> I like to be able to do `make foo` and have buildroot build up an image
> for the board named "foo".  This saves me from having to do a full clean,
> config, and make cycle.  Yes, I am that lazy :P.

I'd prefer not to have this in Buildroot. The general direction we are
taking (from my point of view) is to try to *reduce* the number of make
targets and the number of ways to use Buildroot, in order to make it
easier/simpler to understand for users.

So just like we removed options whose sole purpose was to rename final
target images, I think we should not add new make targets that should
instead simply be a shell invocation "make clean && make
foobar_defconfig && make". In addition to this, I am not sure your
implementation correctly passes down the O= argument for out-of-tree
builds.

Regards,

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

  reply	other threads:[~2010-11-18 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 10:26 [Buildroot] [PATCH] add some simple "config & build" board shortcuts Mike Frysinger
2010-11-18 10:59 ` Thomas Petazzoni [this message]
2010-11-18 11:32   ` Mike Frysinger

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=20101118115910.5261e8af@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