🚀 go-pugleaf

In article <1992Sep4.224643.3520@rei.com> fox@rei.com (Fuzzy Fox) writes:
>levin@world.std.com (Levin F Magruder) writes:
>
>>With the make & tlink that come with BCC 2.0, how do you set
>>things up so that you only need to maintain a single list of
>>object files?
>
>>I defined a macro in make like:
>>OBJECTS=a.obj b.obj ....
>
>>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.

************************************************************************
A note to new readers:  the weasely :-) symbol is frowned upon in this
group.  Any questions, see Phil Gustafson who will gladly rearrange your
diodes for you.
			- From the AFU FAQ -

	- pynq@quads.uchicago.edu, who is still costing the net
	  hundreds, if not thousands, of dollars, every time he posts -
************************************************************************