Hi XG.
I just came across that same problem and it seems i found a cure.
Installed C::B 1.02RC2 with MinGW and tried a console-App, everything OK.
Installed DJGPP same version as you did and set up compiler options for it.
I did that by using a copy of the GNU GCC -Settings used for MinGW.
Then changed the Compiler's installation directory to my DJGPP-Directory
and rebuild.
Just as you stated, it tries to build, but the compiler's output is lost in nowhere.
Tried redirection on the commandline as you did, same results. And exactly the
same behaviour as for MinGW-G++. Strange enough.
So i decided to go a bit deeper and followed both compiler's File-IO with NTFileMon.
Result as followes:
for MinGW-GCC C::B calls the mingw32-g++.exe.
for DJGPP C::B seems to call NTVDM, which then calls gpp.exe
True, C::B will not call NTVDM, instead ye old Windows itself finds gpp.exe is an
old 16-Bit-Program and those get executed in the virtual Dos-Box NTVDM :shock:
So, what's the clue?
Not realy knowing what the problem is with redirection in NTVDM i decided to
try a rude workaround. Just add a "cmd /C " to each command that is a 16-Bit executable.
So, in the Dialog "Compiler Settings" under "Other" -> "Advanced options..."
set "Compile single file to object file" to
cmd /C $compiler $options $includes -c $file -o $object
and alike for the other commands.
And, yes, it works. Now i get propper parsed compiler output.
It's not linking now, but that'll be a minor problem with startup-Code, i think.
And, i do get a Build message for that :-)
Good luck to XG an who else tries C::B to replace the fairly old RHIde.
Stefan