Date: Sun, 11 Mar 2001 14:27:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Paul Michailidis <paulm14 AT home DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: ARRRRGGG!!!! - Problem Solved
In-Reply-To: <3AAB0579.C04BE507@home.com>
Message-ID: <Pine.SUN.3.91.1010311142707.13811O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 11 Mar 2001, Paul Michailidis wrote:

> Anyway, just a general question. What is the point of running "make" in
> the allegro folder? why is it that you have to make allegro. Shouldn't
> it be ready to run once you download it?

Allegro is a library, not a stand-alone program.  Libraries are used
by linking your program with the library.  Linking with a library
requires a working compiler installation.  By successfully compiling
the library, you prove to yourself that your compiler installation is
fully functional.

> Also, before you run make,
> there already exists an allegro.h file. Wouldn't that suffice in order
> to successfully include allegro.

No, you need liballeg.a, the library itself.  The allegro.h header
file just declares the function prototypes, but bears no real code.