Re: [wxhaskell-users] Re: unicode support

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

Hi there,

To be honest, I have no idea how things work on Windows, so bear with me
:-) =20

I assume you are following the instructions on this page:
  http://wxhaskell.sourceforge.net/building-msc.html

You seem to be including wxWidgets 2.6.2 headers but linking against
2.4.2 library.  Is this the case, or am I misreading things?

Anyone else have ideas?

Thanks for trying it out!

--eric

On Thu, Nov 10, 2005 at 02:59:56 +0900, shelarcy wrote:
> VC reports this error:
>=20
> 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
> and reports also unresolved external symbol. I think these come
> from wxString::String's error.
>=20
> eljwindow.obj : error LNK2001: unresolved external symbol "char const *
> const wxEmptyString" (?wxEmptyString@@3PBDB)

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