From: Zbynek Winkler (zw-bjam_at_[hidden])
Date: 2005-10-07 09:29:40
David Abrahams wrote:
>At a meeting of the Boost moderators who attended the C++ committee
>meeting last night we decided to change the output that bjam spits out
>by default to be more consistent with most peoples' expectations: the
>command being executed will appear on the console (like -d+2) and then
>the command's output will follow. Rationale is that:
> a. People who use Make and even many IDEs are used to it
> b. The current "actions" output is too complicated to be
> appreciated as a simplification
> c. The current "actions" output is next to useless. When people
> run into problems they always need -d+2, and newbies don't know
> how to get it.
>I think we may need some small extension to allow the suppression of
>the executed commands for cases like the "run" rule that's used in
>testing: it's so ugly as to be unhelpful.
>If I don't hear loud objections in the next 24 hours, I'm going to
>implement this change and check it in.
I am sad to hear that. Not outputting the commands executed is one of
the things I most appreciate about BB. Always when I see the output that
is generated by compilation of a project that uses the autotools makes
want run away and scream in horror. 5 to 15 lines of output (especially
when using gettext) for each file compiled that scrolls by so fast and
so unexpectedly causes that it takes me an awful lot of time just to
figure out the name of the file being compiled. If the command works, I
do not really care about all the options. I just want to know what is
happening (compiling, linking... name of the files involved etc).
Can we have at least an option (command line or rule to put in Jamroot)
to retain the current style of output? Thanks.
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