'make languages' or 'cd languages && make' is a shortcut for building
most language implementations
in 'languages'.
When the building one language, e.g. m4, fails, then it is sane that the
remaining languages are still being built.
but what is all this .dummy business?
tcl: tcl.dummy
tcl.dummy:
- $(MAKE_C) tcl
tcl.test:
- $(MAKE_C) tcl test
tcl.clean:
- $(MAKE_C) tcl clean
can't that just be
tcl:
- $(MAKE_C) tcl
etc.
~jerry
Picking a dummy target like this is a way to force the target to
always be built, regardless.
Doesn't make have something called "PHONY" to handle that exact case?
Matt
--
"Computer Science is merely the post-Turing Decline of Formal Systems Theory."
-Stan Kelly-Bootle, The Devil's DP Dictionary
According to
http://www.bell-labs.com/project/nmake/faq/gmake.html
nmake has something similar called .VIRTUAL - someone could abstract
out the makefile-specifics of this, and have the various
makefile.in's automatically generate the best code for the particular
make you're using.
One of the original goals was to replace make with something driven
by miniparrot - If that's still a goal, our energy is probably better
spent doing that than customizing the generated makefiles.
At the moment, however, I'm of the mind: if it ain't broke, don't fix
it.
Regards.
>
> leo's fix (r8695) works just fine on windows :)
IIRC bernhard's and ...
> but what is all this .dummy business?
that is a thing I thought too several times.
leo
Jonathan