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 606030 - @dot fails if used together with @defgroup
@dot fails if used together with @defgroup
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.6.2
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-01-04 17:07 UTC by Hubert Mackenberg
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hubert Mackenberg 2010-01-04 17:07:34 UTC
Doxygen fails with error

   Error opening map file xxx for inclusion in the docs!

if @dot is used inside a group.

Note: 
  - This appears to be different from Bug 525273
  - This is new in doxygen 1.6.2, it does not appear in doxygen 1.6.1


Example:

1. Create a file test.h with this contents:

        /** \defgroup test Test
         **
        \dot
           digraph example {
                // nodes
                A
                B

                // edges
                A -> B
           }
        \enddot
         **/

2. Create an default configuration file using:

      doxygen -g

3.  In Doxfile, change the following settings:

     INPUT                  = test.h
     HAVE_DOT               = YES

4. Run doxygen:

     doxygen

If test.h is located in D:/x23 you will get the following error message
(note the incorrect path D:/x23/html/D:/x23/html):

Error opening map file D:/x23/html/D:/x23/html/inline_dotgraph_1.dot.map for   inclusion in the docs!
If you installed Graphviz/dot after a previous failing run,
try deleting the output directory and rerun doxygen.
Comment 1 Dimitri van Heesch 2010-01-04 20:53:47 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2010-02-21 12:57:36 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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.