You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On 2016-03-10 19:36:32 +0000, Sebastien Loriot wrote:
Created attachment 323659
minimal example showing the pb
Setting:
A is a project with no dependency
B imports A.tag
C imports A.tag and B.tag
The mainpage from project A has a section in its mainpage (A/main.txt) which anchor is copied in tagfiles of project B and C, triggering a duplicate anchor warning during the compilation of project C.
How to reproduce using the attachement:
cd doxy_br/A && doxygen && cd ../B && doxygen && cd ../C && doxygen
The bugreport is done over 1.8.11 because master@7584c292 seems to not produce mainpages (thus the bug reported here cannot be observed).
On 2016-03-14 19:42:20 +0000, Dimitri van Heesch wrote:
The master version does still produce mainpages, but no longer parses .txt files as if they were C files (which was a bit strange and error prone anyway).
If you still want this behavior, please configure doxygen as follows:
EXTENSION_MAPPING = txt=C
The warning should be fixed in the next GIT update.
On 2016-05-25 21:15:59 +0000, Sebastien Loriot wrote:
I confirm that the warnings are gone. However in the full project (not the minimal example), the size of the tag file keeps growing after each run. Do you want me to open a new ticket for this?
On 2016-05-26 22:02:38 +0000, Dimitri van Heesch wrote:
Yes please. Try to include an example if possible, or at least the delta between subsequent tag files showing what was added as growth.
On 2016-09-05 13:45:49 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).
The text was updated successfully, but these errors were encountered:
status RESOLVED severity normal in component general for ---
Reported in version 1.8.11 on platform Other
Assigned to: Dimitri van Heesch
Original attachment names and IDs:
On 2016-03-10 19:36:32 +0000, Sebastien Loriot wrote:
On 2016-03-14 19:42:20 +0000, Dimitri van Heesch wrote:
On 2016-05-25 21:15:59 +0000, Sebastien Loriot wrote:
On 2016-05-26 22:02:38 +0000, Dimitri van Heesch wrote:
On 2016-09-05 13:45:49 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: