Compiling ... messages
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Wed Oct 24 09:34:00 PDT 2012
When the dust has settled on my latest race of log changing, things now
work like this:
> A minor comment but when compiling the native code in the jdk
> repository then the "Compiling ..." messages only print the file name
> so it's not obvious what code is being compiled (unless there is a
> warning or an error, in which case the full path is revealed). When
> compiling hotspot then the messages have the full path which is much
> clearer in my view.
The default log level now hides printing of individual filenames (unless
there is an error/warning).
If you run with LOG=info, individual filenames will be printed as
before, but now also the target library/binary will be printed, e.g.
Compiling hubbabubba.cpp (for libhubba.so)
>
> 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.
/Magnus
More information about the build-infra-dev
mailing list