Dynamic libraries by default and GHC 7.8
cdsmith at gmail.com
Wed Dec 5 06:03:06 CET 2012
I'm curious how much of the "compile twice" situation for static and
dynamic libraries could actually be shared. Even if it's not likely to be
implemented in the next year or two, IMO it would make a big difference if
it were feasible to generate both static and dynamic libraries at the same
time and share some large percent of the compile time.
It seems to me that making GHCi always dynamic but GHC static by default,
with the default being for Cabal to build both static and dynamic
libraries, is the right answer. After all, static binaries are the right
answer for binaries on everything but a few resource-limited mobile
platforms anyway. Doubling the compile times is harsh, but I think it's
particularly justifiable if it were something that eventually, if it annoys
someone enough, they will pound out the code to fix it.
Or... how hard would it be to make GHCi fall back to interpreting modules
from any packages that don't have dynamic libraries?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Glasgow-haskell-users