"Fossies" - the Fresh Open Source Software Archive

Member "lapack-3.9.1/DOCS/Doxyfile" (25 Mar 2021, 114131 Bytes) of package /linux/misc/lapack-3.9.1.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "Doxyfile": 3.9.0_vs_3.9.1.

    1 # Doxyfile 1.9.1
    2 
    3 # This file describes the settings to be used by the documentation system
    4 # doxygen (www.doxygen.org) for a project.
    5 #
    6 # All text after a double hash (##) is considered a comment and is placed in
    7 # front of the TAG it is preceding.
    8 #
    9 # All text after a single hash (#) is considered a comment and will be ignored.
   10 # The format is:
   11 # TAG = value [value, ...]
   12 # For lists, items can also be appended using:
   13 # TAG += value [value, ...]
   14 # Values that contain spaces should be placed between quotes (\" \").
   15 
   16 #---------------------------------------------------------------------------
   17 # Project related configuration options
   18 #---------------------------------------------------------------------------
   19 
   20 # This tag specifies the encoding used for all characters in the configuration
   21 # file that follow. The default is UTF-8 which is also the encoding used for all
   22 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
   23 # iconv built into libc) for the transcoding. See
   24 # https://www.gnu.org/software/libiconv/ for the list of possible encodings.
   25 # The default value is: UTF-8.
   26 
   27 DOXYFILE_ENCODING      = UTF-8
   28 
   29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
   30 # double-quotes, unless you are using Doxywizard) that should identify the
   31 # project for which the documentation is generated. This name is used in the
   32 # title of most generated pages and in a few other places.
   33 # The default value is: My Project.
   34 
   35 PROJECT_NAME           = LAPACK
   36 
   37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
   38 # could be handy for archiving the generated documentation or if some version
   39 # control system is used.
   40 
   41 PROJECT_NUMBER         = 3.9.1
   42 
   43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
   44 # for a project that appears at the top of each page and should give viewer a
   45 # quick idea about the purpose of the project. Keep the description short.
   46 
   47 PROJECT_BRIEF          = "LAPACK: Linear Algebra PACKage"
   48 
   49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
   50 # in the documentation. The maximum height of the logo should not exceed 55
   51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
   52 # the logo to the output directory.
   53 
   54 PROJECT_LOGO           = DOCS/lapack.png
   55 
   56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
   57 # into which the generated documentation will be written. If a relative path is
   58 # entered, it will be relative to the location where doxygen was started. If
   59 # left blank the current directory will be used.
   60 
   61 OUTPUT_DIRECTORY       = DOCS
   62 
   63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
   64 # directories (in 2 levels) under the output directory of each output format and
   65 # will distribute the generated files over these directories. Enabling this
   66 # option can be useful when feeding doxygen a huge amount of source files, where
   67 # putting all generated files in the same directory would otherwise causes
   68 # performance problems for the file system.
   69 # The default value is: NO.
   70 
   71 CREATE_SUBDIRS         = YES
   72 
   73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
   74 # characters to appear in the names of generated files. If set to NO, non-ASCII
   75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
   76 # U+3044.
   77 # The default value is: NO.
   78 
   79 ALLOW_UNICODE_NAMES    = NO
   80 
   81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
   82 # documentation generated by doxygen is written. Doxygen will use this
   83 # information to generate all constant output in the proper language.
   84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
   85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
   86 # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
   87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
   88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
   89 # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
   90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
   91 # Ukrainian and Vietnamese.
   92 # The default value is: English.
   93 
   94 OUTPUT_LANGUAGE        = English
   95 
   96 # The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
   97 # documentation generated by doxygen is written. Doxygen will use this
   98 # information to generate all generated output in the proper direction.
   99 # Possible values are: None, LTR, RTL and Context.
  100 # The default value is: None.
  101 
  102 OUTPUT_TEXT_DIRECTION  = None
  103 
  104 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
  105 # descriptions after the members that are listed in the file and class
  106 # documentation (similar to Javadoc). Set to NO to disable this.
  107 # The default value is: YES.
  108 
  109 BRIEF_MEMBER_DESC      = YES
  110 
  111 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
  112 # description of a member or function before the detailed description
  113 #
  114 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
  115 # brief descriptions will be completely suppressed.
  116 # The default value is: YES.
  117 
  118 REPEAT_BRIEF           = YES
  119 
  120 # This tag implements a quasi-intelligent brief description abbreviator that is
  121 # used to form the text in various listings. Each string in this list, if found
  122 # as the leading text of the brief description, will be stripped from the text
  123 # and the result, after processing the whole list, is used as the annotated
  124 # text. Otherwise, the brief description is used as-is. If left blank, the
  125 # following values are used ($name is automatically replaced with the name of
  126 # the entity):The $name class, The $name widget, The $name file, is, provides,
  127 # specifies, contains, represents, a, an and the.
  128 
  129 ABBREVIATE_BRIEF       =
  130 
  131 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
  132 # doxygen will generate a detailed section even if there is only a brief
  133 # description.
  134 # The default value is: NO.
  135 
  136 ALWAYS_DETAILED_SEC    = NO
  137 
  138 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
  139 # inherited members of a class in the documentation of that class as if those
  140 # members were ordinary class members. Constructors, destructors and assignment
  141 # operators of the base classes will not be shown.
  142 # The default value is: NO.
  143 
  144 INLINE_INHERITED_MEMB  = NO
  145 
  146 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
  147 # before files name in the file list and in the header files. If set to NO the
  148 # shortest path that makes the file name unique will be used
  149 # The default value is: YES.
  150 
  151 FULL_PATH_NAMES        = YES
  152 
  153 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
  154 # Stripping is only done if one of the specified strings matches the left-hand
  155 # part of the path. The tag can be used to show relative paths in the file list.
  156 # If left blank the directory from which doxygen is run is used as the path to
  157 # strip.
  158 #
  159 # Note that you can specify absolute paths here, but also relative paths, which
  160 # will be relative from the directory where doxygen is started.
  161 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
  162 
  163 STRIP_FROM_PATH        =
  164 
  165 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
  166 # path mentioned in the documentation of a class, which tells the reader which
  167 # header file to include in order to use a class. If left blank only the name of
  168 # the header file containing the class definition is used. Otherwise one should
  169 # specify the list of include paths that are normally passed to the compiler
  170 # using the -I flag.
  171 
  172 STRIP_FROM_INC_PATH    =
  173 
  174 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
  175 # less readable) file names. This can be useful is your file systems doesn't
  176 # support long names like on DOS, Mac, or CD-ROM.
  177 # The default value is: NO.
  178 
  179 SHORT_NAMES            = NO
  180 
  181 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
  182 # first line (until the first dot) of a Javadoc-style comment as the brief
  183 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
  184 # style comments (thus requiring an explicit @brief command for a brief
  185 # description.)
  186 # The default value is: NO.
  187 
  188 JAVADOC_AUTOBRIEF      = NO
  189 
  190 # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
  191 # such as
  192 # /***************
  193 # as being the beginning of a Javadoc-style comment "banner". If set to NO, the
  194 # Javadoc-style will behave just like regular comments and it will not be
  195 # interpreted by doxygen.
  196 # The default value is: NO.
  197 
  198 JAVADOC_BANNER         = NO
  199 
  200 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
  201 # line (until the first dot) of a Qt-style comment as the brief description. If
  202 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
  203 # requiring an explicit \brief command for a brief description.)
  204 # The default value is: NO.
  205 
  206 QT_AUTOBRIEF           = NO
  207 
  208 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
  209 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
  210 # a brief description. This used to be the default behavior. The new default is
  211 # to treat a multi-line C++ comment block as a detailed description. Set this
  212 # tag to YES if you prefer the old behavior instead.
  213 #
  214 # Note that setting this tag to YES also means that rational rose comments are
  215 # not recognized any more.
  216 # The default value is: NO.
  217 
  218 MULTILINE_CPP_IS_BRIEF = NO
  219 
  220 # By default Python docstrings are displayed as preformatted text and doxygen's
  221 # special commands cannot be used. By setting PYTHON_DOCSTRING to NO the
  222 # doxygen's special commands can be used and the contents of the docstring
  223 # documentation blocks is shown as doxygen documentation.
  224 # The default value is: YES.
  225 
  226 PYTHON_DOCSTRING       = YES
  227 
  228 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
  229 # documentation from any documented member that it re-implements.
  230 # The default value is: YES.
  231 
  232 INHERIT_DOCS           = YES
  233 
  234 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
  235 # page for each member. If set to NO, the documentation of a member will be part
  236 # of the file/class/namespace that contains it.
  237 # The default value is: NO.
  238 
  239 SEPARATE_MEMBER_PAGES  = YES
  240 
  241 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
  242 # uses this value to replace tabs by spaces in code fragments.
  243 # Minimum value: 1, maximum value: 16, default value: 4.
  244 
  245 TAB_SIZE               = 8
  246 
  247 # This tag can be used to specify a number of aliases that act as commands in
  248 # the documentation. An alias has the form:
  249 # name=value
  250 # For example adding
  251 # "sideeffect=@par Side Effects:\n"
  252 # will allow you to put the command \sideeffect (or @sideeffect) in the
  253 # documentation, which will result in a user-defined paragraph with heading
  254 # "Side Effects:". You can put \n's in the value part of an alias to insert
  255 # newlines (in the resulting output). You can put ^^ in the value part of an
  256 # alias to insert a newline as if a physical newline was in the original file.
  257 # When you need a literal { or } or , in the value part of an alias you have to
  258 # escape them by means of a backslash (\), this can lead to conflicts with the
  259 # commands \{ and \} for these it is advised to use the version @{ and @} or use
  260 # a double escape (\\{ and \\})
  261 
  262 ALIASES                =
  263 
  264 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
  265 # only. Doxygen will then generate output that is more tailored for C. For
  266 # instance, some of the names that are used will be different. The list of all
  267 # members will be omitted, etc.
  268 # The default value is: NO.
  269 
  270 OPTIMIZE_OUTPUT_FOR_C  = NO
  271 
  272 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
  273 # Python sources only. Doxygen will then generate output that is more tailored
  274 # for that language. For instance, namespaces will be presented as packages,
  275 # qualified scopes will look different, etc.
  276 # The default value is: NO.
  277 
  278 OPTIMIZE_OUTPUT_JAVA   = NO
  279 
  280 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
  281 # sources. Doxygen will then generate output that is tailored for Fortran.
  282 # The default value is: NO.
  283 
  284 OPTIMIZE_FOR_FORTRAN   = YES
  285 
  286 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
  287 # sources. Doxygen will then generate output that is tailored for VHDL.
  288 # The default value is: NO.
  289 
  290 OPTIMIZE_OUTPUT_VHDL   = NO
  291 
  292 # Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
  293 # sources only. Doxygen will then generate output that is more tailored for that
  294 # language. For instance, namespaces will be presented as modules, types will be
  295 # separated into more groups, etc.
  296 # The default value is: NO.
  297 
  298 OPTIMIZE_OUTPUT_SLICE  = NO
  299 
  300 # Doxygen selects the parser to use depending on the extension of the files it
  301 # parses. With this tag you can assign which parser to use for a given
  302 # extension. Doxygen has a built-in mapping, but you can override or extend it
  303 # using this tag. The format is ext=language, where ext is a file extension, and
  304 # language is one of the parsers supported by doxygen: IDL, Java, JavaScript,
  305 # Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice, VHDL,
  306 # Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
  307 # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
  308 # tries to guess whether the code is fixed or free formatted code, this is the
  309 # default for Fortran type files). For instance to make doxygen treat .inc files
  310 # as Fortran files (default is PHP), and .f files as C (default is Fortran),
  311 # use: inc=Fortran f=C.
  312 #
  313 # Note: For files without extension you can use no_extension as a placeholder.
  314 #
  315 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
  316 # the files are not read by doxygen. When specifying no_extension you should add
  317 # * to the FILE_PATTERNS.
  318 #
  319 # Note see also the list of default file extension mappings.
  320 
  321 EXTENSION_MAPPING      =
  322 
  323 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
  324 # according to the Markdown format, which allows for more readable
  325 # documentation. See https://daringfireball.net/projects/markdown/ for details.
  326 # The output of markdown processing is further processed by doxygen, so you can
  327 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
  328 # case of backward compatibilities issues.
  329 # The default value is: YES.
  330 
  331 MARKDOWN_SUPPORT       = YES
  332 
  333 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
  334 # to that level are automatically included in the table of contents, even if
  335 # they do not have an id attribute.
  336 # Note: This feature currently applies only to Markdown headings.
  337 # Minimum value: 0, maximum value: 99, default value: 5.
  338 # This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
  339 
  340 TOC_INCLUDE_HEADINGS   = 5
  341 
  342 # When enabled doxygen tries to link words that correspond to documented
  343 # classes, or namespaces to their corresponding documentation. Such a link can
  344 # be prevented in individual cases by putting a % sign in front of the word or
  345 # globally by setting AUTOLINK_SUPPORT to NO.
  346 # The default value is: YES.
  347 
  348 AUTOLINK_SUPPORT       = YES
  349 
  350 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
  351 # to include (a tag file for) the STL sources as input, then you should set this
  352 # tag to YES in order to let doxygen match functions declarations and
  353 # definitions whose arguments contain STL classes (e.g. func(std::string);
  354 # versus func(std::string) {}). This also make the inheritance and collaboration
  355 # diagrams that involve STL classes more complete and accurate.
  356 # The default value is: NO.
  357 
  358 BUILTIN_STL_SUPPORT    = NO
  359 
  360 # If you use Microsoft's C++/CLI language, you should set this option to YES to
  361 # enable parsing support.
  362 # The default value is: NO.
  363 
  364 CPP_CLI_SUPPORT        = NO
  365 
  366 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
  367 # https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen
  368 # will parse them like normal C++ but will assume all classes use public instead
  369 # of private inheritance when no explicit protection keyword is present.
  370 # The default value is: NO.
  371 
  372 SIP_SUPPORT            = NO
  373 
  374 # For Microsoft's IDL there are propget and propput attributes to indicate
  375 # getter and setter methods for a property. Setting this option to YES will make
  376 # doxygen to replace the get and set methods by a property in the documentation.
  377 # This will only work if the methods are indeed getting or setting a simple
  378 # type. If this is not the case, or you want to show the methods anyway, you
  379 # should set this option to NO.
  380 # The default value is: YES.
  381 
  382 IDL_PROPERTY_SUPPORT   = YES
  383 
  384 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
  385 # tag is set to YES then doxygen will reuse the documentation of the first
  386 # member in the group (if any) for the other members of the group. By default
  387 # all members of a group must be documented explicitly.
  388 # The default value is: NO.
  389 
  390 DISTRIBUTE_GROUP_DOC   = YES
  391 
  392 # If one adds a struct or class to a group and this option is enabled, then also
  393 # any nested class or struct is added to the same group. By default this option
  394 # is disabled and one has to add nested compounds explicitly via \ingroup.
  395 # The default value is: NO.
  396 
  397 GROUP_NESTED_COMPOUNDS = NO
  398 
  399 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
  400 # (for instance a group of public functions) to be put as a subgroup of that
  401 # type (e.g. under the Public Functions section). Set it to NO to prevent
  402 # subgrouping. Alternatively, this can be done per class using the
  403 # \nosubgrouping command.
  404 # The default value is: YES.
  405 
  406 SUBGROUPING            = YES
  407 
  408 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
  409 # are shown inside the group in which they are included (e.g. using \ingroup)
  410 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
  411 # and RTF).
  412 #
  413 # Note that this feature does not work in combination with
  414 # SEPARATE_MEMBER_PAGES.
  415 # The default value is: NO.
  416 
  417 INLINE_GROUPED_CLASSES = NO
  418 
  419 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
  420 # with only public data fields or simple typedef fields will be shown inline in
  421 # the documentation of the scope in which they are defined (i.e. file,
  422 # namespace, or group documentation), provided this scope is documented. If set
  423 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
  424 # Man pages) or section (for LaTeX and RTF).
  425 # The default value is: NO.
  426 
  427 INLINE_SIMPLE_STRUCTS  = NO
  428 
  429 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
  430 # enum is documented as struct, union, or enum with the name of the typedef. So
  431 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
  432 # with name TypeT. When disabled the typedef will appear as a member of a file,
  433 # namespace, or class. And the struct will be named TypeS. This can typically be
  434 # useful for C code in case the coding convention dictates that all compound
  435 # types are typedef'ed and only the typedef is referenced, never the tag name.
  436 # The default value is: NO.
  437 
  438 TYPEDEF_HIDES_STRUCT   = NO
  439 
  440 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
  441 # cache is used to resolve symbols given their name and scope. Since this can be
  442 # an expensive process and often the same symbol appears multiple times in the
  443 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
  444 # doxygen will become slower. If the cache is too large, memory is wasted. The
  445 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
  446 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
  447 # symbols. At the end of a run doxygen will report the cache usage and suggest
  448 # the optimal cache size from a speed point of view.
  449 # Minimum value: 0, maximum value: 9, default value: 0.
  450 
  451 LOOKUP_CACHE_SIZE      = 0
  452 
  453 # The NUM_PROC_THREADS specifies the number threads doxygen is allowed to use
  454 # during processing. When set to 0 doxygen will based this on the number of
  455 # cores available in the system. You can set it explicitly to a value larger
  456 # than 0 to get more control over the balance between CPU load and processing
  457 # speed. At this moment only the input processing can be done using multiple
  458 # threads. Since this is still an experimental feature the default is set to 1,
  459 # which efficively disables parallel processing. Please report any issues you
  460 # encounter. Generating dot graphs in parallel is controlled by the
  461 # DOT_NUM_THREADS setting.
  462 # Minimum value: 0, maximum value: 32, default value: 1.
  463 
  464 NUM_PROC_THREADS       = 1
  465 
  466 #---------------------------------------------------------------------------
  467 # Build related configuration options
  468 #---------------------------------------------------------------------------
  469 
  470 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
  471 # documentation are documented, even if no documentation was available. Private
  472 # class members and static file members will be hidden unless the
  473 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
  474 # Note: This will also disable the warnings about undocumented members that are
  475 # normally produced when WARNINGS is set to YES.
  476 # The default value is: NO.
  477 
  478 EXTRACT_ALL            = YES
  479 
  480 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
  481 # be included in the documentation.
  482 # The default value is: NO.
  483 
  484 EXTRACT_PRIVATE        = NO
  485 
  486 # If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
  487 # methods of a class will be included in the documentation.
  488 # The default value is: NO.
  489 
  490 EXTRACT_PRIV_VIRTUAL   = NO
  491 
  492 # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
  493 # scope will be included in the documentation.
  494 # The default value is: NO.
  495 
  496 EXTRACT_PACKAGE        = NO
  497 
  498 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
  499 # included in the documentation.
  500 # The default value is: NO.
  501 
  502 EXTRACT_STATIC         = NO
  503 
  504 # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
  505 # locally in source files will be included in the documentation. If set to NO,
  506 # only classes defined in header files are included. Does not have any effect
  507 # for Java sources.
  508 # The default value is: YES.
  509 
  510 EXTRACT_LOCAL_CLASSES  = YES
  511 
  512 # This flag is only useful for Objective-C code. If set to YES, local methods,
  513 # which are defined in the implementation section but not in the interface are
  514 # included in the documentation. If set to NO, only methods in the interface are
  515 # included.
  516 # The default value is: NO.
  517 
  518 EXTRACT_LOCAL_METHODS  = NO
  519 
  520 # If this flag is set to YES, the members of anonymous namespaces will be
  521 # extracted and appear in the documentation as a namespace called
  522 # 'anonymous_namespace{file}', where file will be replaced with the base name of
  523 # the file that contains the anonymous namespace. By default anonymous namespace
  524 # are hidden.
  525 # The default value is: NO.
  526 
  527 EXTRACT_ANON_NSPACES   = NO
  528 
  529 # If this flag is set to YES, the name of an unnamed parameter in a declaration
  530 # will be determined by the corresponding definition. By default unnamed
  531 # parameters remain unnamed in the output.
  532 # The default value is: YES.
  533 
  534 RESOLVE_UNNAMED_PARAMS = YES
  535 
  536 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
  537 # undocumented members inside documented classes or files. If set to NO these
  538 # members will be included in the various overviews, but no documentation
  539 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
  540 # The default value is: NO.
  541 
  542 HIDE_UNDOC_MEMBERS     = NO
  543 
  544 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
  545 # undocumented classes that are normally visible in the class hierarchy. If set
  546 # to NO, these classes will be included in the various overviews. This option
  547 # has no effect if EXTRACT_ALL is enabled.
  548 # The default value is: NO.
  549 
  550 HIDE_UNDOC_CLASSES     = NO
  551 
  552 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
  553 # declarations. If set to NO, these declarations will be included in the
  554 # documentation.
  555 # The default value is: NO.
  556 
  557 HIDE_FRIEND_COMPOUNDS  = NO
  558 
  559 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
  560 # documentation blocks found inside the body of a function. If set to NO, these
  561 # blocks will be appended to the function's detailed documentation block.
  562 # The default value is: NO.
  563 
  564 HIDE_IN_BODY_DOCS      = NO
  565 
  566 # The INTERNAL_DOCS tag determines if documentation that is typed after a
  567 # \internal command is included. If the tag is set to NO then the documentation
  568 # will be excluded. Set it to YES to include the internal documentation.
  569 # The default value is: NO.
  570 
  571 INTERNAL_DOCS          = NO
  572 
  573 # With the correct setting of option CASE_SENSE_NAMES doxygen will better be
  574 # able to match the capabilities of the underlying filesystem. In case the
  575 # filesystem is case sensitive (i.e. it supports files in the same directory
  576 # whose names only differ in casing), the option must be set to YES to properly
  577 # deal with such files in case they appear in the input. For filesystems that
  578 # are not case sensitive the option should be be set to NO to properly deal with
  579 # output files written for symbols that only differ in casing, such as for two
  580 # classes, one named CLASS and the other named Class, and to also support
  581 # references to files without having to specify the exact matching casing. On
  582 # Windows (including Cygwin) and MacOS, users should typically set this option
  583 # to NO, whereas on Linux or other Unix flavors it should typically be set to
  584 # YES.
  585 # The default value is: system dependent.
  586 
  587 CASE_SENSE_NAMES       = NO
  588 
  589 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
  590 # their full class and namespace scopes in the documentation. If set to YES, the
  591 # scope will be hidden.
  592 # The default value is: NO.
  593 
  594 HIDE_SCOPE_NAMES       = NO
  595 
  596 # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
  597 # append additional text to a page's title, such as Class Reference. If set to
  598 # YES the compound reference will be hidden.
  599 # The default value is: NO.
  600 
  601 HIDE_COMPOUND_REFERENCE= NO
  602 
  603 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
  604 # the files that are included by a file in the documentation of that file.
  605 # The default value is: YES.
  606 
  607 SHOW_INCLUDE_FILES     = YES
  608 
  609 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
  610 # grouped member an include statement to the documentation, telling the reader
  611 # which file to include in order to use the member.
  612 # The default value is: NO.
  613 
  614 SHOW_GROUPED_MEMB_INC  = NO
  615 
  616 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
  617 # files with double quotes in the documentation rather than with sharp brackets.
  618 # The default value is: NO.
  619 
  620 FORCE_LOCAL_INCLUDES   = NO
  621 
  622 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
  623 # documentation for inline members.
  624 # The default value is: YES.
  625 
  626 INLINE_INFO            = YES
  627 
  628 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
  629 # (detailed) documentation of file and class members alphabetically by member
  630 # name. If set to NO, the members will appear in declaration order.
  631 # The default value is: YES.
  632 
  633 SORT_MEMBER_DOCS       = YES
  634 
  635 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
  636 # descriptions of file, namespace and class members alphabetically by member
  637 # name. If set to NO, the members will appear in declaration order. Note that
  638 # this will also influence the order of the classes in the class list.
  639 # The default value is: NO.
  640 
  641 SORT_BRIEF_DOCS        = NO
  642 
  643 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
  644 # (brief and detailed) documentation of class members so that constructors and
  645 # destructors are listed first. If set to NO the constructors will appear in the
  646 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
  647 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
  648 # member documentation.
  649 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
  650 # detailed member documentation.
  651 # The default value is: NO.
  652 
  653 SORT_MEMBERS_CTORS_1ST = NO
  654 
  655 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
  656 # of group names into alphabetical order. If set to NO the group names will
  657 # appear in their defined order.
  658 # The default value is: NO.
  659 
  660 SORT_GROUP_NAMES       = NO
  661 
  662 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
  663 # fully-qualified names, including namespaces. If set to NO, the class list will
  664 # be sorted only by class name, not including the namespace part.
  665 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
  666 # Note: This option applies only to the class list, not to the alphabetical
  667 # list.
  668 # The default value is: NO.
  669 
  670 SORT_BY_SCOPE_NAME     = NO
  671 
  672 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
  673 # type resolution of all parameters of a function it will reject a match between
  674 # the prototype and the implementation of a member function even if there is
  675 # only one candidate or it is obvious which candidate to choose by doing a
  676 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
  677 # accept a match between prototype and implementation in such cases.
  678 # The default value is: NO.
  679 
  680 STRICT_PROTO_MATCHING  = NO
  681 
  682 # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
  683 # list. This list is created by putting \todo commands in the documentation.
  684 # The default value is: YES.
  685 
  686 GENERATE_TODOLIST      = YES
  687 
  688 # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
  689 # list. This list is created by putting \test commands in the documentation.
  690 # The default value is: YES.
  691 
  692 GENERATE_TESTLIST      = YES
  693 
  694 # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
  695 # list. This list is created by putting \bug commands in the documentation.
  696 # The default value is: YES.
  697 
  698 GENERATE_BUGLIST       = YES
  699 
  700 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
  701 # the deprecated list. This list is created by putting \deprecated commands in
  702 # the documentation.
  703 # The default value is: YES.
  704 
  705 GENERATE_DEPRECATEDLIST= YES
  706 
  707 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
  708 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
  709 # ... \endcond blocks.
  710 
  711 ENABLED_SECTIONS       =
  712 
  713 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
  714 # initial value of a variable or macro / define can have for it to appear in the
  715 # documentation. If the initializer consists of more lines than specified here
  716 # it will be hidden. Use a value of 0 to hide initializers completely. The
  717 # appearance of the value of individual variables and macros / defines can be
  718 # controlled using \showinitializer or \hideinitializer command in the
  719 # documentation regardless of this setting.
  720 # Minimum value: 0, maximum value: 10000, default value: 30.
  721 
  722 MAX_INITIALIZER_LINES  = 30
  723 
  724 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
  725 # the bottom of the documentation of classes and structs. If set to YES, the
  726 # list will mention the files that were used to generate the documentation.
  727 # The default value is: YES.
  728 
  729 SHOW_USED_FILES        = YES
  730 
  731 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
  732 # will remove the Files entry from the Quick Index and from the Folder Tree View
  733 # (if specified).
  734 # The default value is: YES.
  735 
  736 SHOW_FILES             = YES
  737 
  738 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
  739 # page. This will remove the Namespaces entry from the Quick Index and from the
  740 # Folder Tree View (if specified).
  741 # The default value is: YES.
  742 
  743 SHOW_NAMESPACES        = YES
  744 
  745 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
  746 # doxygen should invoke to get the current version for each file (typically from
  747 # the version control system). Doxygen will invoke the program by executing (via
  748 # popen()) the command command input-file, where command is the value of the
  749 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
  750 # by doxygen. Whatever the program writes to standard output is used as the file
  751 # version. For an example see the documentation.
  752 
  753 FILE_VERSION_FILTER    =
  754 
  755 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
  756 # by doxygen. The layout file controls the global structure of the generated
  757 # output files in an output format independent way. To create the layout file
  758 # that represents doxygen's defaults, run doxygen with the -l option. You can
  759 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
  760 # will be used as the name of the layout file.
  761 #
  762 # Note that if you run doxygen from a directory containing a file called
  763 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
  764 # tag is left empty.
  765 
  766 LAYOUT_FILE            =
  767 
  768 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
  769 # the reference definitions. This must be a list of .bib files. The .bib
  770 # extension is automatically appended if omitted. This requires the bibtex tool
  771 # to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
  772 # For LaTeX the style of the bibliography can be controlled using
  773 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
  774 # search path. See also \cite for info how to create references.
  775 
  776 CITE_BIB_FILES         =
  777 
  778 #---------------------------------------------------------------------------
  779 # Configuration options related to warning and progress messages
  780 #---------------------------------------------------------------------------
  781 
  782 # The QUIET tag can be used to turn on/off the messages that are generated to
  783 # standard output by doxygen. If QUIET is set to YES this implies that the
  784 # messages are off.
  785 # The default value is: NO.
  786 
  787 QUIET                  = YES
  788 
  789 # The WARNINGS tag can be used to turn on/off the warning messages that are
  790 # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
  791 # this implies that the warnings are on.
  792 #
  793 # Tip: Turn warnings on while writing the documentation.
  794 # The default value is: YES.
  795 
  796 WARNINGS               = YES
  797 
  798 # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
  799 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
  800 # will automatically be disabled.
  801 # The default value is: YES.
  802 
  803 WARN_IF_UNDOCUMENTED   = YES
  804 
  805 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
  806 # potential errors in the documentation, such as not documenting some parameters
  807 # in a documented function, or documenting parameters that don't exist or using
  808 # markup commands wrongly.
  809 # The default value is: YES.
  810 
  811 WARN_IF_DOC_ERROR      = YES
  812 
  813 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
  814 # are documented, but have no documentation for their parameters or return
  815 # value. If set to NO, doxygen will only warn about wrong or incomplete
  816 # parameter documentation, but not about the absence of documentation. If
  817 # EXTRACT_ALL is set to YES then this flag will automatically be disabled.
  818 # The default value is: NO.
  819 
  820 WARN_NO_PARAMDOC       = NO
  821 
  822 # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
  823 # a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
  824 # then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but
  825 # at the end of the doxygen process doxygen will return with a non-zero status.
  826 # Possible values are: NO, YES and FAIL_ON_WARNINGS.
  827 # The default value is: NO.
  828 
  829 WARN_AS_ERROR          = NO
  830 
  831 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
  832 # can produce. The string should contain the $file, $line, and $text tags, which
  833 # will be replaced by the file and line number from which the warning originated
  834 # and the warning text. Optionally the format may contain $version, which will
  835 # be replaced by the version of the file (if it could be obtained via
  836 # FILE_VERSION_FILTER)
  837 # The default value is: $file:$line: $text.
  838 
  839 WARN_FORMAT            = "$file:$line: $text"
  840 
  841 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
  842 # messages should be written. If left blank the output is written to standard
  843 # error (stderr).
  844 
  845 WARN_LOGFILE           = output_err
  846 
  847 #---------------------------------------------------------------------------
  848 # Configuration options related to the input files
  849 #---------------------------------------------------------------------------
  850 
  851 # The INPUT tag is used to specify the files and/or directories that contain
  852 # documented source files. You may enter file names like myfile.cpp or
  853 # directories like /usr/src/myproject. Separate the files or directories with
  854 # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
  855 # Note: If this tag is empty the current directory is searched.
  856 
  857 INPUT                  = . \
  858                          DOCS/groups-usr.dox
  859 
  860 # This tag can be used to specify the character encoding of the source files
  861 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
  862 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
  863 # documentation (see:
  864 # https://www.gnu.org/software/libiconv/) for the list of possible encodings.
  865 # The default value is: UTF-8.
  866 
  867 INPUT_ENCODING         = UTF-8
  868 
  869 # If the value of the INPUT tag contains directories, you can use the
  870 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
  871 # *.h) to filter out the source-files in the directories.
  872 #
  873 # Note that for custom extensions or not directly supported extensions you also
  874 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
  875 # read by doxygen.
  876 #
  877 # Note the list of default checked file patterns might differ from the list of
  878 # default file extension mappings.
  879 #
  880 # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
  881 # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
  882 # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
  883 # *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C comment),
  884 # *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd, *.vhdl,
  885 # *.ucf, *.qsf and *.ice.
  886 
  887 FILE_PATTERNS          = *.c \
  888                          *.f \
  889                          *.h
  890 
  891 # The RECURSIVE tag can be used to specify whether or not subdirectories should
  892 # be searched for input files as well.
  893 # The default value is: NO.
  894 
  895 RECURSIVE              = YES
  896 
  897 # The EXCLUDE tag can be used to specify files and/or directories that should be
  898 # excluded from the INPUT source files. This way you can easily exclude a
  899 # subdirectory from a directory tree whose root is specified with the INPUT tag.
  900 #
  901 # Note that relative paths are relative to the directory from which doxygen is
  902 # run.
  903 
  904 EXCLUDE                = CMAKE \
  905                          DOCS \
  906                          .svn \
  907                          CBLAS/.svn \
  908                          CBLAS/src/.svn \
  909                          CBLAS/testing/.svn \
  910                          CBLAS/example/.svn \
  911                          CBLAS/include/.svn \
  912                          BLAS/.svn \
  913                          BLAS/SRC/.svn \
  914                          BLAS/TESTING/.svn \
  915                          SRC/.svn \
  916                          SRC/VARIANTS/.svn \
  917                          SRC/VARIANTS/LIB/.svn \
  918                          SRC/VARIANTS/cholesky/.svn \
  919                          SRC/VARIANTS/cholesky/RL/.svn \
  920                          SRC/VARIANTS/cholesky/TOP/.svn \
  921                          SRC/VARIANTS/lu/.svn \
  922                          SRC/VARIANTS/lu/CR/.svn \
  923                          SRC/VARIANTS/lu/LL/.svn \
  924                          SRC/VARIANTS/lu/REC/.svn \
  925                          SRC/VARIANTS/qr/.svn \
  926                          SRC/VARIANTS/qr/LL/.svn \
  927                          INSTALL/.svn \
  928                          TESTING/.svn \
  929                          TESTING/EIG/.svn \
  930                          TESTING/MATGEN/.svn \
  931                          TESTING/LIN/.svn
  932 
  933 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
  934 # directories that are symbolic links (a Unix file system feature) are excluded
  935 # from the input.
  936 # The default value is: NO.
  937 
  938 EXCLUDE_SYMLINKS       = NO
  939 
  940 # If the value of the INPUT tag contains directories, you can use the
  941 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
  942 # certain files from those directories.
  943 #
  944 # Note that the wildcards are matched against the file with absolute path, so to
  945 # exclude all test directories for example use the pattern */test/*
  946 
  947 EXCLUDE_PATTERNS       = *.py \
  948                          *.txt \
  949                          *.in \
  950                          *.inc \
  951                          Makefile
  952 
  953 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
  954 # (namespaces, classes, functions, etc.) that should be excluded from the
  955 # output. The symbol name can be a fully qualified name, a word, or if the
  956 # wildcard * is used, a substring. Examples: ANamespace, AClass,
  957 # AClass::ANamespace, ANamespace::*Test
  958 #
  959 # Note that the wildcards are matched against the file with absolute path, so to
  960 # exclude all test directories use the pattern */test/*
  961 
  962 EXCLUDE_SYMBOLS        =
  963 
  964 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
  965 # that contain example code fragments that are included (see the \include
  966 # command).
  967 
  968 EXAMPLE_PATH           =
  969 
  970 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
  971 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
  972 # *.h) to filter out the source-files in the directories. If left blank all
  973 # files are included.
  974 
  975 EXAMPLE_PATTERNS       =
  976 
  977 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
  978 # searched for input files to be used with the \include or \dontinclude commands
  979 # irrespective of the value of the RECURSIVE tag.
  980 # The default value is: NO.
  981 
  982 EXAMPLE_RECURSIVE      = NO
  983 
  984 # The IMAGE_PATH tag can be used to specify one or more files or directories
  985 # that contain images that are to be included in the documentation (see the
  986 # \image command).
  987 
  988 IMAGE_PATH             =
  989 
  990 # The INPUT_FILTER tag can be used to specify a program that doxygen should
  991 # invoke to filter for each input file. Doxygen will invoke the filter program
  992 # by executing (via popen()) the command:
  993 #
  994 # <filter> <input-file>
  995 #
  996 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
  997 # name of an input file. Doxygen will then use the output that the filter
  998 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
  999 # will be ignored.
 1000 #
 1001 # Note that the filter must not add or remove lines; it is applied before the
 1002 # code is scanned, but not when the output code is generated. If lines are added
 1003 # or removed, the anchors will not be placed correctly.
 1004 #
 1005 # Note that for custom extensions or not directly supported extensions you also
 1006 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
 1007 # properly processed by doxygen.
 1008 
 1009 INPUT_FILTER           =
 1010 
 1011 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
 1012 # basis. Doxygen will compare the file name with each pattern and apply the
 1013 # filter if there is a match. The filters are a list of the form: pattern=filter
 1014 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
 1015 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
 1016 # patterns match the file name, INPUT_FILTER is applied.
 1017 #
 1018 # Note that for custom extensions or not directly supported extensions you also
 1019 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
 1020 # properly processed by doxygen.
 1021 
 1022 FILTER_PATTERNS        =
 1023 
 1024 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
 1025 # INPUT_FILTER) will also be used to filter the input files that are used for
 1026 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
 1027 # The default value is: NO.
 1028 
 1029 FILTER_SOURCE_FILES    = NO
 1030 
 1031 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
 1032 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
 1033 # it is also possible to disable source filtering for a specific pattern using
 1034 # *.ext= (so without naming a filter).
 1035 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
 1036 
 1037 FILTER_SOURCE_PATTERNS =
 1038 
 1039 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
 1040 # is part of the input, its contents will be placed on the main page
 1041 # (index.html). This can be useful if you have a project on for instance GitHub
 1042 # and want to reuse the introduction page also for the doxygen output.
 1043 
 1044 USE_MDFILE_AS_MAINPAGE =
 1045 
 1046 #---------------------------------------------------------------------------
 1047 # Configuration options related to source browsing
 1048 #---------------------------------------------------------------------------
 1049 
 1050 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
 1051 # generated. Documented entities will be cross-referenced with these sources.
 1052 #
 1053 # Note: To get rid of all source code in the generated output, make sure that
 1054 # also VERBATIM_HEADERS is set to NO.
 1055 # The default value is: NO.
 1056 
 1057 SOURCE_BROWSER         = YES
 1058 
 1059 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
 1060 # classes and enums directly into the documentation.
 1061 # The default value is: NO.
 1062 
 1063 INLINE_SOURCES         = YES
 1064 
 1065 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
 1066 # special comment blocks from generated source code fragments. Normal C, C++ and
 1067 # Fortran comments will always remain visible.
 1068 # The default value is: YES.
 1069 
 1070 STRIP_CODE_COMMENTS    = YES
 1071 
 1072 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
 1073 # entity all documented functions referencing it will be listed.
 1074 # The default value is: NO.
 1075 
 1076 REFERENCED_BY_RELATION = NO
 1077 
 1078 # If the REFERENCES_RELATION tag is set to YES then for each documented function
 1079 # all documented entities called/used by that function will be listed.
 1080 # The default value is: NO.
 1081 
 1082 REFERENCES_RELATION    = NO
 1083 
 1084 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
 1085 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
 1086 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
 1087 # link to the documentation.
 1088 # The default value is: YES.
 1089 
 1090 REFERENCES_LINK_SOURCE = YES
 1091 
 1092 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
 1093 # source code will show a tooltip with additional information such as prototype,
 1094 # brief description and links to the definition and documentation. Since this
 1095 # will make the HTML file larger and loading of large files a bit slower, you
 1096 # can opt to disable this feature.
 1097 # The default value is: YES.
 1098 # This tag requires that the tag SOURCE_BROWSER is set to YES.
 1099 
 1100 SOURCE_TOOLTIPS        = YES
 1101 
 1102 # If the USE_HTAGS tag is set to YES then the references to source code will
 1103 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
 1104 # source browser. The htags tool is part of GNU's global source tagging system
 1105 # (see https://www.gnu.org/software/global/global.html). You will need version
 1106 # 4.8.6 or higher.
 1107 #
 1108 # To use it do the following:
 1109 # - Install the latest version of global
 1110 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
 1111 # - Make sure the INPUT points to the root of the source tree
 1112 # - Run doxygen as normal
 1113 #
 1114 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
 1115 # tools must be available from the command line (i.e. in the search path).
 1116 #
 1117 # The result: instead of the source browser generated by doxygen, the links to
 1118 # source code will now point to the output of htags.
 1119 # The default value is: NO.
 1120 # This tag requires that the tag SOURCE_BROWSER is set to YES.
 1121 
 1122 USE_HTAGS              = NO
 1123 
 1124 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
 1125 # verbatim copy of the header file for each class for which an include is
 1126 # specified. Set to NO to disable this.
 1127 # See also: Section \class.
 1128 # The default value is: YES.
 1129 
 1130 VERBATIM_HEADERS       = YES
 1131 
 1132 #---------------------------------------------------------------------------
 1133 # Configuration options related to the alphabetical class index
 1134 #---------------------------------------------------------------------------
 1135 
 1136 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
 1137 # compounds will be generated. Enable this if the project contains a lot of
 1138 # classes, structs, unions or interfaces.
 1139 # The default value is: YES.
 1140 
 1141 ALPHABETICAL_INDEX     = YES
 1142 
 1143 # In case all classes in a project start with a common prefix, all classes will
 1144 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
 1145 # can be used to specify a prefix (or a list of prefixes) that should be ignored
 1146 # while generating the index headers.
 1147 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
 1148 
 1149 IGNORE_PREFIX          =
 1150 
 1151 #---------------------------------------------------------------------------
 1152 # Configuration options related to the HTML output
 1153 #---------------------------------------------------------------------------
 1154 
 1155 # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
 1156 # The default value is: YES.
 1157 
 1158 GENERATE_HTML          = YES
 1159 
 1160 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
 1161 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
 1162 # it.
 1163 # The default directory is: html.
 1164 # This tag requires that the tag GENERATE_HTML is set to YES.
 1165 
 1166 HTML_OUTPUT            = explore-html
 1167 
 1168 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
 1169 # generated HTML page (for example: .htm, .php, .asp).
 1170 # The default value is: .html.
 1171 # This tag requires that the tag GENERATE_HTML is set to YES.
 1172 
 1173 HTML_FILE_EXTENSION    = .html
 1174 
 1175 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
 1176 # each generated HTML page. If the tag is left blank doxygen will generate a
 1177 # standard header.
 1178 #
 1179 # To get valid HTML the header file that includes any scripts and style sheets
 1180 # that doxygen needs, which is dependent on the configuration options used (e.g.
 1181 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
 1182 # default header using
 1183 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
 1184 # YourConfigFile
 1185 # and then modify the file new_header.html. See also section "Doxygen usage"
 1186 # for information on how to generate the default header that doxygen normally
 1187 # uses.
 1188 # Note: The header is subject to change so you typically have to regenerate the
 1189 # default header when upgrading to a newer version of doxygen. For a description
 1190 # of the possible markers and block names see the documentation.
 1191 # This tag requires that the tag GENERATE_HTML is set to YES.
 1192 
 1193 HTML_HEADER            =
 1194 
 1195 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
 1196 # generated HTML page. If the tag is left blank doxygen will generate a standard
 1197 # footer. See HTML_HEADER for more information on how to generate a default
 1198 # footer and what special commands can be used inside the footer. See also
 1199 # section "Doxygen usage" for information on how to generate the default footer
 1200 # that doxygen normally uses.
 1201 # This tag requires that the tag GENERATE_HTML is set to YES.
 1202 
 1203 HTML_FOOTER            =
 1204 
 1205 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
 1206 # sheet that is used by each HTML page. It can be used to fine-tune the look of
 1207 # the HTML output. If left blank doxygen will generate a default style sheet.
 1208 # See also section "Doxygen usage" for information on how to generate the style
 1209 # sheet that doxygen normally uses.
 1210 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
 1211 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
 1212 # obsolete.
 1213 # This tag requires that the tag GENERATE_HTML is set to YES.
 1214 
 1215 HTML_STYLESHEET        =
 1216 
 1217 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
 1218 # cascading style sheets that are included after the standard style sheets
 1219 # created by doxygen. Using this option one can overrule certain style aspects.
 1220 # This is preferred over using HTML_STYLESHEET since it does not replace the
 1221 # standard style sheet and is therefore more robust against future updates.
 1222 # Doxygen will copy the style sheet files to the output directory.
 1223 # Note: The order of the extra style sheet files is of importance (e.g. the last
 1224 # style sheet in the list overrules the setting of the previous ones in the
 1225 # list). For an example see the documentation.
 1226 # This tag requires that the tag GENERATE_HTML is set to YES.
 1227 
 1228 HTML_EXTRA_STYLESHEET  =
 1229 
 1230 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
 1231 # other source files which should be copied to the HTML output directory. Note
 1232 # that these files will be copied to the base HTML output directory. Use the
 1233 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
 1234 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
 1235 # files will be copied as-is; there are no commands or markers available.
 1236 # This tag requires that the tag GENERATE_HTML is set to YES.
 1237 
 1238 HTML_EXTRA_FILES       =
 1239 
 1240 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
 1241 # will adjust the colors in the style sheet and background images according to
 1242 # this color. Hue is specified as an angle on a colorwheel, see
 1243 # https://en.wikipedia.org/wiki/Hue for more information. For instance the value
 1244 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
 1245 # purple, and 360 is red again.
 1246 # Minimum value: 0, maximum value: 359, default value: 220.
 1247 # This tag requires that the tag GENERATE_HTML is set to YES.
 1248 
 1249 HTML_COLORSTYLE_HUE    = 220
 1250 
 1251 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
 1252 # in the HTML output. For a value of 0 the output will use grayscales only. A
 1253 # value of 255 will produce the most vivid colors.
 1254 # Minimum value: 0, maximum value: 255, default value: 100.
 1255 # This tag requires that the tag GENERATE_HTML is set to YES.
 1256 
 1257 HTML_COLORSTYLE_SAT    = 100
 1258 
 1259 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
 1260 # luminance component of the colors in the HTML output. Values below 100
 1261 # gradually make the output lighter, whereas values above 100 make the output
 1262 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
 1263 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
 1264 # change the gamma.
 1265 # Minimum value: 40, maximum value: 240, default value: 80.
 1266 # This tag requires that the tag GENERATE_HTML is set to YES.
 1267 
 1268 HTML_COLORSTYLE_GAMMA  = 80
 1269 
 1270 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
 1271 # page will contain the date and time when the page was generated. Setting this
 1272 # to YES can help to show when doxygen was last run and thus if the
 1273 # documentation is up to date.
 1274 # The default value is: NO.
 1275 # This tag requires that the tag GENERATE_HTML is set to YES.
 1276 
 1277 HTML_TIMESTAMP         = YES
 1278 
 1279 # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
 1280 # documentation will contain a main index with vertical navigation menus that
 1281 # are dynamically created via JavaScript. If disabled, the navigation index will
 1282 # consists of multiple levels of tabs that are statically embedded in every HTML
 1283 # page. Disable this option to support browsers that do not have JavaScript,
 1284 # like the Qt help browser.
 1285 # The default value is: YES.
 1286 # This tag requires that the tag GENERATE_HTML is set to YES.
 1287 
 1288 HTML_DYNAMIC_MENUS     = YES
 1289 
 1290 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
 1291 # documentation will contain sections that can be hidden and shown after the
 1292 # page has loaded.
 1293 # The default value is: NO.
 1294 # This tag requires that the tag GENERATE_HTML is set to YES.
 1295 
 1296 HTML_DYNAMIC_SECTIONS  = NO
 1297 
 1298 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
 1299 # shown in the various tree structured indices initially; the user can expand
 1300 # and collapse entries dynamically later on. Doxygen will expand the tree to
 1301 # such a level that at most the specified number of entries are visible (unless
 1302 # a fully collapsed tree already exceeds this amount). So setting the number of
 1303 # entries 1 will produce a full collapsed tree by default. 0 is a special value
 1304 # representing an infinite number of entries and will result in a full expanded
 1305 # tree by default.
 1306 # Minimum value: 0, maximum value: 9999, default value: 100.
 1307 # This tag requires that the tag GENERATE_HTML is set to YES.
 1308 
 1309 HTML_INDEX_NUM_ENTRIES = 100
 1310 
 1311 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
 1312 # generated that can be used as input for Apple's Xcode 3 integrated development
 1313 # environment (see:
 1314 # https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To
 1315 # create a documentation set, doxygen will generate a Makefile in the HTML
 1316 # output directory. Running make will produce the docset in that directory and
 1317 # running make install will install the docset in
 1318 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
 1319 # startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
 1320 # genXcode/_index.html for more information.
 1321 # The default value is: NO.
 1322 # This tag requires that the tag GENERATE_HTML is set to YES.
 1323 
 1324 GENERATE_DOCSET        = NO
 1325 
 1326 # This tag determines the name of the docset feed. A documentation feed provides
 1327 # an umbrella under which multiple documentation sets from a single provider
 1328 # (such as a company or product suite) can be grouped.
 1329 # The default value is: Doxygen generated docs.
 1330 # This tag requires that the tag GENERATE_DOCSET is set to YES.
 1331 
 1332 DOCSET_FEEDNAME        = "Doxygen generated docs"
 1333 
 1334 # This tag specifies a string that should uniquely identify the documentation
 1335 # set bundle. This should be a reverse domain-name style string, e.g.
 1336 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
 1337 # The default value is: org.doxygen.Project.
 1338 # This tag requires that the tag GENERATE_DOCSET is set to YES.
 1339 
 1340 DOCSET_BUNDLE_ID       = org.doxygen.Project
 1341 
 1342 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
 1343 # the documentation publisher. This should be a reverse domain-name style
 1344 # string, e.g. com.mycompany.MyDocSet.documentation.
 1345 # The default value is: org.doxygen.Publisher.
 1346 # This tag requires that the tag GENERATE_DOCSET is set to YES.
 1347 
 1348 DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
 1349 
 1350 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
 1351 # The default value is: Publisher.
 1352 # This tag requires that the tag GENERATE_DOCSET is set to YES.
 1353 
 1354 DOCSET_PUBLISHER_NAME  = Publisher
 1355 
 1356 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
 1357 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
 1358 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
 1359 # (see:
 1360 # https://www.microsoft.com/en-us/download/details.aspx?id=21138) on Windows.
 1361 #
 1362 # The HTML Help Workshop contains a compiler that can convert all HTML output
 1363 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
 1364 # files are now used as the Windows 98 help format, and will replace the old
 1365 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
 1366 # HTML files also contain an index, a table of contents, and you can search for
 1367 # words in the documentation. The HTML workshop also contains a viewer for
 1368 # compressed HTML files.
 1369 # The default value is: NO.
 1370 # This tag requires that the tag GENERATE_HTML is set to YES.
 1371 
 1372 GENERATE_HTMLHELP      = NO
 1373 
 1374 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
 1375 # file. You can add a path in front of the file if the result should not be
 1376 # written to the html output directory.
 1377 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1378 
 1379 CHM_FILE               =
 1380 
 1381 # The HHC_LOCATION tag can be used to specify the location (absolute path
 1382 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
 1383 # doxygen will try to run the HTML help compiler on the generated index.hhp.
 1384 # The file has to be specified with full path.
 1385 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1386 
 1387 HHC_LOCATION           =
 1388 
 1389 # The GENERATE_CHI flag controls if a separate .chi index file is generated
 1390 # (YES) or that it should be included in the main .chm file (NO).
 1391 # The default value is: NO.
 1392 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1393 
 1394 GENERATE_CHI           = NO
 1395 
 1396 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
 1397 # and project file content.
 1398 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1399 
 1400 CHM_INDEX_ENCODING     =
 1401 
 1402 # The BINARY_TOC flag controls whether a binary table of contents is generated
 1403 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
 1404 # enables the Previous and Next buttons.
 1405 # The default value is: NO.
 1406 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1407 
 1408 BINARY_TOC             = NO
 1409 
 1410 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
 1411 # the table of contents of the HTML help documentation and to the tree view.
 1412 # The default value is: NO.
 1413 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 1414 
 1415 TOC_EXPAND             = NO
 1416 
 1417 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
 1418 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
 1419 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
 1420 # (.qch) of the generated HTML documentation.
 1421 # The default value is: NO.
 1422 # This tag requires that the tag GENERATE_HTML is set to YES.
 1423 
 1424 GENERATE_QHP           = NO
 1425 
 1426 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
 1427 # the file name of the resulting .qch file. The path specified is relative to
 1428 # the HTML output folder.
 1429 # This tag requires that the tag GENERATE_QHP is set to YES.
 1430 
 1431 QCH_FILE               =
 1432 
 1433 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
 1434 # Project output. For more information please see Qt Help Project / Namespace
 1435 # (see:
 1436 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
 1437 # The default value is: org.doxygen.Project.
 1438 # This tag requires that the tag GENERATE_QHP is set to YES.
 1439 
 1440 QHP_NAMESPACE          = org.doxygen.Project
 1441 
 1442 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
 1443 # Help Project output. For more information please see Qt Help Project / Virtual
 1444 # Folders (see:
 1445 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
 1446 # The default value is: doc.
 1447 # This tag requires that the tag GENERATE_QHP is set to YES.
 1448 
 1449 QHP_VIRTUAL_FOLDER     = doc
 1450 
 1451 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
 1452 # filter to add. For more information please see Qt Help Project / Custom
 1453 # Filters (see:
 1454 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
 1455 # This tag requires that the tag GENERATE_QHP is set to YES.
 1456 
 1457 QHP_CUST_FILTER_NAME   =
 1458 
 1459 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
 1460 # custom filter to add. For more information please see Qt Help Project / Custom
 1461 # Filters (see:
 1462 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
 1463 # This tag requires that the tag GENERATE_QHP is set to YES.
 1464 
 1465 QHP_CUST_FILTER_ATTRS  =
 1466 
 1467 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
 1468 # project's filter section matches. Qt Help Project / Filter Attributes (see:
 1469 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
 1470 # This tag requires that the tag GENERATE_QHP is set to YES.
 1471 
 1472 QHP_SECT_FILTER_ATTRS  =
 1473 
 1474 # The QHG_LOCATION tag can be used to specify the location (absolute path
 1475 # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
 1476 # run qhelpgenerator on the generated .qhp file.
 1477 # This tag requires that the tag GENERATE_QHP is set to YES.
 1478 
 1479 QHG_LOCATION           =
 1480 
 1481 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
 1482 # generated, together with the HTML files, they form an Eclipse help plugin. To
 1483 # install this plugin and make it available under the help contents menu in
 1484 # Eclipse, the contents of the directory containing the HTML and XML files needs
 1485 # to be copied into the plugins directory of eclipse. The name of the directory
 1486 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
 1487 # After copying Eclipse needs to be restarted before the help appears.
 1488 # The default value is: NO.
 1489 # This tag requires that the tag GENERATE_HTML is set to YES.
 1490 
 1491 GENERATE_ECLIPSEHELP   = NO
 1492 
 1493 # A unique identifier for the Eclipse help plugin. When installing the plugin
 1494 # the directory name containing the HTML and XML files should also have this
 1495 # name. Each documentation set should have its own identifier.
 1496 # The default value is: org.doxygen.Project.
 1497 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
 1498 
 1499 ECLIPSE_DOC_ID         = org.doxygen.Project
 1500 
 1501 # If you want full control over the layout of the generated HTML pages it might
 1502 # be necessary to disable the index and replace it with your own. The
 1503 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
 1504 # of each HTML page. A value of NO enables the index and the value YES disables
 1505 # it. Since the tabs in the index contain the same information as the navigation
 1506 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
 1507 # The default value is: NO.
 1508 # This tag requires that the tag GENERATE_HTML is set to YES.
 1509 
 1510 DISABLE_INDEX          = NO
 1511 
 1512 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
 1513 # structure should be generated to display hierarchical information. If the tag
 1514 # value is set to YES, a side panel will be generated containing a tree-like
 1515 # index structure (just like the one that is generated for HTML Help). For this
 1516 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
 1517 # (i.e. any modern browser). Windows users are probably better off using the
 1518 # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
 1519 # further fine-tune the look of the index. As an example, the default style
 1520 # sheet generated by doxygen has an example that shows how to put an image at
 1521 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
 1522 # the same information as the tab index, you could consider setting
 1523 # DISABLE_INDEX to YES when enabling this option.
 1524 # The default value is: NO.
 1525 # This tag requires that the tag GENERATE_HTML is set to YES.
 1526 
 1527 GENERATE_TREEVIEW      = YES
 1528 
 1529 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
 1530 # doxygen will group on one line in the generated HTML documentation.
 1531 #
 1532 # Note that a value of 0 will completely suppress the enum values from appearing
 1533 # in the overview section.
 1534 # Minimum value: 0, maximum value: 20, default value: 4.
 1535 # This tag requires that the tag GENERATE_HTML is set to YES.
 1536 
 1537 ENUM_VALUES_PER_LINE   = 4
 1538 
 1539 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
 1540 # to set the initial width (in pixels) of the frame in which the tree is shown.
 1541 # Minimum value: 0, maximum value: 1500, default value: 250.
 1542 # This tag requires that the tag GENERATE_HTML is set to YES.
 1543 
 1544 TREEVIEW_WIDTH         = 250
 1545 
 1546 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
 1547 # external symbols imported via tag files in a separate window.
 1548 # The default value is: NO.
 1549 # This tag requires that the tag GENERATE_HTML is set to YES.
 1550 
 1551 EXT_LINKS_IN_WINDOW    = NO
 1552 
 1553 # If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg
 1554 # tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see
 1555 # https://inkscape.org) to generate formulas as SVG images instead of PNGs for
 1556 # the HTML output. These images will generally look nicer at scaled resolutions.
 1557 # Possible values are: png (the default) and svg (looks nicer but requires the
 1558 # pdf2svg or inkscape tool).
 1559 # The default value is: png.
 1560 # This tag requires that the tag GENERATE_HTML is set to YES.
 1561 
 1562 HTML_FORMULA_FORMAT    = png
 1563 
 1564 # Use this tag to change the font size of LaTeX formulas included as images in
 1565 # the HTML documentation. When you change the font size after a successful
 1566 # doxygen run you need to manually remove any form_*.png images from the HTML
 1567 # output directory to force them to be regenerated.
 1568 # Minimum value: 8, maximum value: 50, default value: 10.
 1569 # This tag requires that the tag GENERATE_HTML is set to YES.
 1570 
 1571 FORMULA_FONTSIZE       = 10
 1572 
 1573 # Use the FORMULA_TRANSPARENT tag to determine whether or not the images
 1574 # generated for formulas are transparent PNGs. Transparent PNGs are not
 1575 # supported properly for IE 6.0, but are supported on all modern browsers.
 1576 #
 1577 # Note that when changing this option you need to delete any form_*.png files in
 1578 # the HTML output directory before the changes have effect.
 1579 # The default value is: YES.
 1580 # This tag requires that the tag GENERATE_HTML is set to YES.
 1581 
 1582 FORMULA_TRANSPARENT    = YES
 1583 
 1584 # The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
 1585 # to create new LaTeX commands to be used in formulas as building blocks. See
 1586 # the section "Including formulas" for details.
 1587 
 1588 FORMULA_MACROFILE      =
 1589 
 1590 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
 1591 # https://www.mathjax.org) which uses client side JavaScript for the rendering
 1592 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
 1593 # installed or if you want to formulas look prettier in the HTML output. When
 1594 # enabled you may also need to install MathJax separately and configure the path
 1595 # to it using the MATHJAX_RELPATH option.
 1596 # The default value is: NO.
 1597 # This tag requires that the tag GENERATE_HTML is set to YES.
 1598 
 1599 USE_MATHJAX            = NO
 1600 
 1601 # When MathJax is enabled you can set the default output format to be used for
 1602 # the MathJax output. See the MathJax site (see:
 1603 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details.
 1604 # Possible values are: HTML-CSS (which is slower, but has the best
 1605 # compatibility), NativeMML (i.e. MathML) and SVG.
 1606 # The default value is: HTML-CSS.
 1607 # This tag requires that the tag USE_MATHJAX is set to YES.
 1608 
 1609 MATHJAX_FORMAT         = HTML-CSS
 1610 
 1611 # When MathJax is enabled you need to specify the location relative to the HTML
 1612 # output directory using the MATHJAX_RELPATH option. The destination directory
 1613 # should contain the MathJax.js script. For instance, if the mathjax directory
 1614 # is located at the same level as the HTML output directory, then
 1615 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
 1616 # Content Delivery Network so you can quickly see the result without installing
 1617 # MathJax. However, it is strongly recommended to install a local copy of
 1618 # MathJax from https://www.mathjax.org before deployment.
 1619 # The default value is: https://cdn.jsdelivr.net/npm/mathjax@2.
 1620 # This tag requires that the tag USE_MATHJAX is set to YES.
 1621 
 1622 MATHJAX_RELPATH        = http://www.mathjax.org/mathjax
 1623 
 1624 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
 1625 # extension names that should be enabled during MathJax rendering. For example
 1626 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
 1627 # This tag requires that the tag USE_MATHJAX is set to YES.
 1628 
 1629 MATHJAX_EXTENSIONS     =
 1630 
 1631 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
 1632 # of code that will be used on startup of the MathJax code. See the MathJax site
 1633 # (see:
 1634 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
 1635 # example see the documentation.
 1636 # This tag requires that the tag USE_MATHJAX is set to YES.
 1637 
 1638 MATHJAX_CODEFILE       =
 1639 
 1640 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
 1641 # the HTML output. The underlying search engine uses javascript and DHTML and
 1642 # should work on any modern browser. Note that when using HTML help
 1643 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
 1644 # there is already a search function so this one should typically be disabled.
 1645 # For large projects the javascript based search engine can be slow, then
 1646 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
 1647 # search using the keyboard; to jump to the search box use <access key> + S
 1648 # (what the <access key> is depends on the OS and browser, but it is typically
 1649 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
 1650 # key> to jump into the search results window, the results can be navigated
 1651 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
 1652 # the search. The filter options can be selected when the cursor is inside the
 1653 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
 1654 # to select a filter and <Enter> or <escape> to activate or cancel the filter
 1655 # option.
 1656 # The default value is: YES.
 1657 # This tag requires that the tag GENERATE_HTML is set to YES.
 1658 
 1659 SEARCHENGINE           = YES
 1660 
 1661 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
 1662 # implemented using a web server instead of a web client using JavaScript. There
 1663 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
 1664 # setting. When disabled, doxygen will generate a PHP script for searching and
 1665 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
 1666 # and searching needs to be provided by external tools. See the section
 1667 # "External Indexing and Searching" for details.
 1668 # The default value is: NO.
 1669 # This tag requires that the tag SEARCHENGINE is set to YES.
 1670 
 1671 SERVER_BASED_SEARCH    = NO
 1672 
 1673 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
 1674 # script for searching. Instead the search results are written to an XML file
 1675 # which needs to be processed by an external indexer. Doxygen will invoke an
 1676 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
 1677 # search results.
 1678 #
 1679 # Doxygen ships with an example indexer (doxyindexer) and search engine
 1680 # (doxysearch.cgi) which are based on the open source search engine library
 1681 # Xapian (see:
 1682 # https://xapian.org/).
 1683 #
 1684 # See the section "External Indexing and Searching" for details.
 1685 # The default value is: NO.
 1686 # This tag requires that the tag SEARCHENGINE is set to YES.
 1687 
 1688 EXTERNAL_SEARCH        = NO
 1689 
 1690 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
 1691 # which will return the search results when EXTERNAL_SEARCH is enabled.
 1692 #
 1693 # Doxygen ships with an example indexer (doxyindexer) and search engine
 1694 # (doxysearch.cgi) which are based on the open source search engine library
 1695 # Xapian (see:
 1696 # https://xapian.org/). See the section "External Indexing and Searching" for
 1697 # details.
 1698 # This tag requires that the tag SEARCHENGINE is set to YES.
 1699 
 1700 SEARCHENGINE_URL       =
 1701 
 1702 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
 1703 # search data is written to a file for indexing by an external tool. With the
 1704 # SEARCHDATA_FILE tag the name of this file can be specified.
 1705 # The default file is: searchdata.xml.
 1706 # This tag requires that the tag SEARCHENGINE is set to YES.
 1707 
 1708 SEARCHDATA_FILE        = searchdata.xml
 1709 
 1710 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
 1711 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
 1712 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
 1713 # projects and redirect the results back to the right project.
 1714 # This tag requires that the tag SEARCHENGINE is set to YES.
 1715 
 1716 EXTERNAL_SEARCH_ID     =
 1717 
 1718 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
 1719 # projects other than the one defined by this configuration file, but that are
 1720 # all added to the same external search index. Each project needs to have a
 1721 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
 1722 # to a relative location where the documentation can be found. The format is:
 1723 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
 1724 # This tag requires that the tag SEARCHENGINE is set to YES.
 1725 
 1726 EXTRA_SEARCH_MAPPINGS  =
 1727 
 1728 #---------------------------------------------------------------------------
 1729 # Configuration options related to the LaTeX output
 1730 #---------------------------------------------------------------------------
 1731 
 1732 # If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
 1733 # The default value is: YES.
 1734 
 1735 GENERATE_LATEX         = NO
 1736 
 1737 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
 1738 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
 1739 # it.
 1740 # The default directory is: latex.
 1741 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1742 
 1743 LATEX_OUTPUT           = latex
 1744 
 1745 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
 1746 # invoked.
 1747 #
 1748 # Note that when not enabling USE_PDFLATEX the default is latex when enabling
 1749 # USE_PDFLATEX the default is pdflatex and when in the later case latex is
 1750 # chosen this is overwritten by pdflatex. For specific output languages the
 1751 # default can have been set differently, this depends on the implementation of
 1752 # the output language.
 1753 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1754 
 1755 LATEX_CMD_NAME         = latex
 1756 
 1757 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
 1758 # index for LaTeX.
 1759 # Note: This tag is used in the Makefile / make.bat.
 1760 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
 1761 # (.tex).
 1762 # The default file is: makeindex.
 1763 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1764 
 1765 MAKEINDEX_CMD_NAME     = makeindex
 1766 
 1767 # The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
 1768 # generate index for LaTeX. In case there is no backslash (\) as first character
 1769 # it will be automatically added in the LaTeX code.
 1770 # Note: This tag is used in the generated output file (.tex).
 1771 # See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
 1772 # The default value is: makeindex.
 1773 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1774 
 1775 LATEX_MAKEINDEX_CMD    = makeindex
 1776 
 1777 # If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
 1778 # documents. This may be useful for small projects and may help to save some
 1779 # trees in general.
 1780 # The default value is: NO.
 1781 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1782 
 1783 COMPACT_LATEX          = NO
 1784 
 1785 # The PAPER_TYPE tag can be used to set the paper type that is used by the
 1786 # printer.
 1787 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
 1788 # 14 inches) and executive (7.25 x 10.5 inches).
 1789 # The default value is: a4.
 1790 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1791 
 1792 PAPER_TYPE             = a4
 1793 
 1794 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
 1795 # that should be included in the LaTeX output. The package can be specified just
 1796 # by its name or with the correct syntax as to be used with the LaTeX
 1797 # \usepackage command. To get the times font for instance you can specify :
 1798 # EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
 1799 # To use the option intlimits with the amsmath package you can specify:
 1800 # EXTRA_PACKAGES=[intlimits]{amsmath}
 1801 # If left blank no extra packages will be included.
 1802 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1803 
 1804 EXTRA_PACKAGES         =
 1805 
 1806 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
 1807 # generated LaTeX document. The header should contain everything until the first
 1808 # chapter. If it is left blank doxygen will generate a standard header. See
 1809 # section "Doxygen usage" for information on how to let doxygen write the
 1810 # default header to a separate file.
 1811 #
 1812 # Note: Only use a user-defined header if you know what you are doing! The
 1813 # following commands have a special meaning inside the header: $title,
 1814 # $datetime, $date, $doxygenversion, $projectname, $projectnumber,
 1815 # $projectbrief, $projectlogo. Doxygen will replace $title with the empty
 1816 # string, for the replacement values of the other commands the user is referred
 1817 # to HTML_HEADER.
 1818 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1819 
 1820 LATEX_HEADER           =
 1821 
 1822 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
 1823 # generated LaTeX document. The footer should contain everything after the last
 1824 # chapter. If it is left blank doxygen will generate a standard footer. See
 1825 # LATEX_HEADER for more information on how to generate a default footer and what
 1826 # special commands can be used inside the footer.
 1827 #
 1828 # Note: Only use a user-defined footer if you know what you are doing!
 1829 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1830 
 1831 LATEX_FOOTER           =
 1832 
 1833 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
 1834 # LaTeX style sheets that are included after the standard style sheets created
 1835 # by doxygen. Using this option one can overrule certain style aspects. Doxygen
 1836 # will copy the style sheet files to the output directory.
 1837 # Note: The order of the extra style sheet files is of importance (e.g. the last
 1838 # style sheet in the list overrules the setting of the previous ones in the
 1839 # list).
 1840 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1841 
 1842 LATEX_EXTRA_STYLESHEET =
 1843 
 1844 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
 1845 # other source files which should be copied to the LATEX_OUTPUT output
 1846 # directory. Note that the files will be copied as-is; there are no commands or
 1847 # markers available.
 1848 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1849 
 1850 LATEX_EXTRA_FILES      =
 1851 
 1852 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
 1853 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
 1854 # contain links (just like the HTML output) instead of page references. This
 1855 # makes the output suitable for online browsing using a PDF viewer.
 1856 # The default value is: YES.
 1857 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1858 
 1859 PDF_HYPERLINKS         = YES
 1860 
 1861 # If the USE_PDFLATEX tag is set to YES, doxygen will use the engine as
 1862 # specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
 1863 # files. Set this option to YES, to get a higher quality PDF documentation.
 1864 #
 1865 # See also section LATEX_CMD_NAME for selecting the engine.
 1866 # The default value is: YES.
 1867 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1868 
 1869 USE_PDFLATEX           = YES
 1870 
 1871 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
 1872 # command to the generated LaTeX files. This will instruct LaTeX to keep running
 1873 # if errors occur, instead of asking the user for help. This option is also used
 1874 # when generating formulas in HTML.
 1875 # The default value is: NO.
 1876 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1877 
 1878 LATEX_BATCHMODE        = NO
 1879 
 1880 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
 1881 # index chapters (such as File Index, Compound Index, etc.) in the output.
 1882 # The default value is: NO.
 1883 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1884 
 1885 LATEX_HIDE_INDICES     = NO
 1886 
 1887 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
 1888 # code with syntax highlighting in the LaTeX output.
 1889 #
 1890 # Note that which sources are shown also depends on other settings such as
 1891 # SOURCE_BROWSER.
 1892 # The default value is: NO.
 1893 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1894 
 1895 LATEX_SOURCE_CODE      = NO
 1896 
 1897 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
 1898 # bibliography, e.g. plainnat, or ieeetr. See
 1899 # https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
 1900 # The default value is: plain.
 1901 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1902 
 1903 LATEX_BIB_STYLE        = plain
 1904 
 1905 # If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated
 1906 # page will contain the date and time when the page was generated. Setting this
 1907 # to NO can help when comparing the output of multiple runs.
 1908 # The default value is: NO.
 1909 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1910 
 1911 LATEX_TIMESTAMP        = NO
 1912 
 1913 # The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
 1914 # path from which the emoji images will be read. If a relative path is entered,
 1915 # it will be relative to the LATEX_OUTPUT directory. If left blank the
 1916 # LATEX_OUTPUT directory will be used.
 1917 # This tag requires that the tag GENERATE_LATEX is set to YES.
 1918 
 1919 LATEX_EMOJI_DIRECTORY  =
 1920 
 1921 #---------------------------------------------------------------------------
 1922 # Configuration options related to the RTF output
 1923 #---------------------------------------------------------------------------
 1924 
 1925 # If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
 1926 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
 1927 # readers/editors.
 1928 # The default value is: NO.
 1929 
 1930 GENERATE_RTF           = NO
 1931 
 1932 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
 1933 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
 1934 # it.
 1935 # The default directory is: rtf.
 1936 # This tag requires that the tag GENERATE_RTF is set to YES.
 1937 
 1938 RTF_OUTPUT             = rtf
 1939 
 1940 # If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
 1941 # documents. This may be useful for small projects and may help to save some
 1942 # trees in general.
 1943 # The default value is: NO.
 1944 # This tag requires that the tag GENERATE_RTF is set to YES.
 1945 
 1946 COMPACT_RTF            = NO
 1947 
 1948 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
 1949 # contain hyperlink fields. The RTF file will contain links (just like the HTML
 1950 # output) instead of page references. This makes the output suitable for online
 1951 # browsing using Word or some other Word compatible readers that support those
 1952 # fields.
 1953 #
 1954 # Note: WordPad (write) and others do not support links.
 1955 # The default value is: NO.
 1956 # This tag requires that the tag GENERATE_RTF is set to YES.
 1957 
 1958 RTF_HYPERLINKS         = YES
 1959 
 1960 # Load stylesheet definitions from file. Syntax is similar to doxygen's
 1961 # configuration file, i.e. a series of assignments. You only have to provide
 1962 # replacements, missing definitions are set to their default value.
 1963 #
 1964 # See also section "Doxygen usage" for information on how to generate the
 1965 # default style sheet that doxygen normally uses.
 1966 # This tag requires that the tag GENERATE_RTF is set to YES.
 1967 
 1968 RTF_STYLESHEET_FILE    =
 1969 
 1970 # Set optional variables used in the generation of an RTF document. Syntax is
 1971 # similar to doxygen's configuration file. A template extensions file can be
 1972 # generated using doxygen -e rtf extensionFile.
 1973 # This tag requires that the tag GENERATE_RTF is set to YES.
 1974 
 1975 RTF_EXTENSIONS_FILE    =
 1976 
 1977 # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
 1978 # with syntax highlighting in the RTF output.
 1979 #
 1980 # Note that which sources are shown also depends on other settings such as
 1981 # SOURCE_BROWSER.
 1982 # The default value is: NO.
 1983 # This tag requires that the tag GENERATE_RTF is set to YES.
 1984 
 1985 RTF_SOURCE_CODE        = NO
 1986 
 1987 #---------------------------------------------------------------------------
 1988 # Configuration options related to the man page output
 1989 #---------------------------------------------------------------------------
 1990 
 1991 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
 1992 # classes and files.
 1993 # The default value is: NO.
 1994 
 1995 GENERATE_MAN           = NO
 1996 
 1997 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
 1998 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
 1999 # it. A directory man3 will be created inside the directory specified by
 2000 # MAN_OUTPUT.
 2001 # The default directory is: man.
 2002 # This tag requires that the tag GENERATE_MAN is set to YES.
 2003 
 2004 MAN_OUTPUT             = man
 2005 
 2006 # The MAN_EXTENSION tag determines the extension that is added to the generated
 2007 # man pages. In case the manual section does not start with a number, the number
 2008 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
 2009 # optional.
 2010 # The default value is: .3.
 2011 # This tag requires that the tag GENERATE_MAN is set to YES.
 2012 
 2013 MAN_EXTENSION          = .3
 2014 
 2015 # The MAN_SUBDIR tag determines the name of the directory created within
 2016 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
 2017 # MAN_EXTENSION with the initial . removed.
 2018 # This tag requires that the tag GENERATE_MAN is set to YES.
 2019 
 2020 MAN_SUBDIR             =
 2021 
 2022 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
 2023 # will generate one additional man file for each entity documented in the real
 2024 # man page(s). These additional files only source the real man page, but without
 2025 # them the man command would be unable to find the correct page.
 2026 # The default value is: NO.
 2027 # This tag requires that the tag GENERATE_MAN is set to YES.
 2028 
 2029 MAN_LINKS              = YES
 2030 
 2031 #---------------------------------------------------------------------------
 2032 # Configuration options related to the XML output
 2033 #---------------------------------------------------------------------------
 2034 
 2035 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
 2036 # captures the structure of the code including all documentation.
 2037 # The default value is: NO.
 2038 
 2039 GENERATE_XML           = NO
 2040 
 2041 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
 2042 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
 2043 # it.
 2044 # The default directory is: xml.
 2045 # This tag requires that the tag GENERATE_XML is set to YES.
 2046 
 2047 XML_OUTPUT             = xml
 2048 
 2049 # If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
 2050 # listings (including syntax highlighting and cross-referencing information) to
 2051 # the XML output. Note that enabling this will significantly increase the size
 2052 # of the XML output.
 2053 # The default value is: YES.
 2054 # This tag requires that the tag GENERATE_XML is set to YES.
 2055 
 2056 XML_PROGRAMLISTING     = YES
 2057 
 2058 # If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
 2059 # namespace members in file scope as well, matching the HTML output.
 2060 # The default value is: NO.
 2061 # This tag requires that the tag GENERATE_XML is set to YES.
 2062 
 2063 XML_NS_MEMB_FILE_SCOPE = NO
 2064 
 2065 #---------------------------------------------------------------------------
 2066 # Configuration options related to the DOCBOOK output
 2067 #---------------------------------------------------------------------------
 2068 
 2069 # If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
 2070 # that can be used to generate PDF.
 2071 # The default value is: NO.
 2072 
 2073 GENERATE_DOCBOOK       = NO
 2074 
 2075 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
 2076 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
 2077 # front of it.
 2078 # The default directory is: docbook.
 2079 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
 2080 
 2081 DOCBOOK_OUTPUT         = docbook
 2082 
 2083 # If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
 2084 # program listings (including syntax highlighting and cross-referencing
 2085 # information) to the DOCBOOK output. Note that enabling this will significantly
 2086 # increase the size of the DOCBOOK output.
 2087 # The default value is: NO.
 2088 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
 2089 
 2090 DOCBOOK_PROGRAMLISTING = NO
 2091 
 2092 #---------------------------------------------------------------------------
 2093 # Configuration options for the AutoGen Definitions output
 2094 #---------------------------------------------------------------------------
 2095 
 2096 # If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
 2097 # AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
 2098 # the structure of the code including all documentation. Note that this feature
 2099 # is still experimental and incomplete at the moment.
 2100 # The default value is: NO.
 2101 
 2102 GENERATE_AUTOGEN_DEF   = NO
 2103 
 2104 #---------------------------------------------------------------------------
 2105 # Configuration options related to the Perl module output
 2106 #---------------------------------------------------------------------------
 2107 
 2108 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
 2109 # file that captures the structure of the code including all documentation.
 2110 #
 2111 # Note that this feature is still experimental and incomplete at the moment.
 2112 # The default value is: NO.
 2113 
 2114 GENERATE_PERLMOD       = NO
 2115 
 2116 # If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
 2117 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
 2118 # output from the Perl module output.
 2119 # The default value is: NO.
 2120 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
 2121 
 2122 PERLMOD_LATEX          = NO
 2123 
 2124 # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
 2125 # formatted so it can be parsed by a human reader. This is useful if you want to
 2126 # understand what is going on. On the other hand, if this tag is set to NO, the
 2127 # size of the Perl module output will be much smaller and Perl will parse it
 2128 # just the same.
 2129 # The default value is: YES.
 2130 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
 2131 
 2132 PERLMOD_PRETTY         = YES
 2133 
 2134 # The names of the make variables in the generated doxyrules.make file are
 2135 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
 2136 # so different doxyrules.make files included by the same Makefile don't
 2137 # overwrite each other's variables.
 2138 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
 2139 
 2140 PERLMOD_MAKEVAR_PREFIX =
 2141 
 2142 #---------------------------------------------------------------------------
 2143 # Configuration options related to the preprocessor
 2144 #---------------------------------------------------------------------------
 2145 
 2146 # If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
 2147 # C-preprocessor directives found in the sources and include files.
 2148 # The default value is: YES.
 2149 
 2150 ENABLE_PREPROCESSING   = YES
 2151 
 2152 # If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
 2153 # in the source code. If set to NO, only conditional compilation will be
 2154 # performed. Macro expansion can be done in a controlled way by setting
 2155 # EXPAND_ONLY_PREDEF to YES.
 2156 # The default value is: NO.
 2157 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2158 
 2159 MACRO_EXPANSION        = NO
 2160 
 2161 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
 2162 # the macro expansion is limited to the macros specified with the PREDEFINED and
 2163 # EXPAND_AS_DEFINED tags.
 2164 # The default value is: NO.
 2165 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2166 
 2167 EXPAND_ONLY_PREDEF     = NO
 2168 
 2169 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
 2170 # INCLUDE_PATH will be searched if a #include is found.
 2171 # The default value is: YES.
 2172 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2173 
 2174 SEARCH_INCLUDES        = YES
 2175 
 2176 # The INCLUDE_PATH tag can be used to specify one or more directories that
 2177 # contain include files that are not input files but should be processed by the
 2178 # preprocessor.
 2179 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
 2180 
 2181 INCLUDE_PATH           =
 2182 
 2183 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
 2184 # patterns (like *.h and *.hpp) to filter out the header-files in the
 2185 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
 2186 # used.
 2187 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2188 
 2189 INCLUDE_FILE_PATTERNS  =
 2190 
 2191 # The PREDEFINED tag can be used to specify one or more macro names that are
 2192 # defined before the preprocessor is started (similar to the -D option of e.g.
 2193 # gcc). The argument of the tag is a list of macros of the form: name or
 2194 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
 2195 # is assumed. To prevent a macro definition from being undefined via #undef or
 2196 # recursively expanded use the := operator instead of the = operator.
 2197 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2198 
 2199 PREDEFINED             =
 2200 
 2201 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
 2202 # tag can be used to specify a list of macro names that should be expanded. The
 2203 # macro definition that is found in the sources will be used. Use the PREDEFINED
 2204 # tag if you want to use a different macro definition that overrules the
 2205 # definition found in the source code.
 2206 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2207 
 2208 EXPAND_AS_DEFINED      =
 2209 
 2210 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
 2211 # remove all references to function-like macros that are alone on a line, have
 2212 # an all uppercase name, and do not end with a semicolon. Such function macros
 2213 # are typically used for boiler-plate code, and will confuse the parser if not
 2214 # removed.
 2215 # The default value is: YES.
 2216 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 2217 
 2218 SKIP_FUNCTION_MACROS   = YES
 2219 
 2220 #---------------------------------------------------------------------------
 2221 # Configuration options related to external references
 2222 #---------------------------------------------------------------------------
 2223 
 2224 # The TAGFILES tag can be used to specify one or more tag files. For each tag
 2225 # file the location of the external documentation should be added. The format of
 2226 # a tag file without this location is as follows:
 2227 # TAGFILES = file1 file2 ...
 2228 # Adding location for the tag files is done as follows:
 2229 # TAGFILES = file1=loc1 "file2 = loc2" ...
 2230 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
 2231 # section "Linking to external documentation" for more information about the use
 2232 # of tag files.
 2233 # Note: Each tag file must have a unique name (where the name does NOT include
 2234 # the path). If a tag file is not located in the directory in which doxygen is
 2235 # run, you must also specify the path to the tagfile here.
 2236 
 2237 TAGFILES               =
 2238 
 2239 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
 2240 # tag file that is based on the input files it reads. See section "Linking to
 2241 # external documentation" for more information about the usage of tag files.
 2242 
 2243 GENERATE_TAGFILE       =
 2244 
 2245 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
 2246 # the class index. If set to NO, only the inherited external classes will be
 2247 # listed.
 2248 # The default value is: NO.
 2249 
 2250 ALLEXTERNALS           = NO
 2251 
 2252 # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
 2253 # in the modules index. If set to NO, only the current project's groups will be
 2254 # listed.
 2255 # The default value is: YES.
 2256 
 2257 EXTERNAL_GROUPS        = YES
 2258 
 2259 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
 2260 # the related pages index. If set to NO, only the current project's pages will
 2261 # be listed.
 2262 # The default value is: YES.
 2263 
 2264 EXTERNAL_PAGES         = YES
 2265 
 2266 #---------------------------------------------------------------------------
 2267 # Configuration options related to the dot tool
 2268 #---------------------------------------------------------------------------
 2269 
 2270 # If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
 2271 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
 2272 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
 2273 # disabled, but it is recommended to install and use dot, since it yields more
 2274 # powerful graphs.
 2275 # The default value is: YES.
 2276 
 2277 CLASS_DIAGRAMS         = YES
 2278 
 2279 # You can include diagrams made with dia in doxygen documentation. Doxygen will
 2280 # then run dia to produce the diagram and insert it in the documentation. The
 2281 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
 2282 # If left empty dia is assumed to be found in the default search path.
 2283 
 2284 DIA_PATH               =
 2285 
 2286 # If set to YES the inheritance and collaboration graphs will hide inheritance
 2287 # and usage relations if the target is undocumented or is not a class.
 2288 # The default value is: YES.
 2289 
 2290 HIDE_UNDOC_RELATIONS   = YES
 2291 
 2292 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
 2293 # available from the path. This tool is part of Graphviz (see:
 2294 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
 2295 # Bell Labs. The other options in this section have no effect if this option is
 2296 # set to NO
 2297 # The default value is: NO.
 2298 
 2299 HAVE_DOT               = YES
 2300 
 2301 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
 2302 # to run in parallel. When set to 0 doxygen will base this on the number of
 2303 # processors available in the system. You can set it explicitly to a value
 2304 # larger than 0 to get control over the balance between CPU load and processing
 2305 # speed.
 2306 # Minimum value: 0, maximum value: 32, default value: 0.
 2307 # This tag requires that the tag HAVE_DOT is set to YES.
 2308 
 2309 DOT_NUM_THREADS        = 0
 2310 
 2311 # When you want a differently looking font in the dot files that doxygen
 2312 # generates you can specify the font name using DOT_FONTNAME. You need to make
 2313 # sure dot is able to find the font, which can be done by putting it in a
 2314 # standard location or by setting the DOTFONTPATH environment variable or by
 2315 # setting DOT_FONTPATH to the directory containing the font.
 2316 # The default value is: Helvetica.
 2317 # This tag requires that the tag HAVE_DOT is set to YES.
 2318 
 2319 DOT_FONTNAME           = Helvetica
 2320 
 2321 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
 2322 # dot graphs.
 2323 # Minimum value: 4, maximum value: 24, default value: 10.
 2324 # This tag requires that the tag HAVE_DOT is set to YES.
 2325 
 2326 DOT_FONTSIZE           = 10
 2327 
 2328 # By default doxygen will tell dot to use the default font as specified with
 2329 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
 2330 # the path where dot can find it using this tag.
 2331 # This tag requires that the tag HAVE_DOT is set to YES.
 2332 
 2333 DOT_FONTPATH           =
 2334 
 2335 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
 2336 # each documented class showing the direct and indirect inheritance relations.
 2337 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
 2338 # The default value is: YES.
 2339 # This tag requires that the tag HAVE_DOT is set to YES.
 2340 
 2341 CLASS_GRAPH            = YES
 2342 
 2343 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
 2344 # graph for each documented class showing the direct and indirect implementation
 2345 # dependencies (inheritance, containment, and class references variables) of the
 2346 # class with other documented classes.
 2347 # The default value is: YES.
 2348 # This tag requires that the tag HAVE_DOT is set to YES.
 2349 
 2350 COLLABORATION_GRAPH    = YES
 2351 
 2352 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
 2353 # groups, showing the direct groups dependencies.
 2354 # The default value is: YES.
 2355 # This tag requires that the tag HAVE_DOT is set to YES.
 2356 
 2357 GROUP_GRAPHS           = YES
 2358 
 2359 # If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
 2360 # collaboration diagrams in a style similar to the OMG's Unified Modeling
 2361 # Language.
 2362 # The default value is: NO.
 2363 # This tag requires that the tag HAVE_DOT is set to YES.
 2364 
 2365 UML_LOOK               = NO
 2366 
 2367 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
 2368 # class node. If there are many fields or methods and many nodes the graph may
 2369 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
 2370 # number of items for each type to make the size more manageable. Set this to 0
 2371 # for no limit. Note that the threshold may be exceeded by 50% before the limit
 2372 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
 2373 # but if the number exceeds 15, the total amount of fields shown is limited to
 2374 # 10.
 2375 # Minimum value: 0, maximum value: 100, default value: 10.
 2376 # This tag requires that the tag UML_LOOK is set to YES.
 2377 
 2378 UML_LIMIT_NUM_FIELDS   = 10
 2379 
 2380 # If the DOT_UML_DETAILS tag is set to NO, doxygen will show attributes and
 2381 # methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
 2382 # tag is set to YES, doxygen will add type and arguments for attributes and
 2383 # methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen
 2384 # will not generate fields with class member information in the UML graphs. The
 2385 # class diagrams will look similar to the default class diagrams but using UML
 2386 # notation for the relationships.
 2387 # Possible values are: NO, YES and NONE.
 2388 # The default value is: NO.
 2389 # This tag requires that the tag UML_LOOK is set to YES.
 2390 
 2391 DOT_UML_DETAILS        = NO
 2392 
 2393 # The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters
 2394 # to display on a single line. If the actual line length exceeds this threshold
 2395 # significantly it will wrapped across multiple lines. Some heuristics are apply
 2396 # to avoid ugly line breaks.
 2397 # Minimum value: 0, maximum value: 1000, default value: 17.
 2398 # This tag requires that the tag HAVE_DOT is set to YES.
 2399 
 2400 DOT_WRAP_THRESHOLD     = 17
 2401 
 2402 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
 2403 # collaboration graphs will show the relations between templates and their
 2404 # instances.
 2405 # The default value is: NO.
 2406 # This tag requires that the tag HAVE_DOT is set to YES.
 2407 
 2408 TEMPLATE_RELATIONS     = NO
 2409 
 2410 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
 2411 # YES then doxygen will generate a graph for each documented file showing the
 2412 # direct and indirect include dependencies of the file with other documented
 2413 # files.
 2414 # The default value is: YES.
 2415 # This tag requires that the tag HAVE_DOT is set to YES.
 2416 
 2417 INCLUDE_GRAPH          = YES
 2418 
 2419 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
 2420 # set to YES then doxygen will generate a graph for each documented file showing
 2421 # the direct and indirect include dependencies of the file with other documented
 2422 # files.
 2423 # The default value is: YES.
 2424 # This tag requires that the tag HAVE_DOT is set to YES.
 2425 
 2426 INCLUDED_BY_GRAPH      = YES
 2427 
 2428 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
 2429 # dependency graph for every global function or class method.
 2430 #
 2431 # Note that enabling this option will significantly increase the time of a run.
 2432 # So in most cases it will be better to enable call graphs for selected
 2433 # functions only using the \callgraph command. Disabling a call graph can be
 2434 # accomplished by means of the command \hidecallgraph.
 2435 # The default value is: NO.
 2436 # This tag requires that the tag HAVE_DOT is set to YES.
 2437 
 2438 CALL_GRAPH             = YES
 2439 
 2440 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
 2441 # dependency graph for every global function or class method.
 2442 #
 2443 # Note that enabling this option will significantly increase the time of a run.
 2444 # So in most cases it will be better to enable caller graphs for selected
 2445 # functions only using the \callergraph command. Disabling a caller graph can be
 2446 # accomplished by means of the command \hidecallergraph.
 2447 # The default value is: NO.
 2448 # This tag requires that the tag HAVE_DOT is set to YES.
 2449 
 2450 CALLER_GRAPH           = YES
 2451 
 2452 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
 2453 # hierarchy of all classes instead of a textual one.
 2454 # The default value is: YES.
 2455 # This tag requires that the tag HAVE_DOT is set to YES.
 2456 
 2457 GRAPHICAL_HIERARCHY    = YES
 2458 
 2459 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
 2460 # dependencies a directory has on other directories in a graphical way. The
 2461 # dependency relations are determined by the #include relations between the
 2462 # files in the directories.
 2463 # The default value is: YES.
 2464 # This tag requires that the tag HAVE_DOT is set to YES.
 2465 
 2466 DIRECTORY_GRAPH        = YES
 2467 
 2468 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
 2469 # generated by dot. For an explanation of the image formats see the section
 2470 # output formats in the documentation of the dot tool (Graphviz (see:
 2471 # http://www.graphviz.org/)).
 2472 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
 2473 # to make the SVG files visible in IE 9+ (other browsers do not have this
 2474 # requirement).
 2475 # Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
 2476 # png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
 2477 # png:gdiplus:gdiplus.
 2478 # The default value is: png.
 2479 # This tag requires that the tag HAVE_DOT is set to YES.
 2480 
 2481 DOT_IMAGE_FORMAT       = svg
 2482 
 2483 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
 2484 # enable generation of interactive SVG images that allow zooming and panning.
 2485 #
 2486 # Note that this requires a modern browser other than Internet Explorer. Tested
 2487 # and working are Firefox, Chrome, Safari, and Opera.
 2488 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
 2489 # the SVG files visible. Older versions of IE do not have SVG support.
 2490 # The default value is: NO.
 2491 # This tag requires that the tag HAVE_DOT is set to YES.
 2492 
 2493 INTERACTIVE_SVG        = YES
 2494 
 2495 # The DOT_PATH tag can be used to specify the path where the dot tool can be
 2496 # found. If left blank, it is assumed the dot tool can be found in the path.
 2497 # This tag requires that the tag HAVE_DOT is set to YES.
 2498 
 2499 DOT_PATH               =
 2500 
 2501 # The DOTFILE_DIRS tag can be used to specify one or more directories that
 2502 # contain dot files that are included in the documentation (see the \dotfile
 2503 # command).
 2504 # This tag requires that the tag HAVE_DOT is set to YES.
 2505 
 2506 DOTFILE_DIRS           =
 2507 
 2508 # The MSCFILE_DIRS tag can be used to specify one or more directories that
 2509 # contain msc files that are included in the documentation (see the \mscfile
 2510 # command).
 2511 
 2512 MSCFILE_DIRS           =
 2513 
 2514 # The DIAFILE_DIRS tag can be used to specify one or more directories that
 2515 # contain dia files that are included in the documentation (see the \diafile
 2516 # command).
 2517 
 2518 DIAFILE_DIRS           =
 2519 
 2520 # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
 2521 # path where java can find the plantuml.jar file. If left blank, it is assumed
 2522 # PlantUML is not used or called during a preprocessing step. Doxygen will
 2523 # generate a warning when it encounters a \startuml command in this case and
 2524 # will not generate output for the diagram.
 2525 
 2526 PLANTUML_JAR_PATH      =
 2527 
 2528 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
 2529 # configuration file for plantuml.
 2530 
 2531 PLANTUML_CFG_FILE      =
 2532 
 2533 # When using plantuml, the specified paths are searched for files specified by
 2534 # the !include statement in a plantuml block.
 2535 
 2536 PLANTUML_INCLUDE_PATH  =
 2537 
 2538 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
 2539 # that will be shown in the graph. If the number of nodes in a graph becomes
 2540 # larger than this value, doxygen will truncate the graph, which is visualized
 2541 # by representing a node as a red box. Note that doxygen if the number of direct
 2542 # children of the root node in a graph is already larger than
 2543 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
 2544 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
 2545 # Minimum value: 0, maximum value: 10000, default value: 50.
 2546 # This tag requires that the tag HAVE_DOT is set to YES.
 2547 
 2548 DOT_GRAPH_MAX_NODES    = 50
 2549 
 2550 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
 2551 # generated by dot. A depth value of 3 means that only nodes reachable from the
 2552 # root by following a path via at most 3 edges will be shown. Nodes that lay
 2553 # further from the root node will be omitted. Note that setting this option to 1
 2554 # or 2 may greatly reduce the computation time needed for large code bases. Also
 2555 # note that the size of a graph can be further restricted by
 2556 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
 2557 # Minimum value: 0, maximum value: 1000, default value: 0.
 2558 # This tag requires that the tag HAVE_DOT is set to YES.
 2559 
 2560 MAX_DOT_GRAPH_DEPTH    = 0
 2561 
 2562 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
 2563 # background. This is disabled by default, because dot on Windows does not seem
 2564 # to support this out of the box.
 2565 #
 2566 # Warning: Depending on the platform used, enabling this option may lead to
 2567 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
 2568 # read).
 2569 # The default value is: NO.
 2570 # This tag requires that the tag HAVE_DOT is set to YES.
 2571 
 2572 DOT_TRANSPARENT        = NO
 2573 
 2574 # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
 2575 # files in one run (i.e. multiple -o and -T options on the command line). This
 2576 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
 2577 # this, this feature is disabled by default.
 2578 # The default value is: NO.
 2579 # This tag requires that the tag HAVE_DOT is set to YES.
 2580 
 2581 DOT_MULTI_TARGETS      = NO
 2582 
 2583 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
 2584 # explaining the meaning of the various boxes and arrows in the dot generated
 2585 # graphs.
 2586 # The default value is: YES.
 2587 # This tag requires that the tag HAVE_DOT is set to YES.
 2588 
 2589 GENERATE_LEGEND        = YES
 2590 
 2591 # If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate
 2592 # files that are used to generate the various graphs.
 2593 #
 2594 # Note: This setting is not only used for dot files but also for msc and
 2595 # plantuml temporary files.
 2596 # The default value is: YES.
 2597 
 2598 DOT_CLEANUP            = YES