Message-Id: <199709220624.BAA22861@fly.HiWAAY.net>
Reply-To: <kwall AT utw DOT com>
From: "Kurt Wall" <kwall AT utw DOT com>
To: <djgpp AT delorie DOT com>
Subject: Re: Projects in RHIDE?!?!
Date: Mon, 22 Sep 1997 01:24:17 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk

A "project" is RHIDE's idea of a makefile (it can actually be converted to
a makefile). 

Most large programming projects (not to be confused with RHIDE project) get
divided into multiple files.  Each group of related functions/data
structures is maintained in its own source and header files (*.c, *.h). 
The header files, of course, can be included in whatever other source files
you want .

When you are ready to compile your project, all of the associated files are
compiled to object code, then the linker glues it all together to create
(for DOS) a *.exe file.  The RHIDE project provides the logic (usually put
in a makefile) for making sure that everything gets compiled and linked
correctly.

HTH.

Kurt

----------
> From: Alex Kain <syntaxlogic AT nospam DOT net>
> To: djgpp AT delorie DOT com
> Subject: Q: Projects in RHIDE?!?!
> Date: Saturday, September 20, 1997 2:56 PM
> 
> Looking into released professional source code and Allegro source I've
> noticed that they managed to compile a program using projects by
splitting
> their code into multiple *.c or *.cc files and not all as headers, or *.h
> files.  The documentation for Rhide expects that the reader has
experience
> with projects.  I don't.
> 
> So can anyone tell me the methologies of doing such projects with Rhide? 
> 
> -- 
> Alex Kain
> syntaxlogic AT earthlink DOT net