From: "Matthew Smith" <matt AT the-good-stuff DOT freeserve DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How to set path to the allegro folder
Date: Thu, 5 Jul 2001 07:08:14 +0100
Lines: 24
Message-ID: <9i10ia$2dg$1@news6.svr.pol.co.uk>
References: <W4e07.7369$MO1 DOT 1151895 AT news0 DOT telusplanet DOT net> <9htij2$jhu$1 AT news8 DOT svr DOT pol DOT co DOT uk>
NNTP-Posting-Host: modem-507.bellsprout.dialup.pol.co.uk
X-Trace: news6.svr.pol.co.uk 994313610 2480 217.135.29.251 (5 Jul 2001 06:13:30 GMT)
NNTP-Posting-Date: 5 Jul 2001 06:13:30 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

the files created by rhide will really be      exhello.gpr and
exhello.gdt
the default targetname will be exhello.exe but you can change this in
one of the menus

I should maybe have explained better that RHIDE does not need to point
to the allegro folder.  When you "make install" the Allegro library,
the headers are placed in the compiler's include folder.  This means
that any program with #include <allegro.h> can find and use the
Allegro code.

The only thing further you have to do is link the liballeg.a file with
your code.
you do this in RHIDE with the "[X] 0 alleg " setting I described.

RHIDE's view of things is centered on it's GPR file and the directory
in which it is started.  It knows (from the DJGPP environment
variable) where your compiler is.
It keeps a list (the project items) which need compiling, and it lets
the compiler build
your program, and then acts as a debugging program to test your code.