Re: [wxhaskell-users] Re: unicode support

[shelarcy <she...@ca...>]

I found where is the problem,

On wxMsc, wx/setup.h define wxUSE_UNICODE=3D0 in default - because
Windows 98 can't use unicode build - so, I should define wxUSE_UNICODE=3D=
1
in project files.

I tried to build with wxUSE_UNICODE=3D1, I found char problem by Visual C=
++
2005 compiler, so I also change wxChar instead of char and wxT("foo")
instead of "", then I can build with Unicode version.

I send Windows patch for your Unicode patch.


Some problem is exist now... but this is not Unicode versions problem.
Because, this problem is also exist on not unicode version.

And I have good news. using this patch's project file, ghc-6.4.1 with
wxWidgets-2.6.2 version can use ghci, too.
(This problem came from, Daan doesn't synch higher wxWidgets-2.5.X's
project file.)


On Fri, 11 Nov 2005 03:58:55 +0900, Eric Y. Kow <Eri...@lo...> wrote=
:
> I see; it's just wxc being named 2.4.2 no matter what wxWidgets it is
> based on.  Also, I hadn't realised that there were .dsw and .dsp files
> in the wxc directory that you had based this on.
>
> Hmm... well, I'll look into it, but without a Windows machine to play
> around with, i'm pretty lost on this one
>
> But just to clarify :
> 1. It compiles fine, but does not link properly?
> 2. Do you have cygwin? Would you be willing to try the cygwin
>    build and see if it's any easier?

Cygwin version has more problems....
http://sourceforge.net/mailarchive/message.php?msg_id=3D11715526

--=20
shelarcy <shelarcy capella.freemail.ne.jp>
http://page.freett.com/shelarcy/