Glenn Linderman wrote:
[snipped conversation on the merits of MinGW, VC++ 6.0 and VC++ 7.0 (aka
.net)
I believe there are some library changes and such that cause VC++ 6.0
and 7.0 and .net to require different versions of the libraries... and
since ActiveState is compiled with 6.0 that it is best to compile XS
extensions with 6.0 rather than the newer compilers. Not that it
can't be made to work, I think, but that the footprint of required
libraries is larger. PAR-built applications could balloon in size,
for example, if built with multiple compilers. At least, that I how I
understand it.
OK, there's an article discussing the VC 6/7 issues here:
http://www.perlmonks.org/?node=Free%20MSVC%20tools%20%2B%20Activestate%20to%20compile%20CPAN%20Modules
You need to be able to sort the wheat from the chaff, but I think the
bottom line is that VC7 links against a new msvcr71.dll. As I see it
this will have the following effects:
(1) On a system with the new DLL it will load an extra DLL into memory.
I may then still not work.
(2) On a system without the new DLL it will fail to load.
In either case this is not what we want, and so I think rules out this
route. VC5 might be a possibility if there is a free download for that?
I think this leaves us with either MinGW or VC6 for the release builds.
I'm leaning towards VC6 for the size reasons (there seems to be
suggestions that it is better, as ActiveState use it, but I have yet to
see convincing arguments for this particular reason).
Glenn, when we get to it I assume that you could do the perl 5.8 build.
Do we have anyone with VC++ and perl 5.6 who can do the 5.6 build for
us? If not we might have to go with MinGW for this?
Regards,
Rob.
