So, I have a collection of projects that are documented using doxygen (and that should be doxygen). I run doxygen separately for each project and use the "link to external documentation" http://www.stack.nl/~dimitri/doxygen/manual/external.html to connect the documentation. For example, I import a tag file for a library project into another project where it is used. Thus, links to library classes are automatically generated when they are used in other project documentation.
Now for the problem, let's say I have a libA library that is used in another libB library. libA and libB have a main page. In the libB documentation, I import the tag file for libA. So far, so good, but now I have a third project that allows me to name this application, which uses both libA and libB. I import both tagfiles and links for both, but he also complains that the libA main page bindings are duplicated. I understand that they, since they are imported both through libB and into libA directly, however, if I do not import the libA tag file into the application, then links for the libA classes are not created.
Now the resulting documentation seems fine if I just import both tags and ignore the warnings, but the warnings will clutter the log file, so I can skip some other warning, for example, that I forgot to document the method or something like that.
So, any ideas how to solve this? Is this a bug in doxygen? Can I suppress this particular warning? Is there a better way to document a collection of projects like this with doxygen?
source
share