Re: narwhal and PGDLLIMPORT
От | Tom Lane |
---|---|
Тема | Re: narwhal and PGDLLIMPORT |
Дата | |
Msg-id | 29597.1391437557@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: narwhal and PGDLLIMPORT (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: narwhal and PGDLLIMPORT
|
Список | pgsql-hackers |
Andres Freund <andres@2ndquadrant.com> writes: > What about the completely crazy thing of simply redefining export to > include the declspec on windows for backend build? That will possibly > blow up the size of the .def files et al a bit, but I have little mercy > with that. You mean "#define extern extern PGDLLIMPORT" ? What will that do to function declarations that have "extern"? Are we sure C compilers are smart enough to not go into an infinite loop on such a macro? Anyway, narwhal's latest results thicken the plot even more. How come pg_buffercache has been building OK on the other Windows critters, when MainLWLockArray lacks PGDLLIMPORT? That lets out the theory about linking to libpq having something to do with it. regards, tom lane
В списке pgsql-hackers по дате отправления: