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 645742 - Cannot link symbols from doxytag file in comments
Cannot link symbols from doxytag file in comments
Status: RESOLVED DUPLICATE of bug 635537
Product: doxygen
Classification: Other
Component: general
1.7.3
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-03-26 12:19 UTC by Michael Henry
Modified: 2011-03-26 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Demonstrates problem linking to symbols using doxytag (1.77 KB, text/plain)
2011-03-26 12:23 UTC, Michael Henry
Details

Description Michael Henry 2011-03-26 12:19:25 UTC
Symbols defined in a doxytag file are not linked properly when
referenced from the context of a comment, though they *are*
properly linked when referenced from within normal code.  For
example, a reference like this:

/** The symbol ::Lib_variable is defined in a doxytag. */

fails with a warning:
  explicit link request to 'Lib_variable' could not be resolved

**Warning** Attached script destroys and re-creates the directory doxytag_bug.

Attached is a script that creates a complete example to demonstrate
the problem.  Note that the comment for App_function fails to
link to symbols from Lib, yet the body of App_function successfully
links to these same symbols.  Locally defined symbols are successfully
linked both in the comments and in the function body.

Operating system: Fedora 11, Ubuntu 10.10
Doxygen version: 1.7.3 release
Comment 1 Michael Henry 2011-03-26 12:23:58 UTC
Created attachment 184283 [details]
Demonstrates problem linking to symbols using doxytag
Comment 2 Dimitri van Heesch 2011-03-26 12:48:18 UTC
I think this is related to bug 635537. I'm my working version the warning is no longer generated.

*** This bug has been marked as a duplicate of bug 635537 ***