
Key: |
QB-2666
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Benoit Maury-Bouet
|
Votes: |
0
|
Watchers: |
1
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 16/Mar/16 01:29 PM
Updated: 19/Jan/18 08:31 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
6.1.10
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Dear all,
It would be nice in the advanced options for devenv and msbuild step to have an option to force warnings to be treated as error when parsing visualstudio log.
And it would be nice also to have an option to exclude certain warnings from triggering an error.
Because if you do have a "warning as error" flag set on your compilation the error returned by visual studio will be :
error C2220: warning treated as error - no 'object' file generated
Which is not very informative, as the valuable information is in the warning message : warning C4189: 'width': local variable is initialized but not referenced
Thanks a lot!
Ben
|
Description
|
Dear all,
It would be nice in the advanced options for devenv and msbuild step to have an option to force warnings to be treated as error when parsing visualstudio log.
And it would be nice also to have an option to exclude certain warnings from triggering an error.
Because if you do have a "warning as error" flag set on your compilation the error returned by visual studio will be :
error C2220: warning treated as error - no 'object' file generated
Which is not very informative, as the valuable information is in the warning message : warning C4189: 'width': local variable is initialized but not referenced
Thanks a lot!
Ben |
Show » |
No work has yet been logged on this issue.
|
|