GNOME Bugzilla – Bug 778730
doxygen build fails
Last modified: 2018-02-20 14:47:29 UTC
Created attachment 345909 [details] ZIP file containing doxygen configuration file and doxygen log file I have a doxygen project which builds successfully. When I remove one function from one of the classes in the project, doxygen fails to build successfully. It appears to be failing at the point it calls latex. I have no clue how to resolve this problem thus all I could do is supply you with the configuration file I'm using and a copy of the doxygen log. Can you please let me know how to resolve this issue.
So you are not compiling Doxygen itself, but a project in Doxygen? From your attachment: [322 ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd fstartlink. \AtBegShi@Output ...ipout \box \AtBeginShipoutBox \fi \fi l.283 \end{DoxyParams}
No I'm not compiling doxygen, I'm running a build on my library which invokes doxygen to generate my library documentation. This type of error is out of my depth because I only know how to create the doxygen configuration file and the doxygen special comment blocks. I have not really studied the internal workings of doxygen and how it generates my PDF documentation.
Can you please attach a self-contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
I'm sorry I'm unable to reproduce the same problem in a small example and I'm unwilling to send my complete library. Also, I have opted to produce HTML documentation instead of PDF therefore I'm changing the severity of this bug report.
It is indeed hard to reproduce this problem but some severe effort it was possible, the problem is also quite sensible for small changes in the layout. I just pushed a proposed patch to github (pull request 600)
Has been integrated in the main branch of github (September 21. 2017)
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.14. 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 (preferably in the form of a self-contained example).