Build log verbosity changes

[Kelly O'Hair]

Just so you know,  changing this stuff is a pain for many of us.

From now on we need to be extremely aware of the impact on our users of the new build-infra makefiles and
not make spelling or option changes unless we feel it's a critical issue to resolve.

-kto

On Oct 12, 2012, at 8:39 AM, Magnus Ihse Bursie wrote:

> On 2012-10-12 12:58, David Holmes wrote:
>> On 12/10/2012 7:42 PM, Magnus Ihse Bursie wrote:
>>> On 2012-10-12 04:21, David Holmes wrote:
>>>> Hi Magnus,
>>>> 
>>>> How does VERBOSE= on the make invocation relate to this ??
>>> 
>>> The VERBOSE= option is deprecated and will soon go away. It was very
>>> crude, just a way of passing make flags (or rather, stop passing make
>>> flags which was kind of weird). The LOG=<loglevel> gives more freedom to
>>> adjust logging in several ways.
>> 
>> Ok, but what log level gives me the equivalent of VERBOSE= ?
>> 
>> I typically want full build logs but not any extra "debugging" stuff.
> 
> If you want to see command lines you should use LOG=debug. Basically, the only extra "debugging" stuff you will see is how the SetupFoo macros is called, but that is usually not much compared to all the command lines, and it helps a lot to improve understanding on what's going on and why.
> 
> (However, some of these expand with too long lines. I am planning to truncate too long lines at the debug level and only show that on the trace level.)
> 
> /Magnus
>