Sender: nate AT cartsys DOT com
Message-ID: <36466A79.70DE541E@cartsys.com>
Date: Sun, 08 Nov 1998 20:07:21 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i486)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Rhide and G++
References: <7256vf$hf6$1 AT fir DOT prod DOT itd DOT earthlink DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Albert Yi wrote:
> 
> I had the problem where I could compile with RHIDE but I couldn't link them.
> I soon received a suggestion to use g++ to link, which seems to work fine.
> Unfortunately, the file is always name a.exe for some reason.

Same as with `gcc', you use the `-o' option to specify the name of the
executable.

g++ -o foo.exe foo.cc

This comes from an old Unix tradition of executable names defaulting to
`a.out'.  For DJGPP, a corresponding `.exe' is created, so the file can
actually be run.

> Also, is there
> a way to use g++ through RHIDE? It's a bit tiresome to always quit RHIDE
> to run g++ and then run RHIDE again.

It ought to link C++ correctly by default.  Your problem may be that
addressed in `gnu/gcc-2.81/problems.txt'.  Also see chapter 8 of the
FAQ.
-- 

Nate Eldredge
nate AT cartsys DOT com