www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/02/28/00:21:09

To: djgpp AT delorie DOT com
Subject: Re: Trimming program size
Message-ID: <19970227.211926.4943.2.chambersb@juno.com>
References: <01bc2468$540f0340$8c081ecb AT sly>
<19970227 DOT 220001 DOT 7167 DOT 0 DOT fwec AT juno DOT com>
From: chambersb AT juno DOT com (Benjamin D Chambers)
Date: Fri, 28 Feb 1997 00:16:26 EST

On Thu, 27 Feb 1997 21:53:25 EST fwec AT juno DOT com (Mark T Logan) writes:
>
>On 27 Feb 1997 05:36:23 GMT "Sly" <sly AT aussie DOT net> writes:
>>I am (slowly) developing a game using the Allegro library.  I was 
>>wondering
>>whether it would be possible to be able to trim the library when the
>>program is ready for general distribution.  That is, remove any 
>unused
>>sections, like video card specific drivers (my program just uses 
>>Mode-X
>>resolutions) and any other sections not required.  Would this be
>>advantageous, or just too difficult to contemplate?
>>
>
>I'm sure Shawn will reply to this message too, but I'll put my 2 cents 
>in
>anyway.
>
>Since allegro is distributed with all the sources, all you have to do 
>is link
>in only the object files which you need.  For example, if 
I thought the linker already did this for you - as in, any object files
in a library that go unreferenced are unlinked (however, all it takes is
a single reference and the entire object file is linked in).  Somebody
correct me if I'm wrong.

...Chambers

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019