msvcrt vs std incl
Dimitrie O. Paun
dpaun at rogers.com
Tue Nov 19 12:05:57 CST 2002
On November 19, 2002 12:55 pm, Greg Turner wrote:
> The wine headers are very interesting to me right now. I guess we need
> to do something like
>
> #if (some hairy condition)
> typedef WCHAR wchar_t
> #endif
>
> in the appropriate place (I guess, stddef.h)?
Here's what I did:
Index: include/msvcrt/stddef.h
===================================================================
RCS file: /var/cvs/wine/include/msvcrt/stddef.h,v
retrieving revision 1.4
diff -u -r1.4 stddef.h
--- include/msvcrt/stddef.h 10 Mar 2002 00:02:38 -0000 1.4
+++ include/msvcrt/stddef.h 19 Nov 2002 17:09:20 -0000
@@ -32,6 +32,9 @@
#endif
/* Best to leave this one alone: wchar_t */
+#ifdef WINE_DEFINE_WCHAR_T
+typedef short unsigned int wchar_t;
+#endif
#define offsetof(s,m) (size_t)&(((s*)NULL)->m)
> It would be helpful to me (not just for this problem, which I don't
> intend to try and solve) to get a clear picture of all usage scenarios
> that the wine headers are supposed to support... Obviously there are
>
> o compile wine under unix-like platforms, excluding cygwin
> o compile a c winelib app for unix-like platforms, excluding cygwin
>
> but what else? in particular, should we worry about any of these?
>
> o compile wine for cygwin
> o compile winelib app under cygwin
> o compile wine under msvc
> o compile winelib app under msvc
> o be a replacement for a standard unix header (native compile)
> o be a replacement for an msvc header (native compile)
> o something else I didn't think of
> o c++ support combined with any of the above
Why not? All of the above should work in theory, no?
--
Dimi.
More information about the wine-devel
mailing list