Mail Archives: djgpp/1999/08/27/14:52:50
François Jacques wrote:
> Sorry dudes for the delay , I've been busy these last days... =)
>
> salvador wrote:
>
> > > 1. I need to configure Borland IDE to use GCC with C/CPP files. That is,
> > > set gcc as my C/CPP translator. Probably no prob there but haven't tried
> > > it yet.
> >
> > I think that's impossible. I'm registered user of BC++ 3.1, I paid 350 dollars
> > for this crap (back in 1993). I think that's impossible because the compiler and
> > linker are *inside* the IDE. So the IDE doesn't call external programs and
> > doesn't collect the errors from any program.
>
> Would surprise me a lot! They would have two compiler editions? One embedded in the
> IDE and one command line? Why would they do so? As a decent software engineer, I
> would rather exec() the compiler and reuse the output in the IDE.
Don't forget it was created in 1992, no much memory, spawning a second program is
slower and needs much more memory.
But according to Laszlo you can do it using the features to run external programs
(Alt+Space menu).
> > The debugger is also inside and the help system can't read the djgpp's
> > documentation.
>
> Is DJGPP documentation in .hlp format (or at least available somewherein such a
> format) ? If yes, we could make good use of ObjectScripting, have a function key
> assigned to call the macro which would launch the help system with DJGPP doc as
> input file.... What do you guys think?
I think there are some converter from .info to rtf, but don't know if it also converts
to Windows .hlp files.
> There's one script in BC5 (or maybe even BC4.5) that allows watches in tooltips
> "a-la-Visual-Studio". Sounds like ObjectScripting is quite powerful.
>
> > > 2. Need to configure Borland IDE to parse output from GCC (like in
> > > Codewright) *OR* use a perl script to adapt GCC output to Borland
> > > format. I do not think that would be a problem but sincerly haven't
> > > tried it. Anyone did?
> >
> > As I said before: At least BC++ 3.1 doesn't parse anything the compiler is
> > inside.
> >
>
> That got refuted later in the thread.
>
> > > 3. Have Borland to read debug .o files
> >
> > :-))), you should rewrite most of the Borland's debugger and I doubt you'll get
> > the source ;-)
>
> U'r right there :)
>
> > > OR have GCC compile borland debug
> > > .obj
> >
> > That's a huge task.
>
> I've read somewhere that borland turbo debugger compatible debug symbols where part
> of NASM or at least someone added that support in a plugin or whatever (I don't use
> NASM, just read that while searching) If somebody did it for nasm...
There are a project to use nasm as replacement for "as" (the assembler used by gcc),
look for it, if nasm really supports it.
But I think Borland's debugger will have a lot of troubles to debug a dpmi
application.
> > > OR have the debug .o converted to borland debug .obj
> >
> > Impossible.
>
> ... they have Win32 binaries converted to OS/2 format... I don't like the word
> impossible. Let's say rather very difficult.
As you like, nothing is impossible, but you must know when something is impossible in
the real life ;-)
SET
--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013
- Raw text -