On Sun, Jan 26, 2014 at 1:13 AM, Andrew Dunstan <and...@dunslane.net> wrote:
> > 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. > Seems reasonable to follow the same pattern, and apply it for 9.3 stable and 9.4dev. The argument being that it's a new build env, and it's not likely that people are going to use that t o build very old versions of postgres. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
