Re: narwhal and PGDLLIMPORT

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <pg@heroku.com>, Craig Ringer <craig@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-02-05T18:56:54Z
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/05/2014 01:41 PM, Joshua D. Drake wrote:
>
> On 02/03/2014 07:04 AM, Robert Haas wrote:
>>
>> On Mon, Feb 3, 2014 at 9:57 AM, Andrew Dunstan <andrew@dunslane.net> 
>> wrote:
>>> 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.
>>
>> +1.
>>
>
> It appears that LLVM supports Windows:
>
> http://llvm.org/docs/GettingStartedVS.html
>
>


If someone wants to work on getting a Windows build working with llvm 
then go for it. But until then the Mingw tools are the only thing we 
have that we know works other than Microsoft tools. Having a compiler 
that's alleged to work is only one step of many in getting there.

cheers

andrew