RE: [Doxygen-users] Using doxygen with large projects

[Glenn M. <gle...@vo...>]

Hi Ray,

You already have the solution. Break your system up into smaller pieces.
Have separate doxygen project files for the various subsystems. They
each can output to their own directories. The advantage of this is that
each subset will run faster. If something changes, you won't necessarily
have to regenerate the world.

For dependencies between systems, you need to generate tag files and
include them where appropriate in other project files. These are two
options that are documented (tersely) in the default Doxygen project
file.

Note: If two sub-systems depend upon each other, you may have to run
Doxygen twice so that it can resolve things using the tag files.

I successfully use this technique and it works like a charm.

I admit, however, that I wrote some homegrown Perl tools to wrap the
multiple outputs from Doxygen (and HTML output from various FrameMaker
books) into a comprehensive help system. For information available upon
request.=20

HTH,

Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
gle...@vo...


> -----Original Message-----
> From: Ray F. Cowan [mailto:rf...@SL...]
> Sent: Monday, December 17, 2001 1:56 PM
> To: dox...@li...
> Cc: Stephen Gowdy; Ruth Schmitz
> Subject: [Doxygen-users] Using doxygen with large projects
>=20
>=20
> Hi,
>=20
> I am attempting to use doxygen to produce docs for a rather large C++
> project, about 1000 packages containing in total some 20,000=20
> individual
> {.cc,.hh} files.  This is the bulk of the software used by=20
> the international
> high-energy physics experiment, BaBar=20
> (www-public.slac.stanford.edu/babar).
>=20
> However, attempts to run doxygen fail when running on our=20
> complete code base;
> on a linux box doxygen runs for four hours or so in the=20
> 'Reading input files'
> stage, reaches around 900 MB of memory use, then aborts.
>=20
> Doxygen runs fine on small subsets of our code,
> so I think our problem is due to the large amount of source=20
> code when running all of it together.
>=20
> Another problem--assuming we can get doxygen to run on our=20
> code--is that all
> the output html files are placed in a single directory. =20
=20
> Any suggestions for solving these problems would be=20
> appreciated.  Thanks much.
>=20