Horton

Re: narwhal and PGDLLIMPORT

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Peter Geoghegan <pg@heroku.com>
Cc: Craig Ringer <craig@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2014-02-03T14:57:46Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. MinGW: Link with shell32.dll instead of shfolder.dll.

  2. Centralize getopt-related declarations in a new header file pg_getopt.h.

  3. Get rid of use of dlltool in Mingw builds.

  4. Export a few more symbols required for test_shm_mq module.

  5. Export set_latch_on_sigusr1 symbol for Windows.

  6. Use SHGetFolderPath instead of SHGetSpecialFolderPath to find the

On 02/03/2014 01:13 AM, Peter Geoghegan wrote:
> On Sun, Feb 2, 2014 at 5:22 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
>> I'm not a fan of MinGW (gcc) on Windows, it's a right pain. It's also
>> the only open source compiler currently supported for PostgreSQL on
>> Windows - practically the only one available. I don't know about you,
>> but I'm not too keen on assuming Microsoft will continue to offer free
>> toolchains that're usable for our purposes. They're crippling their free
>> build tools more and more with each release, which isn't a good trend.
> I was under the impression that Microsoft had finally come around to
> implementing a few C99 features in Visual Studio 2013 precisely
> because they want there to be an open source ecosystem on Windows.
>
>


It's not so long ago that they were saying they would no longer publish 
free-as-in-beer command line compilers at all. The outrage made them 
change their minds, but we really can't rely on only Microsoft compilers 
for Windows.

cheers

andrew