[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 142551] goto next error: treat warnings as errors
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-05-24 21:12:14
Message-ID: 20070524211214.5974.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=142551         




------- Additional Comments From apaku gmx de  2007-05-24 23:12 -------
I misunderstood that then. Also your initial wish is actually invalid because a \
shortcut that says it goes to the next/previous error should only go to the \
next/previous error. Wether you think that any warning is an error is irrelevant for \
this.

As far as using -Werror goes: That doesn't make gcc output the warnings as errors, it \
just makes gcc stop compilation. Thus these are still warnings and treated as such by \
kdevelop. Which is correct and KDevelop can't do anything about it because it doesn't \
know that these warnings are suddenly considered errors by gcc. Well of course we \
could start to parse every line and check if gcc is called with -Werror for a given \
file and store a flag for this file. Then later when getting an error we can lookup \
the file and see if the flag exists. 

The problem here are two things:
a) we'd also need to keep track of the directory thats currently processed by make \
(which we already do, IIRC) b) (much harder) this still breaks when doing parallel \
make because then having main.cpp:1 warning: ... main.cpp:1 warning: ...

may not reference the same main.cpp. This gets really complex and thus would slow \
down the outputview.


[prev in list] [next in list] [prev in thread] [next in thread]