Re: Compiling extensions on Windows

On 01/11/2014 01:55 PM, Magnus Hagander wrote:
> On Sat, Jan 11, 2014 at 7:05 PM, Tom Lane <tgl@sss.pgh.pa.us 
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>     Magnus Hagander <magnus@hagander.net <mailto:magnus@hagander.net>>
>     writes:
>     > On Sat, Jan 11, 2014 at 5:00 PM, Tom Lane <tgl@sss.pgh.pa.us
>     <mailto:tgl@sss.pgh.pa.us>> wrote:
>     >> I'm not sure I believe this.  I don't see any PGDLLEXPORT
>     symbols in any
>     >> of the standard contrib modules; how is it that they work?
>
>     > They are built through our perl toolkit, which enables exporting
>     of *all*
>     > symbols, regardless of flags in the code.
>
>     That seems like a perfectly reasonable solution, given the way we use
>     loadable modules.  Excess symbols in the module shouldn't really do
>     any harm.  Can't we just document the flags to use for this, if you're
>     building in some other way?
>
>
> It's not a build flag, and that's the main problem. It's the 
> src/tools/msvc/gendef.pl <http://gendef.pl> script that builds the 
> export list. And what Craig is after here is being able to build 
> extensions using standard tools without needing our full build 
> infrastructure.
>
>


What I'd like is something that would use or mimic our msvc build tools 
but for extensions. (And no, I don't have time to build it.)

cheers

andrew