Obtaining compiler warnings
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
Thanks! Johan
On 2/21/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
Thanks! Johan
As far as I remember, batch redirections are similar to bash ones, so 2> compiler-out.txt at the end of the command line should work.
Romain
On Wed, Feb 21, 2007 at 11:23:49AM +0100, Romain Thouvenin wrote:
On 2/21/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
Thanks! Johan
As far as I remember, batch redirections are similar to bash ones, so 2> compiler-out.txt at the end of the command line should work.
Romain
Also, the -s and -k options to make can be helpful here.
Bryce
J.B.C.Engelen@...1578... wrote:
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
Thanks! Johan
Excellent idea. It is already catching the piped stdout and stderr output of the shelled-out compiler call. It would be easy to save it to "build.lst" or something, I guess.
bob
J.B.C.Engelen@...1578... wrote:
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
CMake does this by default. :-)
Aaron Spike
On Feb 21, 2007, at 1:55 AM, <J.B.C.Engelen@...1578...> wrote:
Does anybody know a way to neatly catch compiler warnings on windows? I'd like to only see a list of compiler warnings, instead of the complete compiler commandline as it is now. For example: It would be very nice if the buildtool could generate a separate file (say compiler-out.txt) in which all special compiler messages are put such as: gradient-context.cpp:325: warning: 'pointtype' may be used uninitialized in this function
Arrrgh!!!! I forgot a very simple, yet effective solution.
Just run the compile from inside of emacs.
:-)
Just install and run it. I think I got the *-fullbin* one at ftp://ftp.gnu.org/gnu/emacs/windows/
Then execute a shell and you'll be in a dos window but will full emacs scrollback.
participants (6)
-
unknown＠example.com -
Aaron Spike -
Bob Jamison -
Bryce Harrington -
Jon A. Cruz -
Romain Thouvenin