-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gcc, ARM-Gcc and Doxygen #38
Comments
Can you provide some output from GCC and Doxygen? |
Example output:
ARM-Gcc (4.9 2015q3):
Doxygen has the ability to change the warning format. The default format is: "$file:$line: $text". Doxygen:
|
You are right. A particularitiy of Doxygen is that there are warning messages over multiple lines (2nd warning). |
I implementing it without supporting the whole message from Doxygen. Perhaps someone can add that later. Now I'm just including the first line because that was a very simple thing to support. And it is supported with the |
Released in the plugins now. |
Hi, the idea is to be able to recognize compiler warnings as well. Compiler warnings can also be seen as static code analysis results providing valuable hints where problems can hide.
In an environment of continuous integration, various builds with different compiler flags can be executed ending in possibly different warnings. Also compilation with different compilers may be necessary. Adding support for compiler warnings in this lib would eliminate the need to compile these things manually and enable to comment on pull requests for compiler warnings (Bitbucket Server in my case).
In detail, as I am working on C++ projects, I am very interested in support for GCC compiler and Doxygen generation warnings.
The text was updated successfully, but these errors were encountered: