精华内容
下载资源
问答
  • doxygen工具

    2012-01-20 09:52:10
    Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成HTML...
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成HTML...
  • Doxygen-程序文档工具

    2016-11-28 11:42:15
    Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统

      Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释的语法与Qt-Doc、KDoc和JavaDoc兼容。Doxygen可以从一套归档源文件开始,生成HTML格式的在线类浏览器,或离线的LATEX、RTF参考手册。

      对于未归档的源文件,也可以通过配置Doxygen来提取代码结构。或者借助自动生成的包含依赖图(includedependency graphs)、继承图(inheritance diagram)以及协作图(collaborationdiagram)来可视化文档之间的关系。Doxygen生成的帮助文档的格式可以是CHM、RTF、PostScript、PDF、HTML和Unixman page等。
      
      一个好的程序设计师,在写程序时,都会在适当的地方加上合适的批注。如果,能够在撰写批注时,稍微符合某种格式,接着就可以透过一个工具程序依据程序结构及您的批注产生出漂亮的文件。这将令许多工作繁重的程序设计师有时间多喝几杯咖啡。
    Doxygen 就是这样的一个工具。在您写批注时,稍微按照一些它所制订的规则。接着,他就可以帮您产生出漂亮的文件了。因此,Doxygen 的使用可分为两大部分。首先是特定格式的批注撰写,第二便是利用Doxygen的工具来产生文件。

    ftp://ftp.stack.nl/pub/users/dimitri/doxygen-1.8.12-setup.exe

    展开全文
  • Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。...首先是特定格式的批注撰写,第二便是利用Doxygen的工具来产生文档。
  • 文档生产工具 Doxygen

    2014-06-06 17:55:00
    Doxygen是一种开源跨平台类似JavaDoc风格描述文档系统,支持C、C++、Java、Objective-C等语言。可以从一套归档源文件开始,生成HTML,XML,pdf等不同风格格式。 按照约定格式注释源代码,用工具处理注释过...

    Doxygen是一种开源跨平台的,类似JavaDoc风格描述的文档系统,支持C、C++、Java、Objective-C等语言。可以从一套归档源文件开始,生成HTML,XML,pdf等不同风格的格式。

    按照约定的格式注释源代码,用工具处理注释过的源代码产生文档,通过这种方式产生文档,有以下几个好处。

    1. 便于代码和文档保持同步

    2. 可以对文档做版本管理

     

     

    使用方法

    要使用Doxygen生成文档,主要有两件事

    1. 一般用Doxywizard生成Doxyfile后,再手工修改或者通过向导进行修改。建议,一个项目使用单独的Doxyfile配置文件。

    2. 按照Doxygen的约定,将代码文档化

    3. 执行 doxygen Doxyfile

     

     

    Doxygen统一采用UTF-8作为输出文件的编码格式。但微软的CHM编译工具(hhc.exe)不支持UTF-8,它支持GB2132

    Doxygen的最新版本,可以从Doxygen的网站下载,我使用的是doxygen-1.8.7-setup.exe

    Graphviz是一个图形可视化软件。Doxygen使用Graphviz生成各种图形,例如类的继承关系图、合作图,头文件包含关系图等。可以从Graphviz的网站下载Graphviz的最新版本。Doxygen使用了Graphviz的布局引擎dot,所以在文档中将其称作dot。

     

     

    image

     

    Mode页面

    image

    Output页面:

    image

    Diagrams页面:

    image

     

    Expert页面:

    我们关心这个页面下的HTML生成选项:

      image

    image

     

    Input页面:

    image

     

    编码相关

    Doxygen涉及的东西很多,编码设置很重要,如果设置不当,生成的文档会乱码,因此,需要认真对待。

    所有的高级编码设置都在Expert标签下面:

    image

    image

     

     image

     

    配置文件的格式是unix下通常的文件格式,注释以#开头,tag = value1 [,value2 ].

    所有配置,按照功能,分为两类。

    一是控制输入选项,控制如何解释源代码,

    二是项目相关的信息,比如项目名称、源代码目录、输出文档目录等。

     

    注释风格

    头文件模板:
    /** @brief 这里写你的摘要
    *  @file 你的文件名
    *  @author 谁tmd的搞的
    *  @version 版本了
    *  @date  你啥时候搞的
    *  @note       注解. 例如: 本文件有什么具体功能啊,使用时要注意什么啊…..
    *  @since    自从  例如: 自从2012年地球爆炸后这个文件就从地球上消失了…..
    */

     

    函数的注释:
    /**  这里写这个函数是干什么用的
    @param[in]  输入参数1
    @param[in]  输入参数2
    @param[out]  输出参数1
    @return    返回值解释一下
    @warning 警告: 例如: 参数不能为空啊,内存要外部释放之类的费话
    @note 注解 随便你了
    @see                相当于是请参考xxoo函数之类的
    */

     

    变量或者只有一行注解的东东,不超过一行的注释:
    /**< 在这里写你要加的东西 */
    OR
    ///< 在这里写你要加的东西

     

    doxygen代码规范使用说明连接: http://blog.csdn.net/augusdi/article/details/6749845

    转载于:https://www.cnblogs.com/cherishui/p/3773108.html

    展开全文
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容... Doxygen是一个程序文件产生工具,可将...

             Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释的语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成HTML格式的在线类浏览器,或离线的LATEX、RTF参考手册。

     

    Doxygen 是一个程序的文件生工具,可将程序中的特定批注转换为说明文件。通常我们在写程序时,或多或少都会写上批注,但是对于其它人而言,要直接探索程序里的批注,与打捞铁达尼号的辛苦。大部分有用的批注都是属于针对函式,类别等等的说明。所以,如果能依据程序本身的结构,将批注经过处理重新整理成个纯粹的参考手册于后面利用您的程序代码的人而言将会减少许多的负担。不过,反过来说,整理文件的工作对于您来说,就是沉重的负担。
    Doxygen 就是在您写批注时,稍微按照一些它所制订的规则。接着,他就可以帮您产生出漂亮的文档了。

    因此,Doxygen 的使用可分为两大部分。首先是特定格式的批注撰,第二便是利用Doxygen的工具来产生文档

     

     

    使用步骤

    1、第一次使用需要安装doxygen的程序

     

    2、生成doxygen配置文件

    3、编码时,按照某种格式编写注释
           4、生成对应文档

    1、安装doxygen及其相关程序

    1.1Doxygen下载

    http://sourceforge.net/projects/doxygen/?source=dlp 进行下载

    本文使用的为Doxygen 1.8.3.1

    安装,我们将在配置的时候使用doxywizard,Doxygen的GUI版本。

    1.2HTML Help Workshop下载

    如果你希望你的Doxygen自动生成chm,那么请下载HTML Help Workshop,我们将要使用当中的hcc.exe文件以及相关dll

    http://www.microsoft.com/en-us/download/details.aspx?id=21138 进行下载

    下载其中的htmlhelp.exe并安装,记住安装目录,我们将在Doxygen配置时使用。

    1.3 Graphviz

    graphviz 是一个由AT&T实验室启动的开源工具包,用于绘制DOT语言脚本描述的图形Doxygen 使用 graphviz 自动生成类之间和文件之间的调用关系图,如不需要此功能可不安装该工具包。

    安装并记录安装目录,同样我们一会需要配置Doxygen


    2.配置Doxygen

    2.1基本配置

    在基本配置中,会介绍一些关于Doxygen的基本配置,例如各种乱码,输出内容等。

    首先我们打开开始-》所有程序-》Doxygen-》doxywizard

    第一步,选择你的工作目录(配置文件位置  D:\Doxygen),点击Select。

    第二步,进行配置

    Wizard选项卡:

    首先修改Project name,选择扫描源代码的目录,Source code directory:,勾选Scan recursively  (递归扫描),之后选择输出目录,作为测试选择桌面进行查看。


    在Wizard的Topics下的Mode,选择All Entities,可以输出相对完整的功能,是否包含源代码看你自身情况,在下面选择好你的语言。这里作者使用的是C#  所以选择Java or C#


    在Output中,如果你需要输出chm格式,请勾选。


    在Diagrams中选择使用GraphViz包,来输出UML


    Expert选项卡:


    说明:编码格式,UTF-8 是首选。如果需要显示中文则选择GB2312.

    TAB_SIZE 主要是帮助文件中代码的缩进尺寸,譬如@code@endcode段中代码的排版,建议设置成4

     


    Build页面,这个页面是生成帮助信息中比较关键的配置页面:

    EXTRACT_ALL 表示:输出所有的函数,但是privatestatic函数不属于其管制

    EXTRACT_PRIVATE 表示:输出private函数。

    EXTRACT_STATIC 表示:输出static函数。同时还有几个EXTRACT,相应查看文档即可。

    SHOW_INCLUDE_FILES 表示:是否显示包含文件,如果开启,帮助中会专门生成一个页面,里面包含所有包含文件的列

    表。

    INLINE_INFO :如果开启,那么在帮助文档中,inline函数前面会有一个inline修饰词来标明。

    SORT_MEMBER_DOCS :如果开启,那么在帮助文档列表显示的时候,函数名称会排序,否则按照解释的顺序显

    示。

     


    说明:INPUT_ENCODING (输入的源文件的编码),要与源文件的编码格式相同。如果源文件不是UTF-8编码最好转一下。

    总结:我查看到我的代码文件是utf-8的(vs2013中打开文件 选另存为可看到编码格式)((VS2012的话):文件->高级保存选项)。


     

    在Expert的HTML中,首先要看HHC_LOCATION选项,添加安装目录(注:作者目录为C:/Program Files (x86)/HTML Help Workshop/hhc.exe)

    勾选CHM_INDEX_ENCODING,在你源代码中的字符集是什么就填写什么,


    之后在Expert的Dot中勾选CLASS_DIAGRAMS,UML_LOOK

    为了减少chm体积,在DOT_IMAGE_FORMAT中选择gif或者jpg,均可。

    最后选择好DOT_PATH所输出的位置。


    点击 Run doxygen 按钮, Doxygen 就会从源代码中抓取符合规范的注释生成你定制的格式的文档。
    几个错误:

    Error: When enabling GENERATE_HTMLHELP the search engine (SEARCHENGINE) should be disabled. I'll do it for you.

    warning: The selected output language "chinese" has not been updated

    since release 1.8.2. As a result some sentences may appear in English.

    解决:把HTML里面的SEARCHENGINE设置为NO


    接下来的工作就是学习 doxygen 的注释规范了,参考 《doxygen 快速入门》第 2 节 “常用注释语法”。慢慢的就可以体会到 doxygen 的方便性。

     

    3、doxygen 的注释规范 

     

     

    并非所有程序代中的批注都会被Doxygen 理。您必需依照正确的格式撰原则上,Doxygen 仅处理与程序构相关的批注,
    Function,Class ,档案的批注等。Function内部的批注不做处理。Doxygen可处理下面几种类型的批注。

    JavaDoc类型:

    /**
     * ... 批注 ...
     */


    Qt类型:

    /*!
     * ... 批注 ...
     */

         
    单行型式的批注:

    /// ... 批注 ...

    或    

    //! ... 批注 ...

        
      
    要使用哪种型态完全看自己的喜好。以笔者自己来说,
    大范围的注解我会使用JavaDoc 型的。单行的批注则使用"///" 的类型。

    此外,由于Doxygen 对于批注是视为在解释后面的程序代码。也就是说,任何一个批注都是在说明其后的程序代码。如果要批注前面的程
    式码则需用下面格式的批注符号。

    /*!< ... 批注 ... */
    /**< ... 批注 ... */
    //!< ... 批注 ...
    ///< ... 批注 ...

        
    上面这个方式并不适用于任何地方,只能用在class 的member或是function的参数上。

    举例来说,若我们有下面这样的class。
        class MyClass {
            public:
                int member1 ;
                int member2:
                void member_function();
        };
        
    加上批注后,就变成这样:

        /**
         * 我的自订类别说明 ...
         */
        class MyClass {
            public:
                int member1 ; ///< 第一个member说明 ...
                int member2:  ///< 第二个member说明 ...
                int member_function(int a, int b);
        };
        
        /**
         * 自订类别的member_funtion说明 ...
         *
         * @param a 参数a的说明
         * @param b 参数b的说明
         *
         * @return 传回a+b。
         */ 
        int MyClass::member_function( int a, int b ) 
        {
            return a+b ;
        }
        
    当您使用Doxygen 产生说明文档时,Doxygen 会帮您parsing 您的程式码。并且依据程序结构建立对应的文件。然后再将您的批注,依据其位置套入于正确的地方。您可能已经注意到,
    除了一般文字说明外,还有一些其它特别的指令,像是@param及@return 等。这正是Doxygen 另外一个重要的部分,因为一个类别或是函式其实都有固定几个要说明的部分。为了让Doxygen 能够判断,所有我们就必需使用这些指令,来告诉Doxygen 后面的批注是在说明什么东西。Doxygen 在处理时,就会帮您把这些部分做特别的处理或是排版。甚至是制作参考连结。
    首先,我们先说明在Doxygen 中对于类别或是函数批注的一个特定格式。
        /**
         * class或function的简易说明...
         *
         * class或function的详细说明...
         * ...
         */ 
    上面这个例子要说的是,在Doxygen 处理一个class 或是function注解时,会先判断第一行为简易说明。这个简易说明将一直到空一行的出现。或是遇到第一个"." 为止。之后的批注将会被视为详细说明。两者的差异在于Doxygen 在某些地方只会显示简易说明,而不显示详细说明。如:class 或function的列表。

    另一种比较清楚的方式是指定@brief的指令。这将会明确的告诉Doxygen,何者是简易说明。例如:
        /**
         * @brief class或function的简易说明...
         *
         * class或function的详细说明...
         * ...
         */

    除了这个class 及function外,Doxygen 也可针对档案做说明,条件是该批注需置于档案的前面。主要也是利用一些指令,通常这部分注解都会放在档案的开始地方。如:

        /*! \file myfile.h
            \brief 档案简易说明
        
            详细说明.
            
            \author 作者信息
        */

    如您所见,档案批注约略格式如上,请别被"\" 所搞混。其实,"\" 与"@" 都是一样的,都是告诉Doxygen 后面是一个指令。两种在Doxygen 都可使用。笔者自己比较偏好使用"@"。
    接着我们来针对一些常用的指令做说明:

    @file

    档案的批注说明。

    @author

    作者的信息

    @brief

    用于class 或function的批注中,后面为class 或function的简易说明。

    @param

    格式为

    @param arg_name 参数说明

    主要用于函式说明中,后面接参数的名字,然后再接关于该参数的说明

    @return

    后面接函数传回值的说明。用于function的批注中。说明该函数的传回值。

    @retval

    格式为

    @retval value 传回值说明

    主要用于函式说明中,说明特定传回值的意义。所以后面要先接一个传回值。然后在放该传回值的说明。

           
    Doxygen 所支持的指令很多,有些甚至是关于输出排版的控制。您可从Doxygen的使用说明中找到详尽的说明。

    下面我们准备一组example.h 及example.cpp 来说明Doxygen 批注的使用方式:

    example.h:

        /**
         * @file 本范例的include档案。
         *
         * 这个档案只定义example这个class。
         *
         * @author garylee@localhost
         */
                
        #define EXAMPLE_OK  0   ///< 定义EXAMPLE_OK的宏为0。
        
        /**
         * @brief Example class的简易说明
         *
         * 本范例说明Example class。
         * 这是一个极为简单的范例。
         * 
         */
        class Example {
            private:
                int var1 ; ///< 这是一个private的变数
            public:
                int var2 ; ///< 这是一个public的变数成员。
                int var3 ; ///< 这是另一个public的变数成员。
                void ExFunc1(void); 
                int ExFunc2(int a, char b);
                char *ExFunc3(char *c) ;
        };
        
        
    example.cpp:

        /**
         * @file 本范例的程序代码档案。
         *
         * 这个档案用来定义example这个class的
         * member function。
         *
         * @author garylee@localhost
         */
        
        /**
         * @brief ExFunc1的简易说明
         *
         * ExFunc1没有任何参数及传回值。
         */
        void Example::ExFunc1(void)
        {
            // empty funcion.
        }

        /**
         * @brief ExFunc2的简易说明
         *
         * ExFunc3()传回两个参数相加的值。
         *
         * @param a 用来相加的参数。
         * @param b 用来相加的参数。
         * @return 传回两个参数相加的结果。
         */
        int ExFunc2(int a, char b)
        {
            return (a+b);
        }
        
        /**
         * @brief ExFunc3的简易说明
         *
         * ExFunc3()只传回参数输入的指标。
         *
         * @param c 传进的字符指针。
         * @retval NULL 空字符串。
         * @retval !NULL 非空字符串。
         */
        char * ExFunc2(char * c)
        {
            return c;
        }    


    附:我的配置文件

    # Doxyfile 1.8.9.1


    # This file describes the settings to be used by the documentation system
    # doxygen (www.doxygen.org) for a project.
    #
    # All text after a double hash (##) is considered a comment and is placed in
    # front of the TAG it is preceding.
    #
    # All text after a single hash (#) is considered a comment and will be ignored.
    # The format is:
    # TAG = value [value, ...]
    # For lists, items can also be appended using:
    # TAG += value [value, ...]
    # Values that contain spaces should be placed between quotes (\" \").


    #---------------------------------------------------------------------------
    # Project related configuration options
    #---------------------------------------------------------------------------


    # This tag specifies the encoding used for all characters in the config file
    # that follow. The default is UTF-8 which is also the encoding used for all text
    # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
    # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
    # for the list of possible encodings.
    # The default value is: UTF-8.


    DOXYFILE_ENCODING      = GB2312


    # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
    # double-quotes, unless you are using Doxywizard) that should identify the
    # project for which the documentation is generated. This name is used in the
    # title of most generated pages and in a few other places.
    # The default value is: My Project.


    PROJECT_NAME           = MyProgram


    # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
    # could be handy for archiving the generated documentation or if some version
    # control system is used.


    PROJECT_NUMBER         = 1.000


    # Using the PROJECT_BRIEF tag one can provide an optional one line description
    # for a project that appears at the top of each page and should give viewer a
    # quick idea about the purpose of the project. Keep the description short.


    PROJECT_BRIEF          = 


    # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
    # in the documentation. The maximum height of the logo should not exceed 55
    # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
    # the logo to the output directory.


    PROJECT_LOGO           = 


    # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
    # into which the generated documentation will be written. If a relative path is
    # entered, it will be relative to the location where doxygen was started. If
    # left blank the current directory will be used.


    OUTPUT_DIRECTORY       = .


    # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
    # directories (in 2 levels) under the output directory of each output format and
    # will distribute the generated files over these directories. Enabling this
    # option can be useful when feeding doxygen a huge amount of source files, where
    # putting all generated files in the same directory would otherwise causes
    # performance problems for the file system.
    # The default value is: NO.


    CREATE_SUBDIRS         = NO


    # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
    # characters to appear in the names of generated files. If set to NO, non-ASCII
    # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
    # U+3044.
    # The default value is: NO.


    ALLOW_UNICODE_NAMES    = NO


    # The OUTPUT_LANGUAGE tag is used to specify the language in which all
    # documentation generated by doxygen is written. Doxygen will use this
    # information to generate all constant output in the proper language.
    # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
    # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
    # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
    # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
    # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
    # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
    # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
    # Ukrainian and Vietnamese.
    # The default value is: English.


    OUTPUT_LANGUAGE        = Chinese


    # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
    # descriptions after the members that are listed in the file and class
    # documentation (similar to Javadoc). Set to NO to disable this.
    # The default value is: YES.


    BRIEF_MEMBER_DESC      = YES


    # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
    # description of a member or function before the detailed description
    #
    # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
    # brief descriptions will be completely suppressed.
    # The default value is: YES.


    REPEAT_BRIEF           = YES


    # This tag implements a quasi-intelligent brief description abbreviator that is
    # used to form the text in various listings. Each string in this list, if found
    # as the leading text of the brief description, will be stripped from the text
    # and the result, after processing the whole list, is used as the annotated
    # text. Otherwise, the brief description is used as-is. If left blank, the
    # following values are used ($name is automatically replaced with the name of
    # the entity):The $name class, The $name widget, The $name file, is, provides,
    # specifies, contains, represents, a, an and the.


    ABBREVIATE_BRIEF       = "The $name class" \
                             "The $name widget" \
                             "The $name file" \
                             is \
                             provides \
                             specifies \
                             contains \
                             represents \
                             a \
                             an \
                             the


    # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
    # doxygen will generate a detailed section even if there is only a brief
    # description.
    # The default value is: NO.


    ALWAYS_DETAILED_SEC    = NO


    # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
    # inherited members of a class in the documentation of that class as if those
    # members were ordinary class members. Constructors, destructors and assignment
    # operators of the base classes will not be shown.
    # The default value is: NO.


    INLINE_INHERITED_MEMB  = NO


    # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
    # before files name in the file list and in the header files. If set to NO the
    # shortest path that makes the file name unique will be used
    # The default value is: YES.


    FULL_PATH_NAMES        = YES


    # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
    # Stripping is only done if one of the specified strings matches the left-hand
    # part of the path. The tag can be used to show relative paths in the file list.
    # If left blank the directory from which doxygen is run is used as the path to
    # strip.
    #
    # Note that you can specify absolute paths here, but also relative paths, which
    # will be relative from the directory where doxygen is started.
    # This tag requires that the tag FULL_PATH_NAMES is set to YES.


    STRIP_FROM_PATH        = 


    # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
    # path mentioned in the documentation of a class, which tells the reader which
    # header file to include in order to use a class. If left blank only the name of
    # the header file containing the class definition is used. Otherwise one should
    # specify the list of include paths that are normally passed to the compiler
    # using the -I flag.


    STRIP_FROM_INC_PATH    = 


    # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
    # less readable) file names. This can be useful is your file systems doesn't
    # support long names like on DOS, Mac, or CD-ROM.
    # The default value is: NO.


    SHORT_NAMES            = NO


    # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
    # first line (until the first dot) of a Javadoc-style comment as the brief
    # description. If set to NO, the Javadoc-style will behave just like regular Qt-
    # style comments (thus requiring an explicit @brief command for a brief
    # description.)
    # The default value is: NO.


    JAVADOC_AUTOBRIEF      = NO


    # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
    # line (until the first dot) of a Qt-style comment as the brief description. If
    # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
    # requiring an explicit \brief command for a brief description.)
    # The default value is: NO.


    QT_AUTOBRIEF           = NO


    # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
    # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
    # a brief description. This used to be the default behavior. The new default is
    # to treat a multi-line C++ comment block as a detailed description. Set this
    # tag to YES if you prefer the old behavior instead.
    #
    # Note that setting this tag to YES also means that rational rose comments are
    # not recognized any more.
    # The default value is: NO.


    MULTILINE_CPP_IS_BRIEF = NO


    # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
    # documentation from any documented member that it re-implements.
    # The default value is: YES.


    INHERIT_DOCS           = YES


    # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
    # page for each member. If set to NO, the documentation of a member will be part
    # of the file/class/namespace that contains it.
    # The default value is: NO.


    SEPARATE_MEMBER_PAGES  = NO


    # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
    # uses this value to replace tabs by spaces in code fragments.
    # Minimum value: 1, maximum value: 16, default value: 4.


    TAB_SIZE               = 4


    # This tag can be used to specify a number of aliases that act as commands in
    # the documentation. An alias has the form:
    # name=value
    # For example adding
    # "sideeffect=@par Side Effects:\n"
    # will allow you to put the command \sideeffect (or @sideeffect) in the
    # documentation, which will result in a user-defined paragraph with heading
    # "Side Effects:". You can put \n's in the value part of an alias to insert
    # newlines.


    ALIASES                = 


    # This tag can be used to specify a number of word-keyword mappings (TCL only).
    # A mapping has the form "name=value". For example adding "class=itcl::class"
    # will allow you to use the command class in the itcl::class meaning.


    TCL_SUBST              = 


    # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
    # only. Doxygen will then generate output that is more tailored for C. For
    # instance, some of the names that are used will be different. The list of all
    # members will be omitted, etc.
    # The default value is: NO.


    OPTIMIZE_OUTPUT_FOR_C  = NO


    # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
    # Python sources only. Doxygen will then generate output that is more tailored
    # for that language. For instance, namespaces will be presented as packages,
    # qualified scopes will look different, etc.
    # The default value is: NO.


    OPTIMIZE_OUTPUT_JAVA   = YES


    # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
    # sources. Doxygen will then generate output that is tailored for Fortran.
    # The default value is: NO.


    OPTIMIZE_FOR_FORTRAN   = NO


    # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
    # sources. Doxygen will then generate output that is tailored for VHDL.
    # The default value is: NO.


    OPTIMIZE_OUTPUT_VHDL   = NO


    # Doxygen selects the parser to use depending on the extension of the files it
    # parses. With this tag you can assign which parser to use for a given
    # extension. Doxygen has a built-in mapping, but you can override or extend it
    # using this tag. The format is ext=language, where ext is a file extension, and
    # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
    # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
    # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
    # Fortran. In the later case the parser tries to guess whether the code is fixed
    # or free formatted code, this is the default for Fortran type files), VHDL. For
    # instance to make doxygen treat .inc files as Fortran files (default is PHP),
    # and .f files as C (default is Fortran), use: inc=Fortran f=C.
    #
    # Note: For files without extension you can use no_extension as a placeholder.
    #
    # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
    # the files are not read by doxygen.


    EXTENSION_MAPPING      = 


    # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
    # according to the Markdown format, which allows for more readable
    # documentation. See http://daringfireball.net/projects/markdown/ for details.
    # The output of markdown processing is further processed by doxygen, so you can
    # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
    # case of backward compatibilities issues.
    # The default value is: YES.


    MARKDOWN_SUPPORT       = YES


    # When enabled doxygen tries to link words that correspond to documented
    # classes, or namespaces to their corresponding documentation. Such a link can
    # be prevented in individual cases by putting a % sign in front of the word or
    # globally by setting AUTOLINK_SUPPORT to NO.
    # The default value is: YES.


    AUTOLINK_SUPPORT       = YES


    # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
    # to include (a tag file for) the STL sources as input, then you should set this
    # tag to YES in order to let doxygen match functions declarations and
    # definitions whose arguments contain STL classes (e.g. func(std::string);
    # versus func(std::string) {}). This also make the inheritance and collaboration
    # diagrams that involve STL classes more complete and accurate.
    # The default value is: NO.


    BUILTIN_STL_SUPPORT    = NO


    # If you use Microsoft's C++/CLI language, you should set this option to YES to
    # enable parsing support.
    # The default value is: NO.


    CPP_CLI_SUPPORT        = NO


    # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
    # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
    # will parse them like normal C++ but will assume all classes use public instead
    # of private inheritance when no explicit protection keyword is present.
    # The default value is: NO.


    SIP_SUPPORT            = NO


    # For Microsoft's IDL there are propget and propput attributes to indicate
    # getter and setter methods for a property. Setting this option to YES will make
    # doxygen to replace the get and set methods by a property in the documentation.
    # This will only work if the methods are indeed getting or setting a simple
    # type. If this is not the case, or you want to show the methods anyway, you
    # should set this option to NO.
    # The default value is: YES.


    IDL_PROPERTY_SUPPORT   = YES


    # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
    # tag is set to YES then doxygen will reuse the documentation of the first
    # member in the group (if any) for the other members of the group. By default
    # all members of a group must be documented explicitly.
    # The default value is: NO.


    DISTRIBUTE_GROUP_DOC   = NO


    # Set the SUBGROUPING tag to YES to allow class member groups of the same type
    # (for instance a group of public functions) to be put as a subgroup of that
    # type (e.g. under the Public Functions section). Set it to NO to prevent
    # subgrouping. Alternatively, this can be done per class using the
    # \nosubgrouping command.
    # The default value is: YES.


    SUBGROUPING            = YES


    # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
    # are shown inside the group in which they are included (e.g. using \ingroup)
    # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
    # and RTF).
    #
    # Note that this feature does not work in combination with
    # SEPARATE_MEMBER_PAGES.
    # The default value is: NO.


    INLINE_GROUPED_CLASSES = YES


    # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
    # with only public data fields or simple typedef fields will be shown inline in
    # the documentation of the scope in which they are defined (i.e. file,
    # namespace, or group documentation), provided this scope is documented. If set
    # to NO, structs, classes, and unions are shown on a separate page (for HTML and
    # Man pages) or section (for LaTeX and RTF).
    # The default value is: NO.


    INLINE_SIMPLE_STRUCTS  = NO


    # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
    # enum is documented as struct, union, or enum with the name of the typedef. So
    # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
    # with name TypeT. When disabled the typedef will appear as a member of a file,
    # namespace, or class. And the struct will be named TypeS. This can typically be
    # useful for C code in case the coding convention dictates that all compound
    # types are typedef'ed and only the typedef is referenced, never the tag name.
    # The default value is: NO.


    TYPEDEF_HIDES_STRUCT   = NO


    # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
    # cache is used to resolve symbols given their name and scope. Since this can be
    # an expensive process and often the same symbol appears multiple times in the
    # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
    # doxygen will become slower. If the cache is too large, memory is wasted. The
    # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
    # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
    # symbols. At the end of a run doxygen will report the cache usage and suggest
    # the optimal cache size from a speed point of view.
    # Minimum value: 0, maximum value: 9, default value: 0.


    LOOKUP_CACHE_SIZE      = 0


    #---------------------------------------------------------------------------
    # Build related configuration options
    #---------------------------------------------------------------------------


    # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
    # documentation are documented, even if no documentation was available. Private
    # class members and static file members will be hidden unless the
    # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
    # Note: This will also disable the warnings about undocumented members that are
    # normally produced when WARNINGS is set to YES.
    # The default value is: NO.


    EXTRACT_ALL            = YES


    # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
    # be included in the documentation.
    # The default value is: NO.


    EXTRACT_PRIVATE        = YES


    # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
    # scope will be included in the documentation.
    # The default value is: NO.


    EXTRACT_PACKAGE        = NO


    # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
    # included in the documentation.
    # The default value is: NO.


    EXTRACT_STATIC         = YES


    # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
    # locally in source files will be included in the documentation. If set to NO,
    # only classes defined in header files are included. Does not have any effect
    # for Java sources.
    # The default value is: YES.


    EXTRACT_LOCAL_CLASSES  = YES


    # This flag is only useful for Objective-C code. If set to YES, local methods,
    # which are defined in the implementation section but not in the interface are
    # included in the documentation. If set to NO, only methods in the interface are
    # included.
    # The default value is: NO.


    EXTRACT_LOCAL_METHODS  = NO


    # If this flag is set to YES, the members of anonymous namespaces will be
    # extracted and appear in the documentation as a namespace called
    # 'anonymous_namespace{file}', where file will be replaced with the base name of
    # the file that contains the anonymous namespace. By default anonymous namespace
    # are hidden.
    # The default value is: NO.


    EXTRACT_ANON_NSPACES   = NO


    # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
    # undocumented members inside documented classes or files. If set to NO these
    # members will be included in the various overviews, but no documentation
    # section is generated. This option has no effect if EXTRACT_ALL is enabled.
    # The default value is: NO.


    HIDE_UNDOC_MEMBERS     = NO


    # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
    # undocumented classes that are normally visible in the class hierarchy. If set
    # to NO, these classes will be included in the various overviews. This option
    # has no effect if EXTRACT_ALL is enabled.
    # The default value is: NO.


    HIDE_UNDOC_CLASSES     = NO


    # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
    # (class|struct|union) declarations. If set to NO, these declarations will be
    # included in the documentation.
    # The default value is: NO.


    HIDE_FRIEND_COMPOUNDS  = NO


    # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
    # documentation blocks found inside the body of a function. If set to NO, these
    # blocks will be appended to the function's detailed documentation block.
    # The default value is: NO.


    HIDE_IN_BODY_DOCS      = NO


    # The INTERNAL_DOCS tag determines if documentation that is typed after a
    # \internal command is included. If the tag is set to NO then the documentation
    # will be excluded. Set it to YES to include the internal documentation.
    # The default value is: NO.


    INTERNAL_DOCS          = NO


    # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
    # names in lower-case letters. If set to YES, upper-case letters are also
    # allowed. This is useful if you have classes or files whose names only differ
    # in case and if your file system supports case sensitive file names. Windows
    # and Mac users are advised to set this option to NO.
    # The default value is: system dependent.


    CASE_SENSE_NAMES       = NO


    # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
    # their full class and namespace scopes in the documentation. If set to YES, the
    # scope will be hidden.
    # The default value is: NO.


    HIDE_SCOPE_NAMES       = NO


    # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
    # append additional text to a page's title, such as Class Reference. If set to
    # YES the compound reference will be hidden.
    # The default value is: NO.


    HIDE_COMPOUND_REFERENCE= NO


    # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
    # the files that are included by a file in the documentation of that file.
    # The default value is: YES.


    SHOW_INCLUDE_FILES     = YES


    # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
    # grouped member an include statement to the documentation, telling the reader
    # which file to include in order to use the member.
    # The default value is: NO.


    SHOW_GROUPED_MEMB_INC  = NO


    # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
    # files with double quotes in the documentation rather than with sharp brackets.
    # The default value is: NO.


    FORCE_LOCAL_INCLUDES   = NO


    # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
    # documentation for inline members.
    # The default value is: YES.


    INLINE_INFO            = YES


    # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
    # (detailed) documentation of file and class members alphabetically by member
    # name. If set to NO, the members will appear in declaration order.
    # The default value is: YES.


    SORT_MEMBER_DOCS       = NO


    # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
    # descriptions of file, namespace and class members alphabetically by member
    # name. If set to NO, the members will appear in declaration order. Note that
    # this will also influence the order of the classes in the class list.
    # The default value is: NO.


    SORT_BRIEF_DOCS        = NO


    # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
    # (brief and detailed) documentation of class members so that constructors and
    # destructors are listed first. If set to NO the constructors will appear in the
    # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
    # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
    # member documentation.
    # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
    # detailed member documentation.
    # The default value is: NO.


    SORT_MEMBERS_CTORS_1ST = NO


    # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
    # of group names into alphabetical order. If set to NO the group names will
    # appear in their defined order.
    # The default value is: NO.


    SORT_GROUP_NAMES       = NO


    # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
    # fully-qualified names, including namespaces. If set to NO, the class list will
    # be sorted only by class name, not including the namespace part.
    # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
    # Note: This option applies only to the class list, not to the alphabetical
    # list.
    # The default value is: NO.


    SORT_BY_SCOPE_NAME     = NO


    # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
    # type resolution of all parameters of a function it will reject a match between
    # the prototype and the implementation of a member function even if there is
    # only one candidate or it is obvious which candidate to choose by doing a
    # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
    # accept a match between prototype and implementation in such cases.
    # The default value is: NO.


    STRICT_PROTO_MATCHING  = NO


    # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
    # list. This list is created by putting \todo commands in the documentation.
    # The default value is: YES.


    GENERATE_TODOLIST      = YES


    # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
    # list. This list is created by putting \test commands in the documentation.
    # The default value is: YES.


    GENERATE_TESTLIST      = YES


    # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
    # list. This list is created by putting \bug commands in the documentation.
    # The default value is: YES.


    GENERATE_BUGLIST       = YES


    # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
    # the deprecated list. This list is created by putting \deprecated commands in
    # the documentation.
    # The default value is: YES.


    GENERATE_DEPRECATEDLIST= YES


    # The ENABLED_SECTIONS tag can be used to enable conditional documentation
    # sections, marked by \if <section_label> ... \endif and \cond <section_label>
    # ... \endcond blocks.


    ENABLED_SECTIONS       = 


    # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
    # initial value of a variable or macro / define can have for it to appear in the
    # documentation. If the initializer consists of more lines than specified here
    # it will be hidden. Use a value of 0 to hide initializers completely. The
    # appearance of the value of individual variables and macros / defines can be
    # controlled using \showinitializer or \hideinitializer command in the
    # documentation regardless of this setting.
    # Minimum value: 0, maximum value: 10000, default value: 30.


    MAX_INITIALIZER_LINES  = 30


    # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
    # the bottom of the documentation of classes and structs. If set to YES, the
    # list will mention the files that were used to generate the documentation.
    # The default value is: YES.


    SHOW_USED_FILES        = NO


    # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
    # will remove the Files entry from the Quick Index and from the Folder Tree View
    # (if specified).
    # The default value is: YES.


    SHOW_FILES             = YES


    # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
    # page. This will remove the Namespaces entry from the Quick Index and from the
    # Folder Tree View (if specified).
    # The default value is: YES.


    SHOW_NAMESPACES        = YES


    # The FILE_VERSION_FILTER tag can be used to specify a program or script that
    # doxygen should invoke to get the current version for each file (typically from
    # the version control system). Doxygen will invoke the program by executing (via
    # popen()) the command command input-file, where command is the value of the
    # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
    # by doxygen. Whatever the program writes to standard output is used as the file
    # version. For an example see the documentation.


    FILE_VERSION_FILTER    = 


    # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
    # by doxygen. The layout file controls the global structure of the generated
    # output files in an output format independent way. To create the layout file
    # that represents doxygen's defaults, run doxygen with the -l option. You can
    # optionally specify a file name after the option, if omitted DoxygenLayout.xml
    # will be used as the name of the layout file.
    #
    # Note that if you run doxygen from a directory containing a file called
    # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
    # tag is left empty.


    LAYOUT_FILE            = 


    # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
    # the reference definitions. This must be a list of .bib files. The .bib
    # extension is automatically appended if omitted. This requires the bibtex tool
    # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
    # For LaTeX the style of the bibliography can be controlled using
    # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
    # search path. See also \cite for info how to create references.


    CITE_BIB_FILES         = 


    #---------------------------------------------------------------------------
    # Configuration options related to warning and progress messages
    #---------------------------------------------------------------------------


    # The QUIET tag can be used to turn on/off the messages that are generated to
    # standard output by doxygen. If QUIET is set to YES this implies that the
    # messages are off.
    # The default value is: NO.


    QUIET                  = NO


    # The WARNINGS tag can be used to turn on/off the warning messages that are
    # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
    # this implies that the warnings are on.
    #
    # Tip: Turn warnings on while writing the documentation.
    # The default value is: YES.


    WARNINGS               = YES


    # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
    # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
    # will automatically be disabled.
    # The default value is: YES.


    WARN_IF_UNDOCUMENTED   = YES


    # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
    # potential errors in the documentation, such as not documenting some parameters
    # in a documented function, or documenting parameters that don't exist or using
    # markup commands wrongly.
    # The default value is: YES.


    WARN_IF_DOC_ERROR      = YES


    # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
    # are documented, but have no documentation for their parameters or return
    # value. If set to NO, doxygen will only warn about wrong or incomplete
    # parameter documentation, but not about the absence of documentation.
    # The default value is: NO.


    WARN_NO_PARAMDOC       = NO


    # The WARN_FORMAT tag determines the format of the warning messages that doxygen
    # can produce. The string should contain the $file, $line, and $text tags, which
    # will be replaced by the file and line number from which the warning originated
    # and the warning text. Optionally the format may contain $version, which will
    # be replaced by the version of the file (if it could be obtained via
    # FILE_VERSION_FILTER)
    # The default value is: $file:$line: $text.


    WARN_FORMAT            = "$file:$line: $text"


    # The WARN_LOGFILE tag can be used to specify a file to which warning and error
    # messages should be written. If left blank the output is written to standard
    # error (stderr).


    WARN_LOGFILE           = 


    #---------------------------------------------------------------------------
    # Configuration options related to the input files
    #---------------------------------------------------------------------------


    # The INPUT tag is used to specify the files and/or directories that contain
    # documented source files. You may enter file names like myfile.cpp or
    # directories like /usr/src/myproject. Separate the files or directories with
    # spaces.
    # Note: If this tag is empty the current directory is searched.


    INPUT                  = "Power Manager"


    # This tag can be used to specify the character encoding of the source files
    # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
    # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
    # documentation (see: http://www.gnu.org/software/libiconv) for the list of
    # possible encodings.
    # The default value is: UTF-8.


    INPUT_ENCODING         = UTF-8


    # If the value of the INPUT tag contains directories, you can use the
    # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
    # *.h) to filter out the source-files in the directories. If left blank the
    # following patterns are tested:*.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, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
    # *.qsf, *.as and *.js.


    FILE_PATTERNS          = *.c \
                             *.cc \
                             *.cxx \
                             *.cpp \
                             *.c++ \
                             *.d \
                             *.java \
                             *.ii \
                             *.ixx \
                             *.ipp \
                             *.i++ \
                             *.inl \
                             *.h \
                             *.hh \
                             *.hxx \
                             *.hpp \
                             *.h++ \
                             *.idl \
                             *.odl \
                             *.cs \
                             *.php \
                             *.php3 \
                             *.inc \
                             *.m \
                             *.mm \
                             *.dox \
                             *.py \
                             *.f90 \
                             *.f \
                             *.for \
                             *.vhd \
                             *.vhdl


    # The RECURSIVE tag can be used to specify whether or not subdirectories should
    # be searched for input files as well.
    # The default value is: NO.


    RECURSIVE              = YES


    # The EXCLUDE tag can be used to specify files and/or directories that should be
    # excluded from the INPUT source files. This way you can easily exclude a
    # subdirectory from a directory tree whose root is specified with the INPUT tag.
    #
    # Note that relative paths are relative to the directory from which doxygen is
    # run.


    EXCLUDE                = 


    # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
    # directories that are symbolic links (a Unix file system feature) are excluded
    # from the input.
    # The default value is: NO.


    EXCLUDE_SYMLINKS       = NO


    # If the value of the INPUT tag contains directories, you can use the
    # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
    # certain files from those directories.
    #
    # Note that the wildcards are matched against the file with absolute path, so to
    # exclude all test directories for example use the pattern */test/*


    EXCLUDE_PATTERNS       = 


    # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
    # (namespaces, classes, functions, etc.) that should be excluded from the
    # output. The symbol name can be a fully qualified name, a word, or if the
    # wildcard * is used, a substring. Examples: ANamespace, AClass,
    # AClass::ANamespace, ANamespace::*Test
    #
    # Note that the wildcards are matched against the file with absolute path, so to
    # exclude all test directories use the pattern */test/*


    EXCLUDE_SYMBOLS        = 


    # The EXAMPLE_PATH tag can be used to specify one or more files or directories
    # that contain example code fragments that are included (see the \include
    # command).


    EXAMPLE_PATH           = 


    # If the value of the EXAMPLE_PATH tag contains directories, you can use the
    # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
    # *.h) to filter out the source-files in the directories. If left blank all
    # files are included.


    EXAMPLE_PATTERNS       = *


    # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
    # searched for input files to be used with the \include or \dontinclude commands
    # irrespective of the value of the RECURSIVE tag.
    # The default value is: NO.


    EXAMPLE_RECURSIVE      = NO


    # The IMAGE_PATH tag can be used to specify one or more files or directories
    # that contain images that are to be included in the documentation (see the
    # \image command).


    IMAGE_PATH             = 


    # The INPUT_FILTER tag can be used to specify a program that doxygen should
    # invoke to filter for each input file. Doxygen will invoke the filter program
    # by executing (via popen()) the command:
    #
    # <filter> <input-file>
    #
    # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
    # name of an input file. Doxygen will then use the output that the filter
    # program writes to standard output. If FILTER_PATTERNS is specified, this tag
    # will be ignored.
    #
    # Note that the filter must not add or remove lines; it is applied before the
    # code is scanned, but not when the output code is generated. If lines are added
    # or removed, the anchors will not be placed correctly.


    INPUT_FILTER           = 


    # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
    # basis. Doxygen will compare the file name with each pattern and apply the
    # filter if there is a match. The filters are a list of the form: pattern=filter
    # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
    # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
    # patterns match the file name, INPUT_FILTER is applied.


    FILTER_PATTERNS        = 


    # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
    # INPUT_FILTER) will also be used to filter the input files that are used for
    # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
    # The default value is: NO.


    FILTER_SOURCE_FILES    = NO


    # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
    # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
    # it is also possible to disable source filtering for a specific pattern using
    # *.ext= (so without naming a filter).
    # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.


    FILTER_SOURCE_PATTERNS = 


    # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
    # is part of the input, its contents will be placed on the main page
    # (index.html). This can be useful if you have a project on for instance GitHub
    # and want to reuse the introduction page also for the doxygen output.


    USE_MDFILE_AS_MAINPAGE = 


    #---------------------------------------------------------------------------
    # Configuration options related to source browsing
    #---------------------------------------------------------------------------


    # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
    # generated. Documented entities will be cross-referenced with these sources.
    #
    # Note: To get rid of all source code in the generated output, make sure that
    # also VERBATIM_HEADERS is set to NO.
    # The default value is: NO.


    SOURCE_BROWSER         = NO


    # Setting the INLINE_SOURCES tag to YES will include the body of functions,
    # classes and enums directly into the documentation.
    # The default value is: NO.


    INLINE_SOURCES         = NO


    # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
    # special comment blocks from generated source code fragments. Normal C, C++ and
    # Fortran comments will always remain visible.
    # The default value is: YES.


    STRIP_CODE_COMMENTS    = YES


    # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
    # function all documented functions referencing it will be listed.
    # The default value is: NO.


    REFERENCED_BY_RELATION = NO


    # If the REFERENCES_RELATION tag is set to YES then for each documented function
    # all documented entities called/used by that function will be listed.
    # The default value is: NO.


    REFERENCES_RELATION    = NO


    # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
    # to YES then the hyperlinks from functions in REFERENCES_RELATION and
    # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
    # link to the documentation.
    # The default value is: YES.


    REFERENCES_LINK_SOURCE = YES


    # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
    # source code will show a tooltip with additional information such as prototype,
    # brief description and links to the definition and documentation. Since this
    # will make the HTML file larger and loading of large files a bit slower, you
    # can opt to disable this feature.
    # The default value is: YES.
    # This tag requires that the tag SOURCE_BROWSER is set to YES.


    SOURCE_TOOLTIPS        = YES


    # If the USE_HTAGS tag is set to YES then the references to source code will
    # point to the HTML generated by the htags(1) tool instead of doxygen built-in
    # source browser. The htags tool is part of GNU's global source tagging system
    # (see http://www.gnu.org/software/global/global.html). You will need version
    # 4.8.6 or higher.
    #
    # To use it do the following:
    # - Install the latest version of global
    # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
    # - Make sure the INPUT points to the root of the source tree
    # - Run doxygen as normal
    #
    # Doxygen will invoke htags (and that will in turn invoke gtags), so these
    # tools must be available from the command line (i.e. in the search path).
    #
    # The result: instead of the source browser generated by doxygen, the links to
    # source code will now point to the output of htags.
    # The default value is: NO.
    # This tag requires that the tag SOURCE_BROWSER is set to YES.


    USE_HTAGS              = NO


    # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
    # verbatim copy of the header file for each class for which an include is
    # specified. Set to NO to disable this.
    # See also: Section \class.
    # The default value is: YES.


    VERBATIM_HEADERS       = YES


    # If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the
    # clang parser (see: http://clang.llvm.org/) for more accurate parsing at the
    # cost of reduced performance. This can be particularly helpful with template
    # rich C++ code for which doxygen's built-in parser lacks the necessary type
    # information.
    # Note: The availability of this option depends on whether or not doxygen was
    # compiled with the --with-libclang option.
    # The default value is: NO.


    CLANG_ASSISTED_PARSING = NO


    # If clang assisted parsing is enabled you can provide the compiler with command
    # line options that you would normally use when invoking the compiler. Note that
    # the include paths will already be set by doxygen for the files and directories
    # specified with INPUT and INCLUDE_PATH.
    # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.


    CLANG_OPTIONS          = 


    #---------------------------------------------------------------------------
    # Configuration options related to the alphabetical class index
    #---------------------------------------------------------------------------


    # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
    # compounds will be generated. Enable this if the project contains a lot of
    # classes, structs, unions or interfaces.
    # The default value is: YES.


    ALPHABETICAL_INDEX     = YES


    # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
    # which the alphabetical index list will be split.
    # Minimum value: 1, maximum value: 20, default value: 5.
    # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.


    COLS_IN_ALPHA_INDEX    = 5


    # In case all classes in a project start with a common prefix, all classes will
    # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
    # can be used to specify a prefix (or a list of prefixes) that should be ignored
    # while generating the index headers.
    # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.


    IGNORE_PREFIX          = 


    #---------------------------------------------------------------------------
    # Configuration options related to the HTML output
    #---------------------------------------------------------------------------


    # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
    # The default value is: YES.


    GENERATE_HTML          = YES


    # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
    # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
    # it.
    # The default directory is: html.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_OUTPUT            = html


    # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
    # generated HTML page (for example: .htm, .php, .asp).
    # The default value is: .html.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_FILE_EXTENSION    = .html


    # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
    # each generated HTML page. If the tag is left blank doxygen will generate a
    # standard header.
    #
    # To get valid HTML the header file that includes any scripts and style sheets
    # that doxygen needs, which is dependent on the configuration options used (e.g.
    # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
    # default header using
    # doxygen -w html new_header.html new_footer.html new_stylesheet.css
    # YourConfigFile
    # and then modify the file new_header.html. See also section "Doxygen usage"
    # for information on how to generate the default header that doxygen normally
    # uses.
    # Note: The header is subject to change so you typically have to regenerate the
    # default header when upgrading to a newer version of doxygen. For a description
    # of the possible markers and block names see the documentation.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_HEADER            = 


    # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
    # generated HTML page. If the tag is left blank doxygen will generate a standard
    # footer. See HTML_HEADER for more information on how to generate a default
    # footer and what special commands can be used inside the footer. See also
    # section "Doxygen usage" for information on how to generate the default footer
    # that doxygen normally uses.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_FOOTER            = 


    # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
    # sheet that is used by each HTML page. It can be used to fine-tune the look of
    # the HTML output. If left blank doxygen will generate a default style sheet.
    # See also section "Doxygen usage" for information on how to generate the style
    # sheet that doxygen normally uses.
    # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
    # it is more robust and this tag (HTML_STYLESHEET) will in the future become
    # obsolete.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_STYLESHEET        = 


    # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
    # cascading style sheets that are included after the standard style sheets
    # created by doxygen. Using this option one can overrule certain style aspects.
    # This is preferred over using HTML_STYLESHEET since it does not replace the
    # standard style sheet and is therefore more robust against future updates.
    # Doxygen will copy the style sheet files to the output directory.
    # Note: The order of the extra style sheet files is of importance (e.g. the last
    # style sheet in the list overrules the setting of the previous ones in the
    # list). For an example see the documentation.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_EXTRA_STYLESHEET  = 


    # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
    # other source files which should be copied to the HTML output directory. Note
    # that these files will be copied to the base HTML output directory. Use the
    # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
    # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
    # files will be copied as-is; there are no commands or markers available.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_EXTRA_FILES       = 


    # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
    # will adjust the colors in the style sheet and background images according to
    # this color. Hue is specified as an angle on a colorwheel, see
    # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
    # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
    # purple, and 360 is red again.
    # Minimum value: 0, maximum value: 359, default value: 220.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_COLORSTYLE_HUE    = 220


    # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
    # in the HTML output. For a value of 0 the output will use grayscales only. A
    # value of 255 will produce the most vivid colors.
    # Minimum value: 0, maximum value: 255, default value: 100.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_COLORSTYLE_SAT    = 100


    # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
    # luminance component of the colors in the HTML output. Values below 100
    # gradually make the output lighter, whereas values above 100 make the output
    # darker. The value divided by 100 is the actual gamma applied, so 80 represents
    # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
    # change the gamma.
    # Minimum value: 40, maximum value: 240, default value: 80.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_COLORSTYLE_GAMMA  = 80


    # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
    # page will contain the date and time when the page was generated. Setting this
    # to NO can help when comparing the output of multiple runs.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_TIMESTAMP         = YES


    # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
    # documentation will contain sections that can be hidden and shown after the
    # page has loaded.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_DYNAMIC_SECTIONS  = NO


    # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
    # shown in the various tree structured indices initially; the user can expand
    # and collapse entries dynamically later on. Doxygen will expand the tree to
    # such a level that at most the specified number of entries are visible (unless
    # a fully collapsed tree already exceeds this amount). So setting the number of
    # entries 1 will produce a full collapsed tree by default. 0 is a special value
    # representing an infinite number of entries and will result in a full expanded
    # tree by default.
    # Minimum value: 0, maximum value: 9999, default value: 100.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    HTML_INDEX_NUM_ENTRIES = 100


    # If the GENERATE_DOCSET tag is set to YES, additional index files will be
    # generated that can be used as input for Apple's Xcode 3 integrated development
    # environment (see: http://developer.apple.com/tools/xcode/), introduced with
    # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
    # Makefile in the HTML output directory. Running make will produce the docset in
    # that directory and running make install will install the docset in
    # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
    # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
    # for more information.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    GENERATE_DOCSET        = NO


    # This tag determines the name of the docset feed. A documentation feed provides
    # an umbrella under which multiple documentation sets from a single provider
    # (such as a company or product suite) can be grouped.
    # The default value is: Doxygen generated docs.
    # This tag requires that the tag GENERATE_DOCSET is set to YES.


    DOCSET_FEEDNAME        = "Doxygen generated docs"


    # This tag specifies a string that should uniquely identify the documentation
    # set bundle. This should be a reverse domain-name style string, e.g.
    # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
    # The default value is: org.doxygen.Project.
    # This tag requires that the tag GENERATE_DOCSET is set to YES.


    DOCSET_BUNDLE_ID       = org.doxygen.Project


    # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
    # the documentation publisher. This should be a reverse domain-name style
    # string, e.g. com.mycompany.MyDocSet.documentation.
    # The default value is: org.doxygen.Publisher.
    # This tag requires that the tag GENERATE_DOCSET is set to YES.


    DOCSET_PUBLISHER_ID    = org.doxygen.Publisher


    # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
    # The default value is: Publisher.
    # This tag requires that the tag GENERATE_DOCSET is set to YES.


    DOCSET_PUBLISHER_NAME  = Publisher


    # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
    # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
    # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
    # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
    # Windows.
    #
    # The HTML Help Workshop contains a compiler that can convert all HTML output
    # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
    # files are now used as the Windows 98 help format, and will replace the old
    # Windows help format (.hlp) on all Windows platforms in the future. Compressed
    # HTML files also contain an index, a table of contents, and you can search for
    # words in the documentation. The HTML workshop also contains a viewer for
    # compressed HTML files.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    GENERATE_HTMLHELP      = YES


    # The CHM_FILE tag can be used to specify the file name of the resulting .chm
    # file. You can add a path in front of the file if the result should not be
    # written to the html output directory.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    CHM_FILE               = 


    # The HHC_LOCATION tag can be used to specify the location (absolute path
    # including file name) of the HTML help compiler (hhc.exe). If non-empty,
    # doxygen will try to run the HTML help compiler on the generated index.hhp.
    # The file has to be specified with full path.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    HHC_LOCATION           = "C:/Program Files (x86)/HTML Help Workshop/hhc.exe"


    # The GENERATE_CHI flag controls if a separate .chi index file is generated
    # (YES) or that it should be included in the master .chm file (NO).
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    GENERATE_CHI           = NO


    # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
    # and project file content.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    CHM_INDEX_ENCODING     = GB2312


    # The BINARY_TOC flag controls whether a binary table of contents is generated
    # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
    # enables the Previous and Next buttons.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    BINARY_TOC             = NO


    # The TOC_EXPAND flag can be set to YES to add extra items for group members to
    # the table of contents of the HTML help documentation and to the tree view.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTMLHELP is set to YES.


    TOC_EXPAND             = NO


    # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
    # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
    # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
    # (.qch) of the generated HTML documentation.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    GENERATE_QHP           = NO


    # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
    # the file name of the resulting .qch file. The path specified is relative to
    # the HTML output folder.
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QCH_FILE               = 


    # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
    # Project output. For more information please see Qt Help Project / Namespace
    # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
    # The default value is: org.doxygen.Project.
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHP_NAMESPACE          = org.doxygen.Project


    # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
    # Help Project output. For more information please see Qt Help Project / Virtual
    # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
    # folders).
    # The default value is: doc.
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHP_VIRTUAL_FOLDER     = doc


    # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
    # filter to add. For more information please see Qt Help Project / Custom
    # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
    # filters).
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHP_CUST_FILTER_NAME   = 


    # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
    # custom filter to add. For more information please see Qt Help Project / Custom
    # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
    # filters).
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHP_CUST_FILTER_ATTRS  = 


    # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
    # project's filter section matches. Qt Help Project / Filter Attributes (see:
    # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHP_SECT_FILTER_ATTRS  = 


    # The QHG_LOCATION tag can be used to specify the location of Qt's
    # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
    # generated .qhp file.
    # This tag requires that the tag GENERATE_QHP is set to YES.


    QHG_LOCATION           = 


    # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
    # generated, together with the HTML files, they form an Eclipse help plugin. To
    # install this plugin and make it available under the help contents menu in
    # Eclipse, the contents of the directory containing the HTML and XML files needs
    # to be copied into the plugins directory of eclipse. The name of the directory
    # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
    # After copying Eclipse needs to be restarted before the help appears.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    GENERATE_ECLIPSEHELP   = NO


    # A unique identifier for the Eclipse help plugin. When installing the plugin
    # the directory name containing the HTML and XML files should also have this
    # name. Each documentation set should have its own identifier.
    # The default value is: org.doxygen.Project.
    # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.


    ECLIPSE_DOC_ID         = org.doxygen.Project


    # If you want full control over the layout of the generated HTML pages it might
    # be necessary to disable the index and replace it with your own. The
    # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
    # of each HTML page. A value of NO enables the index and the value YES disables
    # it. Since the tabs in the index contain the same information as the navigation
    # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    DISABLE_INDEX          = NO


    # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
    # structure should be generated to display hierarchical information. If the tag
    # value is set to YES, a side panel will be generated containing a tree-like
    # index structure (just like the one that is generated for HTML Help). For this
    # to work a browser that supports JavaScript, DHTML, CSS and frames is required
    # (i.e. any modern browser). Windows users are probably better off using the
    # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
    # further fine-tune the look of the index. As an example, the default style
    # sheet generated by doxygen has an example that shows how to put an image at
    # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
    # the same information as the tab index, you could consider setting
    # DISABLE_INDEX to YES when enabling this option.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    GENERATE_TREEVIEW      = NO


    # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
    # doxygen will group on one line in the generated HTML documentation.
    #
    # Note that a value of 0 will completely suppress the enum values from appearing
    # in the overview section.
    # Minimum value: 0, maximum value: 20, default value: 4.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    ENUM_VALUES_PER_LINE   = 4


    # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
    # to set the initial width (in pixels) of the frame in which the tree is shown.
    # Minimum value: 0, maximum value: 1500, default value: 250.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    TREEVIEW_WIDTH         = 250


    # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
    # external symbols imported via tag files in a separate window.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    EXT_LINKS_IN_WINDOW    = NO


    # Use this tag to change the font size of LaTeX formulas included as images in
    # the HTML documentation. When you change the font size after a successful
    # doxygen run you need to manually remove any form_*.png images from the HTML
    # output directory to force them to be regenerated.
    # Minimum value: 8, maximum value: 50, default value: 10.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    FORMULA_FONTSIZE       = 10


    # Use the FORMULA_TRANPARENT tag to determine whether or not the images
    # generated for formulas are transparent PNGs. Transparent PNGs are not
    # supported properly for IE 6.0, but are supported on all modern browsers.
    #
    # Note that when changing this option you need to delete any form_*.png files in
    # the HTML output directory before the changes have effect.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    FORMULA_TRANSPARENT    = YES


    # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
    # http://www.mathjax.org) which uses client side Javascript for the rendering
    # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
    # installed or if you want to formulas look prettier in the HTML output. When
    # enabled you may also need to install MathJax separately and configure the path
    # to it using the MATHJAX_RELPATH option.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    USE_MATHJAX            = NO


    # When MathJax is enabled you can set the default output format to be used for
    # the MathJax output. See the MathJax site (see:
    # http://docs.mathjax.org/en/latest/output.html) for more details.
    # Possible values are: HTML-CSS (which is slower, but has the best
    # compatibility), NativeMML (i.e. MathML) and SVG.
    # The default value is: HTML-CSS.
    # This tag requires that the tag USE_MATHJAX is set to YES.


    MATHJAX_FORMAT         = HTML-CSS


    # When MathJax is enabled you need to specify the location relative to the HTML
    # output directory using the MATHJAX_RELPATH option. The destination directory
    # should contain the MathJax.js script. For instance, if the mathjax directory
    # is located at the same level as the HTML output directory, then
    # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
    # Content Delivery Network so you can quickly see the result without installing
    # MathJax. However, it is strongly recommended to install a local copy of
    # MathJax from http://www.mathjax.org before deployment.
    # The default value is: http://cdn.mathjax.org/mathjax/latest.
    # This tag requires that the tag USE_MATHJAX is set to YES.


    MATHJAX_RELPATH        = http://www.mathjax.org/mathjax


    # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
    # extension names that should be enabled during MathJax rendering. For example
    # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
    # This tag requires that the tag USE_MATHJAX is set to YES.


    MATHJAX_EXTENSIONS     = 


    # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
    # of code that will be used on startup of the MathJax code. See the MathJax site
    # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
    # example see the documentation.
    # This tag requires that the tag USE_MATHJAX is set to YES.


    MATHJAX_CODEFILE       = 


    # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
    # the HTML output. The underlying search engine uses javascript and DHTML and
    # should work on any modern browser. Note that when using HTML help
    # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
    # there is already a search function so this one should typically be disabled.
    # For large projects the javascript based search engine can be slow, then
    # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
    # search using the keyboard; to jump to the search box use <access key> + S
    # (what the <access key> is depends on the OS and browser, but it is typically
    # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
    # key> to jump into the search results window, the results can be navigated
    # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
    # the search. The filter options can be selected when the cursor is inside the
    # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
    # to select a filter and <Enter> or <escape> to activate or cancel the filter
    # option.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_HTML is set to YES.


    SEARCHENGINE           = NO


    # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
    # implemented using a web server instead of a web client using Javascript. There
    # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
    # setting. When disabled, doxygen will generate a PHP script for searching and
    # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
    # and searching needs to be provided by external tools. See the section
    # "External Indexing and Searching" for details.
    # The default value is: NO.
    # This tag requires that the tag SEARCHENGINE is set to YES.


    SERVER_BASED_SEARCH    = NO


    # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
    # script for searching. Instead the search results are written to an XML file
    # which needs to be processed by an external indexer. Doxygen will invoke an
    # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
    # search results.
    #
    # Doxygen ships with an example indexer (doxyindexer) and search engine
    # (doxysearch.cgi) which are based on the open source search engine library
    # Xapian (see: http://xapian.org/).
    #
    # See the section "External Indexing and Searching" for details.
    # The default value is: NO.
    # This tag requires that the tag SEARCHENGINE is set to YES.


    EXTERNAL_SEARCH        = NO


    # The SEARCHENGINE_URL should point to a search engine hosted by a web server
    # which will return the search results when EXTERNAL_SEARCH is enabled.
    #
    # Doxygen ships with an example indexer (doxyindexer) and search engine
    # (doxysearch.cgi) which are based on the open source search engine library
    # Xapian (see: http://xapian.org/). See the section "External Indexing and
    # Searching" for details.
    # This tag requires that the tag SEARCHENGINE is set to YES.


    SEARCHENGINE_URL       = 


    # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
    # search data is written to a file for indexing by an external tool. With the
    # SEARCHDATA_FILE tag the name of this file can be specified.
    # The default file is: searchdata.xml.
    # This tag requires that the tag SEARCHENGINE is set to YES.


    SEARCHDATA_FILE        = searchdata.xml


    # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
    # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
    # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
    # projects and redirect the results back to the right project.
    # This tag requires that the tag SEARCHENGINE is set to YES.


    EXTERNAL_SEARCH_ID     = 


    # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
    # projects other than the one defined by this configuration file, but that are
    # all added to the same external search index. Each project needs to have a
    # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
    # to a relative location where the documentation can be found. The format is:
    # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
    # This tag requires that the tag SEARCHENGINE is set to YES.


    EXTRA_SEARCH_MAPPINGS  = 


    #---------------------------------------------------------------------------
    # Configuration options related to the LaTeX output
    #---------------------------------------------------------------------------


    # If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
    # The default value is: YES.


    GENERATE_LATEX         = NO


    # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
    # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
    # it.
    # The default directory is: latex.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_OUTPUT           = latex


    # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
    # invoked.
    #
    # Note that when enabling USE_PDFLATEX this option is only used for generating
    # bitmaps for formulas in the HTML output, but not in the Makefile that is
    # written to the output directory.
    # The default file is: latex.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_CMD_NAME         = latex


    # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
    # index for LaTeX.
    # The default file is: makeindex.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    MAKEINDEX_CMD_NAME     = makeindex


    # If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
    # documents. This may be useful for small projects and may help to save some
    # trees in general.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    COMPACT_LATEX          = NO


    # The PAPER_TYPE tag can be used to set the paper type that is used by the
    # printer.
    # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
    # 14 inches) and executive (7.25 x 10.5 inches).
    # The default value is: a4.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    PAPER_TYPE             = a4


    # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
    # that should be included in the LaTeX output. To get the times font for
    # instance you can specify
    # EXTRA_PACKAGES=times
    # If left blank no extra packages will be included.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    EXTRA_PACKAGES         = 


    # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
    # generated LaTeX document. The header should contain everything until the first
    # chapter. If it is left blank doxygen will generate a standard header. See
    # section "Doxygen usage" for information on how to let doxygen write the
    # default header to a separate file.
    #
    # Note: Only use a user-defined header if you know what you are doing! The
    # following commands have a special meaning inside the header: $title,
    # $datetime, $date, $doxygenversion, $projectname, $projectnumber,
    # $projectbrief, $projectlogo. Doxygen will replace $title with the empty
    # string, for the replacement values of the other commands the user is referred
    # to HTML_HEADER.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_HEADER           = 


    # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
    # generated LaTeX document. The footer should contain everything after the last
    # chapter. If it is left blank doxygen will generate a standard footer. See
    # LATEX_HEADER for more information on how to generate a default footer and what
    # special commands can be used inside the footer.
    #
    # Note: Only use a user-defined footer if you know what you are doing!
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_FOOTER           = 


    # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
    # LaTeX style sheets that are included after the standard style sheets created
    # by doxygen. Using this option one can overrule certain style aspects. Doxygen
    # will copy the style sheet files to the output directory.
    # Note: The order of the extra style sheet files is of importance (e.g. the last
    # style sheet in the list overrules the setting of the previous ones in the
    # list).
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_EXTRA_STYLESHEET = 


    # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
    # other source files which should be copied to the LATEX_OUTPUT output
    # directory. Note that the files will be copied as-is; there are no commands or
    # markers available.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_EXTRA_FILES      = 


    # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
    # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
    # contain links (just like the HTML output) instead of page references. This
    # makes the output suitable for online browsing using a PDF viewer.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    PDF_HYPERLINKS         = YES


    # If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
    # the PDF file directly from the LaTeX files. Set this option to YES, to get a
    # higher quality PDF documentation.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    USE_PDFLATEX           = YES


    # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
    # command to the generated LaTeX files. This will instruct LaTeX to keep running
    # if errors occur, instead of asking the user for help. This option is also used
    # when generating formulas in HTML.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_BATCHMODE        = NO


    # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
    # index chapters (such as File Index, Compound Index, etc.) in the output.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_HIDE_INDICES     = NO


    # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
    # code with syntax highlighting in the LaTeX output.
    #
    # Note that which sources are shown also depends on other settings such as
    # SOURCE_BROWSER.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_SOURCE_CODE      = NO


    # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
    # bibliography, e.g. plainnat, or ieeetr. See
    # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
    # The default value is: plain.
    # This tag requires that the tag GENERATE_LATEX is set to YES.


    LATEX_BIB_STYLE        = plain


    #---------------------------------------------------------------------------
    # Configuration options related to the RTF output
    #---------------------------------------------------------------------------


    # If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
    # RTF output is optimized for Word 97 and may not look too pretty with other RTF
    # readers/editors.
    # The default value is: NO.


    GENERATE_RTF           = NO


    # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
    # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
    # it.
    # The default directory is: rtf.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    RTF_OUTPUT             = rtf


    # If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
    # documents. This may be useful for small projects and may help to save some
    # trees in general.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    COMPACT_RTF            = NO


    # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
    # contain hyperlink fields. The RTF file will contain links (just like the HTML
    # output) instead of page references. This makes the output suitable for online
    # browsing using Word or some other Word compatible readers that support those
    # fields.
    #
    # Note: WordPad (write) and others do not support links.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    RTF_HYPERLINKS         = NO


    # Load stylesheet definitions from file. Syntax is similar to doxygen's config
    # file, i.e. a series of assignments. You only have to provide replacements,
    # missing definitions are set to their default value.
    #
    # See also section "Doxygen usage" for information on how to generate the
    # default style sheet that doxygen normally uses.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    RTF_STYLESHEET_FILE    = 


    # Set optional variables used in the generation of an RTF document. Syntax is
    # similar to doxygen's config file. A template extensions file can be generated
    # using doxygen -e rtf extensionFile.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    RTF_EXTENSIONS_FILE    = 


    # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
    # with syntax highlighting in the RTF output.
    #
    # Note that which sources are shown also depends on other settings such as
    # SOURCE_BROWSER.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_RTF is set to YES.


    RTF_SOURCE_CODE        = NO


    #---------------------------------------------------------------------------
    # Configuration options related to the man page output
    #---------------------------------------------------------------------------


    # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
    # classes and files.
    # The default value is: NO.


    GENERATE_MAN           = NO


    # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
    # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
    # it. A directory man3 will be created inside the directory specified by
    # MAN_OUTPUT.
    # The default directory is: man.
    # This tag requires that the tag GENERATE_MAN is set to YES.


    MAN_OUTPUT             = man


    # The MAN_EXTENSION tag determines the extension that is added to the generated
    # man pages. In case the manual section does not start with a number, the number
    # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
    # optional.
    # The default value is: .3.
    # This tag requires that the tag GENERATE_MAN is set to YES.


    MAN_EXTENSION          = .3


    # The MAN_SUBDIR tag determines the name of the directory created within
    # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
    # MAN_EXTENSION with the initial . removed.
    # This tag requires that the tag GENERATE_MAN is set to YES.


    MAN_SUBDIR             = 


    # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
    # will generate one additional man file for each entity documented in the real
    # man page(s). These additional files only source the real man page, but without
    # them the man command would be unable to find the correct page.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_MAN is set to YES.


    MAN_LINKS              = NO


    #---------------------------------------------------------------------------
    # Configuration options related to the XML output
    #---------------------------------------------------------------------------


    # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
    # captures the structure of the code including all documentation.
    # The default value is: NO.


    GENERATE_XML           = NO


    # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
    # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
    # it.
    # The default directory is: xml.
    # This tag requires that the tag GENERATE_XML is set to YES.


    XML_OUTPUT             = xml


    # If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
    # listings (including syntax highlighting and cross-referencing information) to
    # the XML output. Note that enabling this will significantly increase the size
    # of the XML output.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_XML is set to YES.


    XML_PROGRAMLISTING     = YES


    #---------------------------------------------------------------------------
    # Configuration options related to the DOCBOOK output
    #---------------------------------------------------------------------------


    # If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
    # that can be used to generate PDF.
    # The default value is: NO.


    GENERATE_DOCBOOK       = NO


    # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
    # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
    # front of it.
    # The default directory is: docbook.
    # This tag requires that the tag GENERATE_DOCBOOK is set to YES.


    DOCBOOK_OUTPUT         = docbook


    # If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
    # program listings (including syntax highlighting and cross-referencing
    # information) to the DOCBOOK output. Note that enabling this will significantly
    # increase the size of the DOCBOOK output.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_DOCBOOK is set to YES.


    DOCBOOK_PROGRAMLISTING = NO


    #---------------------------------------------------------------------------
    # Configuration options for the AutoGen Definitions output
    #---------------------------------------------------------------------------


    # If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
    # AutoGen Definitions (see http://autogen.sf.net) file that captures the
    # structure of the code including all documentation. Note that this feature is
    # still experimental and incomplete at the moment.
    # The default value is: NO.


    GENERATE_AUTOGEN_DEF   = NO


    #---------------------------------------------------------------------------
    # Configuration options related to the Perl module output
    #---------------------------------------------------------------------------


    # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
    # file that captures the structure of the code including all documentation.
    #
    # Note that this feature is still experimental and incomplete at the moment.
    # The default value is: NO.


    GENERATE_PERLMOD       = NO


    # If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
    # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
    # output from the Perl module output.
    # The default value is: NO.
    # This tag requires that the tag GENERATE_PERLMOD is set to YES.


    PERLMOD_LATEX          = NO


    # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
    # formatted so it can be parsed by a human reader. This is useful if you want to
    # understand what is going on. On the other hand, if this tag is set to NO, the
    # size of the Perl module output will be much smaller and Perl will parse it
    # just the same.
    # The default value is: YES.
    # This tag requires that the tag GENERATE_PERLMOD is set to YES.


    PERLMOD_PRETTY         = YES


    # The names of the make variables in the generated doxyrules.make file are
    # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
    # so different doxyrules.make files included by the same Makefile don't
    # overwrite each other's variables.
    # This tag requires that the tag GENERATE_PERLMOD is set to YES.


    PERLMOD_MAKEVAR_PREFIX = 


    #---------------------------------------------------------------------------
    # Configuration options related to the preprocessor
    #---------------------------------------------------------------------------


    # If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
    # C-preprocessor directives found in the sources and include files.
    # The default value is: YES.


    ENABLE_PREPROCESSING   = YES


    # If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
    # in the source code. If set to NO, only conditional compilation will be
    # performed. Macro expansion can be done in a controlled way by setting
    # EXPAND_ONLY_PREDEF to YES.
    # The default value is: NO.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    MACRO_EXPANSION        = NO


    # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
    # the macro expansion is limited to the macros specified with the PREDEFINED and
    # EXPAND_AS_DEFINED tags.
    # The default value is: NO.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    EXPAND_ONLY_PREDEF     = NO


    # If the SEARCH_INCLUDES tag is set to YES, the include files in the
    # INCLUDE_PATH will be searched if a #include is found.
    # The default value is: YES.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    SEARCH_INCLUDES        = YES


    # The INCLUDE_PATH tag can be used to specify one or more directories that
    # contain include files that are not input files but should be processed by the
    # preprocessor.
    # This tag requires that the tag SEARCH_INCLUDES is set to YES.


    INCLUDE_PATH           = 


    # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
    # patterns (like *.h and *.hpp) to filter out the header-files in the
    # directories. If left blank, the patterns specified with FILE_PATTERNS will be
    # used.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    INCLUDE_FILE_PATTERNS  = 


    # The PREDEFINED tag can be used to specify one or more macro names that are
    # defined before the preprocessor is started (similar to the -D option of e.g.
    # gcc). The argument of the tag is a list of macros of the form: name or
    # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
    # is assumed. To prevent a macro definition from being undefined via #undef or
    # recursively expanded use the := operator instead of the = operator.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    PREDEFINED             = 


    # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
    # tag can be used to specify a list of macro names that should be expanded. The
    # macro definition that is found in the sources will be used. Use the PREDEFINED
    # tag if you want to use a different macro definition that overrules the
    # definition found in the source code.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    EXPAND_AS_DEFINED      = 


    # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
    # remove all references to function-like macros that are alone on a line, have
    # an all uppercase name, and do not end with a semicolon. Such function macros
    # are typically used for boiler-plate code, and will confuse the parser if not
    # removed.
    # The default value is: YES.
    # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.


    SKIP_FUNCTION_MACROS   = YES


    #---------------------------------------------------------------------------
    # Configuration options related to external references
    #---------------------------------------------------------------------------


    # The TAGFILES tag can be used to specify one or more tag files. For each tag
    # file the location of the external documentation should be added. The format of
    # a tag file without this location is as follows:
    # TAGFILES = file1 file2 ...
    # Adding location for the tag files is done as follows:
    # TAGFILES = file1=loc1 "file2 = loc2" ...
    # where loc1 and loc2 can be relative or absolute paths or URLs. See the
    # section "Linking to external documentation" for more information about the use
    # of tag files.
    # Note: Each tag file must have a unique name (where the name does NOT include
    # the path). If a tag file is not located in the directory in which doxygen is
    # run, you must also specify the path to the tagfile here.


    TAGFILES               = 


    # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
    # tag file that is based on the input files it reads. See section "Linking to
    # external documentation" for more information about the usage of tag files.


    GENERATE_TAGFILE       = 


    # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
    # the class index. If set to NO, only the inherited external classes will be
    # listed.
    # The default value is: NO.


    ALLEXTERNALS           = NO


    # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
    # in the modules index. If set to NO, only the current project's groups will be
    # listed.
    # The default value is: YES.


    EXTERNAL_GROUPS        = YES


    # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
    # the related pages index. If set to NO, only the current project's pages will
    # be listed.
    # The default value is: YES.


    EXTERNAL_PAGES         = YES


    # The PERL_PATH should be the absolute path and name of the perl script
    # interpreter (i.e. the result of 'which perl').
    # The default file (with absolute path) is: /usr/bin/perl.


    PERL_PATH              = /usr/bin/perl


    #---------------------------------------------------------------------------
    # Configuration options related to the dot tool
    #---------------------------------------------------------------------------


    # If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
    # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
    # NO turns the diagrams off. Note that this option also works with HAVE_DOT
    # disabled, but it is recommended to install and use dot, since it yields more
    # powerful graphs.
    # The default value is: YES.


    CLASS_DIAGRAMS         = YES


    # You can define message sequence charts within doxygen comments using the \msc
    # command. Doxygen will then run the mscgen tool (see:
    # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
    # documentation. The MSCGEN_PATH tag allows you to specify the directory where
    # the mscgen tool resides. If left empty the tool is assumed to be found in the
    # default search path.


    MSCGEN_PATH            = 


    # You can include diagrams made with dia in doxygen documentation. Doxygen will
    # then run dia to produce the diagram and insert it in the documentation. The
    # DIA_PATH tag allows you to specify the directory where the dia binary resides.
    # If left empty dia is assumed to be found in the default search path.


    DIA_PATH               = 


    # If set to YES the inheritance and collaboration graphs will hide inheritance
    # and usage relations if the target is undocumented or is not a class.
    # The default value is: YES.


    HIDE_UNDOC_RELATIONS   = YES


    # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
    # available from the path. This tool is part of Graphviz (see:
    # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
    # Bell Labs. The other options in this section have no effect if this option is
    # set to NO
    # The default value is: NO.


    HAVE_DOT               = YES


    # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
    # to run in parallel. When set to 0 doxygen will base this on the number of
    # processors available in the system. You can set it explicitly to a value
    # larger than 0 to get control over the balance between CPU load and processing
    # speed.
    # Minimum value: 0, maximum value: 32, default value: 0.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_NUM_THREADS        = 0


    # When you want a differently looking font in the dot files that doxygen
    # generates you can specify the font name using DOT_FONTNAME. You need to make
    # sure dot is able to find the font, which can be done by putting it in a
    # standard location or by setting the DOTFONTPATH environment variable or by
    # setting DOT_FONTPATH to the directory containing the font.
    # The default value is: Helvetica.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_FONTNAME           = Helvetica


    # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
    # dot graphs.
    # Minimum value: 4, maximum value: 24, default value: 10.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_FONTSIZE           = 10


    # By default doxygen will tell dot to use the default font as specified with
    # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
    # the path where dot can find it using this tag.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_FONTPATH           = 


    # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
    # each documented class showing the direct and indirect inheritance relations.
    # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    CLASS_GRAPH            = YES


    # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
    # graph for each documented class showing the direct and indirect implementation
    # dependencies (inheritance, containment, and class references variables) of the
    # class with other documented classes.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    COLLABORATION_GRAPH    = YES


    # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
    # groups, showing the direct groups dependencies.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    GROUP_GRAPHS           = YES


    # If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
    # collaboration diagrams in a style similar to the OMG's Unified Modeling
    # Language.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    UML_LOOK               = YES


    # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
    # class node. If there are many fields or methods and many nodes the graph may
    # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
    # number of items for each type to make the size more manageable. Set this to 0
    # for no limit. Note that the threshold may be exceeded by 50% before the limit
    # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
    # but if the number exceeds 15, the total amount of fields shown is limited to
    # 10.
    # Minimum value: 0, maximum value: 100, default value: 10.
    # This tag requires that the tag HAVE_DOT is set to YES.


    UML_LIMIT_NUM_FIELDS   = 10


    # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
    # collaboration graphs will show the relations between templates and their
    # instances.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    TEMPLATE_RELATIONS     = NO


    # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
    # YES then doxygen will generate a graph for each documented file showing the
    # direct and indirect include dependencies of the file with other documented
    # files.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    INCLUDE_GRAPH          = YES


    # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
    # set to YES then doxygen will generate a graph for each documented file showing
    # the direct and indirect include dependencies of the file with other documented
    # files.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    INCLUDED_BY_GRAPH      = YES


    # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
    # dependency graph for every global function or class method.
    #
    # Note that enabling this option will significantly increase the time of a run.
    # So in most cases it will be better to enable call graphs for selected
    # functions only using the \callgraph command.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    CALL_GRAPH             = YES


    # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
    # dependency graph for every global function or class method.
    #
    # Note that enabling this option will significantly increase the time of a run.
    # So in most cases it will be better to enable caller graphs for selected
    # functions only using the \callergraph command.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    CALLER_GRAPH           = YES


    # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
    # hierarchy of all classes instead of a textual one.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    GRAPHICAL_HIERARCHY    = YES


    # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
    # dependencies a directory has on other directories in a graphical way. The
    # dependency relations are determined by the #include relations between the
    # files in the directories.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DIRECTORY_GRAPH        = YES


    # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
    # generated by dot.
    # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
    # to make the SVG files visible in IE 9+ (other browsers do not have this
    # requirement).
    # Possible values are: png, jpg, gif and svg.
    # The default value is: png.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_IMAGE_FORMAT       = jpg


    # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
    # enable generation of interactive SVG images that allow zooming and panning.
    #
    # Note that this requires a modern browser other than Internet Explorer. Tested
    # and working are Firefox, Chrome, Safari, and Opera.
    # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
    # the SVG files visible. Older versions of IE do not have SVG support.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    INTERACTIVE_SVG        = NO


    # The DOT_PATH tag can be used to specify the path where the dot tool can be
    # found. If left blank, it is assumed the dot tool can be found in the path.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_PATH               = "C:/Program Files (x86)/Graphviz2.37/bin"


    # The DOTFILE_DIRS tag can be used to specify one or more directories that
    # contain dot files that are included in the documentation (see the \dotfile
    # command).
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOTFILE_DIRS           = 


    # The MSCFILE_DIRS tag can be used to specify one or more directories that
    # contain msc files that are included in the documentation (see the \mscfile
    # command).


    MSCFILE_DIRS           = 


    # The DIAFILE_DIRS tag can be used to specify one or more directories that
    # contain dia files that are included in the documentation (see the \diafile
    # command).


    DIAFILE_DIRS           = 


    # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
    # path where java can find the plantuml.jar file. If left blank, it is assumed
    # PlantUML is not used or called during a preprocessing step. Doxygen will
    # generate a warning when it encounters a \startuml command in this case and
    # will not generate output for the diagram.


    PLANTUML_JAR_PATH      = 


    # When using plantuml, the specified paths are searched for files specified by
    # the !include statement in a plantuml block.


    PLANTUML_INCLUDE_PATH  = 


    # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
    # that will be shown in the graph. If the number of nodes in a graph becomes
    # larger than this value, doxygen will truncate the graph, which is visualized
    # by representing a node as a red box. Note that doxygen if the number of direct
    # children of the root node in a graph is already larger than
    # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
    # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
    # Minimum value: 0, maximum value: 10000, default value: 50.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_GRAPH_MAX_NODES    = 50


    # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
    # generated by dot. A depth value of 3 means that only nodes reachable from the
    # root by following a path via at most 3 edges will be shown. Nodes that lay
    # further from the root node will be omitted. Note that setting this option to 1
    # or 2 may greatly reduce the computation time needed for large code bases. Also
    # note that the size of a graph can be further restricted by
    # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
    # Minimum value: 0, maximum value: 1000, default value: 0.
    # This tag requires that the tag HAVE_DOT is set to YES.


    MAX_DOT_GRAPH_DEPTH    = 0


    # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
    # background. This is disabled by default, because dot on Windows does not seem
    # to support this out of the box.
    #
    # Warning: Depending on the platform used, enabling this option may lead to
    # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
    # read).
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_TRANSPARENT        = NO


    # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
    # files in one run (i.e. multiple -o and -T options on the command line). This
    # makes dot run faster, but since only newer versions of dot (>1.8.10) support
    # this, this feature is disabled by default.
    # The default value is: NO.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_MULTI_TARGETS      = NO


    # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
    # explaining the meaning of the various boxes and arrows in the dot generated
    # graphs.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    GENERATE_LEGEND        = YES


    # If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot
    # files that are used to generate the various graphs.
    # The default value is: YES.
    # This tag requires that the tag HAVE_DOT is set to YES.


    DOT_CLEANUP            = YES






    转载于:https://www.cnblogs.com/peterYong/p/6556706.html

    展开全文
  • 你有为软件编写说明文档苦恼吗?当别人甩给你一个庞大系统,让你根据里面代码注释理解后写出一份完整开发文档,你会怎么办?一个个看代码然后耗时N天来写吗...有没有类似Javadoc东西? Yes,Doxygen就是这

    你有为软件编写说明文档的苦恼吗?当别人甩给你一个庞大的系统,让你根据里面的代码注释理解后写出一份完整的开发文档,你会怎么办?一个个的看代码然后耗时N天来写吗?这既是一份苦差事也极其耗时,有没有更好的办法呢?比如根据代码注释自动生成详尽的说明文档……可能有人会说用Javadoc就是了,要是C/C++、Python、C#等语言写的软件呢?有没有类似Javadoc的东西?

    Yes,当然有,Doxygen就是这样一个能满足你需求的工具。Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释的语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,可将程序中的特定批注转换成为说明文件,生成HTML格式的在线类浏览器,或离线的LATEX、RTF参考手册。被Boost、OpenCasCade等诸多项目作为文档生成工具的不二选择

    由于我主要的开发语言是Java,所以在这里主要说明Doxygen在Eclipse里的集成及使用步骤。

     

    1. 安装doxygen工具

    在集成之前需要安装doxygen工具,下载方法有两种:目前最新版是1.8.6

    (1)官方网站下载(建议):Doxygen:Downloads


     (2)在sourceforge下载:Doxygen



    2.安装doxygen在Eclipse中的插件:Eclox

    建议在其官方网站下载:Eclox


     

    下载eclox_0.8.0.zip后解压,安装插件的方法也有几种:

    1. 将eclox_0.8.0中的plugins和features目录里的内容,移动到eclipse中的plugins和features目录里重启即可,最简单。

    2. 通过links方法安装插件(建议该方法,具体可Google)。

    2. 采用Eclipse里的update manager安装插件,具体方法请看这里

    注意:网上都说同时要下载eclox.update_0.8.0.zip并解压安装,其实完全没必要,eclox.update_0.8.0只是版本的更新过程,里面包含的都是最新版本和历史版本插件,而我们需要的只是最新版本的,故不需要下载此压缩文件。


    如果这两个步骤都完成后,重启eclipse之后,就可以发现在工具栏上多了一个@的图标,如下图所示,表示安装成功。


    3. 在Eclipse中配置doxygen运行环境

    工具栏上 windows->preferences->Doxygen, 点击Add,添加doxygen安装目录中的bin目录,如下图所示:


     

    到此doxygen在Eclipse中的集成工作就完成了。

     

    4. 使用Doxygen生成文档过程举例

    4.1 自动生成工程的doxygen文件

    首先选择你要生成文档的工程,

    然后File->New->others....,出现下面的选择框,选择Other中的Doxyfile。



    点击next,配置Doxygen,定好文件的名字,点击Finish就OK了。

    当然到此还没结束,最重要的一步还没完成,就是自动生成doxygen文件后需要我们自己配置各个参数和选项。

    4.2 配置doxygen文件参数和选项

    配置Doxygen文件参数也有三种方式:


    4.2.1 使用Eclipse中集成的doxygen editor进行修改

    在Eclipse中打开刚刚自动生成的doxygen文件,默认的配置如下:


    比如在Eclipse中我用的配置选项如下:


    建议大家如果不理解各个选项,可以尝试每个选项的生成效果,以找出自己最想要的文档格式。


    4.2.2 使用Doxygen安装程序自带的GUI工具

    找到Doxygen的安装目录下的bin目录里,如下图所示可以看到有个GUI工具:


    打开后如下图所示:


    与Eclipse中大同小异,各个参数选项慢慢琢磨吧,很简单。


    4.2.3 直接用文本编辑器进行修改

    针对doxyfile可直接用文本编辑器进行编辑,建议用Notepad++或写字板等打开,不要用无排版的记事本。

    主要有以下内容需关注:

    • <OUTPUT_DIRECTORY>必须在这里提供一个目录名,例如 /home/user1/documentation,这个目录是放置生成的文档文件的位置。如果提供一个不存在的目录名,doxygen 会以这个名称创建具有适当用户权限的目录。
    • <INPUT>这个标记创建一个以空格分隔的所有目录的列表,这个列表包含需要生成文档的 C/C++ 源代码文件和头文件。如果项目只有一个源代码根目录,其中有多个子目录,那么只需指定根目录并把<RECURSIVE> 标记设置为Yes
    • <FILE_PATTERNS>在默认情况下,doxygen 会搜索具有典型 C/C++ 扩展名的文件,比如.c、.cc、.cpp、.h.hpp。如果<FILE_PATTERNS> 标记没有相关联的值,doxygen 就会这样做。如果源代码文件采用不同的命名约定,就应该相应地更新这个标记。例如,如果项目使用.c86 作为C 文件扩展名,就应该在<FILE_PATTERNS> 标记中添加这个扩展名。
    • <RECURSIVE>如果源代码层次结构是嵌套的,而且需要为所有层次上的 C/C++ 文件生成文档,就把这个标记设置为Yes。例如,请考虑源代码根目录层次结构 /home/user1/project/kernel,其中有 /home/user1/project/kernel/vmm 和 /home/user1/project/kernel/asm 等子目录。如果这个标记设置为Yes,doxygen 就会递归地搜索整个层次结构并提取信息。
    • <EXTRACT_ALL>这个标记告诉 doxygen,即使各个类或函数没有文档,也要提取信息。必须把这个标记设置为Yes
    • <EXTRACT_PRIVATE>把这个标记设置为 Yes。否则,文档不包含类的私有数据成员。
    • <EXTRACT_STATIC>把这个标记设置为 Yes。否则,文档不包含文件的静态成员(函数和变量)。
    • <OUTPUT_LANGUAGE>默认 = English,文档语言(自动生成的文字部分),可以指定为Chinese。
    • <DOXYFILE_ENCODING>默认 = UTF-8,默认编码为UTF-8,这样可以支持中文。
    • <PROJECT_NAME>项目名称,多个单词需要使用引号(“”)。
    • <PROJECT_NUMBER>项目版本号。


    4.3 运行doxygen文件生成最后的文档

    配置完成后在Eclipse中点击@插件按钮选择doxygen配置文件即可生成文档了。

    可以在控制台看到生成详细过程,如果有如何配置错误如指定的路径或文件不存在等,都会给出提示,按要求重新配置即可。


    打开生成文档里的index.html(如果是html格式),在浏览器查看,点击各个选项查看效果如下:

    主界面:

    查看某个函数的界面:


    展开全文
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxygen可以从一套归档源文件开始,生成...
  • Doxygen 使用简介

    2017-10-09 10:25:00
    Doxygen 是一个类似 JavaDoc 文档生成工具。有了它,C++爱好者就可以为自己源代码很方便地生成美观实用文档了。为代码生成文档标注基础 您可以使用JavaDoc风格,类似于由C风格注释块: /** * ... 文本 ... *...
  • 在VS2103环境中集成Doxygen工具

    千次阅读 2016-09-20 14:05:43
     Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成...
  • Doxygen是一种开源跨平台的工具,其功能是从程序源代码中抽取类、方法、成员的注 释,形成一个和源代码配套的API(Application Programming Interface,应用程序编程接口)帮助文档。Doxygen工具,以类似JavaDoc风格...
  • 开发文档生成工具--Doxygen

    千次阅读 2013-12-18 12:40:33
    Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。...Doxygen 是一个程序文件产生工具,可将
  • 你有为软件编写说明文档苦恼吗?当别人甩给你一个庞大系统,让你根据里面代码注释理解后写出一份完整开发文档,你会怎么办?一个个看代码 然后耗时N天来写吗...有没有类似Javadoc东西? Yes,当然有,Doxy
  • doxygen的安装与配置

    2017-09-03 19:57:42
    最近接触了一款程序 文档生成工具-Doxygen。在网上一搜索原来这么多人知道,打算把它使用做一个总结,以及其...Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、 class="replace_w
  • Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统,可以从一套归档源文件开始,生成API文档的工具Doxygen是一个程序的文档产生工具,可以将程序中的注释转换成说明文档或者说是API参考手册,从而减少...
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成...
  • Doxygen是一种开源跨平台,以类似JavaDoc风格描述文档系统,完全支持C、C++、Java、Objective-C和IDL语言,部分支持PHP、C#。注释语法与Qt-Doc、KDoc和JavaDoc兼容。Doxgen可以从一套归档源文件开始,生成HTML...
  • Doxygen是一种文档生成工具,可以抽取代码中注释,生成类似JavaDoc文档。 该工具支持平台有Linux、Max OS X、Windows;支持编程语言包括:C/C++、Java、Python、C#等数十种语言。 Doxygen是以GPL授权方式...
  • Linux下Doxygen的安装配置与使用

    千次阅读 2018-05-11 15:47:51
    1 简介Doxygen是一种开源跨平台的,以类似JavaDoc风格描述的文档系统....LATEX也可以转成PDF....首先是特定格式的批注撰写,第二便是利用Doxygen的工具来产生文件。1.1 语言支持C/C++JavaObjective-CPythonIDL (...

空空如也

空空如也

1 2 3 4 5 6
收藏数 108
精华内容 43
关键字:

doxygen类似的工具