From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Proposal:Use PGDLLEXPORT for libpq |
Date: | 2016-01-27 12:54:21 |
Message-ID: | 20160127125421.GA642827@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yury Zhuravlev wrote:
> If so many problems with MSVC can discard his support of Postgres?
That doesn't sound likely. Keep in mind that users might want to
compile extension modules, and not everyone is going to use mingw for
that. As far as I know, stuff compiled with MSVC is not compatible with
mingw compiled objects. So even if the main packages switched to
compiling with mingw, we'd probably still want to support MSVC.
> Under windows we can use MinGW64/Msys or LLVM/Clang for MSVC.
I'm guessing that LLVM/Clang port would be useful for something, but I'm
not clear what.
Are we moving forward with the CMake stuff? It would be *awesome* to
get rid of the MSVC build scripts, and perhaps we can move forward on
some smaller items such as PGDLLEXPORT markings as well.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-01-27 13:05:06 | Re: Proposal:Use PGDLLEXPORT for libpq |
Previous Message | Michael Paquier | 2016-01-27 12:44:56 | Re: Proposal:Use PGDLLEXPORT for libpq |