MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011770CMakeCMakepublic2011-01-27 08:032016-06-10 14:31
ReporterDaniel Pinyol 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformPCOSLinuxOS VersionUbuntu 10.4
Product VersionCMake 2.8.3 
Target VersionFixed in Version 
Summary0011770: Enable using system dependency scanner
DescriptionAs described in http://www.cmake.org/Wiki/CMake_FAQ#CMake_dependency_scanner [^] , cmake dependency scanner will add as dependency headers all those for which a #include clause is detected in a source file, no matter whether the include is within a #if 0 or a /** **/ comment.
This is rather inconvenient, specially if the include is in a header, as it causes too many recompilations. As header dependency functionality is already provided by gcc -M (which does takes #if and comments into account), it would be nice to add the possibility to use native dependency scanner
Steps To Reproducehttp://www.cmake.org/Wiki/CMake_FAQ#CMake_dependency_scanner [^]
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-01-27 08:03Daniel PinyolNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030225
2016-06-10 14:28Kitware RobotNote Added: 0041790
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
(0030225)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone 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.
(0041790)
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.