Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doxygen should support tag files with same name (Origin: bugzilla #693406) #5060

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

status RESOLVED severity enhancement in component general for ---
Reported in version on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-02-08 09:43:01 +0000, wrote:

Created attachment 235492
TAG file issue

As an example, if one adds this to Doxyfile:


...only links to documentation in C will work while links to A and B will use the base URL of C and are therefore broken.
Attached you will find an example project.

Dimitri has confirmed that this is an issue because the tag file names are used to identify the link target.
So if two or more tag files have the same name, the base URL of the last of these in TAGFILES will be used for all of them.

Doxygen should support tag files with identical names, e.g., by identifying the link targets by tag file path (directory + filename).

On 2013-02-09 18:00:46 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-05-19 12:35:41 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

On 2015-08-29 15:04:19 +0000, Daniel Elstner wrote:

This change broke install-time rewriting of documentation references in our custom script in mm-common. We are now working around the issue by stripping the tagfile directory prefix in a post-processing step, so it's no longer a problem for us.

However, another visible side effect of this change is that the generated HTML files are now full of local path references leaked from the build environment, which is rather ugly.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.