Re: finding the dependecies of cabal packages

Visual Haskell works quite well with hooks. We are already using hooks
in order to build Visual Haskell itself. In Visual C++ projects you
can specify a sequence of shell commands which can be executed at
specified point in the build process. In Visual Haskell you can use
Cabal hooks to perform the same actions but the hooks approach is more
flexible.
The only limitation of Visual Haskell is that it can work only with
the simple build architecture. It can be extended with the makefile
based system but the drawback will be that we will lose the project
editing features, interactive type checking and all other advanced
features. The situation is the same with the Makefile based Visual C++
projects. Visual C++ provides only basic support for Makefiles.

Cheers,
  Krasimir

On 8/1/05, Simon Marlow <simonmar <at> microsoft.com> wrote:
> On 29 July 2005 21:18, Duncan Coutts wrote:
> 
> > However an IDE wants even more. It wants to be able to rebuild
> > individual files quickly (so dependency tracking is required and
> > linear build scripts are out). It will want to provide a GUI
> > interface for changing build system parameters (which means that the
> > build system has to be declarative, not scripted). And no doubt there
> > are other things too.
> >
> > The point is that fulfilling these requirements might be possible for
> > some imagined future version of the "simple" build system, however if
> > the Cabal interface is extended to stipulate these same features then
> > it would exclude most other build system implementations.
> 
> My feeling is that the requirements for incremental building should be
> part of the simple build system.
> 
> It's not quite true now, because we allow arbitrary hooks into the
> simple build system.  So tools like Visual Haskell only work properly if
> you don't use hooks.  This is one reason why being more explicit about
> whether a package uses hooks or not would be useful.
> 
> Cheers,
>        Simon
> _______________________________________________
> Libraries mailing list
> Libraries <at> haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>