From: David Abrahams (dave_at_[hidden])
Date: 2005-10-11 07:30:08
Alo Sarv <alo.sarv_at_[hidden]> writes:
> If errors happen, bjam automatically prints
> the command-line, which IMHO is the best behaviour - keep output clean
> when there's no errors, and when errors happen, print the offending
> command-line as well. I also don't see how the current "actions"
> output is complicated (I'm assuming we'r talking about bbv2 here):
No, we're talking about both BBv1 and BBv2
> gcc.compile.c++ bin\src\gcc\debug\threading-multi\log.o
It's not that it's complicated; it's that it is confusing to the
> It says all that's needed - compiler, action, language, configuration,
> object being compiled - perfect. I have no need to see the full ugly
> command-line every time I compile. Furthermore, clean output also puts
> higher priority to warnings, which otherwise simply get hidden between
> the long command-lines.
I always thought that was better too, but then we constantly hear from
new users who can't tell what the build system is doing, and who find
these "actions" messages cryptic. For those of us who've been around
the block a little bit longer, I think it should be possible to set up
the output preferences differently. For some of users, it has been
suggested, even "actions" are too much -- some would like to see
nothing more than a "rotating bar" | / - \ | / - ...
Well, this seems like sufficient resistance that I'm not going to act
right away, but I'd like to hear more from those concerned about
whether this is a problem.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk