in reply to Re: Compiling Perl Modules on Windows
in thread Compiling Perl Modules on Windows
Sometimes ActivePerl seems to spot that you've got MinGW on board and adjust things accordingly
I think that, starting with build 815, it should "spot that you've got MinGW on board". For earlier builds (including the 5.6 builds) you'll need ExtUtils::FakeConfig - which actually provides better milage than the automatic procedure that kicks in with build 815 and later.
There's a few bugs in the set up that ActiveState provide (but EU::FC seems to get everything right). For builds 815-819 I think you'll find that 'perl -V:ld' tells you 'ld' is set to 'gcc', whereas it should be set to 'g++'. (It only makes a difference when an attempt is made to compile C++ code.) And, for some reason they left 'lib_ext' set to '.lib' - which can also pose problems. With build 820, they've pretty much got everything right - one exception is that 'perl -V:obj_ext' reports '.obj' instead of the correct '.o'. (To fix, comment out the line obj_ext => '.obj', in Perl/site/lib/Config.pm'.)
Cheers,
Rob