What's the oldest MS VC version Parrot should built with?

[Ron Blaschke]

Vadim Konovalov wrote:
> 在 Thursday 18 December 2008 22:43:29，Ron Blaschke 写道：
>> Vadim Konovalov wrote:
>>> the more compilers the better, especially if there is already a support
>>> for it dropping it wouldn't be a win.
>> I agree there's some value to variation, but supporting every compiler
>> in every version is not desirable, and most end users don't, and
>> shouldn't, care.  For example, I don't, and shouldn't, care which
>> compiler Firefox, Python or Tcl on my box were compiled with, and I
>> doubt they are all compiled with the same.  I'd be surprised, actually.
> 
> it would be not a desired thing if resulting binary will use more than one 
> CRT. Fortunately it is easy to see what DLLs are needed by binary.

I've probably just been lucky, but I've never had any issue because of
using different CRTs.  If you or anyone else have, please share your
experience, I really would like to hear them!

> But there is another point: one of the widely used compilers on Win32 is GCC 
> in "no-cygwin" mode, which is ordinary GCC in cygwin but it will create 
> binaries dependant on VC6 CRT, AFAIK.
> 
> It would be a pity to lose a possibility to create binary on the same CRT.

MinGW and Cygwin are supported, and if they use the standard (VC6) CRT
that's fine.  I'm not discouraging the use of the library, just the use
of a decade old, no longer maintained compiler.  Actually, if the CRT is
of prime importance, I strongly second Jerry's suggestion of using MinGW.

Ron