On Jan 27, 2008 3:51 AM, Frederic Bouvier wrote:
> Stuart Buchanan a écrit :
> > Hi All,
> >
> > One of the frustrations of using Windows for development is the lack of
> a
> > sensible way to re-direct stderr to a file. This is particularly
> annoying if you
> > want to use a --log-level=debug.
> >
> > To fix this, I've changed the global_logstream to use stdout for windows
> only.
> >
>
> Is there a reason why we shouldn't do that for unix too ? is stdout used
> for something else than logging ?
>
> > The patch below does this.
> >
> > If someone could test that this doesn't mess up *nix, and commit it,
> that would
> > be great.
> >
>
> If we can avoid #ifdef, it's better isn't it ?
I don't mind writing these messages to stdout versus stderr,
On unix you can just run program > file 2>&1 in order to capture stderr as
well as stdout. Is that not possible in windows? I bet a cygwin shell
could do this.
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
