The thing is, I'm generating all of the projects myself. I have 3 different doxygen config files for 3 projects (Remember A, B, C before in my previous example). In addition, the order in which I process each project is linear and their dependencies are not.<div>
<br></div><div>What I really need is the ability to tell doxygen to do a "first pass" that does nothing more than generate tag files for projects that specify it with GENERATE_TAGFILE. If a project does not have this, it is simply ignored. I can then do a "second pass" which is the full build of documentation. Except this time, all of the tag files have been generated so it doesn't matter which order I build them in.</div>
<div><br></div><div>Chances are, most projects will do both: They will generate a tag file and also reference other tag files. All paths will be local, no URLs will be used to reference tag files.<br><br><div class="gmail_quote">
On Sat, Mar 28, 2009 at 6:44 AM, Benoit <span dir="ltr"><<a href="mailto:benpaka.spam@gmail.com">benpaka.spam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hy,<br><br>You should generate a B.tag file for the B library by setting in B.doxyfile the parameters: GENERATE_TAGFILE = B.tag<br>Then you could use B documentation in A by setting in A.doxyfile the parameters: TAGFILES : B.tag=<a href="http://yourserver/yourBdocpath/" target="_blank">http://yourserver/yourBdocpath/</a><br>
<br>Hope it can help you!<br><br>The only probleme you can have is the cross-dependencies, but it also a big probleme at link stage so you shouldn't have it.<br><br clear="all"><br>--<br>Benoit RAT<br><a href="http://www.neub.co.nr" target="_blank">www.neub.co.nr</a><br>
<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Sat, Mar 28, 2009 at 12:27 AM, Robert Dailey <span dir="ltr"><<a href="mailto:rcdailey@gmail.com" target="_blank">rcdailey@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex"><div><div></div><div class="h5">
Hi,<div><br></div><div>Suppose I have three C++ libraries called A, B, and C.</div><div><br></div><div>Each project has its own doxygen configuration file and doxygen processes documentation for each of them independently. The HTML output for each is located in A/html, B/html, and C/html on the filesystem.</div>
<div><br></div><div>If A has an explicit dependency on B (i.e., A uses classes from library B), how can I ensure that the HTML documentation for A knows how to find the documentation for B so that it may link to B's appropriate HTML files? There is the possibility of having to reference identifiers located in B's documentation from A's documentation.</div>
<div><br></div><div>If the best solution for this ends up being that I need to generate documentation for A, B, and C all in one go, what is the best way to do this?</div>
<br></div></div>------------------------------------------------------------------------------<br>
<br>_______________________________________________<br>
Doxygen-users mailing list<br>
<a href="mailto:Doxygen-users@lists.sourceforge.net" target="_blank">Doxygen-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/doxygen-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/doxygen-users</a><br>
<br></blockquote></div><br>
</blockquote></div><br></div>