<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<br>
Hi, <br>
I am running into troubles compiling WXDialog against a WX compiled as
UNICODE build. <br>
<br>
Using <br>
- CMake CVS from yesterday, <br>
- wx UNICODE build on Linux (because the defalt Suse 10.1 supplied
binary rpms are build with unicode)<br>
- wx non-Unicode "ansi" on Windows makes no problem (compiled
by me),<br>
- wx 2.6.3<br>
<br>
With UNICODE build there are lots of errors regarding conversions
between non-std:.string, char* and wxString, wxChar because of missing
""<br>
<br>
The errors can be solved using <br>
- wx underscore macro, e.g. _("foo") <br>
- explicit wxString contructors, e.g. wxString(std::string.c_str(),
wxConvUTF8)<br>
- explcit Ascii conversion, e.g. wxString.ToAscii()<br>
See <a class="moz-txt-link-freetext"
href="http://www.wxwindows.org/manuals/2.6.3/wx_unicode.html">http://www.wxwindows.org/manuals/2.6.3/wx_unicode.html</a><br>
<br>
I started fixing them, then noticed Mathieu already fixed some of them
and submitted a patch: <br>
<a class="moz-txt-link-freetext"
href="http://public.kitware.com/pipermail/cmake/2005-August/007058.html">http://public.kitware.com/pipermail/cmake/2005-August/007058.html</a><br>
<br>
(1) However, the patch was not applied to CMake CVS, right? Why not?<br>
(2) The patch does not fix all problems in yesterdays cvs - at least
some argv conversions (char** / wxChar**) need a fix.<br>
(3) Has anybody solved the issue and can submit a patch that will be
included in CVS ?<br>
<br>
WXDialog is using the CMakeLib through its char* interfaces.<br>
(4) Will Cmake always use ascii or are there future plans to switch
CMake to UNICODE wchar ? <br>
The explicit wxUTF8 conversion will only work, if Cmake itself is build
as unicode/wchar.<br>
Thus I have a feeling to avoid unicode in CMakeLib interfaces. <br>
<br>
I like WXDialog
more than than MFCDialog/Cursesdialog because <br>
- running the same gui on Windows and Linux is great,<br>
- WXDialog does not jump to beginning of list after deleting a single
cache entry. <br>
<br>
To conclude: <br>
Great work , Jorgen! <br>
We just need 1% more coding to make it useable with Unicode builds
which seem to be default at least on Linux, now.<br>
<br>
Best,<br>
Jan<br>
<pre class="moz-signature" cols="72">--
Dipl.-Ing. Jan Woetzel
--------------------------------------------------
University of Kiel
Institute of Computer Science and Applied Mathematics
Hermann-Rodewald-Str. 3 [room 310]
24098 Kiel/Germany
--------------------------------------------------
Phone +49-431-880-4477
Fax +49-431-880-4054
Mob. +49-179-2937346
--------------------------------------------------
Url <a
class="moz-txt-link-abbreviated"
href="http://www.mip.informatik.uni-kiel.de/%7Ejw">www.mip.informatik.uni-kiel.de/~jw</a>
Email <a
class="moz-txt-link-abbreviated"
href="mailto:jw@mip.informatik.uni-kiel.de">jw@mip.informatik.uni-kiel.de</a>
</pre>
</body>
</html>