Hi, from the proposal it sounds like you are planning to only extend the single-shot mode with the new options, is that right?
I think `ghc --make` could also benefit from being able to communicate non-module graph dependencies such as `addDependentFile` and CPP #include to build-tools, no? I've always been annoyed by the fact that if such dependencies change cabal will not consider rebuilding. --Daniel On Tue, Jul 30, 2019 at 06:58:29PM +0100, David Eichmann wrote: > Hello GHC Developers, > > > I've recently been working on a proposal (found here > <https://github.com/ghc-proposals/ghc-proposals/pull/245>[1]) for "Extended > Dependency Generation". This new feature takes the form of a new build > option/mode that outputs comprehensive build dependencies for building > Haskell modules. This allows external build tools, such as cabal-install, to > implement correct incremental builds with recompilation avoidance using > GHC's one shot mode to compile individual modules. > > All input is appreciated. It would be particularly helpful to hear from the > Cabal, Stack, and Shake communities. > > > Looking forward to hearing your comments, > > David Eichmann > > > [1] https://github.com/ghc-proposals/ghc-proposals/pull/245 > > -- > David Eichmann, Haskell Consultant > Well-Typed LLP, http://www.well-typed.com > > Registered in England & Wales, OC335890 > 118 Wymering Mansions, Wymering Road, London W9 2NF, England > > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
