Well what would be awesome is having the launcher extract individual
diagnostic messages.
Then each diagnostic message could be categorized as warning, error or other
and flagged as ignored or visible.
One could even extract line (and column) information.
Then CDash could selectively:
- show only diagnostic messages which are not being ignored
- show all diagnostics (maybe with ignored diagnostics having distinct
coloring)
- allow dynamic search to filter diagnostics
With line information one could even build external links for some web
repository viewers.
Nils
On 10/16/2012 07:44 PM, David Cole wrote:
On Mon, Oct 15, 2012 at 10:50 AM, Nils Gladitz <glad...@sci-vis.de> wrote:
I think I just had erroneous expectations about how warnings would be
filtered when using launchers.
Apparently warning output is not removed on a per warning basis but rather
the whole output of a compile step is included if there are any unsuppressed
warnings.
With ~500 lines of compiler output I just overlooked a single warning which
has not been suppressed.
After solving that single warning all output of that compile step is
suppressed.
In practice finding the unsuppressed warnings in the compiler output can be
rather difficult (unless it is the only warning in that compilation unit)
since from the output alone they can not be distinguished.
I'll just disable launchers for now.
Sounds like it's just a "the way things are" sort of problem here.
Let me know if there's anything you think needs to be changed in ctest
to improve the experience here.
--
Nils Gladitz, B.Sc.
DICOM, Konnektivität und Entwicklung
Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
GERMANY
Handelsregister Nr. / Trade Register No. B3100 Göttingen
Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland
Tel: 0049 (0)551 634181-28
E-Mail: glad...@scivis.de
Web: www.scivis.de
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
