Patrik Stridvall <[EMAIL PROTECTED]> writes:
> With mixed mode we link with the Unix C library and hope that the
> clever header tricks will save us. For some application it will,
> for some it won't. At least it is better than nothing.
I don't see why header tricks would be necessary. If you use the Unix
libc you should be able to use the libc includes. The few extensions
like _fullpath can be put in a separate header, and all you do is add
a #include in the app; I don't think we need to setup a heavy include
infrastructure just to ensure that _fullpath is defined in stdlib.h.
And the places where the Wine and Unix headers are really different
(fd_set, wchar_t etc.) are the things you cannot use anyway.
> With Unix mode, we treat WineLib as any Unix library and calls
> to Windows extensions like _fullpath are forbidden.
If you want to treat Winelib as a normal Unix library you need to
recompile it using libc definitions exclusively, to make it
binary-compatible with libc (and of course no longer compatible with
Window binaries).
--
Alexandre Julliard
[EMAIL PROTECTED]
