[M3devel] NT386 problem with C runtime/tools versions
Olaf Wagner
wagner at elegosoft.com
Thu Jul 23 07:55:03 CEST 2009
Quoting Jay K <jay.krell at cornell.edu>:
>
> 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.
Please add these topics in trac to the roadmap for the next release.
Olaf
--
Olaf Wagner -- elego Software Solutions GmbH
Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
More information about the M3devel
mailing list