GNOME Bugzilla – Bug 641336
Include files not found in include path, or duplicate entry of include file is inserted
Last modified: 2011-12-03 18:22:48 UTC
Created attachment 179982 [details] Minimum Project demonstrating strange behavior, html output included Perhaps related to BUG535045 (https://bugzilla.gnome.org/show_bug.cgi?id=535045) My rather large project that I am assigned to maintain spans several folders. There are some include files that don't seem to be found (not clickable). The odd time the generated documentation also indicates files included twice, although the source code only has it once. Of the duplicate include files, one is with a clickable link and the other is not clickable. This seriously hinders my confidence in the Doxygen output as it seems to be inconsistent. I spent several days trying to characterize what is going on, but I'm still lost.
Confirmed. Should be fixed in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.4. 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.
The change in pre.l:readIncludeFile just changed manifestation of this bug, but did not fix it: some includes with realtive paths containing '../' still fail to be found as fileDefs. Quick fix: Use (newly constructed) absolute path for findFileDef() if fs=findFile() returns NULL Proposed solution: Do not throw away the result of findFile/checkAndOpenFile if the file was already included, use the already constructed absolute path to find the filedef for the given file.
Created attachment 197166 [details] [review] absIncFileName instead of incFileName for findFileDef
Using the absolute include file name for the invocation of findFileDef instead of the original file name avoids finding problems when the original file name starts with "../" (or "..\\", for Windows). The enclosed patch for src/pre.l for version 1.7.5.1 seems to solve that problem.
Hi Thomas, Thanks for the patch, I'll include the patch in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.6. 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.