Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!karln!karln
From: karln@uunet.uu.net
Newsgroups: comp.lang.c
Subject: Re: C program structure -- generate a tree diagram?
Message-ID: <1991Mar1.185113.17704@uunet.uu.net>
Date: 1 Mar 91 18:51:13 GMT
References: <1148@cthulhuControl.COM>
Reply-To: karln@karln.UUCP ()
Distribution: comp
Organization: Sam76 - Pennington NJ
Lines: 26

In article <1148@cthulhuControl.COM> raisch@Control.COM (Robert Raisch) writes:
>
>I have a rather large system, running under MSDOS (Gack.) that I need to
>extract only the bits that do the work, and Microsoft C seems to want to
>*always* link in ALL the modules I tell it to, regardless of whether or
>not the code is actually used.  <heavy sigh>  Makes for an enormous 
>executable, even when I *know* I'm only using a small portion of the code.
>

	Just a point of order here, I am pretty sure, after 8 years of using
MSC, that you can link only the modules you want ONLY IF you put them into
your own library. This would be done with 

lib mylib+mod1+mod2+mod3

then compile main and link in this library.

	Fair warning though, you are going to have a b*tch of a time
figuring out how to get the make 'proceedure' to update the library
in a convient fashion. Clue: I had to echo the compiled module names
to a temp file and then include them all at once to the library ..

like they say "Mess-Dos"

Karl Nicholas
karln!karln@uunet.uu.net