[Doxygen-develop] tagfiles and external modules
Brought to you by:
dimitri
From: joe b. <be...@mc...> - 2001-11-29 19:08:24
|
I have been using the external documentation support in doxygen to produce a set of API documents for a set of C libraries. In my group, we use modules (@defgroup/@ingroup) to associate related parts of the documentation within a library, and are trying to use tagfiles to link together the documentation for separate libraries which may share data types, or perhaps document links to enums or functions from other libraries. However, when using tagfiles to link together the documentation, I've run into a couple of problems. One is that external modules (in another library's tagfile) are showing up in the modules page for libraries that use the tagfile. This makes the documentation for the higher-level libraries more cluttered. The first attachment is a patch which disables the listing of external modules in the module page. I'm also having problems linking to external functions and typedefs (structs are ok). The second attachment is a tarfile containing two sample modules, the second one which refers to a typedef, function, and struct in the first. If you create the documentation (make will do so) and look at the documentation in modules2/html/group__module2.html, you can see that links are not made for all of the elements in the tagfile (links foo and bar in particular are missing). I didn't make much progress in a quick check to find out why this was happening. thanks, joe |