"Fossies" - the Fresh Open Source Software Archive

Member "netcdf-fortran-4.4.5/docs/Doxyfile.in" (31 Jan 2019, 101855 Bytes) of package /linux/misc/netcdf-fortran-4.4.5.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.in": 4.4.4_vs_4.4.5.

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