From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
Cc: | Christian Ullrich <chris(at)chrullrich(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: VS 2015 support in src/tools/msvc |
Date: | 2016-04-11 07:47:21 |
Message-ID: | CAB7nPqRNwNXQ6C_1kODE5kN0WQUqLuWtPdLD4rn5nGmJUiibLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 11, 2016 at 3:25 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)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 | Content-Type | Size |
---|---|---|
0001-Support-for-VS-2015-getlocaleinfoex.patch | binary/octet-stream | 7.9 KB |
0001-Support-for-VS-2015-locale-hack.patch | binary/octet-stream | 6.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2016-04-11 08:16:00 | Re: Optimization for updating foreign tables in Postgres FDW |
Previous Message | Michael Paquier | 2016-04-11 07:44:12 | Re: Some other things about contrib/bloom and generic_xlog.c |