Re: PG compilation error with Visual Studio 2015/2017/2019

From: davinder singh <davindersingh2692(at)gmail(dot)com>
To: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG compilation error with Visual Studio 2015/2017/2019
Date: 2020-04-07 05:43:59
Message-ID: CAHzhFSGFSSMfX2uPV+CVfP73KtHVFEt7=BP+ZzGaJ54W+jYStQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2020 at 8:17 PM Juan José Santamaría Flecha <
juanjo(dot)santamaria(at)gmail(dot)com> wrote:

>
> How do you reproduce this issue with Visual Studio? I see there is an
> ifdef directive above IsoLocaleName():
>
> #if defined(WIN32) && defined(LC_MESSAGES)
>
> I would expect defined(LC_MESSAGES) to be false in MSVC.
>

You need to enable NLS support in the config file. Let me know if that
answers your question.

--
Regards,
Davinder.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuro Yamada 2020-04-07 06:40:34 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Previous Message movead.li@highgo.ca 2020-04-07 05:39:37 Re: A bug when use get_bit() function for a long bytea string