Hi Noel,
You missed the MAKEFILES portion of my email.
I haven't tried it, but I'm thinking of something like:
# bootstrap.mk ifeq ($(MAKELEVEL),0) # re-exec make with new MAKEFLAGS endif
It is easy to say "re-exec make with new MAKEFLAGS. How are you going to reliably achieve this if it's not the only code in the makefile? What if I say
make foo.o
I don't understand what the problem is. The "gmake self wrapper" trick deals with whatever target you give gmake.
Also it means that the whole makefile is going to be read before re-execution. This could be unacceptable like in my case. So the only viable solution I can see is by bloating every makefile with
if check
include rexec.make
else
#my code
endif
Are you using recursive make? Have you read http://www.pcug.org.au/~millerp/rmch/recu-make-cons-harm.html?
If, for some reason you're "forced" to use recursive make, why not have:
# bootstrap.mk
ifeq ($(MAKELEVEL),0)
MAKEFILES :=# re-exec make with new MAKEFLAGS endif
then set MAKEFLAGS=bootstrap.mk.
Set where? in environment? No, thank you! ;-)
One idea, from an offline thread, is to have a configuration file similar to CVS's .cvsrc. One thought is to have a global configuration file that can set MAKEFILES.
Of course, this all depends on what sort of project you're supporting.
Noel
_______________________________________________ Help-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/help-make
