Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!ucsd!sdcsvax!amos!hartung
From: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C links in everything in obj's
Message-ID: <6139@sdcsvax.UCSD.Edu>
Date: 24 Mar 89 05:15:17 GMT
References: <1065@ptolemy.arc.nasa.gov> <7337@phoenix.Princeton.EDU>
Sender: nobody@sdcsvax.UCSD.Edu
Reply-To: hartung@amos.UUCP (Jeff Hartung)
Organization: Univ. of Calif., San Diego
Lines: 35

In article <7337@phoenix.Princeton.EDU> caromero@phoenix.Princeton.EDU (C. Antonio Romero) writes:

[response to complaint that Turbo C's TLINK can't leave out unused functions]

>If this is a big problem for your application, why not turn a,b,c,d,and
>e into a library and link with that? (Don't ask me how to do this with
>Turbo C, I don't develop software for PCs anymore.  But I'm sure it's
>possible, somehow... there must be some sort of library manager for
>Turbo.)

This is fairly simple and is done with TLIB.  The proper syntax is

	tlib <libname> [/C] [/E] [operations] [, listfile]

where /C is the case sensitive flag, /E is to create an extended dictionary,
the operations are:
	+	Add named .OBJ file to the library.
	- 	Remove the named module from the library.
	*	Extract the named file (i.e. creates a .OBJ file from the
		module).
	+- OR
	-+	Replace the module with the named file.
	-* OR
	*-	Extract the module to the corresponding filename and remove it
		from the library.
and listfile is the optional listing of the library contents to be produced.

The library you described would thus be produced with:

	tlib foo +a +b +c +d +e foolist

 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 Internet - hartung@amos.ling.ucsd.edu          
 UUCP - ucsd!amos.ucsd.edu!hartung