Tommy Thorn writes:
> I use a lot of Makefiles, but why must we use ugly tools with beatiful
> languages? They are especially bad for a novice, just trying to gain
> a little more speed on his Hugs program.
I agree, which is why I adapted 'hbcmake' and 'nhcmake' to come up with
'hmake' - a compiler-independent tool for import-chasing. (Credit for
the original tools belongs to Thomas Hallgren.) It is currently
available as part of the nhc13 distribution, and has been verified to
work with both nhc13 and hbc. I have yet to ensure that it works
completely with ghc, but when I do so, I'll make it available
separately as a stand-alone tool.
> What I'd really like to do is just: ``ghc Main.hs'', and obtain a Main
> executable. For the more advance user (using Green-Card, Happy, and
> whatnot) there should always be the brainless "C-style" way.
'hmake Main' compiles and links everything necessary to obtain a Main
executable. 'hmake Module.hs' compiles everything that Module.o
depends on, but omits the link. 'hmake Main cfile.o' links the extra
object file into the final executable. It is all pretty straightforward.
'hmake' copes with GreenCard transparently, and calls the C
pre-processor when required. However it does not know about Happy
sources.
Again, let me point out that I haven't checked whether 'hmake' works
fully and correctly with ghc, but you are welcome to try it out.
Regards,
Malcolm
------------------------------------------------ [EMAIL PROTECTED]
Dr Malcolm Wallace (functional programming research) +44 1904 434756
Department of Computer Science, University of York, YORK YO1 5DD, U.K.
----------------------------------- http://www.cs.york.ac.uk/~malcolm/
