C reference parsing library for eno notation
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2483 lines
106 KiB

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