Re: PG compilation error with Visual Studio 2015/2017/2019 - Mailing list pgsql-hackers

From davinder singh
Subject Re: PG compilation error with Visual Studio 2015/2017/2019
Date
Msg-id CAHzhFSGFSSMfX2uPV+CVfP73KtHVFEt7=BP+ZzGaJ54W+jYStQ@mail.gmail.com
Whole thread Raw
In response to Re: PG compilation error with Visual Studio 2015/2017/2019  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: PG compilation error with Visual Studio 2015/2017/2019  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
List pgsql-hackers


On Mon, Apr 6, 2020 at 8:17 PM Juan José Santamaría Flecha <juanjo.santamaria@gmail.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.

pgsql-hackers by date:

Previous
From: "movead.li@highgo.ca"
Date:
Subject: Re: A bug when use get_bit() function for a long bytea string
Next
From: Tatsuro Yamada
Date:
Subject: Re: Feature improvement: can we add queryId forpg_catalog.pg_stat_activity view?