After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 700510 - Bibliography duplicate filenames fails
Bibliography duplicate filenames fails
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.3.1-SVN
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-05-17 10:14 UTC by Philip Blakely
Modified: 2014-08-24 11:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example code as referenced in bug-report (808 bytes, application/x-bzip)
2013-05-17 10:14 UTC, Philip Blakely
Details

Description Philip Blakely 2013-05-17 10:14:31 UTC
Created attachment 244497 [details]
Example code as referenced in bug-report

If two files in the CITE_BIB_FILES list have the same name, but are in different directories, then only one of them is parsed.

Also, if (one of) the references.bib files exists in the same directory as the one in which doxygen is being run, then it is deleted following the run.

In the attached example code, running doxygen in doxygen-bib-test results in only one reference being put into citelist.html, whereas two should be, one from testDir/references.bib and one from testDir2/references.bib.

However, if in Doxyfile, testDir2/references.bib is replaced by testDir2/references2.bib (a sym-link to the same file), then two references are correctly put into citelist.html.

This error occurs with the latest version of doxygen as in the repository (rev 848).
Comment 1 albert 2014-07-05 16:27:43 UTC
Problem in the bug report is that the bib files in the different directories have the same name and thus overwrite each other.
This patch solves this problem as well as the possibility to have spaces in the file name.

I've just pushed a possible solution to github (pull request 194)
Comment 2 Philip Blakely 2014-07-06 07:48:28 UTC
Thanks; I've tested this with the test-case I attached and with the original code-base I'd found the problem on and both now work as I would expect.
Comment 3 Dimitri van Heesch 2014-08-24 11:36:29 UTC
Fixed in release 1.8.8.