Re: Proposal:Use PGDLLEXPORT for libpq - Mailing list pgsql-hackers

From Yury Zhuravlev
Subject Re: Proposal:Use PGDLLEXPORT for libpq
Date
Msg-id e44a4c31-4778-418c-a08c-4b5eaedb1542@postgrespro.ru
Whole thread Raw
In response to Re: Proposal:Use PGDLLEXPORT for libpq  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Proposal:Use PGDLLEXPORT for libpq  (Michael Paquier <michael.paquier@gmail.com>)
Re: Proposal:Use PGDLLEXPORT for libpq  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Craig Ringer wrote:
> On 27 January 2016 at 00:16, Yury Zhuravlev
> <u.zhuravlev@postgrespro.ru> wrote:
>
> It says more about the modules, and not about libpq. Using
> gendef.pl for this library in the light of the development of my
> CMake build seems silly.
>
>
> For what it's worth I personally agree. I'd rather have
> PGDLLEXPORT used directly, not least because it'd let us built
> with -fvisibility=hidden under *nix. But I'm in the minority and
> not inclined to push the point.
>
If so many problems with MSVC can discard his support of Postgres?
MSVC:
Not supported C99-C1x.
Problems build dynamic library.
Realy problems build out-tree module.
etc

Under windows we can use MinGW64/Msys or LLVM/Clang for MSVC.
The current situation is similar to masochism. We're not trying to change
the code to make it more portable.
But at the same time try using black magic to make Postgres work on
non-POSIX systems.
What's the point now support the MSVC?

Thanks.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Artur Zakirov
Date:
Subject: Re: Mac OS: invalid byte sequence for encoding "UTF8"
Next
From: Torsten Zühlsdorff
Date:
Subject: Re: Add generate_series(date,date) and generate_series(date,date,integer)