Date: Tue, 10 Mar 1998 22:52:19 +0100
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id: <199803102152.WAA27292@acp3bf.physik.rwth-aachen.de>
To: andrewda AT cogs DOT susx DOT ac DOT uk (Andrew Smythe Davidson)
Cc: djgpp AT delorie DOT com
Subject: Re: Rhide compiling problems
Newsgroups: comp.os.msdos.djgpp
Organization: RWTH Aachen, III. physikalisches Institut B
Precedence: bulk

In article <6e3ogs$302$1 AT infa DOT central DOT susx DOT ac DOT uk> you wrote:

> gcc hellow.o hellow.o -o hellow.exe

> Instead of:

> gcc hellow.o -o hellow.exe

You added 'hellow.o' to the list of files for your project, it seems.
Do *not* do that. It's RHIDE's own business to know that .c files are
compiled into .o, and that those .o files are to be linked with the
rest, finally. Adding .o files only makes sense when you don't have
the corresponding .c file (not at all, or at least not in this project
definition).

> While I'm on the subject of Rhide, is there any way to save global
> preferences (like editor preferences) that are automatically loaded
> every time I start the ide? 

IIRC, saving options when you were in the bin directory of DJGPP at
RHIDE starting time does just that. But don't quote me on this...

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