Currently the output of bgdc.exe goes to stdout.txt; this is not an operation one would expect. I see why it could be useful, but it's not handy for IDE's catching the screen output. So my suggestion is that there be at least a parameter switch telling bgdc.exe to output its info to the screen and not the stdout.txt. Ultimately I would like outputting to screen to be standard operation but I'll be happy with the switch.
Quote from: Sandman on September 09, 2007, 02:07:35 PM
Currently the output of bgdc.exe goes to stdout.txt; this is not an operation one would expect.
Wop! Already exists a Bennu compiler version? I didn't heard anything about...
QuoteI see why it could be useful, but it's not handy for IDE's catching the screen output. So my suggestion is that there be at least a parameter switch telling bgdc.exe to output its info to the screen and not the stdout.txt. Ultimately I would like outputting to screen to be standard operation but I'll be happy with the switch.
If default output is screen (or command-line) I think it's easy to redirect to a file. For that you hace to type something like this:
bgdc.exe -> outputefile.txt
And the data that must go to screen will go to this file.
Yes but that's not how it is done now; now it's going to stdout.txt and not the screen.
And what you meant is:
bgdc.exe >> outputfile.txt
SDL catch the main proc and redirect stdout and stderr... only in windows... I can use a script for avoid it.
bgcd.bat
@echo off
c:\bennu\bin\bgdc.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
type c:\bennu\bin\stdout.txt
del c:\bennu\bin\stdout.txt
That would be cool, thanks. Originally Fenix did this as well (fxc.exe v0.84a for example), but it was later changed.
I know of the batch file, I've been using it and it is a working work around, but not a solution in my opinion.
Sorry, SDL problem...