delorie.com/archives/browse.cgi | search |
From: | tomtomb AT geicities DOT com (Tom Beauchamp) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Running Rhide easily under Windows? |
Date: | Fri, 10 Jul 1998 16:50:02 GMT |
Organization: | IDT (Best News In The World) |
Lines: | 7 |
Message-ID: | <35a64592.5620272@gateway> |
References: | <199807030019 DOT BAA27198 AT sable DOT ox DOT ac DOT uk> <6nip5d$88h$1 AT nnrp1 DOT dejanews DOT com> <1998Jul7 DOT 113610 DOT 16036 AT catorobots DOT ox DOT ac DOT uk> <6o5826$b8s$1 AT xenon DOT inbe DOT net> |
NNTP-Posting-Host: | ppp-15.ts-9.hp.idt.net |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
I've run into this problem also. RHIDE dosen't like to compile things that aren't in the directory that it was started in. If you have RHIDE in C:\djgpp\rhide or whatever, windows will start it like this "C:\djgpp\rhide\rhide.exe D:\csource\file.cpp" so the current directory will be C:\djgpp\rhide. You can avoid this by writing a batch file that changes to the directory of the source file and then starts rhide.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |