Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!moray!urchin!p6.f506.n106.z1.fidonet.org!Bob.Stout
From: Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout)
Newsgroups: comp.lang.c
Subject: Re: MSC 5.1 make
Message-ID: <6784.25911AD0@urchin.fidonet.org>
Date: 21 Dec 89 11:56:49 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.6 - Fulcrum's Edge, Spring TX
Lines: 13

In an article of <19 Dec 89 19:53:27 GMT>, (David Brown) writes:

 >My biggest problem is not with Microsoft's make, per se, but with the
 >command line limits on utilities such as the linker.
 >
 >What do the rest of you do if you have a lot of object files to make?

  The technique I sometimes use when compiling libraries (i.e. it only works  
if all the objects are together in one subdirectory by themselves) is to run a  
program which generates a linker response file for me by listing all the  
available .OBJ's and adding the extra verbage expected by the linker. This is  
the same technique used in the CXL windowing library, although I wrote my own  
for inclusion with my Microsoft library. If you'd like I can post the source.