[M3devel] NT386 problem with C runtime/tools versions

[Jay K]

I just discovered that..well..if the user has a different version of Visual C++ tools/libraries than the distribution is built with..many scenarios don't work -- e.g. not using build_standalone.
It should have worked better.
Until/unless I work out something better here, I'd suggest we build multiple releases, one for each likely to be used toolset. 8.0/2005 and 9.0/2008 are probably a good mix currently.
 
 
I guess in some ways this isn't surprising, IF any of the Modula-3 libraries traffic in either FILE* (fopen/fread/fwrite/fclose) or "int file" (open/close/read/write), but they might not. Or malloc/free, which they might. We might consider ensuring the untraced heap is via HeapAlloc(GetProcessHeap()) in order to be independent of the C runtime -- in general the C runtime dependencies probably can/should be limited, but this is another topic, another release.
 
 
 - Jay