Okay, but have you ever felt the need to make in the same project a library and an executable which depends on this library (even just like me, for testing purpose)? How would you do it?
Jason Dusek wrote: > > My development environment is a Screen with Bash, Vim and GHCi > running. > > If I can just load the files in GHCi or compile them with GHC > without specifying many options or extensions, then I just do > it that way. As soon as I feel a need to write a Makefile or a > little build script, I write a Cabal file instead and switch > to using `cabal-install'. > > When I say "many" options or extensions, I nearly mean "any". > Most projects of mine get a Cabal file at the point where I > feel the need for the first `LANGUAGE' pragma. (I usually omit > `LANGUAGE' pragmas, delegating to Cabal for that. I'm not sure > whether this is good or bad practice.) > > -- > Jason Dusek > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > > -- View this message in context: http://old.nabble.com/Using-Cabal-during-development-tp27515446p27518960.html Sent from the Haskell - Haskell-Cafe mailing list archive at Nabble.com. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe