🚀 go-pugleaf

In article <4q4kd5$cm3@Starbase.NeoSoft.COM>, I responded to
Ronan Viel  <viel@efp.poznan.pl>'s article
<31BEEDDD.41C6@efp.poznan.pl>, in which he asked:
>>I'm looking for a Make (GNU) documentation. I had a doc called
			.
			.
			.
><URL:http://www.rz.go.dlr.de:8081/pdinfo_dv/gnumake.html>
			.
			.
			.
While we're on the subject, I have a couple of usage questions,
one of which I'll offer now.  Is there a way to parametrize de-
pendencies?  Here's an example of what I mean:

	# This is a GNUmakefile for that classic
	#     situation in which one wants to main-
	#     tain multiple objects derived from a
	#     single source base

	# Lots of other set-up might be here ...

	both:
		gnumake -f make_single_executable \
			OPTION="" OBJ=for_real \
			EXECUTABLE=application
		gnumake -f make_single_executable \
			OPTION="-DTEST" OBJ=test \
			EXECUTABLE=test_application
	============================================
	# This is make_single_executable.

	OBJECTS = $(OBJ)/module1.o \
			$(OBJ)/module2.o \
			$(OBJ)/module3.o

	$(OBJ)/%.o:  %.c
		cc $(OPTION) $*.c -o $(OBJ)/$*.o

	$(EXECUTABLE):  $(OBJECTS)
		cc -o $(EXECUTABLE) $(OBJECTS)

Is there a way to "single-source" that efficiently, so that
"recursion" of makefiles is not necessary?

I've trimmed follow-ups a bit.
-- 

Cameron Laird           http://starbase.neosoft.com/~claird/home.html
claird@NeoSoft.com      +1 713 623 8000 #227
                        +1 713 996 8546 FAX