From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: linking
Date: 18 Jun 2001 11:50:31 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 23
Message-ID: <9gkpu7$lkh$1@nets3.rz.RWTH-Aachen.DE>
References: <OE47zfoV1qdiixjnzi90000c37c AT hotmail DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 992865031 22161 137.226.32.75 (18 Jun 2001 11:50:31 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 18 Jun 2001 11:50:31 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Noah Fields <hano11188 AT hotmail DOT com> wrote:
> It would be great if someone answered this because then you would be the best support ever!:

> I am starting C++ and I got RHIDE and DJGPP.  

> In the Rhide editor I went to File and clicked new.

Wrong choice. A crucial concept of RHIDE which you haven't grasped yet
is that of a "project". It's the project list that defines what
happens when you link. Not the set of files currently open inside
RHIDE or anything like that.

So: open a new project, put your hellow.cpp into it, and build it.

> It said it compiled fine.  So then I wasn't sure what to do and
> opened the object file "hellow.o" in the editor window

That's hardly ever a sensible thing to do. *.o files are binary
garbage, as far as RHIDE and most humans' eyes are concerned.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.