Raimund --

On Wed, Feb 27, 2013 at 5:48 AM, Klein, Raimund
<raimund.kl...@berenberg.de>wrote:

> However, my experience regarding the placement of documentation files is
> the same as Tom’s: The directory paths are non-predictable and pretty much
> change with every run. That might be related to new source files being
> added, but adding new files is more or less an everyday process. No matter
> what, permanent paths definitely don’t work for us (believe me, I’ve tried).
>

Even using current release and long filenames (i.e., SHORT_NAMES=no)?  That
surprises me.

I can see the anchors changing -- I'm pretty sure they're a hash of
filename + line number, so any code motion will invalidate them -- but if
you use the long filenames option, the anchorfiles themselves shouldn't
change.

Maybe there's some combination of options that modifies the incoming
filenames before the path-to-anchorfile transform is done.  In my codebase,
with my config file, I don't see the anchorfiles changing.

****
>
> The idea of the wiki interpreting the tag files sounds interesting, I’ll
> try digging into this. However, in our case, the Wiki and the doxygen
> documentation are on two different machines which don’t really know much
> about each other, so I’m not sure if it even will be possible to make the
> tagfiles visible.
>

Hm.  You might still be able to post-process the tag file on the doxygen
machine, so that you can create your wiki links to:

http://doxygen-machine/index.html#filename:compoundname:membername:signature

(Or something similar)

Requires an extra click, or some javascript, but that would provide the
extra layer of indirection to handle the changes.


> ****
>
> ** **
>
> Since you were asking, the Javadoc tool handles this actually in a
> straightforward way: The generated documentation represents the source
> files’ package structure. Thus, the directory paths are not only stable,
> but actually predictable just by looking at the source code. Most likely
> this mechanism relies on Java’s specific requirement that the directory
> structures must match the package structures.
>

Makes sense, and I probably could have looked it up myself.  :)  Been a
long while since I've worked with Java...

Good luck!

Best regards,
Anthony Foiani
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to