Re: [xml] python bindings on windows

[Igor Zlatkovic <igor stud fh-frankfurt de>]

Daniel Veillard wrote:
>   to unify the setup.py for both. There is also a nasty problem of
> interdependance of the wrapper modules and the shared libraries, as a
> result it's better to handle both at the same time...

Stephane Bidoul wrote:
> It's for easier packaging. However if libxslt files is not present
> in gnome-xml/python, setup.py will not attempt to create 
> the libxslt binding (I have not tested that very much, though).

Okay, now I see clearer. Setup.py of libxml does not require libxslt, as I 
thought. It just handles both of both are available, at least it is thought 
to work that way. That is okay.

Stephane Bidoul wrote:
> Following the same logic, one could say that libxml2.dll and
> libxslt.dll are separate pieces of software, living more or
> less independently of the python bindings. 
>
> That's why I put the WITHDLLS option in setup.py. 
> If WITHDLLS is true (the default) libxml2.dll,
> libxslt.dll and iconv.dll are put in the same package as the 
> python bindings, so you get a nice standalone package for
> the bindings with all their dependencies. 
>
> However, if WITHDLLS is false, the package for the python bindings
> does not include the libxml dlls nor iconv.dll (just like on unix)
> and the user must install those separately. 
>
> I think that WITHDLLS=1 is not only easier but 
> really safer (it avoids version conflicts),
> but in specific situations, you can still use WITHDLLS=0.

Okay, that does make sense. Thanks for the answer to both of you.

Ciao
Igor