Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add some simple "config & build" board shortcuts
Date: Thu, 18 Nov 2010 06:32:20 -0500	[thread overview]
Message-ID: <201011180632.21272.vapier@gentoo.org> (raw)
In-Reply-To: <20101118115910.5261e8af@surf>

On Thursday, November 18, 2010 05:59:10 Thomas Petazzoni wrote:
> On Thu, 18 Nov 2010 05:26:36 -0500 Mike Frysinger 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.

i dont think this has any real impact on "usability" for new users.  buildroot 
shouldnt really be forcing people into strict usage patterns to cater to new 
users while screwing power users.  the existing distro for Blackfin processors 
has similar targets and gets used quite a bit.

> 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.

i dont see any reason why it wouldnt work.  it's using $(MAKE) after all, not 
`make`, to process the sub-targets, and that, by design, preserves the 
original make setup.  and if this were true, i dont see how any of the current 
$(MAKE) usage in the top level Makefile wouldnt also be broken.

also, please maintain proper CC when replying.  not everyone gets e-mail from 
the buildroot list.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101118/d8d247c0/attachment.pgp>

      reply	other threads:[~2010-11-18 11:32 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
2010-11-18 11:32   ` Mike Frysinger [this message]

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=201011180632.21272.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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