Compiling ... messages

[Kelly O'Hair]

On Oct 24, 2012, at 9:54 AM, Alan Bateman wrote:

> On 24/10/2012 17:34, Magnus Ihse Bursie wrote:
>> 
>> The default log level now hides printing of individual filenames (unless there is an error/warning).
> I noticed this so I switched to LOG=info because I prefer to see the compilations whizz by. What the default output is obviously very subjective. Personally I do not like long pauses as it's not clear whether the compiler or linker or some tool has gone into a loop or not.

I agree. I like lots of feedback as to what is happening.

> 
>> 
>>> 
>>> Another thing that would be helpful is the compilation of the launchers where the build emits messages like this:
>>> 
>>> Compiling main.c
>>> Compiling main.c
>>> Compiling main.c
>> ... which looks like this with LOG=info now:
>> 
>> Compiling main.c (for javac)
>> Compiling main.c (for java)
>> Compiling main.c (for javap)
>> 
>> I hope this seems satisfactory to you.
> Yes, for the launchers this makes sense to me.

Yes, this looks very good to me, good idea adding the launcher name.

-kto

> 
> -Alan