From: Bram de Greve <Bram DOT deGreve AT rug DOT ac DOT be>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro question...
Date: Wed, 21 Feb 2001 14:16:44 +0100
Organization: University of Ghent, Belgium
Lines: 28
Message-ID: <3A93BFBC.984C3A79@rug.ac.be>
References: <3a922ed2_2 AT news1 DOT prserv DOT net>
NNTP-Posting-Host: ftwe71.rug.ac.be
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Count Mecha wrote:

> I use rhide.  every time I open Rhide I have to go into options/libray and
> type "alleg".  How do I automate this(have the allegro known each time I run
> RHIDE w/out going into options all the time.

The best way is to use a project file per program you make (It's also a good
practice to save all files of a program in a seperate directory)
When you start a new program, you go to "open project" and type in "myProj" and
click on "open".  Now you have created your project file

With that project file, you can save many options of rhide, specified for your
program.  e.g. you it has to use the alleg library.  It can also remember where
to search for the source files and where to put the object/exe files of this
project (e.g. everything it that seperate directory)

It can also save which *.cpp files that go with the project.  You can add a cpp
file with "add item".  With the "projet window" (somewhere in the window menu)
you can see what cpp files are included in the project.

If you click on "build all" then rhide will automatically recompile all these
cpp's and build an executable of your program.
If you click on "run" it will check if some of these files are changed since the
last 'build' and if so, it will recompile these and rebuild the executable.
Afterwards, it will always run the executable.

Experiment with these features, it's very handy.