Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!usc!elroy.jpl.nasa.gov!cit-vax!tybalt.caltech.edu!josephc
From: josephc@tybalt.caltech.edu (Joseph Chiu)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C Linking Problem
Message-ID: <13494@cit-vax.Caltech.Edu>
Date: 22 Jan 90 02:18:08 GMT
References: <1997@uwm.edu>
Sender: news@cit-vax.Caltech.Edu
Distribution: usa
Organization: California Institute of Technology
Lines: 15

peter@csd4.csd.uwm.edu (Peter J Diaz de Leon) writes:

>        tlink c0m closure.obj error.obj lalr.obj lr0.obj main.obj mkpar.obj output.obj reader.obj skeleton.obj symtab.obj verbose.obj warshall.obj ,byacc,mbyacc,cm
>Fatal: Command arguments too long

I suggest you look in the manual on the specifics, but Turbo C allows you to
have various configuration information in the file TURBOC.CFG to allow lots
of commands (and probably file names) to be specified.  Also, if you look
in the manual, there is a way to enter all the filenames through yet another
file. (Sort of like a make).

My advice is to put every .obj's into a library of your own, then link c0m with
your main.obj and let the library take care of itself from there.

Joseph