claus.reinke at talk21.com
Tue Jun 24 09:14:50 EDT 2008
> We discussed this on IRC recently, and the options we came up with were:
#ghc? are there logs for this channel, similar to http://tunes.org/~nef/logs/haskell/ ?
> * Simon's ghc-paths package
> Pro: With dynamic libraries, you can move a binary to a different
> machine (with GHC in a different place) and it will work
> Con: Needing to compile it on installation
a slight variation would be to have Setup.hs write the paths to
a ghc-paths data-file, from which GHC.Paths could read them
(no dynamic linking required: on updating the package, old
linked versions would read the new data-file). but i can't seem
to get Cabal data-files to work (symbol not found errors, iirc).
the other options seem less attractive somehow.
note that Cabal already does similar things with Paths_pkg.hs
for each package. and it would be nice if all that known tool
configuration stuff could be moved out of Cabal into a known
More information about the Cvs-libraries