doxygen-users — List for users of doxygen

[Doxygen-users] Documentation for typedefs not generated, C++ code

[Sam V. <mr...@co...>]

With doxygen-1.8.12, in an otherwise empty directory:

$ doxygen -g


Configuration file `Doxyfile' created.

Now edit the configuration file and enter

  doxygen Doxyfile

to generate the documentation for your project

$ cat >foo.hh

//! A documented typedef

typedef int zz;
[mrsam@octopus zz]$ doxygen
Searching for include files..

The resulting documentation in the html directory is empty. The typedef is  
not documented. The generated documentation does have a "Files" section,  
that dutifully includes the foo.hh file, showing the typedef inside it, but  
with the doxygen comment block removed.

Replacing the typedef with "class zz{};" results in the expected output.

I must be missing something obvious.

[Doxygen-users] (no subject)

[Nick N. <nic...@ya...>]

Unable to show full message.Please click here to view this message
=============
Browser error code: t9fs612/1/2016 11:13:39 AM

[Doxygen-users] Auto-Assigning to Modules

[Christoph L. <chr...@li...>]

Is it possible to automatically assign stuff (files, namespaces,
classes, macros, functions, whatever) to modules without having to
specify this in each source file explicitly?

For example, if a particular directory is assigned to a module, is it
possible to have all the files and subdirectories in that directory to
also be assigned to that module by default?

Likewise, if a particular file is assigned to a module, is it possible
to have all the classes and structures and other stuff defined therein
to also be assigned to that module by default?

Alternatively, if a particular namespace is assigned to a module, is it
possible to automatically have all the stuff in that namespace to also
be assigned to that module by default?

So far I haven't had any success with that.

Re: [Doxygen-users] Additional underscore character added in links to included files 1.8.12

[trosh <jg....@gm...>]

> Please check if things work properly again in the latest version from
Github.

That fixed my problems !

Thanks a bunch for the fast fix :-)

Regards,
John



--
View this message in context: http://doxygen.10944.n7.nabble.com/Additional-underscore-character-added-in-links-to-included-files-1-8-12-tp7734p7765.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Additional underscore character added in links to included files 1.8.12

[Dimitri v. H. <do...@gm...>]

Please check if things work properly again in the latest version from Github.
In particular with this commit included:
https://github.com/doxygen/doxygen/commit/dc02bb977ebc6c683012c106e16e0190ac72b454

Regards,
  Dimitri

> On 28 Nov 2016, at 13:59 , trosh <jg....@gm...> wrote:
> 
> I don't know to what extent this is related, but I have other issues in name
> mangling for includes. (This happens to me when working with tagfiles across
> projects.)
> 
> On top of _ characters being doubled, I have more complex weird
> reinterpretation of urls : for example, a link which should point to
>    .../html/d6/d40/err_8h.html
> in another project actually points to
>    .../html/d1/d4c/d6_2d40_2err__8h.html
> 
> This seems to happen because of subfolder includes like "proj/base/err.h"
> 
> 
> 
> --
> View this message in context: http://doxygen.10944.n7.nabble.com/Additional-underscore-character-added-in-links-to-included-files-1-8-12-tp7734p7762.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Custom "Modules" page

[Christoph L. <chr...@li...>]

Is it possible to add custom text to the main "Modules" page? If so, how?

Re: [Doxygen-users] Additional underscore character added in links to included files 1.8.12

[trosh <jg....@gm...>]

I don't know to what extent this is related, but I have other issues in name
mangling for includes. (This happens to me when working with tagfiles across
projects.)

On top of _ characters being doubled, I have more complex weird
reinterpretation of urls : for example, a link which should point to
    .../html/d6/d40/err_8h.html
in another project actually points to
    .../html/d1/d4c/d6_2d40_2err__8h.html

This seems to happen because of subfolder includes like "proj/base/err.h"



--
View this message in context: http://doxygen.10944.n7.nabble.com/Additional-underscore-character-added-in-links-to-included-files-1-8-12-tp7734p7762.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Remove strange character

[Albert <alb...@gm...>]

The code has to be placed in an own style sheet (e.g. my.css) and ths style
sheet has to be made available in HTML_EXTRA_STYLESHEET

On Tue, Nov 22, 2016 at 6:55 PM, Olivier Couet <Oli...@ce...>
wrote:

> Can you send the actuel code you have ? .. it might be some hidden
> characters.
>
>
> > On 22 Nov 2016, at 17:10, dumas_brian <dum...@st...>
> wrote:
> >
> > In some 'c' functions that I export, the function name is preceded by
> this
> > character '§ '.
> >
> > Is that something I can remove?
> >
> > Image shows the character
> > <http://doxygen.10944.n7.nabble.com/file/n7758/11-22-
> 2016_10-37-23_AM.jpg>
> >
> >
> >
> > --
> > View this message in context: http://doxygen.10944.n7.
> nabble.com/Remove-strange-character-tp7758.html
> > Sent from the Doxygen - Users mailing list archive at Nabble.com.
> >
> > ------------------------------------------------------------
> ------------------
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Remove strange character

[Olivier C. <Oli...@ce...>]

Can you send the actuel code you have ? .. it might be some hidden characters.


> On 22 Nov 2016, at 17:10, dumas_brian <dum...@st...> wrote:
> 
> In some 'c' functions that I export, the function name is preceded by this
> character '§ '.
> 
> Is that something I can remove?
> 
> Image shows the character
> <http://doxygen.10944.n7.nabble.com/file/n7758/11-22-2016_10-37-23_AM.jpg> 
> 
> 
> 
> --
> View this message in context: http://doxygen.10944.n7.nabble.com/Remove-strange-character-tp7758.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Remove strange character

[Albert <alb...@gm...>]

It is possible. Create a HTML_EXTRA_STYLESHEET and place in this:

.permalink{
        display: none;}

See also:
http://stackoverflow.com/questions/40389959/how-to-eliminate-silcrow-paragraph-sign-in-doxygen-for-python

On Tue, Nov 22, 2016 at 5:10 PM, dumas_brian <dum...@st...>
wrote:

> In some 'c' functions that I export, the function name is preceded by this
> character '§ '.
>
> Is that something I can remove?
>
> Image shows the character
> <http://doxygen.10944.n7.nabble.com/file/n7758/11-22-2016_10-37-23_AM.jpg>
>
>
>
> --
> View this message in context: http://doxygen.10944.n7.
> nabble.com/Remove-strange-character-tp7758.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Remove strange character

[dumas_brian <dum...@st...>]

In some 'c' functions that I export, the function name is preceded by this
character '§ '.

Is that something I can remove?

Image shows the character
<http://doxygen.10944.n7.nabble.com/file/n7758/11-22-2016_10-37-23_AM.jpg> 



--
View this message in context: http://doxygen.10944.n7.nabble.com/Remove-strange-character-tp7758.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Two enums with same enumerator name generates incorrect output

[using <jim...@gm...>]

I have submitted a bug report for this.



--
View this message in context: http://doxygen.10944.n7.nabble.com/Two-enums-with-same-enumerator-name-generates-incorrect-output-tp7755p7757.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Two enums with same enumerator name generates incorrect output

[Richard D. <Ri...@Da...>]

On 11/19/16 7:10 AM, using wrote:
> I have the following in a file:
>
> namespace ns {
>      /// \struct A DoxyTest.h
>      struct A
>      {
>          /// \enum A::Enum1
>          /// \var e1
>          /// This is e1
>          /// \var e2
>          /// This is e2
>          enum class Enum1 {
>              e1,
>              e2
>          };
>
>          /// \enum A::Enum2
>          /// \var e3
>          /// This is e3
>          /// \var e2
>          /// This is another e2
>          enum class Enum2 {
>              e3,
>              e2
>          };
>      };
> }
>
> Note that both Enum1 and Enum2 have enumerators called 'e2'. The output from
> Doxygen puts the documentation for both into Enum1::e2. Enum2::e2 is not
> shown at all as seen in the image below. I found  a related topic
> <http://doxygen.10944.n7.nabble.com/enum-value-of-quot-NONE-quot-is-not-understood-by-Doxygen-td6541.html#a6549>
> , but there was no stated resolution other than maybe posting a bug report.
>
> So, is there any way around this problem? Renaming Enum2::e2 to Enum2::e4 is
> not an acceptable option.
>
> <http://doxygen.10944.n7.nabble.com/file/n7755/enum.png>
>
The issue may be that without the 'class' keyword in the definitions, 
your code would be invalid as both e2's would actually be ns:A:e2, so in 
conflict with each other. The referenced related issue looks to be 
exactly that (Not being in the same Translation Unit, the error is not 
required to be diagnosed, but I think still technically a violation of 
the One Definition Rule, which probably is what gives Doxygen the problem).

It may be that Doxygen doesn't fully support the enum class construct, 
and is still keeping track of the enumeration values in the ns::A 
namespace, and not in the appropriate Enum# sub-namespace therein.


-- 
Richard Damon

[Doxygen-users] Two enums with same enumerator name generates incorrect output

[using <jim...@gm...>]

I have the following in a file:

namespace ns {
    /// \struct A DoxyTest.h
    struct A
    {
        /// \enum A::Enum1
        /// \var e1
        /// This is e1
        /// \var e2
        /// This is e2
        enum class Enum1 {
            e1,
            e2
        };

        /// \enum A::Enum2
        /// \var e3
        /// This is e3
        /// \var e2
        /// This is another e2
        enum class Enum2 {
            e3,
            e2
        };
    };
}

Note that both Enum1 and Enum2 have enumerators called 'e2'. The output from
Doxygen puts the documentation for both into Enum1::e2. Enum2::e2 is not
shown at all as seen in the image below. I found  a related topic
<http://doxygen.10944.n7.nabble.com/enum-value-of-quot-NONE-quot-is-not-understood-by-Doxygen-td6541.html#a6549> 
, but there was no stated resolution other than maybe posting a bug report.

So, is there any way around this problem? Renaming Enum2::e2 to Enum2::e4 is
not an acceptable option.

<http://doxygen.10944.n7.nabble.com/file/n7755/enum.png> 

And here is the config file:

# Doxyfile 1.8.12

#---------------------------------------------------------------------------
# Project related configuration options
#---------------------------------------------------------------------------
DOXYFILE_ENCODING      = UTF-8
PROJECT_NAME           = DoxyTest
PROJECT_NUMBER         = 1.0
PROJECT_BRIEF          = 
PROJECT_LOGO           = 
OUTPUT_DIRECTORY       =
C:\Users\jimor_000\Source\Repos\ConsoleTestApp\Documentation
CREATE_SUBDIRS         = NO
ALLOW_UNICODE_NAMES    = NO
OUTPUT_LANGUAGE        = English
BRIEF_MEMBER_DESC      = YES
REPEAT_BRIEF           = YES
ABBREVIATE_BRIEF       = "The $name class" \
                         "The $name widget" \
                         "The $name file" \
                         is \
                         provides \
                         specifies \
                         contains \
                         represents \
                         a \
                         an \
                         the
ALWAYS_DETAILED_SEC    = NO
INLINE_INHERITED_MEMB  = NO
FULL_PATH_NAMES        = YES
STRIP_FROM_PATH        = 
STRIP_FROM_INC_PATH    = 
SHORT_NAMES            = NO
JAVADOC_AUTOBRIEF      = NO
QT_AUTOBRIEF           = NO
MULTILINE_CPP_IS_BRIEF = NO
INHERIT_DOCS           = YES
SEPARATE_MEMBER_PAGES  = NO
TAB_SIZE               = 4
ALIASES                = 
TCL_SUBST              = 
OPTIMIZE_OUTPUT_FOR_C  = NO
OPTIMIZE_OUTPUT_JAVA   = NO
OPTIMIZE_FOR_FORTRAN   = NO
OPTIMIZE_OUTPUT_VHDL   = NO
EXTENSION_MAPPING      = 
MARKDOWN_SUPPORT       = YES
TOC_INCLUDE_HEADINGS   = 0
AUTOLINK_SUPPORT       = YES
BUILTIN_STL_SUPPORT    = NO
CPP_CLI_SUPPORT        = NO
SIP_SUPPORT            = NO
IDL_PROPERTY_SUPPORT   = YES
DISTRIBUTE_GROUP_DOC   = NO
GROUP_NESTED_COMPOUNDS = NO
SUBGROUPING            = YES
INLINE_GROUPED_CLASSES = NO
INLINE_SIMPLE_STRUCTS  = NO
TYPEDEF_HIDES_STRUCT   = NO
LOOKUP_CACHE_SIZE      = 0
#---------------------------------------------------------------------------
# Build related configuration options
#---------------------------------------------------------------------------
EXTRACT_ALL            = NO
EXTRACT_PRIVATE        = NO
EXTRACT_PACKAGE        = NO
EXTRACT_STATIC         = NO
EXTRACT_LOCAL_CLASSES  = YES
EXTRACT_LOCAL_METHODS  = NO
EXTRACT_ANON_NSPACES   = NO
HIDE_UNDOC_MEMBERS     = NO
HIDE_UNDOC_CLASSES     = NO
HIDE_FRIEND_COMPOUNDS  = NO
HIDE_IN_BODY_DOCS      = NO
INTERNAL_DOCS          = NO
CASE_SENSE_NAMES       = NO
HIDE_SCOPE_NAMES       = NO
HIDE_COMPOUND_REFERENCE= NO
SHOW_INCLUDE_FILES     = YES
SHOW_GROUPED_MEMB_INC  = NO
FORCE_LOCAL_INCLUDES   = NO
INLINE_INFO            = YES
SORT_MEMBER_DOCS       = YES
SORT_BRIEF_DOCS        = NO
SORT_MEMBERS_CTORS_1ST = NO
SORT_GROUP_NAMES       = NO
SORT_BY_SCOPE_NAME     = NO
STRICT_PROTO_MATCHING  = NO
GENERATE_TODOLIST      = YES
GENERATE_TESTLIST      = YES
GENERATE_BUGLIST       = YES
GENERATE_DEPRECATEDLIST= YES
ENABLED_SECTIONS       = 
MAX_INITIALIZER_LINES  = 30
SHOW_USED_FILES        = YES
SHOW_FILES             = YES
SHOW_NAMESPACES        = YES
FILE_VERSION_FILTER    = 
LAYOUT_FILE            = 
CITE_BIB_FILES         = 
#---------------------------------------------------------------------------
# Configuration options related to warning and progress messages
#---------------------------------------------------------------------------
QUIET                  = NO
WARNINGS               = YES
WARN_IF_UNDOCUMENTED   = YES
WARN_IF_DOC_ERROR      = YES
WARN_NO_PARAMDOC       = NO
WARN_AS_ERROR          = NO
WARN_FORMAT            = "$file:$line: $text"
WARN_LOGFILE           = 
#---------------------------------------------------------------------------
# Configuration options related to the input files
#---------------------------------------------------------------------------
INPUT                  =
C:\Users\jimor_000\Source\Repos\ConsoleTestApp\ConsoleTestApp
INPUT_ENCODING         = UTF-8
FILE_PATTERNS          = *.c \
                         *.cc \
                         *.cxx \
                         *.cpp \
                         *.c++ \
                         *.java \
                         *.ii \
                         *.ixx \
                         *.ipp \
                         *.i++ \
                         *.inl \
                         *.idl \
                         *.ddl \
                         *.odl \
                         *.h \
                         *.hh \
                         *.hxx \
                         *.hpp \
                         *.h++ \
                         *.cs \
                         *.d \
                         *.php \
                         *.php4 \
                         *.php5 \
                         *.phtml \
                         *.inc \
                         *.m \
                         *.markdown \
                         *.md \
                         *.mm \
                         *.dox \
                         *.py \
                         *.pyw \
                         *.f90 \
                         *.f95 \
                         *.f03 \
                         *.f08 \
                         *.f \
                         *.for \
                         *.tcl \
                         *.vhd \
                         *.vhdl \
                         *.ucf \
                         *.qsf
RECURSIVE              = NO
EXCLUDE                = 
EXCLUDE_SYMLINKS       = NO
EXCLUDE_PATTERNS       = 
EXCLUDE_SYMBOLS        = 
EXAMPLE_PATH           = 
EXAMPLE_PATTERNS       = *
EXAMPLE_RECURSIVE      = NO
IMAGE_PATH             = 
INPUT_FILTER           = 
FILTER_PATTERNS        = 
FILTER_SOURCE_FILES    = NO
FILTER_SOURCE_PATTERNS = 
USE_MDFILE_AS_MAINPAGE = 
#---------------------------------------------------------------------------
# Configuration options related to source browsing
#---------------------------------------------------------------------------
SOURCE_BROWSER         = NO
INLINE_SOURCES         = NO
STRIP_CODE_COMMENTS    = YES
REFERENCED_BY_RELATION = NO
REFERENCES_RELATION    = NO
REFERENCES_LINK_SOURCE = YES
SOURCE_TOOLTIPS        = YES
USE_HTAGS              = NO
VERBATIM_HEADERS       = YES
CLANG_ASSISTED_PARSING = NO
CLANG_OPTIONS          = 
#---------------------------------------------------------------------------
# Configuration options related to the alphabetical class index
#---------------------------------------------------------------------------
ALPHABETICAL_INDEX     = YES
COLS_IN_ALPHA_INDEX    = 5
IGNORE_PREFIX          = 
#---------------------------------------------------------------------------
# Configuration options related to the HTML output
#---------------------------------------------------------------------------
GENERATE_HTML          = YES
HTML_OUTPUT            = html
HTML_FILE_EXTENSION    = .html
HTML_HEADER            = 
HTML_FOOTER            = 
HTML_STYLESHEET        = 
HTML_EXTRA_STYLESHEET  = 
HTML_EXTRA_FILES       = 
HTML_COLORSTYLE_HUE    = 220
HTML_COLORSTYLE_SAT    = 100
HTML_COLORSTYLE_GAMMA  = 80
HTML_TIMESTAMP         = NO
HTML_DYNAMIC_SECTIONS  = NO
HTML_INDEX_NUM_ENTRIES = 100
GENERATE_DOCSET        = NO
DOCSET_FEEDNAME        = "Doxygen generated docs"
DOCSET_BUNDLE_ID       = org.doxygen.Project
DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
DOCSET_PUBLISHER_NAME  = Publisher
GENERATE_HTMLHELP      = NO
CHM_FILE               = 
HHC_LOCATION           = 
GENERATE_CHI           = NO
CHM_INDEX_ENCODING     = 
BINARY_TOC             = NO
TOC_EXPAND             = NO
GENERATE_QHP           = NO
QCH_FILE               = 
QHP_NAMESPACE          = org.doxygen.Project
QHP_VIRTUAL_FOLDER     = doc
QHP_CUST_FILTER_NAME   = 
QHP_CUST_FILTER_ATTRS  = 
QHP_SECT_FILTER_ATTRS  = 
QHG_LOCATION           = 
GENERATE_ECLIPSEHELP   = NO
ECLIPSE_DOC_ID         = org.doxygen.Project
DISABLE_INDEX          = NO
GENERATE_TREEVIEW      = NO
ENUM_VALUES_PER_LINE   = 4
TREEVIEW_WIDTH         = 250
EXT_LINKS_IN_WINDOW    = NO
FORMULA_FONTSIZE       = 10
FORMULA_TRANSPARENT    = YES
USE_MATHJAX            = NO
MATHJAX_FORMAT         = HTML-CSS
MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
MATHJAX_EXTENSIONS     = 
MATHJAX_CODEFILE       = 
SEARCHENGINE           = YES
SERVER_BASED_SEARCH    = NO
EXTERNAL_SEARCH        = NO
SEARCHENGINE_URL       = 
SEARCHDATA_FILE        = searchdata.xml
EXTERNAL_SEARCH_ID     = 
EXTRA_SEARCH_MAPPINGS  = 
#---------------------------------------------------------------------------
# Configuration options related to the LaTeX output
#---------------------------------------------------------------------------
GENERATE_LATEX         = NO
LATEX_OUTPUT           = latex
LATEX_CMD_NAME         = latex
MAKEINDEX_CMD_NAME     = makeindex
COMPACT_LATEX          = NO
PAPER_TYPE             = a4
EXTRA_PACKAGES         = 
LATEX_HEADER           = 
LATEX_FOOTER           = 
LATEX_EXTRA_STYLESHEET = 
LATEX_EXTRA_FILES      = 
PDF_HYPERLINKS         = YES
USE_PDFLATEX           = YES
LATEX_BATCHMODE        = NO
LATEX_HIDE_INDICES     = NO
LATEX_SOURCE_CODE      = NO
LATEX_BIB_STYLE        = plain
LATEX_TIMESTAMP        = NO
#---------------------------------------------------------------------------
# Configuration options related to the RTF output
#---------------------------------------------------------------------------
GENERATE_RTF           = NO
RTF_OUTPUT             = rtf
COMPACT_RTF            = NO
RTF_HYPERLINKS         = NO
RTF_STYLESHEET_FILE    = 
RTF_EXTENSIONS_FILE    = 
RTF_SOURCE_CODE        = NO
#---------------------------------------------------------------------------
# Configuration options related to the man page output
#---------------------------------------------------------------------------
GENERATE_MAN           = NO
MAN_OUTPUT             = man
MAN_EXTENSION          = .3
MAN_SUBDIR             = 
MAN_LINKS              = NO
#---------------------------------------------------------------------------
# Configuration options related to the XML output
#---------------------------------------------------------------------------
GENERATE_XML           = NO
XML_OUTPUT             = xml
XML_PROGRAMLISTING     = YES
#---------------------------------------------------------------------------
# Configuration options related to the DOCBOOK output
#---------------------------------------------------------------------------
GENERATE_DOCBOOK       = NO
DOCBOOK_OUTPUT         = docbook
DOCBOOK_PROGRAMLISTING = NO
#---------------------------------------------------------------------------
# Configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
GENERATE_AUTOGEN_DEF   = NO
#---------------------------------------------------------------------------
# Configuration options related to the Perl module output
#---------------------------------------------------------------------------
GENERATE_PERLMOD       = NO
PERLMOD_LATEX          = NO
PERLMOD_PRETTY         = YES
PERLMOD_MAKEVAR_PREFIX = 
#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
ENABLE_PREPROCESSING   = YES
MACRO_EXPANSION        = NO
EXPAND_ONLY_PREDEF     = NO
SEARCH_INCLUDES        = YES
INCLUDE_PATH           = 
INCLUDE_FILE_PATTERNS  = 
PREDEFINED             = 
EXPAND_AS_DEFINED      = 
SKIP_FUNCTION_MACROS   = YES
#---------------------------------------------------------------------------
# Configuration options related to external references
#---------------------------------------------------------------------------
TAGFILES               = 
GENERATE_TAGFILE       = 
ALLEXTERNALS           = NO
EXTERNAL_GROUPS        = YES
EXTERNAL_PAGES         = YES
PERL_PATH              = /usr/bin/perl
#---------------------------------------------------------------------------
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
CLASS_DIAGRAMS         = YES
MSCGEN_PATH            = 
DIA_PATH               = 
HIDE_UNDOC_RELATIONS   = YES
HAVE_DOT               = NO
DOT_NUM_THREADS        = 0
DOT_FONTNAME           = Helvetica
DOT_FONTSIZE           = 10
DOT_FONTPATH           = 
CLASS_GRAPH            = YES
COLLABORATION_GRAPH    = YES
GROUP_GRAPHS           = YES
UML_LOOK               = NO
UML_LIMIT_NUM_FIELDS   = 10
TEMPLATE_RELATIONS     = NO
INCLUDE_GRAPH          = YES
INCLUDED_BY_GRAPH      = YES
CALL_GRAPH             = NO
CALLER_GRAPH           = NO
GRAPHICAL_HIERARCHY    = YES
DIRECTORY_GRAPH        = YES
DOT_IMAGE_FORMAT       = png
INTERACTIVE_SVG        = NO
DOT_PATH               = 
DOTFILE_DIRS           = 
MSCFILE_DIRS           = 
DIAFILE_DIRS           = 
PLANTUML_JAR_PATH      = 
PLANTUML_INCLUDE_PATH  = 
DOT_GRAPH_MAX_NODES    = 50
MAX_DOT_GRAPH_DEPTH    = 0
DOT_TRANSPARENT        = NO
DOT_MULTI_TARGETS      = NO
GENERATE_LEGEND        = YES
DOT_CLEANUP            = YES



--
View this message in context: http://doxygen.10944.n7.nabble.com/Two-enums-with-same-enumerator-name-generates-incorrect-output-tp7755.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] Bug with list of all namespace members?

[Jens S. <Jen...@t-...>]

Hi Dimitri,

> This is indeed a bug. Please file a bug in the bug tracker next time.

Ok, I will follow it ;-)

> The good news: I found what is causing this and committed a fix:
> https://github.com/doxygen/doxygen/commit/2b722b57f20e044b061423109bfa7168a7a1b913

Great, that fixes all the mentioned problems!

Big thanks

Jens

>> On 27 Oct 2016, at 17:22 , Jens Schleusener <Jen...@t-...> wrote:
>>
>> Hi,
>>
>> for Doxygen 1.8.12 and the current development version I found
>> errors accessing the "Namespace Members" list via
>>
>>  "Namespaces"
>>   -> "Namespace Members"
>>    -> "All"
>>
>> It appears a popup menue with all available (found) initial letters
>> but clicking on a letter one get a "File not found".
>>
>> Maybe the problem occurs not always, but after some playing around with
>> different Doxygen releases, different configurations and different
>> software packages I could reproduce at least for the package
>> wireshark-2.2.1.tar.gz the following behaviour for the current release
>> Doxygen 1.8.12 (and the development version):
>>
>> 1) If using the standard configuration file with the only main change
>> "RECURSIVE = YES" all works as expected and a file "namespacemembers.html"
>> is generated and used that contains 9 anchors with the id attribute to
>> access the accoding position within that file.
>>
>> 2) But if changing additional "EXTRACT_ALL = YES" the list of selectable
>> initial letters is larger but the access no longer works and one get a
>> "File not found" since a non existing file resp. URL
>> ".../namespacemembers_<l>.html#index_<l>" would be accessed (<l> should
>> represent the selected initial letter). But there exists also the file
>> "namespacemembers.html" but that contains only one anchor with an id
>> attribute, in the example only for the letter "z". So I assume that
>> Doxygen generates in that configuration for every found letter a new file
>> "namespacemembers.html" instead of adding resp. merging the
>> information or to generate separate files for every found letter
>> resp. to generate a letter-specific file.
>>
>> By the way, for Doxygen 1.8.11 the reported problem seems not to exist.
>> There appear instead of popup windows horizontal menu bars at the top of
>> the browser window and at least a horizontal bar with all found initial
>> letters. Clicking on such a letter (<l>) a URL
>> ".../namespacemembers_<l>.html#index_<l>" is accessed successfully since
>> for every letter a separate according file was created by Doxygen.
>>
>> Sorry for the a little bit confused report.
>>
>> If helpful or required I can try to put some examples on the Web.
>>
>> Jens
>>
>> ------------------------------------------------------------------------------
>> The Command Line: Reinvented for Modern Developers
>> Did the resurgence of CLI tooling catch you by surprise?
>> Reconnect with the command line and become more productive.
>> Learn the new .NET and ASP.NET CLI. Get your free copy!
>> http://sdm.link/telerik
>> _______________________________________________
>> Doxygen-users mailing list
>> Dox...@li...
>> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Bug with list of all namespace members?

[Dimitri v. H. <do...@gm...>]

Hi Jens,

This is indeed a bug. Please file a bug in the bug tracker next time.
The good news: I found what is causing this and committed a fix:
https://github.com/doxygen/doxygen/commit/2b722b57f20e044b061423109bfa7168a7a1b913

Regards,
  Dimitri

> On 27 Oct 2016, at 17:22 , Jens Schleusener <Jen...@t-...> wrote:
> 
> Hi,
> 
> for Doxygen 1.8.12 and the current development version I found
> errors accessing the "Namespace Members" list via
> 
>  "Namespaces"
>   -> "Namespace Members"
>    -> "All"
> 
> It appears a popup menue with all available (found) initial letters
> but clicking on a letter one get a "File not found".
> 
> Maybe the problem occurs not always, but after some playing around with 
> different Doxygen releases, different configurations and different 
> software packages I could reproduce at least for the package 
> wireshark-2.2.1.tar.gz the following behaviour for the current release 
> Doxygen 1.8.12 (and the development version):
> 
> 1) If using the standard configuration file with the only main change
> "RECURSIVE = YES" all works as expected and a file "namespacemembers.html"
> is generated and used that contains 9 anchors with the id attribute to
> access the accoding position within that file.
> 
> 2) But if changing additional "EXTRACT_ALL = YES" the list of selectable 
> initial letters is larger but the access no longer works and one get a 
> "File not found" since a non existing file resp. URL 
> ".../namespacemembers_<l>.html#index_<l>" would be accessed (<l> should 
> represent the selected initial letter). But there exists also the file 
> "namespacemembers.html" but that contains only one anchor with an id 
> attribute, in the example only for the letter "z". So I assume that 
> Doxygen generates in that configuration for every found letter a new file 
> "namespacemembers.html" instead of adding resp. merging the 
> information or to generate separate files for every found letter
> resp. to generate a letter-specific file.
> 
> By the way, for Doxygen 1.8.11 the reported problem seems not to exist. 
> There appear instead of popup windows horizontal menu bars at the top of 
> the browser window and at least a horizontal bar with all found initial 
> letters. Clicking on such a letter (<l>) a URL 
> ".../namespacemembers_<l>.html#index_<l>" is accessed successfully since 
> for every letter a separate according file was created by Doxygen.
> 
> Sorry for the a little bit confused report.
> 
> If helpful or required I can try to put some examples on the Web.
> 
> Jens
> 
> ------------------------------------------------------------------------------
> The Command Line: Reinvented for Modern Developers
> Did the resurgence of CLI tooling catch you by surprise?
> Reconnect with the command line and become more productive. 
> Learn the new .NET and ASP.NET CLI. Get your free copy!
> http://sdm.link/telerik
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Adding links and breadcrumb trail

[anish <ani...@ya...>]

Hi,

I am using Doxygen 1.8.12 to generate documentation for APIs added to C
header files. I observe the following issues in the CHM generated using
Doxygen:
•	Links are not added to other pages within the same help file. For example,
if the content added to the description for a function X contains references
to other pages within the generated CHM, I would like to add links to those
pages. Is there a tag to use, or is automatic addition of links possible?
•	I see that each page has a link to the group that it belongs to. I would
like to know if there is a way to customize this and add a breadcrumb trail
to the root node (for example, root > group >topic)

Please suggest ways to fix these issues.

Thanks,
Anish



--
View this message in context: http://doxygen.10944.n7.nabble.com/Adding-links-and-breadcrumb-trail-tp7747.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] Bug with list of all namespace members?

[Jens S. <Jen...@t-...>]

Hi,

for Doxygen 1.8.12 and the current development version I found
errors accessing the "Namespace Members" list via

  "Namespaces"
   -> "Namespace Members"
    -> "All"

It appears a popup menue with all available (found) initial letters
but clicking on a letter one get a "File not found".

Maybe the problem occurs not always, but after some playing around with 
different Doxygen releases, different configurations and different 
software packages I could reproduce at least for the package 
wireshark-2.2.1.tar.gz the following behaviour for the current release 
Doxygen 1.8.12 (and the development version):

1) If using the standard configuration file with the only main change
"RECURSIVE = YES" all works as expected and a file "namespacemembers.html"
is generated and used that contains 9 anchors with the id attribute to
access the accoding position within that file.

2) But if changing additional "EXTRACT_ALL = YES" the list of selectable 
initial letters is larger but the access no longer works and one get a 
"File not found" since a non existing file resp. URL 
".../namespacemembers_<l>.html#index_<l>" would be accessed (<l> should 
represent the selected initial letter). But there exists also the file 
"namespacemembers.html" but that contains only one anchor with an id 
attribute, in the example only for the letter "z". So I assume that 
Doxygen generates in that configuration for every found letter a new file 
"namespacemembers.html" instead of adding resp. merging the 
information or to generate separate files for every found letter
resp. to generate a letter-specific file.

By the way, for Doxygen 1.8.11 the reported problem seems not to exist. 
There appear instead of popup windows horizontal menu bars at the top of 
the browser window and at least a horizontal bar with all found initial 
letters. Clicking on such a letter (<l>) a URL 
".../namespacemembers_<l>.html#index_<l>" is accessed successfully since 
for every letter a separate according file was created by Doxygen.

Sorry for the a little bit confused report.

If helpful or required I can try to put some examples on the Web.

Jens

Re: [Doxygen-users] ASSERT: "0" in docparser.cpp (5747)

[mkluwe <mk...@vh...>]

Hi!

>> After adding missing documentation in several files doxygen started to
>> complain, printing several assert messages:
>> 
>>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>>     todo:7: warning: Unexpected tag <dd> found
>>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>>     todo:9: warning: Unexpected tag <dd> found
>>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>>     todo:11: warning: Unexpected tag <dd> found
>>     todo:13: warning: Unexpected tag <dd> found
>>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>>     todo:15: warning: Unexpected tag <dd> found
>>     todo:16: warning: Unexpected tag <dd> found
>>     todo:17: warning: Unexpected tag <dd> found
>>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>>     todo:18: warning: Unexpected tag <dd> found

> I have found it:
> 
> One of my doxygen comment contained a smiley (unicode character WHITE
> SMILING
> FACE, encoded as `0xE2 0x98 0xBA` in my UTF-8 encoded file). After
> removing
> this, the burps above are gone.

Ah, that was a false positive, sorry for the noise. Now for the real reason:

The error is produced by a `\todo` in an XML C# code comment like this

    /// <summary>
    /// \todo tbd
    /// </summary>
    public double Foo { get; set; }

Regards,
Matthias




--
View this message in context: http://doxygen.10944.n7.nabble.com/ASSERT-0-in-docparser-cpp-5747-tp7738p7745.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] ASSERT: "0" in docparser.cpp (5747)

[mkluwe <mk...@vh...>]

Hi!

> After adding missing documentation in several files doxygen started to
> complain, printing several assert messages:
> 
>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>     todo:7: warning: Unexpected tag <dd> found
>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>     todo:9: warning: Unexpected tag <dd> found
>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>     todo:11: warning: Unexpected tag <dd> found
>     todo:13: warning: Unexpected tag <dd> found
>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>     todo:15: warning: Unexpected tag <dd> found
>     todo:16: warning: Unexpected tag <dd> found
>     todo:17: warning: Unexpected tag <dd> found
>     ASSERT: "0" in e:\doxygen\src\docparser.cpp (5747)
>     todo:18: warning: Unexpected tag <dd> found

I have found it:

One of my doxygen comment contained a smiley (unicode character WHITE
SMILING
FACE, encoded as `0xE2 0x98 0xBA` in my UTF-8 encoded file). After removing
this, the burps above are gone.

Regards,
Matthias




--
View this message in context: http://doxygen.10944.n7.nabble.com/ASSERT-0-in-docparser-cpp-5747-tp7738p7744.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] references to nested structure members

[Fabian C. <Cen...@in...>]

At 16:49 25.10.2016, chrisroelle wrote:
>Hi Fabian -
>Thanks for the reply - here is what I've added, same result.... is this what
>you meant?
>
>/// \ref outer::outer_member1

Partly, I also meant using the class name outer_tag instead of the
object name outer (but I haven't tried myself).

bye  Fabi

Re: [Doxygen-users] references to nested structure members

[Dimitri v. H. <do...@gm...>]

The references should follow the structure as it is defined, i.e. 
struct inner is not defined inside struct outer, so you
cannot refer to its members via the outer struct, you have to refer to them directly via inner struct.

If you actually nest the structures you can refer to then via their nesting scope, i.e.:

/// - \ref outer
/// - \ref outer::outer_member1
/// - \ref outer::inner_tag::inner_member

/// struct outer doc
struct outer_tag
{
  /// struct inner doc
  struct inner_tag
  {
    /// inner_member doc
    int inner_member;
  } outer_member1; ///< outer member
};

/// typedef outer struct
typedef struct outer_tag outer;

Regards,
  Dimitri


> On 24 Oct 2016, at 23:24 , chrisroelle <cr...@ee...> wrote:
> 
> Hi -
> 
> First, my apologies if this is a silly or previously-answered question -
> I've googled and read the manuals but am still having trouble.
> 
> My question is - how can I get doxygen to generate references to members of
> nested structures, like in the example below.... the
> outer.outer_member1.inner_member and outer.outer_member2.inner_member
> strings don't appear as references.
> 
> Any advice appreciated,
> CR
> 
> /// \file example.h
> /// \brief Example of references to members of nested struct.
> /// \author Chris Roelle
> ///
> /// what I want to do is see these all as references....
> /// \ref inner
> /// \ref inner.inner_member
> /// \ref outer
> /// \ref outer.outer_member1
> /// \ref outer.outer_member1.inner_member
> /// \ref outer.outer_member2
> /// \ref outer.outer_member2.inner_member
> 
> /// struct inner doc
> struct inner_tag
> {
>  /// inner_member doc
>  int inner_member;
> };
> /// typedef inner doc
> typedef struct inner_tag inner;
> 
> /// struct outer doc
> struct outer_tag
> {
>  /// outer_member1 doc
>  struct inner_tag outer_member1;
>  /// outer_member2 doc
>  inner outer_member2;
> };
> /// typedef outer doc
> typedef struct outer_tag outer;
> 
> 
> 
> --
> View this message in context: http://doxygen.10944.n7.nabble.com/references-to-nested-structure-members-tp7739.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> The Command Line: Reinvented for Modern Developers
> Did the resurgence of CLI tooling catch you by surprise?
> Reconnect with the command line and become more productive. 
> Learn the new .NET and ASP.NET CLI. Get your free copy!
> http://sdm.link/telerik
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] references to nested structure members

[chrisroelle <cr...@ee...>]

Hi Fabian -
Thanks for the reply - here is what I've added, same result.... is this what
you meant?

/// \ref outer::outer_member1
/// \ref outer::outer_member1::inner_member
/// \ref outer::outer_member2
/// \ref outer::outer_member2::inner_member
/// \ref outer::outer_member1
/// \ref outer::outer_member1.inner_member
/// \ref outer::outer_member2
/// \ref outer::outer_member2.inner_member
/// \ref outer.inner.inner_member
/// \ref outer::inner.inner_member
/// \ref outer.inner::inner_member




--
View this message in context: http://doxygen.10944.n7.nabble.com/references-to-nested-structure-members-tp7739p7741.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] references to nested structure members

[Fabian C. <Cen...@in...>]

At 23:24 24.10.2016, chrisroelle wrote:
>Hi -
>
>First, my apologies if this is a silly or previously-answered question -
>I've googled and read the manuals but am still having trouble.
>
>My question is - how can I get doxygen to generate references to members of
>nested structures, like in the example below.... the
>outer.outer_member1.inner_member and outer.outer_member2.inner_member
>strings don't appear as references.

Have you tried the class::member notation (not the object name)?

bye  Fabi

[Doxygen-users] references to nested structure members

[chrisroelle <cr...@ee...>]

Hi -

First, my apologies if this is a silly or previously-answered question -
I've googled and read the manuals but am still having trouble.

My question is - how can I get doxygen to generate references to members of
nested structures, like in the example below.... the
outer.outer_member1.inner_member and outer.outer_member2.inner_member
strings don't appear as references.

Any advice appreciated,
CR

/// \file example.h
/// \brief Example of references to members of nested struct.
/// \author Chris Roelle
///
/// what I want to do is see these all as references....
/// \ref inner
/// \ref inner.inner_member
/// \ref outer
/// \ref outer.outer_member1
/// \ref outer.outer_member1.inner_member
/// \ref outer.outer_member2
/// \ref outer.outer_member2.inner_member

/// struct inner doc
struct inner_tag
{
  /// inner_member doc
  int inner_member;
};
/// typedef inner doc
typedef struct inner_tag inner;

/// struct outer doc
struct outer_tag
{
  /// outer_member1 doc
  struct inner_tag outer_member1;
  /// outer_member2 doc
  inner outer_member2;
};
/// typedef outer doc
typedef struct outer_tag outer;



--
View this message in context: http://doxygen.10944.n7.nabble.com/references-to-nested-structure-members-tp7739.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.