| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: narwhal and PGDLLIMPORT |
| Date: | 2014-02-12 21:35:56 |
| Message-ID: | 52FBE93C.5050300@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/12/14, 4:30 PM, Andres Freund wrote:
>> There are cases where one module needs symbols from another directly.
>> Would that be affected by this?
>
> I don't think we have real infrastructure for that yet. Neither from the POV of loading several .so's, nor from a symbol visibility. Afaics we'd need a working definition of PGDLLIMPORT which inverts the declspecs. I think Tom just removed the remnants of that.
It works reasonably well on other platforms.
Of course, we can barely build extension modules on Windows, so maybe
this is a bit much to ask. But as long as we're dealing only with
functions, not variables, it should work without any dllimport dances,
right?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-12 21:42:03 | Re: narwhal and PGDLLIMPORT |
| Previous Message | Bruce Momjian | 2014-02-12 21:35:40 | Re: memory usage of pg_upgrade |