cvs commit: src/share/mk bsd.obj.mk

[Brian F. Feldman]

Ruslan Ermilov <ru at FreeBSD.org> wrote:
> : $ make MAKE='/usr/bin/make -DFOO' print-make
> : /usr/bin/make -DFOO
> : $ make MAKE='/usr/bin/make -DFOO' -V MAKE
> : make
> 
> If you really need to access command-line arguments, there
> is the .MAKEFLAGS variable available for that purpose.
> 
> But why do you need to ``make MAKE='/usr/bin/make -DFOO' bar''
> in the first place instead of simple ``make -DFOO bar''?  If
> "bar" is recursive (i.e., runs ${MAKE} subprocesses), then
> -DFOO will be properly propagated:

Think about this: what options to ${MAKE} are there that have nothing to do 
with setting defines?  There's actually quite a few; the one in particular 
that I care about is "-f"; if I want to use bsd.subdir.mk to simply apply 
one BSD Makefile to several directions (which I _do_), I need to use -f, 
i.e.:

MAKE+=  -f ${.CURDIR}/drivers/Makefile.subdriver

The only think that broke this was the cleandir target.

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green at FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\