Re: msxml3: Determine whether to call xsltInit() or not at run time.

[Michael Karcher]

Am Montag, den 17.11.2008, 15:09 +0100 schrieb Francois Gouget:
> configure will need to be regenerated. I did not include it here since  
> the consensus seems to be that it should not be included.
> Just a nitpick: Same applies for config.h.in, then.
> As a reminder, the issue is that it's not because the libxslt.so we
> compile against has xlstInit() that the one we load at runtime will have
> it too. And vice versa.
> Wait a moment. I don't know about Wine's dl* functions, but can't we use
> dlsym with the RTLD_DEFAULT handle to look in the libxslt msxml3.dll.so
> is linked with anyway? That would do away with the need to know the
> soname during compilation. As it is hardcoded into the executable during
> link, hard-coding the soname doesn't hurt that much too, but still it
> gets simpler

Regards,
  Michael Karcher

msxml3: Determine whether to call xsltInit() or not at run time.

[Francois Gouget]

Michael Karcher wrote:
[...]
> > As a reminder, the issue is that it's not because the libxslt.so we
> > compile against has xlstInit() that the one we load at runtime will have
> > it too. And vice versa.
> > Wait a moment. I don't know about Wine's dl* functions, but can't we use
> > dlsym with the RTLD_DEFAULT handle to look in the libxslt msxml3.dll.so
> > is linked with anyway? That would do away with the need to know the
> > soname during compilation. As it is hardcoded into the executable during
> > link, hard-coding the soname doesn't hurt that much too, but still it
> > gets simpler

I tried that but apparently libxslt does not get loaded with 
RTLD_GLOBAL. So RTLD_DEFAULT did not work :-(
But if I missed something and there really is a way it would be great.

wine_dl*() is a thin wrapper around the dl*() functions. If you ignore 
the last two parameters (used for error reporting), then they behave 
exactly like the standard functions.

-- 
Francois Gouget
fgouget(a)codeweavers.com