Uwe Bonnes writes:
>Griffiths, Jonathon writes:
>> Hi,
>>
>> I've starting wine hacking as of a week ago, and after looking around the
>> tree, I *think* I trust myself to work on increasing the number of crtdll
>> functions implemented. If there is anyone out there who is working on this
>> DLL please let me know so we don't overlap!
>>
>> I'll try to produce some documentation as well; its a fairly steep learning
>> curve so far :-) My experience is somewhat against me, since most of the
>> coding Ive done on Win32 has been convincing *nix programs to build under it
>> (more on this later wrt some hacks that wont work under wine AFAIK).
>>
>> I've already implemented a few simpler functions and will be testing them
>> shortly. I have a couple of questions though:
>>
>> -The number of implemented functions is quite small - does this mean that
>> most people (including winelib users) are using the M$ version of this DLL?
>>
>> -Does anyone know of a good test suite/app with source for testing crt
>> functions? Or, if I produce a testharness should it be booked in as a
>> sample/tool?
>>
>> -Are there any other issues I should be aware of that leap out at anyone?
>
>Hallo,
>
>my personal believe is that it doesn't make much sense to work more on
>CRTDLL.
>
>Here are some reasons for my believe:
>
>- CRTDLL is hugh with a lot of (unclean and undocumented) entries
>- Native CRTDLL seems abandoned by Microsoft and the MingW people said
>that CRTDLL has problems with threads. Most newer programs use MSVCRT,
>so we would have to implement MSVCRT too
>- Native CRTDLL doesn't implement low level functionality directly but
>uses Kernel for that functionality. So it is save to use native crtdll
>under Wine
>- Native CRTDLL should be distributed with most programs that use it,
>so programs needing it would come with it.
>
>I once started a discussion about that subject on wine-devel, but
>there was no definite outcome.
>
>I vote for switching the default use in wine from "builtin" to
>"native".
>
>PS: Don't let your activity be stopped by my rantings...
>
>Bye
>
>Uwe Bonnes [EMAIL PROTECTED]
>
I feel very much that CRTDLL is needed in Wine. As long as I understand
it is safe to distribute Mingw programs based on CRTDLL (as it is supposed
to exist in any version of Windows) and not so safe to use MSVCRT. So
CRTDLL is very useful for developers who want to have common code base
on Unix and Windows and prefer Unix API. For Windows-less setup
CRTDLL must be part of Wine. One may think that developing Windows
applications on Windows-less machine is a crazy thing, but I feel it
attractive, and gives a lot of oportunities for cross-testing.
It would be nice to have MSVCRT too, but I feel that CRTDLL should
have priority. And implementation of MSVCRT could reuse a lot of
code from CRTDLL -- the C library is standarized.
Waldek Hebisch
[EMAIL PROTECTED] or [EMAIL PROTECTED]
