Building Gtk2Hs on Windows is very straightforward. After Gtk+ is included in the path, cabal install gtk2hs-buildtools will install all the executables needed for building the bindings, but no libraries. cabal install gtk will then install the library.
OTOH, cabal install wxdirect installs both the helper executable and a library. 3 other packages then have to be installed, at least one of which requires environment variables pointing to bits of earlier packages. One upshot of all this is that it's well nigh impossible to use wxhaskell with cabal-dev, whereas with gtk2hs it's really easy (install gtk2hs-buildtools outside the sandbox, then gtk will use it in the sandbox). ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
