Re: libsoup on MS Windows problems

[Tor Lillqvist <tml iki fi>]

> pexport libsoup-2.4-1.dll
> shows *no* sign of functions including soup_*

Does it show anything at all? If it shows at least something, that
might then give a hint what has gone wrong... The heuristics that the
GNU linker uses to decide what to export from a DLL usually work out
fine, but occasionally not. The rule is that if there are no
explicitly marked symbols (functions or variables) to export, it
exports all global symbols. So it might be that you inadvertedly link
libsoup with some other library that has been compiled statically by
mistake, but still marks its functions as "exported". Or something...

> nm libsoup-2.4-1.dll shows a lot of functions including _soup_*

yeah but running nm against a dll is misleading, it looks at the wrong
kind of symbols... pexports tells you what actually is exported. And
running nm against the import library (called lib*.dll.a, typically,
especially for libtool-produced import libraries) then tells you that
the "import stubs" for the exported symbols are present in the import
library.

> From the above it seems that -DDLL_EXPORT is given.

That however is not that relevant, DLL_EXPORT it is typically not
something that would have any effect on what gets exported.

Could you show us the verbose link command line?

--tml