Is the entire API of interest to the end user? Perhaps only the interesting parts need doxygen applied.
On Wed, Dec 10, 2008 at 10:49 AM, Jonathan Robie <[EMAIL PROTECTED]> wrote: > Someone asked me why the API documentation is so large. About 27 Meg is due > to the HTML files, I am not aware of anything we can do to make that part > smaller. > > $ du -bc *html | grep total > 27,031,097 total > > The .md5 and .map files are used to optimize regeneration, they do not need > to be shipped with the documentation. > > $ du -bc *md5 | grep total > 34,976 total > $ du -bc *map | grep total > 1,456,027 total > > But the bulk of the size is due to the .png files: > > $ du -bc *png | grep total > 150,298,506 total > > You can get rid of 2/3 this by setting HAVE_DOT in user.doxygen to "NO" if > you don't want the class, collaboration, and group graphs: > > # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool > is > # available from the path. This tool is part of Graphviz, a graph > visualization > # toolkit from AT&T and Lucent Bell Labs. The other options in this > section > # have no effect if this option is set to NO (the default) > > HAVE_DOT = NO > > But it's still large: > > $ du -bc *png | grep total > 437,850 total > > Is the extra size worth it for these graphs? It's still pretty big even > without them. > > Jonathan > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
