Re: [Mingw-users] messages
alpha-quadrant wrote:
>
> At 07:00 PM 12/28/07, you wrote:
>
>>Hi,
>>
>>assuming you want to read the messages after running make, you can use
>>"make 1>&messages.txt 2>&1".
>>
>>hope that helps.
>
>
> what the heck was all that? I just went with what I knew all along.
>
> mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=1
> BUILD=release clean>messages.txt
> mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=1
> BUILD=release>messages2.txt
>
> Now I got em, so you just confirmed what I already knew (in a very
> round about way)
> Are answers to questions disguised as a test of your ability?
> More times than not it seems.
>
>
The number before the redirection represents the stream to be redirected,
where 1 = stdout and and 2 = stderr. The &1 represents the previously-
mentioned messages.txt, so the command means redirect messages
written to stdout and stderr to messages.txt. The 1> is not necessary,
since by default '>' redirects stdout.
Since gcc writes its warnings and error messages to stderr, your text files
contain neither. You will see only the commands that make executed.
_________________________________________________________________
Share life as it happens with the new Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_122007
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users