Blair Archibald writes:
> The logical first step seems to be to combine the 3 packages (wxcore, wx,
wxc) into some form of singly installed package. I'm a novice when it comes
to cabal so not sure how what the effects of such a change could be.
> I appreciate that cabal is a great system for inst
Simpler would be fantastic, but there are technical reasons for the current
setup. If you can meet the same goals whilst delivering an easier install
experience (or boldly cut off goals that can be better understood as
wrongheaded), more power to ya!
* wxc - C++ to C wrapper. Uses make (or can
I agree that the current deployment system for wxHaskell is not ideal and
we should probably look into changing it. Does anyone have any ideas as to
how we could go about this?
The logical first step seems to be to combine the 3 packages (wxcore, wx,
wxc) into some form of singly installed package
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 t
