<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);"><blockquote type="cite">+ Doxygen API generation ? (Bjoern)<br> + done by Miklos just now - would like to hand it to sysadmin<br> + assuming it will get run regularly.<br> + <a dir="ltr" href="http://docs.libreoffice.org/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="28">http://docs.libreoffice.org/</a><br> + some multi-GB doxygen output - lots of images.</blockquote><br></span><div><span style="background-color: rgba(255, 255, 255, 0);">Just a quick comment: I made an update to the doxygen config file to generate SVGs, and also now use a doxygen controlled scroll and zoom UI. </span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div>I don't think that has increased file sizes.</div><div><br></div><div>However, with the way things work currently what I have noticed is actually the thing that is using most space are the tag files. I don't quite know how to do things much better (have experimented a bit) but the script currently generates tag files and html for each module, then as each module is built it references the previously generated tag files for the previous modules. After the clew module is built I noticed that we start getting massive tag files, over 450MB of text.</div><div><br></div><div>I was thinking maybe there might be a way of reworking the script to generate a tag file for each module first, then do another pass that generates the html from the tag files.</div><div><br></div><div>I don't know if this is feasible: I'm no doxygen expert unfortunately. I got this idea from a comment from the doxygen creator though, which detailed on Stack Overflow:</div><div><br></div><div><a href="http://stackoverflow.com/questions/8247189/doxygen-is-slow/8247993#8247993">http://stackoverflow.com/questions/8247189/doxygen-is-slow/8247993#8247993</a></div><div><br></div><div>Chris</div><div><br></div><div>P.S. There seems to be some issue in doxygen preventing it from matching function declarations and definitions due to it not picking up correct namespaces, in VCL I fixed this by ensuring that we use the css namespace alias, but this is not appropriate for other modules.</div><div><br></div><div>Was going to try to make a reduced test case, but found it hard to reproduce. I wonder if we should reach out to the doxygen guys?</div></div></body></html>