Ok now with clean w32api headers from CVS we can build unicode. This shouldnt break cross compiling or the *nix build but if it does please let me know. Also you can change WINVER >= 0x0500 to whatever as long as it is higher.
Thanks Steven
Changelog: Fix building libwine_unicode with w32api headers.
Index: Makefile.in =================================================================== RCS file: /home/wine/wine/libs/unicode/Makefile.in,v retrieving revision 1.5 diff -u -r1.5 Makefile.in --- Makefile.in 27 Jun 2003 19:02:23 -0000 1.5 +++ Makefile.in 20 Aug 2003 06:13:25 -0000 @@ -4,7 +4,7 @@ VPATH = @srcdir@ LIBRARY = wine_unicode SOVERSION = 1 -EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT +EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT -DWINVER=0x0500
CODEPAGES = \ 037 \
Index: unicode.h =================================================================== RCS file: /home/wine/wine/include/wine/unicode.h,v retrieving revision 1.20 diff -u -r1.20 unicode.h --- unicode.h 27 Jun 2003 19:02:23 -0000 1.20 +++ unicode.h 20 Aug 2003 07:36:07 -0000 @@ -24,6 +24,7 @@ #include <stdarg.h>
#include "windef.h" +#include "winbase.h" #include "winnls.h"
/* code page info common to SBCS and DBCS */
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
Steven Edwards steven_ed4153@yahoo.com writes:
Ok now with clean w32api headers from CVS we can build unicode. This shouldnt break cross compiling or the *nix build but if it does please let me know. Also you can change WINVER >= 0x0500 to whatever as long as it is higher.
It seems to me the w32api headers should define WINVER to the higher version that is supported, defining it in the app should only be necessary if you want compatibility with older versions IMO.
--- Alexandre Julliard julliard@winehq.org wrote:
It seems to me the w32api headers should define WINVER to the higher version that is supported, defining it in the app should only be necessary if you want compatibility with older versions IMO.
The default is currnetly WINVER=0x0400. I guess the thinking is they by default support the lowest common features and if needed the developer can support more. Danny will you accept a patch to up the version number? If not then we may just need to add a case to configure to define WINVER to be higher when targeting WINE for Mingw.
Thanks Steven
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
-
Alexandre Julliard -
Steven Edwards