Mail Archives: djgpp/1997/09/19/11:17:56
In article <xmerm05 DOT 25 DOT 00102DCA AT vse DOT cz> you wrote:
> >Does Rhide support it?? Is it just a matter of renaming it so that Rhide
> >calls this compiler instead of the gcc compiler. Like renaming gcc.exe
> >to gccorig.exe and pgcc.exe to gcc.exe, would it work like the normal
> >gcc.exe in Rhide??
> It doesn't even have to. Basically you're right, but you have to rename gcc.
> exe, cc1.exe and cc1plus.exe (in djgpp/bin dir) and libc.a and specs (in
> djgpp/lib dir). Don't rename gxx.exe, because in pgcc it's totally different
> than in djgpp. There is problem with c++, because you can use the old one (
> cc1plus) only with older specs file, which might not be as good for cc1.exe
> as the new one.
Just to save some you out there some work, here's a little trick you
can pull to save yourselves the work of repeatedly renaming all these
files. It requires a bit of knowledge about the syntax of the
djgpp.env file, so be careful and keep a backup of it handy.
You can have multiple 'gcc' distributions on your machine if you put
them into separate directories and make some clever changes to the
'djgpp.env' file. For the following, let's assume you called your pgcc
version of gcc.exe pgcc.exe, and put it in %DJDIR%/bin. The other files
(cc1.exe and the rest) are in %DJDIR%/bin/pgcc
1) copy the [gcc] section of djgpp.env, and change to the section
name of the copy to [pgcc]
2) Prepend '%DJDIR%/bin/pgcc;' to COMPILER_PATH in [pgcc]
3) If you want a separate set of libs and/or a different specs file,
you may put them into %DJDIR%/lib/pgcc and prepend that directory to
LIBRARY_PATH in [pgcc].
With these modifications, you can use both gcc and pgcc
interchangeably, without any need to move files or whatever.
I don't know wether RHIDE can be convinced to use pgcc.exe instead of
gcc.exe, though. And you'll probably have to wait for the maintainer
of the DJGPP pgcc port to distribute a DJGPP-like pgxx.exe, or build
one yourself from the libsources.
HBB
- Raw text -