Skip to content
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

Error List window in Visual Studio no longer recognizes doxygen warnings (Origin: bugzilla #701550) #5200

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-06-03 18:22:22 +0000, Robert wrote:

Hello.

I have setup a custom tool in Visual Studio that runs doxygen in the Output Window. When warnings appear there, they are conveniently displayed also in the Error List window. The warning messages changed in 1.8.4. Now "Warning:" is capitalized, whereas in 1.8.3 it was lowercase "warning:". Because of this change in case, the Error List no longer recognizes it. The MSVC compiler users lowercase "warning", so the Error List must be hardcoded to be case sensitive.

Please allow me to customize the text for warning in the doxygen config. Default value can be "Warning:", but it will allow me to specify lowercase "warning:" so that Doxygen warnings will be processed by other tools properly.

Example in config:

WARNING_STRING = "warning:"

Thanks.

On 2013-06-03 20:54:59 +0000, Robert wrote:

Created attachment 245961
Add WARN_STRING and ERROR_STRING config options

I have implemented this for you, it was pretty easy to do. I tested doxygen with this change against the code base at work and seems to work perfectly. I didn't update doxywizard or anything other than doxygen.exe. If you provide some guidance I can do that for you but I am not as familiar with the code as you are. Let me know if you like the solution.

On 2013-06-03 21:14:31 +0000, Philipp Moeller wrote:

This also broke some of my tools, but I feel like making those things configurable would be overkill. Doxygen should simply produce warnings and errors that can be parsed by Visual Studio, e.g. lower case "warning" and "error".

On 2013-06-03 21:20:29 +0000, Robert wrote:

Philipp, I think this is a bit overkill as well but consider that while Visual Studio expects lowercase, what if some other IDE expects uppercase? In that case we can never have both tools working. The only way to make them both work is to make it configurable :(

I had more general extensibility in mind, not just Visual Studio. What are your thoughts on this?

On 2013-06-03 21:55:21 +0000, Philipp Moeller wrote:

All IDEs I work with have customizable error output scanners. It comes as a surprise to me that VS doesn't support this and that its scanner is that naive.

On 2013-06-03 21:59:01 +0000, Robert wrote:

I agree Philipp, I tried to find some hidden documentation on possible registry settings to configure or something of that sort but I've had no luck :(

On 2013-06-04 17:57:46 +0000, Dimitri van Heesch wrote:

I will change the defaults to lower case. I see also gcc uses lower case.
This avoids additional options, and will still work for tools that have the necessary flexibility.

On 2013-08-23 15:04:39 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.