Re: narwhal and PGDLLIMPORT

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>, Dave Page <dpage@pgadmin.org>, Alvaro Herrera <alvherre@2ndquadrant.com>, Hiroshi Inoue <inoue@tpf.co.jp>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@2ndquadrant.com>, Amit Kapila <amit.kapila16@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2014-10-15T13:31:05Z
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 10/15/2014 01:53 AM, Craig Ringer wrote:
> On 10/15/2014 12:53 PM, Noah Misch wrote:
>> Windows Server 2003 isn't even EOL yet.  I'd welcome a buildfarm member with
>> that OS and a modern toolchain.
> It's possible to run multiple buildfarm animals on a single Windows
> instance, each with a different toolchain.


Indeed, and even using the same buildroot. That's been built into the 
buildfarm for a long time. For example, nightjar and friarbird do this.

>
> There's the chance of interactions that can't occur if each SDK is used
> in isolation on its own machine, but it should be pretty minimal.


Make sure each has a distinct base_port.


cheers

andrew