10-25-2010, 05:15 PM
(10-23-2010, 05:03 AM)jmeloranta Wrote: ...talking about wx.... has anyone noticed that the latest svn does not build with non-unicode version of wx? (data types char and wxChar are identical and some operator overloadings will fail because of this) It compiles fine with unicode wx.
This is a somewhat serious issue, in that it has no clean fix. When wxWidgets 3.0 is released it will (hopefully) be resolved. Until then, the wxString class has various convenience operator overloads in place that cause problems when combined with other custom-built string types that also have similar operators. Fixing it is possible, but is not pretty.
The blame is partly on the shoulders of the C++ committee for not having a smarter "best match" operator overloading policy, and partly due to Windows using wchar_t and linux using char internally (forcing wxWidgets to be interchangeably accommodating to either string type).
In any case, the unicode build of wx is standard (comes with most linux distros) and recommended. In the meantime I wait for wx 3.0 and its rewritten wxString class, which will apparently be redone in a way that should help solve this very issue.
Jake Stine (Air) - Programmer - PCSX2 Dev Team