[Doxygen-users] External Documentation

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello,

I was wondering if anyone could provide a complete working example of
linking external documentation (eg a working example of the one given in
doxygen manual, about 'proj' 'ext1' and 'ext2' would be great.

Why? I can't get external documentation to work, no matter how hard I try
:-) I've created a common C library that is shared between multiple C
projects. Because these C projects have naming conflicts (I'm constrained by
an API) they cannot be compiled together, and doxygen gets confused if I
build the whole lot in one go because it quite rightly can't tell my
functions apart.

All the doxygen output is perfect if a build proj1 + library, proj2 +
library etc but this is slow and means I have multiple copies of the library
code. The closest I have got is producing a tagfile for the library
(contents look OK, but I'm no expert). The library html output is perfect.
Then for proj1, say, I set the TAGFILES parameter to <tagfile>=<html
directory>. I've tried many permutations of dynamic and static paths,
location of the files. I've also tried using the perl script. Everything has
the same result: external links are left as local link that point nowhere.
This local link looks correct, all that is needed is replacing part of the
path. ie C:\blah\foo\proj1\someDoc.html is what I have, and
C:\blah\foo\ext1\someDoc.html is what I want.

I've also tried reproducing the simple example in the doxygen docs, but
exactly the same thing happens. Hence my request, which is probably the
quickest way for me to get sorted out.

If I do get it sorted out I'll knock up some documentation and put a
'tutorial' on the web for other hopeless cases!

Cheers,

Josh.