MantisBT - CMake
View Issue Details
0012022CMake(No Category)public2011-03-29 08:292016-06-10 14:31
Sergiu Michin 
Kitware Robot 
normalmajoralways
closedmoved 
x86 and x64 Microsoft Windows 76.1.7600
CMake 2.8.3 
 
0012022: CMake, CDash and CTest don’t detect and report error C2220: “warning treated as error”.
CMake, CDash and CTest don’t detect and report error C2220: “warning treated as error”.
No tags attached.
Issue History
2011-03-29 08:29Sergiu MichinNew Issue
2011-03-31 13:45David ColeAssigned To => David Cole
2011-03-31 13:45David ColeStatusnew => assigned
2012-08-13 15:40David ColeStatusassigned => backlog
2012-08-13 15:40David ColeNote Added: 0030625
2012-11-21 14:54David ColeNote Added: 0031647
2012-11-21 14:54David ColeAssigned ToDavid Cole =>
2016-06-10 14:28Kitware RobotNote Added: 0041825
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030625)
David Cole   
2012-08-13 15:40   
Sending old, not-recently-updated issues to the backlog.

(The age of the bug alone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0031647)
David Cole   
2012-11-21 14:54   
Un-assigning bugs that are not on the active roadmap, which no developers are actively working on for the CMake 2.8.11 release.

If one gets put back on the roadmap, re-assign it appropriately at that time.
(0041825)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.