The basic issue issue is that it is highly advantageous to link with MSVCRT.dll because that .dll is integral to Windows and will already be on every Windows system. The clib is very dependent upon this particular.dll (malloc,stdio, etc).
in reply to Re^3: Packaging Perl Programs (is) Painful
in thread Packaging Perl Programs (is) Painful
AS uses VC6 and nmake for their builds because it links with MSVCRT.dll. If you were to build with say Visual Studio 2008, then that compiler will by default link with MSVCR90.dll a compiler specific library and not with MSVCRT.dll. And therefore you will have to distribute the compiler specific library with the compiled result.
As it turns out mingw(gcc) will link with MSVCRT.dll. So for inquiring minds out there, that's why these 2 compilers are recommended.
More info on AS site re: compilers and some 64 bit weirdness, one link: AS compilers for Perl modules.
So far, I've never had to build a module for Windows as I've been able to find what I need on one of the .ppd repositories. I highly recommend NOT re-inventing the wheel. If a module is available as a .ppd, install it with ppm. Its also faster than "roll your own". Note that although not all of CPAN, there are 13K+ modules at AS's repository. That covers a lot of ground!