From:	broeker AT acp3bf DOT knirsch DOT de (Hans-Bernhard Broeker)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: How to configure rhide ?
Date:	11 Oct 1999 14:05:23 +0200
Organization:	RWTH Aachen, III. physikalisches Institut B
Message-ID:	<7tsjq3$65r@acp3bf.knirsch.de>
References:	<v4aM3.1923$KV3 DOT 4748 AT nntpserver DOT swip DOT net>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 939643525 12765 137.226.32.75 (11 Oct 1999 12:05:25 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	11 Oct 1999 12:05:25 GMT
X-Newsreader:	TIN [version 1.2 PL2]
Lines:	23
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Peter Johnsson (peter DOT johnsson AT mbox312 DOT swipnet DOT se) wrote:
> I want to configure where my exe files go to when I compile in rhide,
> someone with a solution ?

The trick is that this is *not* something to be configured. RHIDE puts
the .exe to the directory it's running from. So the usual solution is
to *change* to the directory you want the exe to be in (usually the
same one the sources are), and then start RHIDE there. 

This whole problem is typical of Windows users having little or no
experience at all with the DOS command line. They will set up a
desktop link to RHIDE, and then they're surprised all their .exe's
generated by RHIDE land in their Windows directory.

The essence: _Don't_ start RHIDE by a desktop link with default
settings. At the very least, modify the 'working directory' setting in
the 'Program' tab of the properties of that link. It's usually simpler
to just start a DOS box, 'cd {your project directory}', and then type
'rhide' from there.

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

- Raw text -