Bug 419520 - Build tool view does not parse warnings and errors using clang-cl (on Windows)
Summary: Build tool view does not parse warnings and errors using clang-cl (on Windows)
Status: REPORTED
Alias: None
Product: kdevelop
Classification: Applications
Component: Output Views (show other bugs)
Version: 5.5.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-01 23:24 UTC by Jeremy W. Murphy
Modified: 2020-04-02 05:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy W. Murphy 2020-04-01 23:24:42 UTC 
SUMMARY

Warnings and errors are not highlighted orange and red respectively, although the preceding "In file..." lines do get highlighted blue.

An example warning line is:

Application/Infrastructure/DataManager/Include/EnumeratedItem.hpp(15,10): warning: non-portable path to file '"Application.h"'; specified path differs in case from file name on disk [-Wnonportable-include-path]

STEPS TO REPRODUCE
1. Use clang-cl on Windows
2. Build some code that generates warnings/errors

OBSERVED RESULT

Warnings and errors are not highlighted.

EXPECTED RESULT

Warnings and errors are highlighted.

SOFTWARE/OS VERSIONS
Windows: Server 2016 Standard
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.67.0
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Jeremy W. Murphy 2020-04-02 05:34:55 UTC 
Also, link errors, e.g.:

NodeValueChangeEventLogger.obj : error LNK2019: unresolved external symbol "private: static struct NodeValueChangeEventLoggerElement::NodeValueEvents const * const NodeValueChangeEventLoggerElement::NODES_VALUE_EVENTS" (?NODES_VALUE_EVENTS@NodeValueChangeEventLoggerElement@@0QBUNodeValueEvents@1@B) referenced in function "private: void __thiscall NodeValueChangeEventLoggerElement::InitialiseNodesEvents(void)" (?InitialiseNodesEvents@NodeValueChangeEventLoggerElement@@AAEXXZ)