GNOME Bugzilla – Bug 727796
Generates oddly named "Directory Reference" man pages including build path
Last modified: 2018-07-30 10:42:42 UTC
I am quoting the original Debian bug report at http://bugs.debian.org/742871: > when generating man pages via doxygen, newer versions of doxygen (can't > exactly tell when this behaviour changed), now generate a "Directory > Reference" man page. This file is oddly named though and includes the > full build path. In my case (libdaemon), it generated > > /usr/share/man/man3/_tmp_buildd_libdaemon-0.14_libdaemon_.3.gz > > [...] > > libdaemon 0.14-2, which was built with doxygen 1.6.2-1 [1], doesn't show > this behaviour. So something must have changed between 1.6.2 and 1.8.6 > > I tried to find documentation about how to influence the generation of > this Directory Reference man page, i.e. to either convince it to use a > proper name or not generate it at all. If there is such a configuration > switch and I need to update my doxygen.conf [2], please let me know. > Otherwise this looks like a genuine bug in doxygen. The relevant package sets FULL_PATH_NAMES=NO, but changing that to FULL_PATH_NAMES=YES and leaving STRIP_FROM_PATH at its default does not solve the issue. I narrowed the intrusion of this behaviour to a version window of 1.7.6.1 to 1.8.1, but I couldn't find the offending change in the mess of bison generated/flex generated/uglified javascript files.
Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Created attachment 280561 [details] test case The file is not created if notmuch.h is in the same directory as doxygen.cfg
Are you able to reproduce this? We are hit by the same problem using 1.8.8, sources are in https://bitbucket.org/Coin3D/coin/branch/CMake. Thanks, Bastiaan.
This commit: https://github.com/doxygen/doxygen/commits/master/src/dirdef.cpp resolves the issue on the test case attached to this bug report.
@Paolo Greppi you refer to a file not to a commit, please clarify. Do you suggest that the problem is solved in the current version of doxygen i.e. 1.8.14?
Sorry I meant: https://github.com/doxygen/doxygen/commit/38987846ec0752b8deee7bab69c7890aa861af00 Yes, the issue is resolved in 1.8.14 which includes this commit, at least for the test case attached to this bug report. But I'd wait a bit before marking this bug as closed as I am in the process of testing a few more complex test cases from the originating Debian bug: https://bugs.debian.org/742871 I'll report back when I'm 100% sure that they are all solved now.
Thanks, please don't set to closed (even when it is resolved), make a comment saying that the problem is solved in the mean time (or similar wording) and set status back to "New". In that way it can, possible, be handled in release notes etc.
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!