Micro template library A library for building device drivers
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
 
 
 
 

2499 lignes
106 KiB

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