From:	dmlloyd AT earth DOT execpc DOT com (David Lloyd)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Q: Projects in RHIDE?!?!
Date:	24 Sep 1997 18:53:10 GMT
Organization:	Nope.
Lines:	21
Message-ID:	<slrn62iocm.7rv.dmlloyd@earth.execpc.com>
References:	<199709240324 DOT UAA02112 AT adit DOT ap DOT net>
NNTP-Posting-Host:	earth.execpc.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <199709240324 DOT UAA02112 AT adit DOT ap DOT net>, Nate Eldredge wrote:
>At 07:56  9/20/1997 GMT, Alex Kain wrote:
>>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? 

I figured out how to use projects all on my own, so what I say is not
backed up by any real doucmentation. :) But as far as I know, you _never_
include *.h files in a project.  You only specify the files you want
compiled, therefore *.c files (since the *.h files are processed with the
*.c files that include them, you don't need to explicity list them in the
project window).

-- 
(*)  Dave Lloyd
(*)  dmlloyd @ execpc.com

- Raw text -