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 711386 - Patch for disabling source link in classes and class members
Patch for disabling source link in classes and class members
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: build
1.8.5
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2013-11-04 10:23 UTC by Tom Ghyselinck
Modified: 2018-07-30 10:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
SOURCE_DEFINITION patch (945 bytes, patch)
2013-11-04 10:23 UTC, Tom Ghyselinck
none Details | Review

Description Tom Ghyselinck 2013-11-04 10:23:35 UTC
Created attachment 258905 [details] [review]
SOURCE_DEFINITION patch

Hi all,

We have a special use case of doxygen:

1. We have TCL classes which are implemented in C++.
To generate the documentation, we create a "dummy" (TCL) source file (api.tcl)
which just defines the class and the methods (with their arguments)
without implementation.

During documentation generation, the source code in the file is filtered out
Doxyfile:
    FILTER_SOURCE_FILES = YES
    FILTER_SOURCE_PATTERNS = *api.tcl="api_source_filter.sh"
with api_source_filter.sh being an empty file.

This source code is not desired in our doxygen files listing output,
nor do we want any link to the "filtered-out" source code.



This would work great if we have SOURCE_BROWSER = NO in our Doxyfile, but:

2. We also provide documentation for wrapper scripts for our TCL API.
This part includes (open-source) scripts and tools to ease the use of our API (described in 1.).
This documentation is listed in the Files section of doxygen. So we explicitly need SOURCE_BROWSER = YES in order to make this work.



Another option is to split up the documentation it 2 parts, but:

3. There are some restrictions to do this:
    * The API and TCL wrapper scripts refer to each other
    * We also have example pages which refer to the API and wrapper and vice versa.
  So the documentation MUST be in one Doxygen project.



To remove the linking to the source file in classes and class members,
we created a patch for doxygen 1.8.5 release (see attachment).
It can be controlled by the SOURCE_DEFINITION configuration item.
Linking to the source is still enabled by default.

Note that our patch does not remove the links to source code
for documentation in the Files section!

Any comments or other suggestions for our change are very welcome!

If there are any other suggestions for our flexible documentation,
please let us know!

With best regards,
Tom.
Comment 1 André Klapper 2018-07-30 10:13:37 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!