From: "John M. Aldrich" Newsgroups: comp.os.msdos.djgpp Subject: Re: easy library question Date: Mon, 21 Apr 1997 08:29:01 +0000 Organization: Two pounds of chaos and a pinch of salt Lines: 25 Message-ID: <335B254D.1575@NO.SPAM.cs.com> References: <5jgsq6$kdj$1 AT thor DOT atcon DOT com> Reply-To: fighteer AT cs DOT com NNTP-Posting-Host: ppp108.cs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk SteelGolem wrote: > > how do you tear apart .a files and get the .o files out of them? i want > to use allegro, but i want to take out the parts that i won't be > needing, so that my executable won't be as big as it would be > otherwise.. any help? email, pleeze! Don't you think the linker would be smart enough to do that by itself? Otherwise, every DJGPP compiled program would be over 650K long after the linker got through with 'libc.a'! Since this is obviously not the case, I don't think you need to worry. For tips on reducing the size of DJGPP-compiled executables, read section 8.15 of the FAQ. Second point: since you have obviously built Allegro, the .o files should still be there in the Allegro source directory. You don't need to extract them from the library. If you really do want to extract files from a library, just use 'ar'. -- --------------------------------------------------------------------- | John M. Aldrich, aka Fighteer I | mailto:fighteer AT cs DOT com | | Proud owner of what might one | http://www.cs.com/fighteer | | day be a spectacular MUD... | Plan: To make Bill Gates suffer | ---------------------------------------------------------------------