Andy Dougherty <[EMAIL PROTECTED]> wrote: > On Wed, 6 Oct 2004, Leopold Toetsch via RT wrote:
>> I don't like the change, it just hides all warnings. > Odd. I don't see that. Hiding all warnings Hiding in the sense of: they don't stand out, they aren't really visible. > If 'make -s' is indeed useful, then I agree we oughtn't be doing an end > run around it. Well, 'make -s' is the command I'm using in 99% of compiles ;) For warnings (or errors) I see a nice line, else just filenames ... > tools/dev/cc_flags.pl only print the command if $ENV{MAKEFLAGS} doesn't > contain 's'. Or perhaps it's simpler and better to just retract the > patch. I don't know, if $ENV{MAKEFLAGS} and "-s" is available everywhere. >> But I see of course the point of beeing able to see the current build >> command. What about that: cc_flags.pl prints the build command if it >> changes, i.e. if there are any changes except the filename(s) involved. > That's probably not that useful -- in the usual case, there are no > changes, so the 'Compiling with ....' line might be a couple of thousand > lines above the current executing command. There are some changes e.g. when different CFLAGS settings are used, or for compiling classes. When there is a problem with compiling, just type another 'make' and you'll get again "Compiling with ...". leo