From: <alp...@ea...> - 2007-12-29 16:07:23
|
At 07:53 AM 12/29/07, you wrote: >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. A++ for effort. Thank you. But no working example has been achieved. tried every combination of 1>&messages.txt 2>&1 Ampersands always become part of the filename. adding a 1 or a 2 is never accepted - "no rule to make target '2'" >>mess.txt = stdout >mess.txt >mess2.txt = stdout "You will see only the commands that make executed." yes I noticed that. no working example and no success :-( ( a crying frowny ) |