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 738548 - latex: dead links to source code
latex: dead links to source code
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.8
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-10-14 19:45 UTC by Dmitry
Modified: 2014-12-25 16:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Archive with two files: very simple header file and the doxygen file (29.64 KB, application/zip)
2014-10-14 19:45 UTC, Dmitry
Details

Description Dmitry 2014-10-14 19:45:55 UTC
Created attachment 288546 [details]
Archive with two files: very simple header file and the doxygen file

Doxygen has an option LATEX_SOURCE_CODE, if it is turned on, source code is included in the latex output; otherwise, sources aren't included, but resulting pdf file contains dead links, right after detailed description:

    Definition in file tn_mutex.h

Where tn_mutex.h is a dead link.

--

I've attached the archive with two files: very simple header file and the doxygen file. 

Steps to reproduce the problem:

  - download and unpack archive in some folder, cd to it
  - execute the following commands:
    $ cd <folder_where_archive_unpacked>
    $ doxygen test_doxyfile
    $ cd output/latex
    $ make
  - open refman.pdf file
  - look at the latest page, latest line: "Definition in file test.h", where "test.h" is a dead link (a link that actually brings me at the top of the document)
Comment 1 albert 2014-10-15 11:51:55 UTC
I've just pushed my proposed solution to github (pull request 239)
Comment 2 Dimitri van Heesch 2014-10-21 18:09:27 UTC
Thanks, I've pulled the change
Comment 3 Dimitri van Heesch 2014-12-25 16:03:38 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. 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 (preferrably in the form of a self-contained example).