Peter Tanski wrote:
On Jul 6, 2007, at 3:57 AM, Simon Marlow wrote:
Personally I'd do away with msvc_tools.mk and put it all into GHC.
You'd still have it all in one place, but there'd be much less
plumbing. Is there a reason you can't do that?
No reason I can't; I just don't want to. With all these variables
gathered together in one place it becomes trivial to review them there
and change them in both the Make and GHC worlds and it is better to
coordinate the two. It is also easier for someone who does not know CL
options to look at, say clOmitFramePointer in GHC and know what it means
instead of having to go and look up what the string "-Oy" means.
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?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
