From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Brar Piening <brar(at)gmx(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Visual Studio 2013 build |
Date: | 2014-01-26 00:13:25 |
Message-ID: | 52E45325.5050805@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/02/2013 05:12 PM, Brar Piening wrote:
> Hackers,
> the attached patch enables Microsoft Visual Studio 2013 as additional
> build environment.
> After some tweaking (VS now has got its own rint and a few macro
> definitions that were previously missing) the build runs without
> errors or warnings and the product passes the regression tests.
> I didn't test any special configurations though.
> I'm using full Visual Studio 2013 actually so I can't conform that
> everything still works with Visual Studio Express 2013 for Windows
> Desktop, but there are no documented limitations that make any
> problems foreseeable.
> I will add it to the CommitFest 2014-01 so that there is time for
> testing and tweaking.
>
OK, I have tested this out with the development branch and Visual Studio
Express 2013 for Windows Desktop, on Windows Server 2008 R2-SP1 64 bit.
With a slight adjustment to make the patch apply it works fine.
How far back should we go? About a year ago when we did this we applied
it for 9.2 (then the latest stable release) and 9.3dev.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-01-26 02:13:11 | Re: [COMMITTERS] pgsql: libpq: Support TLS versions beyond TLSv1. |
Previous Message | Peter Geoghegan | 2014-01-26 00:03:09 | Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core |