2.9.0 timeline ?

[Tim Stahlhut]

Vadim Zeitlin wrote:

> On Mon, 12 Nov 2007 10:37:00 +0100 Vaclav Slavik <vslavik at fastmail.fm> wrote:
>
> VS> Or elsewhere for that matter... But yes, doing it for projects files 
> VS> sounds like a good first step.
>
>  What exactly needs to be done elsewhere? For configure based build,
> --enable-unicode is the default now so there doesn't seem to be anything to
> do. For MSW makefiles UNICODE is 1 by default too AFAICS so, again, I'm not
> sure what else needs to be done? The project files are really a special
> case as we can't select the default configuration in them so it seems
> better to just keep only the Unicode build. It will also be a good test for
> compatibility with the existing 2.8 code: if we don't get many complaints
> about not being able to build in ANSI using the MSVC project files, it
> probably means that the compatibility is good enough to drop the ANSI build
> entirely...
>

Might want to change setup.h till you remove the use of wxUSE_UNICODE.

Tim S

Index: include/wx/setup_inc.h
===================================================================
--- include/wx/setup_inc.h	(revision 49858)
+++ include/wx/setup_inc.h	(working copy)
@@ -155,7 +155,7 @@
 //
 // Recommended setting: 1
 #ifndef wxUSE_UNICODE
-    #define wxUSE_UNICODE 0
+    #define wxUSE_UNICODE 1
 #endif
 
 // Setting wxUSE_WCHAR_T to 1 gives you some degree of Unicode support without