Re: [wxhaskell-users] Re: unicode support

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

On Thu, 10 Nov 2005 21:49:48 +0900, Eric Y. Kow <Eri...@lo...> wrote=
:
> 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?

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.

See VC project files - VC project files are plain text.


> 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
>>
>> and reports also unresolved external symbol. I think these come
>> from wxString::String's error.
>>
>> eljwindow.obj : error LNK2001: unresolved external symbol "char const =
*
>> const wxEmptyString" (?wxEmptyString@@3PBDB)
>



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