Reply-To: <arfa AT clara DOT net>
From: "Arthur" <arfa AT clara DOT net>
To: "DJGPP Mailing List" <djgpp AT delorie DOT com>, "Rylan" <rylan AT inbtekom DOT co DOT za>
Subject: RE: Excluding unused Allegro Functions
Date: Thu, 17 Sep 1998 16:25:20 +0100
Message-ID: <000501bde24f$61be5800$a14e08c3@arthur>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6tnk2k$7vm$3@news2.saix.net>
Importance: Normal
Precedence: bulk

> This refers to Mr. Middelditch's post about removing unused library
> functions :
>
> I recently noticed while using FSDB that, when debugging Allegro code (I
> just looked at one of my Allegro using programs) that there are functions
> and routines included in the final .EXE that I do not use AT ALL in the
> program - so I want to ask too if there is anyway to exclude these unused
> library functions, not just for Allegro but any library from the final
> resulting .EXE?

Any functions that are not called from a library should not be included
(this is the point of libraries, and that is why they are different to
simply linking with another file).

Allegro includes some "administrative functions" which enable it to work.
For instance, when you call create_bitmap() the function create_bitmap_ex()
is called from within that, which will be included in your program.

It states in the manual that Allegro includes a 200k overhead in any program
just to get the library to work. I suggest you read the manual because it
goes into some detail on the subject of reducing the executable size if
possible.

James Arthur
jaa AT arfa DOT clara DOT net
ICQ#15054819