Worked some more on wxhaskell and Unicode. Got help from a bunch of different IRC channels (#wxwidgets, #haskell, #macdev, ##c++, #darwinports, plus a private one).

Thing compiles against the wxWidgets which comes pre-installed on Tiger, but then when you try to run a sample application, you get a symbol not found error. Somebody on an IRC channel suggested it was a weird C++ thingy. In fact, they said that a likely cause is a gcc version mismatch. Get this: Apple compiled all their Tiger stuff with gcc 3.3, and yet they give their users gcc 4.0 to use.

Fine, so I thought then that compiling against the darwinports wxWidgets would help (same gcc, right), but now I get something even weirder, something about "weak definitions". Argh.

Following link may turn out to be useful: Executing Mach-O Files.

Other things to try: see if wxhaskell binaries work on Tiger (this way, you at least have something which works, even if no unicode). This is so not what I need to be working on.

what's all this

A work blog. Updated daily (?). Something for me to keep track of my PhD thesis as it slowly advances.

Hacking on wxhaskell C++ code (well, wxc stuff rather, probably from wxEiffel) - trying to get the Unicode stuff working. Mostly consists of converting char to wchar_t, and strcpy to wxStrcpy (and so forth). Some tricky issues to work out. Likely not the most important stuff to be doing now.