cvs commit: fptools/libraries/Cabal/Distribution/Simple Build.hs

[Isaac Jones]

"Simon Marlow" <simonmar at microsoft.com> writes:

> No objections, but I think a better way would be to build the package
> first, install it into a local package.conf and then build the
> executables against the package.  

This is a little tricky for a few reasons... the library might depend
on post-install scripts to work, or may not work in-place at all; it
may require that it's installed at the configured location.

We also will need to build the temporary package.conf file and cause
the build step to use that as well as the localPackageConfig file. And
all this should only happen if the executable has a build-depend on
the library itself...  None of this is TOO hard, but it has a lot of
moving parts.

For now, I just added a (possibly controversial) patch that allows the
executables to peak into the library's hs-source-dir for modules while
building and preprocessing.  It wasn't actually possible before to
build an executable that depended on a library that had its own
hs-source-dir separate from the executable's hs-source-dir.

peace,

  isaac