[wxhaskell-devel] recent work

[Brian L. <br...@lo...>]

Hi, I did some work lately on the wxHaskell build process because I was
unhappy it wouldn't install via cabal without messing with the global
package conf.

The repositories I made are here:
http://github.com/bsl/wxdirect/tree/master
http://github.com/bsl/wxcore/tree/master

wxdirect is just lightly modified stuff from the wxHaskell darcs repo. I
did some minor cleanup and added an empty library module
Application.Wxdirect so it's easier to depend on.

wxcore is wxcore and wxc combined. I did away with 'configure' and
'makefile', so now it is just a build-type: Custom package. It builds
and installs OK via cabal for me in Linux, and the demo programs in
samples/wx work for me, but I'm sure it still has problems, and may not
build on Mac OS X or Windows.

Please take a look and let me know what's wrong and/or add to the
Setup.hs so it works on your platform. It would be cool if all the
wxHaskell packages were just more normal packages on HDB.

Here are some other issues I was thinking about:

To get *.cpp to compile, I had to add a few wxString::FromAscii calls to
wxStringify some char*s. I think this is due to some effort in wxGTK to
support unicode. My changes made the types match up and stuff, but I
felt really unsure about whether it was the correct thing to do. It
feels as if maybe *.cpp thinks the data coming from a Haskell String is
ASCII, which I think would be wrong.

I also get some function deprecation warnings during the build. I don't
know how much that is hurting stuff, but it would probably be good to
fix.

It'd probably be good to get the Haskell sources as -Wall and hlint
clean as is reasonable, and check *.cpp with -W -Wall, etc.