Since in Visual Studio there isn't a "Configure" command I decided to run configure automaticaly when the .cabal file is newer than .setup-config. The same trick can be used in cabal-setup.
Cheers, Krasimir On 8/21/06, Henning Thielemann <[EMAIL PROTECTED]> wrote:
On Thu, 17 Aug 2006, Duncan Coutts wrote: > On Thu, 2006-08-17 at 14:50 +0100, Neil Mitchell wrote: > > > > First off, being a windows user, having a configure/build separation > > seems a bit unusual. > > It's more for developers I'd say. It means you can configure once and > then build, modify code, build, modify code etc etc without having to > reconfigure each time. It's even worse with generation of library documentation. You have to 'configure', 'build', and 'haddock' before 'install'. _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
