Re: Lower msvc build verbosity level - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Lower msvc build verbosity level
Date
Msg-id CAB7nPqSrWFUh_AEt+0qWEPjzecR-MEqrMSj-hNk=h2s_pxuJ_A@mail.gmail.com
Whole thread Raw
In response to Re: Lower msvc build verbosity level  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Sat, Apr 9, 2016 at 1:47 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 04/08/2016 12:24 PM, Christian Ullrich wrote:
>>
>> * Tom Lane wrote:
>>
>>> +several.  Grepping for compiler warnings, for example, is really painful
>>> right now on any MSVC critter.  I've resorted to grepping for "warning
>>> C",
>>> which skips the noise messages, but I'm never sure if I'm missing
>>> something.
>>
>>
>> You miss all diagnostics from other tools than the compiler, for one
>> thing.
>>
>> There is a simple solution to that, however. MSBuild and VCBuild repeat
>> all warnings and errors produced during the build at the bottom of the log.
>> I just checked on mastodon (VS 2005, the oldest), and it does that already.
>>
>> This depends on the whole build being done using a single solution file
>> that contains all the individual projects, but there is no reason to assume
>> we will start building individual projects instead, I assume.
>>
>
> Yeah, what is more on the whole this is going to be far more beneficial,
> because stuff just gets lost badly in the noise. I have committed the
> change.

Thanks a lot! This is making my day, and I suspect many others are to come.
-- 
Michael



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Move PinBuffer and UnpinBuffer to atomics
Next
From: Michael Paquier
Date:
Subject: Re: VS 2015 support in src/tools/msvc