public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Concise Build Output
Date: Thu, 24 Jan 2008 01:41:45 +0100	[thread overview]
Message-ID: <20080124004145.833A52430C@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 23 Jan 2008 16:11:01 CST." <E1JHnoD-0004we-IN@jdl.com>

Dear Jon,

in message <E1JHnoD-0004we-IN@jdl.com> you wrote:
> 
> 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.

Thanks for your efforts.  I  will  not  object  against  adding  such
changes,  but  - speaking strictly for myself only - I don't see much
of improvement from it. It doesn't help me in my daily work.

Usually I find myself in one of two situations: either I just want to
build U-Boot for a board and don't want to see any messages from  the
build  process  except  error messages - then I use "make -s"; or I'm
debugging the make process itself, and I want to see all commands  in
full detail, then I run plain "make".

Well, to be honest, usually I'm doing none of these. In  95%  of  all
cases  I  just  run  "MAKEALL boardname" as this gives me the best of
both solutions: a silent build process with only warnings and  errors
printed,  and if something goes wrong and needs further investigation
I still have the full build lon in the LOG/ directory, i. e. I  don't
have to re-run the make.


So my question is: which problem are you trying to solve that is  not
already solved by "make -s" or "MAKEALL"? I don't really see the need
for a solution between no output and full output. YMMV, of course.

Hope I didn't frustrate you - I still appreciate the effort.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"If God had wanted us to use the metric system, Jesus would have  had
10 apostles."

  parent reply	other threads:[~2008-01-24  0:41 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
2008-01-24  0:41 ` Wolfgang Denk [this message]
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=20080124004145.833A52430C@gemini.denx.de \
    --to=wd@denx.de \
    --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