Mail Archives: djgpp/1997/12/18/18:30:25
Fábio Diales da Rocha wrote in message <67790n$372$1 AT duke DOT telepac DOT pt>...
> RHIDE is a great IDE, and, although it isn't quite as integrated with
>djgpp as you would expect a IDE designed by the same persons that designed
>the compiler, it's almost there.
Robert didn't design gcc. He did (and does) a lot of work for the DJGPP
community though, and
ported and maintains binutils (assembler and loader).
> 1. It refuses to compile "cpp" files, only accepting "cc" ones although
>gcc does fine with "cpp" files
Search the DJ archives, or check Rhide's web page. This was a known bug
with a workaround.
Also, unless you get a patched gcc (SET just released one), you can have
problems debugging
.cpp files. GCC mistakenly puts the file name in the assembly as .cc
instead of .cpp, so the debugger cannot find your source code.
> 2. Its complete inability to find files in the current directory,
>forcing you to add it to the search directories.
Don't know, I use emacs.
>And, NO, i don't like
>projects, they're perfectly supportable if you're actually coding
something,
>but if you want just to browse through some source files they're completly
>insupportable.
I think most people who use rhide do actually want to code something.
> 3. And last, but certanly not least - it takes an unnecessary ammount
of
>time to compile because it spends half the time writting and reading
>something to disk. Example: if just try to run grep (i don't have it) it
>takes about 15 seconds before a simple "Bad command or file name". This is
>extremelly annoying. Believe it or not i've read a book in the interims
>rhide takes to call gcc twice.
How long does it take to compile from a dos prompt? Is it the same amount
of time?
Perhaps you have a network or cd-rom drive in your path ahead of djgpp\bin.
Try putting the
dj directory first in your path.
Andy
- Raw text -