From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Concise Build Output
Date: Wed, 23 Jan 2008 23:33:08 +0100 [thread overview]
Message-ID: <20080123223308.GA21868@game.jcrosoft.org> (raw)
In-Reply-To: <E1JHnoD-0004we-IN@jdl.com>
On 16:11 Wed 23 Jan , Jon Loeliger wrote:
> Folks,
>
> In the spirit of the Linux and Git build systems,
> I have a modified U-Boot build system that supports
> a much more concise output! One of the primary
> motivations for this style of output is that it
> will very readily highlight build issues and problems
> as your build progresses. The original, complete
> build output is obtainable by simply supplying "V=1"
> on the make invocation in exactly the same way as
> both Linux and Git do today.
>
> I've not converted all 300 boards to this new scheme
> yet, but would like your feedback on the approach.
> I know there are a few rough edges; those are easily
> smoothed out. I'd like to hear your comments on the
> overall approach before I spend too much more time
> on it!
>
> The ambitious amongst you can clone or inspect the
> repository with these modifications from here:
>
> git://jdl.com/software/u-boot.cfg
>
> Here is a sample build output for the MPC8641HPCN_config.
>
> Enjoy,
> jdl
>
> ----------------------------------------------------------------
>
> % make
> SUBDIR tools
> SYMLN environment.c
> SYMLN crc32.c
I'm actually working on a same function with the kconfig integration,
I will sumbit it soon.
Best Regards,
J.
next prev parent reply other threads:[~2008-01-23 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 22:11 [U-Boot-Users] RFC: Concise Build Output Jon Loeliger
2008-01-23 22:33 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-01-24 0:41 ` Wolfgang Denk
2008-01-24 22:08 ` Scott Wood
2008-01-24 23:18 ` Wolfgang Denk
2008-01-24 23:26 ` Scott Wood
2008-01-24 23:21 ` Grant Likely
2008-01-25 0:23 ` gvb.uboot
2008-01-29 10:06 ` Stefan Roese
2008-01-25 17:39 ` Jon Loeliger
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=20080123223308.GA21868@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox