All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] MAKEALL: make it generic
Date: Mon, 27 Sep 2010 18:02:29 +0200	[thread overview]
Message-ID: <20100927160229.GI2111@game.jcrosoft.org> (raw)
In-Reply-To: <20100927143508.GY23406@pengutronix.de>

On 16:35 Mon 27 Sep     , Sascha Hauer wrote:
> On Mon, Sep 27, 2010 at 08:12:34AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > add MAKEALL.cfg example
> > 
> > it's allow you to compile specific defconfig or ARCH or all
> > as
> > CROSS_COMPILE=arm-linux- ARCH=arm ./MAKEALL at91sam9263ek_defconfig
> > CROSS_COMPILE=arm-linux- ARCH=arm ./MAKEALL
> > 
> > or via config
> > 
> > CONFIG=./MAKEALL.cfg ARCH=arm ./MAKEALL at91sam9263ek_defconfig
> > CONFIG=./MAKEALL.cfg ARCH=arm ./MAKEALL
> > 
> > and for all
> > 
> > CONFIG=./MAKEALL.cfg ./MAKEALL
> > 
> > you can specify
> > JOBS            jobs
> > BUILDDIR        build dir
> > LOGDIR          log dir
> 
> Would be good to have this example somewhere in the code, maybe as help
> text in MAKEALL
MAKEALL -h is ok?

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-09-27 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  6:12 [PATCH v2] MAKEALL: make it generic Jean-Christophe PLAGNIOL-VILLARD
2010-09-27 14:35 ` Sascha Hauer
2010-09-27 16:02   ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-09-29  7:29     ` Sascha Hauer
2010-09-29 10:31       ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-29 13:33         ` Sascha Hauer
2010-10-01  3:19 ` [PATCH v3] " Jean-Christophe PLAGNIOL-VILLARD
2010-10-01  7:16   ` Sascha Hauer
2010-10-01 16:48     ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-01 16:48   ` [PATCH v4] " Jean-Christophe PLAGNIOL-VILLARD

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=20100927160229.GI2111@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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.