On Sun, Sep 16, 2007 at 10:55:43AM +0200, Sven Panne wrote: > On Sunday 16 September 2007 04:42, Ian Lynagh wrote: > > At the interface to the outside world (i.e. the configure flags) they > > have the normal semantics. We then append "/ghc-$(ProjectVersion)" to > > the internal build system variables. This seems reasonable to me - I > > don't think it would be better to put the "/ghc-$(ProjectVersion)" in > > manually everywhere we use it, if that's what you're suggesting? > > Alas, we do not have the usual interface to the outside world, because the > Makefile variables have a different meaning, e.g. "make libdir=/foo" means > something different in our project than in the rest of the GNU world.
Ah, you are right, the GNU standards talk about both Makefile variables and configure flags. How odd. ghclibdir might be a better name than topdir, as we'll also want names for datadir, docdir etc. > makes this situation even worse is that other tools we use (like Cabal) > expect the GNU meaning, so we have to convert back and forth, with no good > reason for this complexity. Well, when telling Cabal where to install we want to tell it that its "libdir" is $topdir/lib anyway, so we don't really convert back. Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
