Linking hsc2hs .c output on Windows w/ build system: is it
just me..?
Duncan Coutts
duncan.coutts at worc.ox.ac.uk
Fri Apr 24 20:07:12 EDT 2009
On Fri, 2009-04-24 at 15:04 -0700, Sigbjorn Finne wrote:
> There's a couple of things that are odd here:
>
> * base.cabal files have kernel32 and msvcrt as extra-libraries. This
> is clearly not required when doing invocations via ld(1), and causes
> considerable mischief, so it'd be good if there was a way in .cabal
> files to distinguish between stuff that goes into 'extraLibraries' and
> 'extraGHCiLibraries' in package.conf's InstalledPackageInfos. (Is
> there? Couldn't locate anything appropriate while working with the
> Cabal sources..)
Right, extraGHCiLibraries is a hack that Cabal doesn't know anything
about (and if possible I'd prefer to keep it that way).
> * 'base' needing to include these two dependencies even for GHCi
> usage. A running RTS will have these loaded already, so it really
> ought to have primed the list of opened DLLs by explicitly loading
> them upon initialization of the linker.
> [I've got a trivial patch against rts/Linker.c that does this; can
> forward/commit if of interest..]
If that means we can avoid infecting Cabal with knowledge of the
extraGHCiLibraries field then you've got my vote! :-)
Duncan
More information about the Glasgow-haskell-bugs
mailing list