All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] A more readable build output ?
Date: Thu, 17 Sep 2009 09:10:23 +0200	[thread overview]
Message-ID: <87fxamyrkw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090916231925.0a8ce23b@surf> (Thomas Petazzoni's message of "Wed\, 16 Sep 2009 23\:19\:25 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> Currently, Buildroot displays the full build log on the standard
 Thomas> output. Having the full build log is of course nice, but:

 Thomas>  *) It is quite scary for new users

 Thomas>  *) It makes it more complicated for new users to understand the
 Thomas>     different steps of the Buildroot build process

 Thomas>  *) It makes it more complicated to see the progression of the build
 Thomas>     process (what is it doing now ? is it almost at the end ?)

 Thomas> Therefore, I've prototyped a simple thing that redirects the
 Thomas> build log to a file (so that the full build log is not lost and
 Thomas> can be examined for diagnostic purposes) and only display
 Thomas> messages like "Doing this", "Doing that" on the standard
 Thomas> output. The goal is to disable this behaviour when V=1 is
 Thomas> passed, but this isn't implemented yet.

We basically have this already when you build with 'make -s'. It's not
quite as quiet as we could wish, and non-makefile.autotools.in packages
don't print their steps, but we could probably fix that.

We can argue about what the default should be though, as the output is
quite interesting for debugging purposes when things go wrong (your
suggestion about logging to a file is nice).

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-09-17  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 21:19 [Buildroot] A more readable build output ? Thomas Petazzoni
2009-09-17  7:10 ` Peter Korsgaard [this message]
2009-09-17  9:23   ` Will Newton
2009-09-17 14:13   ` Thiago A. Corrêa

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=87fxamyrkw.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 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.