From your doc:
MAKE ... Defaults to $Config{make}.
It should default to not being changed, so as to allow the user to choose
which make he wants to use. Essentially you preclude Perl's own
makepp.sourceforge.net from building subdirectories configured by MakeMaker :-(
There may be special cases where a subdirectory needs to be built by some
special variant of make, so it might make sence to provide a way of specifying
that. But in over 99% of cases the same make tool should build everything,
and it should be the one the user started! Please don't interfere with this
established practice!
You do have the undocumented feature of taking MAKE from the environment, if
present. This is however not a solution, because (recursive make being an
inherently faulty paradigm, search on the web for "recursive make considered
harmful") makepp has some magic in $(MAKE) to feed the targets back to the
main process, which has the complete view of dependencies. (This is a
workaround for legacy builds, if you write makefiles for makepp, they can be
much simpler and cleaner.)
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
--
lerne / learn / apprends / lär dig / ucz się Esperanto:
http://lernu.net / http://ikurso.net
