Re: VS 2015 support in src/tools/msvc - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: VS 2015 support in src/tools/msvc
Date
Msg-id CAB7nPqRNwNXQ6C_1kODE5kN0WQUqLuWtPdLD4rn5nGmJUiibLw@mail.gmail.com
Whole thread Raw
In response to Re: VS 2015 support in src/tools/msvc  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: VS 2015 support in src/tools/msvc  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: VS 2015 support in src/tools/msvc  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Mon, Apr 11, 2016 at 3:25 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Now, I have produced two patches:
> - 0001-Support-for-VS-2015-locale-hack.patch, which makes use of
> __crt_locale_data_public in ucrt/corecrt.h. This is definitely an ugly
> hack, though I am coming to think that this may be the approach that
> would us the less harm, and that's closer to what is done for VS 2012
> and 2013.
> - 0001-Support-for-VS-2015-getlocaleinfoex.patch, which make use of
> GetLocaleInfoEx, this requires us to lower a bit the support grid for
> Windows, basically that's throwing support for XP if compilation is
> done with VS 2015.
> Based on my tests, both are working with short and long local names,
> testing via initdb --locale.

The first patch is actually not what I wanted to send. Here are the
correct ones...
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Some other things about contrib/bloom and generic_xlog.c
Next
From: Etsuro Fujita
Date:
Subject: Re: Optimization for updating foreign tables in Postgres FDW