Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

[CVS ci] make: print filenames only

5 views

Skip to first unread message

Leopold Toetsch

unread,

Jul 28, 2003, 9:34:02 AM7/28/03

to P6I

Echoing all compiler flags clutters the screen too much, so that
warnings easily can get missed.
Earlier I used to run "make -s" which silents "make".
Still better would be:
- echo compiler flags once
- echo filenames only
- let the work depending on "-s" was given to "make" or not or such

leo

Josh Wilmes

unread,

Jul 28, 2003, 4:19:43 PM7/28/03

to Leopold Toetsch, P6I

I don't like the current state of things- it seems to be printing out the
full compilation commands occasionally, but mostly not.

I think that at this stage of development it's best to print out the full
commands being executed.

--Josh

Lars Balker Rasmussen

unread,

Jul 28, 2003, 5:05:00 PM7/28/03

to P6I

Josh Wilmes <jo...@hitchhiker.org> writes:
> I don't like the current state of things- it seems to be printing out the
> full compilation commands occasionally, but mostly not.

That's because not all makefiles use cc_flags.pl

> I think that at this stage of development it's best to print out the full
> commands being executed.

I agree.

Ideally, the best way to avoid warnings is to use -Werror ;-)
--
Lars Balker Rasmussen Consult::Perl

Leopold Toetsch

unread,

Jul 28, 2003, 5:08:54 PM7/28/03

to Josh Wilmes, P6I

[ Please answer inline, to keep the ocntext]
Josh Wilmes wrote:

> I don't like the current state of things- it seems to be printing out the
> full compilation commands occasionally, but mostly not.

Its probably a thing of "like it" or "not like it". I prefer to see
warnings and minimal or no compilation status ("make -s")

> I think that at this stage of development it's best to print out the full
> commands being executed.

That's the reason for my argument:

>>- let the work depending on "-s" was given to "make" or not or such

(with s/the/that/ - sorry)
Seeing the actual command is useful and necessary if the build prcoess
has troubles. For most of "normal" changes its more important to get
warnings/errors not hidden by ever repeating command line echos - IMHO.

> --Josh
leo

Vladimir Lipskiy

unread,

Jul 29, 2003, 6:25:59 AM7/29/03

to Josh Wilmes, Lars Balker Rasmussen, perl6-internals, Leopold Toetsch

Yepper. Leo is right. Most of output produced by make is such a bore.
I'm standing for doing these actions as default, namely:

1) we output "Supplying the following c compiler
flags: -Zi -DDEBUGGING-nologo ..."
once at the begining
2) ouput "Building the classes ..." once and a name of each class as it
being maked.
3) then "Linking the libraries: comdlg32.lib advapi32.lib shell32.lib ...."
4) and finally "Building documentation"

And echoing the whole thingy as the case of the --detailed switch being
passed.
It wouldn't be worth anything to type the only switch for who really wants
the full
output.

0 new messages