| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org> |
| Subject: | Re: Compiling extensions on Windows |
| Date: | 2014-01-11 18:05:11 |
| Message-ID: | 15135.1389463511@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sat, Jan 11, 2014 at 5:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-01-11 18:34:01 | Re: pg_export_snapshot on standby side |
| Previous Message | Andres Freund | 2014-01-11 17:53:28 | Re: Standalone synchronous master |