Re: Compiling extensions on Windows
| От | Magnus Hagander |
|---|---|
| Тема | Re: Compiling extensions on Windows |
| Дата | |
| Msg-id | CABUevEzOhz8E4VPvxg6K8Cpi=sB9o1fQpvGBcmBSG5LXOS4eyQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Compiling extensions on Windows (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Compiling extensions on Windows
|
| Список | pgsql-hackers |
On Sat, Jan 11, 2014 at 7:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
Magnus Hagander <magnus@hagander.net> writes:
> On Sat, Jan 11, 2014 at 5:00 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:>> I'm not sure I believe this. I don't see any PGDLLEXPORT symbols in anyThat seems like a perfectly reasonable solution, given the way we use
>> 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.
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 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.
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: