>>> So Cabal is not meant to install executables? >> Sure it does, but suppose you have a user install of such >> c2hs-gtk2hs (instead of a global install) and your PATH doesn't >> include your user 'bin' directory, calling c2hs from a script >> is probably going to call something else. > > Right. Well, in fact, perhaps it is easier if we ship c2hs-gtk2hs as > a library that the Gtk2Hs modules depend on. Then we merely import it > in our Setup.lhs file (...)
That's also a problem. Setup.lhs is going to check if you do have c2hs-gtk2hs available, so, it can't use it itself. I left a question related to that in haskell-cafe, asking if it's possible to have scripts (like Setup.lhs) importing modules outside base libraries. If it is, that c2hs library could be left side by side with Setup.lhs and be interpreted when it's called. If that's not possible, I think everything should fit inside Main. Maurício ------------------------------------------------------------------------------ _______________________________________________ Gtk2hs-devel mailing list Gtk2hs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk2hs-devel
