Hi, Am Sonntag, den 09.02.2014, 14:37 -0600 schrieb Austin Seipp: > There is one caveat, if I remember correctly: if a package uses > TemplateHaskell, it must declare it as such in the Cabal file. This is > because Cabal does not parse the source to detect if TemplateHaskell > is needed in the dependency graph of the compiled modules. Only GHC > can do this reliably. If you don't specify TemplateHaskell as an > extension, Cabal might not do the right thing. This is noted in the > release notes: > > > Note that Cabal will correctly handle -dynamic-too for you automatically, > > especially when -XTemplateHaskell is needed - but you *must* tell Cabal you > > are using the TemplateHaskell extension.
we need -dynamic-too also for everything that a user ever might want to load in GHCi, right? So doesn’t that already imply that Cabal should and will build libHS*so files always anyways? Greetings, Joachim -- Joachim “nomeata” Breitner m...@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nome...@joachim-breitner.de • GPG-Key: 0x4743206C Debian Developer: nome...@debian.org
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
