Griffiths, Jonathon writes:
> Hi Uwe,
>
> After reading all the posts on this I think I will continue working on this
> dll with a view to eventually starting a msvcrt effort as well (although
> this will be a very big job). I agree that "native" should currently be
> preferred over "builtin" though - the current implementation is largely
> stubs and the native version works fine AFAIK.
>
> My reasoning is:
> -Every win installation from 3.1 to 2k includes it. So its reasonable to
> assume applications still depend on it.
> -About Wine @ winehq states it will be an "alternative implementation
> consisting of 100% Microsoft-free code". IMHO this means anything that comes
> with the o/s is an o/s service and should be provided. I'm not sure about
> the legalities of releasing software including this file either.
> -Non-ix86 winelib apps need a local crt to build against (although msvcrt
> would be the real solution).
> -cygwin looks like it provides a good testbed to test the functionality.
> -I feel a bit lost around the non-dll parts of the tree, and I really don't
> want to break anything for anyone else ;-)
>
> I'm a bit confused at present about winelib programs and the libc they use,
> so I may come back with questions in the near future.
>
> In any case, it will be a while before I'm ready to post any patches; I want
> to test quite thoroughly the different behaviours under Windows and Linux.
>
> >PS: Don't let your activity be stopped by my rantings...
>
> OK :-)
> Thanks a lot for your input (and everyone else who wrote).
>
Your reasoning sounds fine.
Some more things:
My Visual Studio 6 installation comes with a tree
"Microsoft Visual Studio/VC98/CRT" and containing a directory
"SRC". It is on the same directory level then MFC. It seems it should
builds to MSVC40 and/or? MSVCP60.
I remember that the sources to CRTDLL where on some older Microsoft C
Compiler disk.
How should we cope with those things? Should we try to winelib-
compiles those sources like people did for MFC ( and perhaps
distribute either the winelib complide lib or the patches to make the
whole thing winelib-compile). Or can we look at the
code and get inspiration for our own implementation? How can I get the
licence again for VS6? Anybody with deeper knowledge and understanding
about the license?
Bye
Uwe Bonnes [EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
