Re: Building Text::Iconv on Windows

On Oct 9, 7:16 pm, Michael Piotrowski <m...@xxxxxxxxxxx> wrote:
..
..

Just curious, isn't ActivePerl built wich Visual Studio?

Yes (version 6.0, to be precise) - but to successfully build modules
with the MinGW compiler on ActivePerl merely requires that a number of
%Config values be altered.
ActiveState have now put in place a mechanism (for want of a better
word) that detects the presence of the MinGW compiler, and then alters
those %Config values appropriately. So, for example, although
ActivePerl was built using the 'cl' compiler, if the MinGW compiler is
found, 'perl -V:cc' will then report that cc = `gcc`.

Part of the reason this works out so well is that the MinGW port of
gcc uses the same C runtime as Visual Studio 6.0.


All you really need to do
is attend to the /dev/null issue in the Makefile.PL.

Ok, that's very useful information.

Without going back to check, I think that use of File::Spec->devnull()
would also remove the need for some VMS-specific code (that I think I
saw in the Makefile.PL).

I'm not sure if File::Spec was part of Core with perl 5.6 (and
earlier). You might want to check on that if you're wanting to retain
buildability on older versions of perl (and add File::Spec to
PREREQ_PM if need be ... or just code in your own File::Spec-
devnull() replacement).

Cheers,
Rob

.

Relevant Pages

  • Re: Building Text::Iconv on Windows
    ... word) that detects the presence of the MinGW compiler, ... those %Config values appropriately. ... ActivePerl was built using the 'cl' compiler, ... gcc uses the same C runtime as Visual Studio 6.0. ...
    (comp.lang.perl.modules)
  • Re: CPAN - cl is not recognized as an internal or external command,
    ... to build Perl modules that contain any functions written in C. ... Then, starting with build 817, ActivePerl started working ... seamlessly with the MinGW compiler (though ActivePerl is still built with ... provide the milage you get with ExtUtils::FakeConfig. ...
    (comp.lang.perl.misc)