Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!tnoibbc!rs
From: rs@tnoibbc.UUCP (Rob Schoenmaker)
Newsgroups: comp.lang.c
Subject: Re: MSC 5.1 make
Message-ID: <1366@tnoibbc.UUCP>
Date: 20 Dec 89 08:57:16 GMT
References: <1989Dec15.021527.18711@sjuphil.uucp> <2411@jato.Jpl.Nasa.Gov> <78@motto.UUCP>
Reply-To: rs@tnoibbc.UUCP (Rob Schoenmaker)
Organization: Organisation for Applied Scientific Research, IBBC-TNO, The Netherlands
Lines: 29

In article <78@motto.UUCP> dave@motto.UUCP (David Brown) writes:
>However, even if I get around the 512 byte limit in macros by having
>multiple macros (OBJ1, OBJ2, ...), link won't accept so long a command
>line.  I'm forced to keep a separate response file for the link, which
>means maintaining another list of all the object names.
>
>I tried the PDMAKE that was posted here recently.   It solves the macro
>limit problem, but I'm still stuck with the link command line limit.
>
>What do the rest of you do if you have a lot of object files to make?
>

I use Polytron's PolyMake which can generate a response file for you,
like this :

test.exe:	$(OBJS)
		link $(LFLAGS) <@<
		$[s," +\n",$**]
		$@

		$(LIBS)
<


-- 
Rob Schoenmaker: TNO - IBBC                   USENET : rs@tnoibbc
               : lange kleiweg 5              UUCP   : ..!hp4nl!tnoibbc!rs
               : 2288 GH  Rijswijk
               : the Netherlands              VOICE  : +31 15 606410