On Jul 6, 2007, at 10:14 AM, Simon Marlow wrote:
Peter Tanski wrote:
I'm suggesting that instead of defining them in a .mk file and
plumbing them into GHC, that you just define in GHC somewhere
clOmitFramPointer = "-Oy"
the definitions would still all be in one place (definitely a good
thing), and they still have nice names so you can tell what they
mean. Why do they need to be in a .mk file?
Mostly because I wanted them in Make as well, for easy configuration
changes: if I run into a problem (as I often do), I can dumb-down the
ghc-command line and add a few choice -optc's to debug things, all
without having to recompile stage 1. Partly because I was loth to
add another Haskell file, especially when Config.hs, though
generated, was already in place and included by every module I wanted
the variables in. I guess I could hard-code them into
StaticFlags.hs. Eventually I wanted to be able to work with the
tools dynamically, in a "tools" package, but I have to finish the
build first.
Cheers,
Pete
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
