Re: [wxhaskell-users] Re: unicode support

[Eric Y. K. <Eri...@lo...>]

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 :=20
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?

On Fri, Nov 11, 2005 at 01:46:41 +0900, shelarcy wrote:
> Building with msc (VC) require wxc-msw2.4.2-0.9.4 library now, so
> VC generate wxc-msw2.4.2-0.9.4 library by all version.
>=20
> See VC project files - VC project files are plain text.
>=20
>=20
> >On Thu, Nov 10, 2005 at 02:59:56 +0900, shelarcy wrote:
> >>VC reports this error:
> >>
> >>Linking...
> >>wxmswu.lib(string.obj) : error LNK2005: "public: __thiscall
> >>wxString::wxString(char const *,class wxMBConv &,unsigned int)"
> >>(??0wxString@@QAE@PBDAAVwxMBConv@@I@Z) already defined in apppath.obj
> >>    Creating library .\..\out\wxc/wxc-msw2.4.2-0.9.4.lib and object
> >>.\..\out\wxc/wxc-msw2.4.2-0.9.4.exp

--=20
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon fran=E7ais.