Am Mittwoch, 14. Februar 2007 22:21 schrieben Sie: > […] > This looks as though it is a Unicode issue - problems with wxString > usually are. Basically on non-unicode builds the underlying type is a > char * and on Unicode builds it is defined as a suitable pointer for > Unicode strings. Try adding (or removing) --with-unicode from > wxHaskell command line.
Hello, thanks for this. But what do you mean with “wxHaskell command line”? Do you mean the ./configure command line for wxHaskell? Alas, wxHaskell’s configure script doesn’t have an option “--with-unicode”. > running '<path-to>/wx-config --list' will tell you whether you need to > build for Unicode or not. I need to. > Regards > Jeremy Best wishes, Wolfgang ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wxhaskell-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
