Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Hi, quick question: someone mentioned to me today that compiling the perl interpreter on win32 (perl.exe) was "better" using VC++ rather than mingw.

It was an unqualified statement, but it got me thinking, why is that (or is it even accurate)??

I can't find any resources on this - not that it's vital, but it has an impact if you want to compile modules, you don't have vc++, and you do have mingw (need to compile modules using the same compiler you used to compile perl). I know there's a way around this using ExtUtils::FakeConfig, but why bother if mingw works just fine for the original perl compile as well??

I think I read ActiveState uses VC++, but beyond that, haven't come across anything...

  • Comment on Compiling perl (interpreter) on win32 - mingw vs. VC++

Replies are listed 'Best First'.
Re: Compiling perl (interpreter) on win32 - mingw vs. VC++
by chromatic (Archbishop) on Oct 23, 2002 at 23:36 UTC

    Maybe it's not "better", but of the people compiling Perl on Windows these days, there are more reports from Visual Studio users than mingw users. For what it's worth, I'd prefer Cygwin, if I had to use Windows. :)