From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Christian Ullrich <chris(at)chrullrich(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Lower msvc build verbosity level |
Date: | 2016-04-08 16:47:11 |
Message-ID: | 5707E08F.2080907@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-04-08 16:49:45 | Re: Choosing parallel_degree |
Previous Message | Christian Ullrich | 2016-04-08 16:46:44 | Re: VS 2015 support in src/tools/msvc |