Re: Building XML::Parser and expat standalone

..and the resulting Zlib.so (Zlib.dll on Windows) contains the zlib C code ...

There is no c code in there :) What happens is that libzlib is compiled "statically", which is what you need to do with libexpat.

update: You can also copy libexpat.$Config{dlext} to blib/arch/auto/XML/Parser/Expat/ so that it gets installed alongside Expat.$Config{dlext} upon make install. When loading Expat.dll, the OS should look for libexpat.dll there first (auto/XML/Parser/Expat/).

Or you can also put libexpat.dll in $Config{installsitebin}, which works fine for win32, but may not for other platforms.

update: perl -V:obj_ext

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Comment on Re: Building XML::Parser and expat standalone Select or Download Code

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.