After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793088 - Including a .tag file for a library which itself includes a .tag file can provoke duplicate anchor warnings
Including a .tag file for a library which itself includes a .tag file can pro...
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: documentation
1.8.10
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2018-02-01 09:30 UTC by diarmuid.kieran
Modified: 2018-07-30 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Sample three libraries showing how this error occurs (375.52 KB, application/x-gzip)
2018-02-01 14:48 UTC, diarmuid.kieran
Details

Description diarmuid.kieran 2018-02-01 09:30:23 UTC
I have three libraries - libA, libB and libC. 

libA has a .dox file, which contains the following anchors: 

\section First_Section First Section 

\subsection First_Subsection First Subsection 

libB includes the tag file for libA as follows: 
@TAGFILES              =  $(DOXY_OUTPUT)/../libA/libA.tag=../libA 

libC includes the tag files for libA and libB, as follows: 

@TAGFILES              =  $(DOXY_OUTPUT)/../libA/libA.tag=../libA \ 
                                   $(DOXY_OUTPUT)/../libB/libB.tag=../libB 

However, when I run doxygen on libC in order to generate the documentation for libC, I see the following warning messages: 

libB.tag: warning: Duplicate anchor First_Section found 
libB.tag: warning: Duplicate anchor First_Subsection found 

It seems that, because libB uses the tagfile for libA, that when libC tries to use the tagfile for libB, it has in fact already obtained the anchors from libA and so it considers those it finds in libB relating to libA to be duplicates. 

I am using Doxygen 1.8.10.
Comment 1 albert 2018-02-01 10:01:24 UTC
- When cross linking please also mention other references: https://stackoverflow.com/questions/48559226/including-a-tag-file-for-a-library-which-itself-includes-a-tag-file-can-provok
- what happens with doxygen 1.8.14 (I don't expect a difference though)
- Can you please attach a self contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
Comment 2 diarmuid.kieran 2018-02-01 14:48:41 UTC
Created attachment 367759 [details]
Sample three libraries showing how this error occurs

To see warning message:
Navigate to libraryA, run doxygen
Navigate to libraryB, run doxygen
Navigate to libraryC, run doxygen, warnings are now displayed.

You will see the following warnings:

~/libraryB/html/libraryB.tag:11: warning: Duplicate anchor First_Section found

~/libraryB/html/libraryB.tag:11: warning: Duplicate anchor First_Subsection found

I tested this using doxygen 1.8.10.

I am not able to install doxygen 1.8.14, however, when I run the above with doxygen 1.8.13, I do not see the warning message. It seems that the bug is fixed after 1.8.10.
Comment 3 albert 2018-02-01 14:59:18 UTC
I ran the problem with 1.8.10 and with 1.8.14.

With 1.8.14 I got:
.../doxygen_sample/libraryB/html/libraryB.tag:11: warning: Duplicate anchor First_Section found

.../doxygen_sample/libraryB/html/libraryB.tag:11: warning: Duplicate anchor First_Subsection found


With 1.8.14 there were no warnings.

I think that this problem has ben solved in the mean time.
Comment 4 André Klapper 2018-07-30 10:12:05 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!