GNOME Bugzilla – Bug 318002
Most of the links are broken in html output and the RTF output does not work (v. 1.4.5)
Last modified: 2018-07-30 10:20:19 UTC
Please describe the problem: Doxygen V.1.4.5 WINDOWS version - Using for the first time the version 1.4.5 on a open source project (Xerces-J-src.2.6.0) the RTF output is absolutly wrong and the html output is wrong in the 99% of cases. The input filer was *.java, obviously. Steps to reproduce: 1. For example use a large project like in my test (Xerces-J-src.2.6.0) 2. Use the GUI or manually set the Doxyfile for configuration (html and rtf only) 3. Try to browse the links Actual results: Most of the links are broken in html output and the RTF output does not work Expected results: Does this happen every time? YES Other information: I can post the list of the file in the html directory and the Doxyfile.
Created attachment 53049 [details] The Doxyfile config file This is the Doxyfile conf file used. Initially it was created by the GUI, then I have check it and changed something.
Created attachment 53050 [details] This is the directory listing of the html dir created by Doxygen This is the directory listing of the html dir created by Doxygen. On a fors impression something seems goes wrong...
The treeview option doesn't work with this Doxyfile: very strange!
I pretty sure your run of doxygen somehow ended prematurely. If I run doxygen the output directory in the end contains 6884 files and I couldn't find any broken links.
The doxygen was started by the Doxywizard GUI: this can explain the problem? My S.O. is Windows XP Home with all SP installed. Now I'll try to run the task without the GUI...
At the end of processing without the Doxywizard GUI, doxygen shows this lines: ========================== Generating dependency graph for directory C:/Kits/jakarta_apache_org/ xml_apache_org/XercesJsrc/Xerces-J-src.2.6.0/xerces-2_6_0/src/org/apache/ Cannot create file dir_C_3A_2FKits_2Fjakarta_5Fapache_5Forg_2Fxml_5Fapache_5Forg_2FXercesJsrc_2FXer ces_2DJ_2Dsrc_2E2_2E6_2E0_2Fxerces_2D2_5F6_5F0_2Fsr c_2Forg_2Fapache_2F_dep.dot for writing! QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open QFile::writeBlock: File not open Error: Could not open image `dir_C_3A_2FKits_2Fjakarta_5Fapache_5Forg_2Fxml_5Fapache_5Forg_2FXercesJsrc_2FXe rces_2DJ_2Dsrc_2E2_2E6_2E0_2Fxerces_2D2_5F 6_5F0_2Fsrc_2Forg_2Fapache_2F_dep.png' generated by dot! Error opening map file dir_C_3A_2FKits_2Fjakarta_5Fapache_5Forg_2Fxml_5Fapache_5Forg_2FXercesJsrc_2FXer ces_2DJ_2Dsrc_2E2_2E6_2E0_2Fxerces_2D2_5F6_5F0_ 2Fsrc_2Forg_2Fapache_2F_dep.map for inclusion in the docs! Could not open file C:/Kits/jakarta_apache_org/xml_apache_org/XercesJsrc/Xerces- J-src.2.6.0/xerces-2_6_0/src/doxygen/html/dir_C_3A_2FKits_2Fjakarta_5F apache_5Forg_2Fxml_5Fapache_5Forg_2FXercesJsrc_2FXerces_2DJ_2Dsrc_2E2_2E6_2E0_2F xerces_2D2_5F6_5F0_2Fsrc_2Forg_2Fapache_2Fxerces_2Fdom3_2Fas_2F.html f or writing ========================== I help this can be useful...
Testing the same input with Linux there isn't any problem: all is OK and the processing is very fast! Then I suppose that the problem in the Windows version od doxygen can be happen for a memory problem, perhaps not trapped with an exception. Another problem can be the file name too long that generate the error "QFile::writeBlock: File not open". What is the max file name size in Windows? This file is 158 bytes long and the dir name is 100 bytes long then we have 258 bytes for the full file name: this may be a problem... I remember that the default size in an (old) S.O. for a full file name was 255 bytes...
I think it is indeed a file name length issue. You use a full path as INPUT, this makes the encoded directoy name very long. You could try to use a relative path (i.e. put the Doxyfile in the root of the package and use INPUT=src or so). Could you try this? In the next release I plan to use a shorter encoding of directory names again. The Linux version of doxygen is indeed faster, mainly because Linux does a much better job at disk IO, and the filesystem doesn't become extremely slow when putting a lot of files in one directory.
Even using the relative path in the Doxyfile, the doxygen procedure doesn't work fine: ... ... (a lot of logs info) ... ... Generating docs for file C:/Kits/jakarta_apache_org/xml_apache_org/XercesJsrc/ Xerces-J-src.2.6.0/xerces-2_6_0/src/org/w3c/dom/xpath/XPathNSResolver.java... Generating docs for file C:/Kits/jakarta_apache_org/xml_apache_org/XercesJsrc/ Xerces-J-src.2.6.0/xerces-2_6_0/src/org/w3c/dom/xpath/XPathResult.java... Generating class documentation... Generating annotated compound index... Generating alphabetical compound index... Generating hierarchical class index... Generating member index... Generating docs for compound Cloneable... Generating docs for compound ContentDispatcher... Generating docs for compound Dispatcher... Generating docs for compound Error... Generating docs for compound FragmentContentDispatcher... Generating docs for compound javax::xml::parsers::SAXParser... Generating docs for compound RuntimeException... Generating docs for compound java::io::Serializable... Generating page documentation... Generating docs for page deprecated... Generating group documentation... Generating directory documentation... Could not open file C:/Kits/jakarta_apache_org/xml_apache_org/XercesJsrc/Xerces- J-src.2.6.0/xerces-2_6_0/src/doxygen/html/ dir_C_3A_2FKits_2Fjakarta_5Fapache_5Forg_2Fxml_5Fapache_5Forg_2FXercesJsrc_2FXer ces_2DJ_2Dsrc_2E2_2E6_2E0_2Fxerces_2D2_5F6_5F0_2Fsrc_2Forg_2Fapache_2Fxerces_2Fd om3_2Fas_2F.html for writing Then the doxygen applications exit... Plese note that I have define USE_DOT=NO in the Doxyfile and used only the relative path in the input and output dir setting (OUTPUT_DIRECTORY and INPUT config parameters). The last file in the log is 176 bytes long...
reopening as requested information has been provided. paolo, do you still face this issue? if so, which version are you running?
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!