Re: Lower msvc build verbosity level

From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: 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>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lower msvc build verbosity level
Date: 2016-04-08 16:24:07
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

* 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

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.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-04-08 16:25:50 Re: Speed up Clog Access by increasing CLOG buffers
Previous Message Andrew Dunstan 2016-04-08 16:10:04 Re: VS 2015 support in src/tools/msvc