> I'm not sure. large parts of wxcore are generated by running wxdirect > over the wxc headers. I couldn't find a way to make cabal handle this > dependency without moving to the Makefile buildtype.
Well, what I was hoping in my idealised vision of wxc separation was that we could ship wxcore with all the auto-generated parts, leaving the user with only Haskell modules to build. The requirements then would be for the user to have installed wxc already, much in the same way that we already require that they install wxWidgets. [My one worry is how to make it so that when people use the wxcore package, the necessary wxc stuff is linked in, but I'm guessing Cabal has a mechanism for this] For this to work, I'm guessing that your proposal for increased modularity (wx-contribs/) would need to be implemented, so that we can just distribute a bog-standard wxcore, and let people do their own wxdirect on whatever extra modules they want. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
