GNOME Bugzilla – Bug 535045
Missing warning for unreachable #includes
Last modified: 2018-07-30 10:19:09 UTC
For C source files, there should exist a warning, if an #include can’t be resolved properly or the included file is not found. As least there should be a switch for enabling such warnings. E.g. #include <myfarinclude.h> // with INCLUDE_PATH incorrect configured #include “imnotthere.h” // with file not existing The pre-processor of Doxygen just goes on and ignores evaluating the #include with all it's effects. There is no warning, even if WANRINGS and WARN_IF_DOC_ERROR is set to YES. Other information:
Created attachment 179861 [details] Complex include tree with files in other directories 1) typedefs.h is considered not found for 3 files, yet it is found for other files. 2) rsapi.h has 2 include files "isbop.h" and "rssysext.h". They are both documented as being included twice, and the 2nd time not clickable indicating not found. Note: This is not an bug with DOT. DOT is correctly generating an image of what Doxygen has interpreted.
I submitted a new bug report https://bugzilla.gnome.org/show_bug.cgi?id=641336 My report is different because my bug is that Doxygen can't find the files, rather than reporting the absence of the feature "warning about missing files". ...though I would still like for Doxygen to give a warning about missing files :)
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to https://github.com/doxygen/doxygen/issues All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github. Hence I am closing this GNOME Bugzilla ticket. Please use the corresponding ticket in Github instead. Thanks a lot!