🚀 go-pugleaf

I asked how to use make files & tlink together.

In article <1992Sep5.012643.27171@midway.uchicago.edu> pynq@midway.uchicago.edu writes:
>In article <1992Sep4.224643.3520@rei.com> fox@rei.com (Fuzzy Fox) writes:

>>>prog.exe: $(OBJECTS)
>>>    tlink \bc\t0s.obj $(OBJECTS), progname, , ...
>>
>>>worked until the command line overflowed.
>>
>>A work-around:  Create a library and have each source file inserts its
>>object file into the library as part of its build action.  Have the exe
>>file depend on the object files, but have it link from the library.
>>Don't let the library get out of sync with the objects.
>
>Ewww...
>
>Better idea: Get NDMAKE.  It will automatically build response files in
>this kind of situation.

Another reader mailed me a lead that worked out.  There is a 
directive (or whatever you call it) for make named &&.  I was
able to do

prog: $(OBJECTS)
	tlink @&&!
$(OBJECTS)
!, progname.exe, mapname.exe, libs

Or whatever.  I'm not at my pc now.  It works.  It creates a 
tempfile containing the expansion of (OBJECTS) and supplies
that tempfile name to tlink as the response file.

There was another option documented on the same page, <<, that
did something similar, but I couldn't think of a use for it.
I've heard other recommendations for NDMAKE.  But it's shareware,
not freeware, isn't?  I don't want to pay for a make when I have
one that works, and I can't sleep nights if i use shareware and
don't pay for it.

Is there a free gnu make?  Is it any good?