On Sun, Jan 20, 2008 at 06:21:56PM +0000, Duncan Coutts wrote: > > On Sun, 2008-01-20 at 17:37 +0000, Frederik Eaton wrote: > > Hi Duncan, > > > > Thanks, --gen-pkg-config works. > > > > I don't know if Cabal will ever be suitable for me - I prefer to be > > able to build specific targets, and to track dependencies to minimize > > build time, and there is a tool for this called 'make' which is a lot > > older, faster, and more stable which I prefer to use. > > http://hackage.haskell.org/trac/hackage/ticket/15 > > Yes, make style dependency analysis and incremental builds is the next > major feature we need for Cabal. Lots of other stuff that we want to do > depends on that (like building specific targets with minimal and > parallel rebuilds). It should also make it easier to integrate with > other build systems by adding rules in Setup.hs. > > > Cabal does thesethings well if one is not using too many derived > > files, or too many languages other than Haskell, but those > > restrictions aren't compatible with many of my projects (although for > > some it is fine!). > > So don't despair that it'll never work. Make sure your issues are > recorded so we can see features we can pick off once we have dep > tracking.
OK. Well, for me the best way to do dependency analysis would be to allow users to specify a command which should be run on each source file just *before* cabal/ghc checks its timestamp. In my case, this command would be 'make'. So that way, if one source file is generated from another, 'make' will bring it up to date, and cabal will see that its timestamp has changed... (for efficiency, the command could be given multiple file arguments at once). I've already suggested this for ghc... It seems like it should be a simple change. Frederik _______________________________________________ Glasgow-haskell-bugs mailing list [email protected] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
