Mail Archives: djgpp/1998/05/16/01:02:58
From: | "Alberto Chessa" <achessa AT fiar DOT finmeccanica DOT it>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | RHIDE and file extension
|
Date: | 14 May 1998 07:27:35 GMT
|
Organization: | FIAR S.p.A.
|
Lines: | 23
|
Message-ID: | <01bd7f0a$008a3520$92c809c0@chessa>
|
NNTP-Posting-Host: | milano20-14.tin.it
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hello,
due to mystic reasons, I have to name my C source file <name>.c38 - that's
right: just "c38" instead of "c" ! - and I want to use these source in
RHIDE project.
This make no problem (I force compiler type in Local Option) up to
executable generation, but make big trouble with debugger: It seem it's not
able to retrive the correct source out of my objects - It always try to
open <file>.c.
I read that RHIDE has the same problem on C++ file that have not the ".cc"
extension (a GCC problem fixed by 2.8) and work around this with specific
environment variable (rhide_.env)
There's a way to force source file association for non-standard file
extension to work with the debugger under RHIDE ?
I search the help on rhide.env with no success. I simple try to add some
.._C38 rules to my env with no results at all.
(RHIDE Version: 1.4. Sep 30 1997 23:06:59)
Thanks in advance
- Raw text -