KORG microX utility.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1794 lines
76 KiB

  1. # Doxyfile 1.8.1.1
  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 hash (#) is considered a comment and will be ignored
  6. # The format is:
  7. # TAG = value [value, ...]
  8. # For lists items can also be appended using:
  9. # TAG += value [value, ...]
  10. # Values that contain spaces should be placed between quotes (" ")
  11. #---------------------------------------------------------------------------
  12. # Project related configuration options
  13. #---------------------------------------------------------------------------
  14. # This tag specifies the encoding used for all characters in the config file
  15. # that follow. The default is UTF-8 which is also the encoding used for all
  16. # text before the first occurrence of this tag. Doxygen uses libiconv (or the
  17. # iconv built into libc) for the transcoding. See
  18. # http://www.gnu.org/software/libiconv for the list of possible encodings.
  19. DOXYFILE_ENCODING = UTF-8
  20. # The PROJECT_NAME tag is a single word (or sequence of words) that should
  21. # identify the project. Note that if you do not use Doxywizard you need
  22. # to put quotes around the project name if it contains spaces.
  23. PROJECT_NAME = kmxtool
  24. # The PROJECT_NUMBER tag can be used to enter a project or revision number.
  25. # This could be handy for archiving the generated documentation or
  26. # if some version control system is used.
  27. PROJECT_NUMBER = 0.1.0
  28. # Using the PROJECT_BRIEF tag one can provide an optional one line description
  29. # for a project that appears at the top of each page and should give viewer
  30. # a quick idea about the purpose of the project. Keep the description short.
  31. PROJECT_BRIEF = "KORG microX tool"
  32. # With the PROJECT_LOGO tag one can specify an logo or icon that is
  33. # included in the documentation. The maximum height of the logo should not
  34. # exceed 55 pixels and the maximum width should not exceed 200 pixels.
  35. # Doxygen will copy the logo to the output directory.
  36. PROJECT_LOGO =
  37. # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
  38. # base path where the generated documentation will be put.
  39. # If a relative path is entered, it will be relative to the location
  40. # where doxygen was started. If left blank the current directory will be used.
  41. OUTPUT_DIRECTORY = doc
  42. # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
  43. # 4096 sub-directories (in 2 levels) under the output directory of each output
  44. # format and will distribute the generated files over these directories.
  45. # Enabling this option can be useful when feeding doxygen a huge amount of
  46. # source files, where putting all generated files in the same directory would
  47. # otherwise cause performance problems for the file system.
  48. CREATE_SUBDIRS = NO
  49. # The OUTPUT_LANGUAGE tag is used to specify the language in which all
  50. # documentation generated by doxygen is written. Doxygen will use this
  51. # information to generate all constant output in the proper language.
  52. # The default language is English, other supported languages are:
  53. # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
  54. # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
  55. # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
  56. # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
  57. # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
  58. # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
  59. OUTPUT_LANGUAGE = English
  60. # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
  61. # include brief member descriptions after the members that are listed in
  62. # the file and class documentation (similar to JavaDoc).
  63. # Set to NO to disable this.
  64. BRIEF_MEMBER_DESC = YES
  65. # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
  66. # the brief description of a member or function before the detailed description.
  67. # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
  68. # brief descriptions will be completely suppressed.
  69. REPEAT_BRIEF = NO
  70. # This tag implements a quasi-intelligent brief description abbreviator
  71. # that is used to form the text in various listings. Each string
  72. # in this list, if found as the leading text of the brief description, will be
  73. # stripped from the text and the result after processing the whole list, is
  74. # used as the annotated text. Otherwise, the brief description is used as-is.
  75. # If left blank, the following values are used ("$name" is automatically
  76. # replaced with the name of the entity): "The $name class" "The $name widget"
  77. # "The $name file" "is" "provides" "specifies" "contains"
  78. # "represents" "a" "an" "the"
  79. ABBREVIATE_BRIEF = "The $name class" \
  80. "The $name widget" \
  81. "The $name file" \
  82. is \
  83. provides \
  84. specifies \
  85. contains \
  86. represents \
  87. a \
  88. an \
  89. the
  90. # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
  91. # Doxygen will generate a detailed section even if there is only a brief
  92. # description.
  93. ALWAYS_DETAILED_SEC = NO
  94. # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
  95. # inherited members of a class in the documentation of that class as if those
  96. # members were ordinary class members. Constructors, destructors and assignment
  97. # operators of the base classes will not be shown.
  98. INLINE_INHERITED_MEMB = NO
  99. # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
  100. # path before files name in the file list and in the header files. If set
  101. # to NO the shortest path that makes the file name unique will be used.
  102. FULL_PATH_NAMES = YES
  103. # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
  104. # can be used to strip a user-defined part of the path. Stripping is
  105. # only done if one of the specified strings matches the left-hand part of
  106. # the path. The tag can be used to show relative paths in the file list.
  107. # If left blank the directory from which doxygen is run is used as the
  108. # path to strip.
  109. STRIP_FROM_PATH =
  110. # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
  111. # the path mentioned in the documentation of a class, which tells
  112. # the reader which header file to include in order to use a class.
  113. # If left blank only the name of the header file containing the class
  114. # definition is used. Otherwise one should specify the include paths that
  115. # are normally passed to the compiler using the -I flag.
  116. STRIP_FROM_INC_PATH =
  117. # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
  118. # (but less readable) file names. This can be useful if your file system
  119. # doesn't support long names like on DOS, Mac, or CD-ROM.
  120. SHORT_NAMES = NO
  121. # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
  122. # will interpret the first line (until the first dot) of a JavaDoc-style
  123. # comment as the brief description. If set to NO, the JavaDoc
  124. # comments will behave just like regular Qt-style comments
  125. # (thus requiring an explicit @brief command for a brief description.)
  126. JAVADOC_AUTOBRIEF = YES
  127. # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
  128. # interpret the first line (until the first dot) of a Qt-style
  129. # comment as the brief description. If set to NO, the comments
  130. # will behave just like regular Qt-style comments (thus requiring
  131. # an explicit \brief command for a brief description.)
  132. QT_AUTOBRIEF = NO
  133. # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
  134. # treat a multi-line C++ special comment block (i.e. a block of //! or ///
  135. # comments) as a brief description. This used to be the default behaviour.
  136. # The new default is to treat a multi-line C++ comment block as a detailed
  137. # description. Set this tag to YES if you prefer the old behaviour instead.
  138. MULTILINE_CPP_IS_BRIEF = NO
  139. # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
  140. # member inherits the documentation from any documented member that it
  141. # re-implements.
  142. INHERIT_DOCS = YES
  143. # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
  144. # a new page for each member. If set to NO, the documentation of a member will
  145. # be part of the file/class/namespace that contains it.
  146. SEPARATE_MEMBER_PAGES = NO
  147. # The TAB_SIZE tag can be used to set the number of spaces in a tab.
  148. # Doxygen uses this value to replace tabs by spaces in code fragments.
  149. TAB_SIZE = 8
  150. # This tag can be used to specify a number of aliases that acts
  151. # as commands in the documentation. An alias has the form "name=value".
  152. # For example adding "sideeffect=\par Side Effects:\n" will allow you to
  153. # put the command \sideeffect (or @sideeffect) in the documentation, which
  154. # will result in a user-defined paragraph with heading "Side Effects:".
  155. # You can put \n's in the value part of an alias to insert newlines.
  156. ALIASES =
  157. # This tag can be used to specify a number of word-keyword mappings (TCL only).
  158. # A mapping has the form "name=value". For example adding
  159. # "class=itcl::class" will allow you to use the command class in the
  160. # itcl::class meaning.
  161. TCL_SUBST =
  162. # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
  163. # sources only. Doxygen will then generate output that is more tailored for C.
  164. # For instance, some of the names that are used will be different. The list
  165. # of all members will be omitted, etc.
  166. OPTIMIZE_OUTPUT_FOR_C = YES
  167. # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
  168. # sources only. Doxygen will then generate output that is more tailored for
  169. # Java. For instance, namespaces will be presented as packages, qualified
  170. # scopes will look different, etc.
  171. OPTIMIZE_OUTPUT_JAVA = NO
  172. # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
  173. # sources only. Doxygen will then generate output that is more tailored for
  174. # Fortran.
  175. OPTIMIZE_FOR_FORTRAN = NO
  176. # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
  177. # sources. Doxygen will then generate output that is tailored for
  178. # VHDL.
  179. OPTIMIZE_OUTPUT_VHDL = NO
  180. # Doxygen selects the parser to use depending on the extension of the files it
  181. # parses. With this tag you can assign which parser to use for a given extension.
  182. # Doxygen has a built-in mapping, but you can override or extend it using this
  183. # tag. The format is ext=language, where ext is a file extension, and language
  184. # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
  185. # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
  186. # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
  187. # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
  188. # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
  189. EXTENSION_MAPPING =
  190. # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all
  191. # comments according to the Markdown format, which allows for more readable
  192. # documentation. See http://daringfireball.net/projects/markdown/ for details.
  193. # The output of markdown processing is further processed by doxygen, so you
  194. # can mix doxygen, HTML, and XML commands with Markdown formatting.
  195. # Disable only in case of backward compatibilities issues.
  196. MARKDOWN_SUPPORT = YES
  197. # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
  198. # to include (a tag file for) the STL sources as input, then you should
  199. # set this tag to YES in order to let doxygen match functions declarations and
  200. # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
  201. # func(std::string) {}). This also makes the inheritance and collaboration
  202. # diagrams that involve STL classes more complete and accurate.
  203. BUILTIN_STL_SUPPORT = NO
  204. # If you use Microsoft's C++/CLI language, you should set this option to YES to
  205. # enable parsing support.
  206. CPP_CLI_SUPPORT = NO
  207. # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
  208. # Doxygen will parse them like normal C++ but will assume all classes use public
  209. # instead of private inheritance when no explicit protection keyword is present.
  210. SIP_SUPPORT = NO
  211. # For Microsoft's IDL there are propget and propput attributes to indicate getter
  212. # and setter methods for a property. Setting this option to YES (the default)
  213. # will make doxygen replace the get and set methods by a property in the
  214. # documentation. This will only work if the methods are indeed getting or
  215. # setting a simple type. If this is not the case, or you want to show the
  216. # methods anyway, you should set this option to NO.
  217. IDL_PROPERTY_SUPPORT = YES
  218. # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
  219. # tag is set to YES, then doxygen will reuse the documentation of the first
  220. # member in the group (if any) for the other members of the group. By default
  221. # all members of a group must be documented explicitly.
  222. DISTRIBUTE_GROUP_DOC = NO
  223. # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
  224. # the same type (for instance a group of public functions) to be put as a
  225. # subgroup of that type (e.g. under the Public Functions section). Set it to
  226. # NO to prevent subgrouping. Alternatively, this can be done per class using
  227. # the \nosubgrouping command.
  228. SUBGROUPING = YES
  229. # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
  230. # unions are shown inside the group in which they are included (e.g. using
  231. # @ingroup) instead of on a separate page (for HTML and Man pages) or
  232. # section (for LaTeX and RTF).
  233. INLINE_GROUPED_CLASSES = NO
  234. # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
  235. # unions with only public data fields will be shown inline in the documentation
  236. # of the scope in which they are defined (i.e. file, namespace, or group
  237. # documentation), provided this scope is documented. If set to NO (the default),
  238. # structs, classes, and unions are shown on a separate page (for HTML and Man
  239. # pages) or section (for LaTeX and RTF).
  240. INLINE_SIMPLE_STRUCTS = NO
  241. # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
  242. # is documented as struct, union, or enum with the name of the typedef. So
  243. # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
  244. # with name TypeT. When disabled the typedef will appear as a member of a file,
  245. # namespace, or class. And the struct will be named TypeS. This can typically
  246. # be useful for C code in case the coding convention dictates that all compound
  247. # types are typedef'ed and only the typedef is referenced, never the tag name.
  248. TYPEDEF_HIDES_STRUCT = NO
  249. # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
  250. # determine which symbols to keep in memory and which to flush to disk.
  251. # When the cache is full, less often used symbols will be written to disk.
  252. # For small to medium size projects (<1000 input files) the default value is
  253. # probably good enough. For larger projects a too small cache size can cause
  254. # doxygen to be busy swapping symbols to and from disk most of the time
  255. # causing a significant performance penalty.
  256. # If the system has enough physical memory increasing the cache will improve the
  257. # performance by keeping more symbols in memory. Note that the value works on
  258. # a logarithmic scale so increasing the size by one will roughly double the
  259. # memory usage. The cache size is given by this formula:
  260. # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
  261. # corresponding to a cache size of 2^16 = 65536 symbols.
  262. SYMBOL_CACHE_SIZE = 0
  263. # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be
  264. # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
  265. # their name and scope. Since this can be an expensive process and often the
  266. # same symbol appear multiple times in the code, doxygen keeps a cache of
  267. # pre-resolved symbols. If the cache is too small doxygen will become slower.
  268. # If the cache is too large, memory is wasted. The cache size is given by this
  269. # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,
  270. # corresponding to a cache size of 2^16 = 65536 symbols.
  271. LOOKUP_CACHE_SIZE = 0
  272. #---------------------------------------------------------------------------
  273. # Build related configuration options
  274. #---------------------------------------------------------------------------
  275. # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
  276. # documentation are documented, even if no documentation was available.
  277. # Private class members and static file members will be hidden unless
  278. # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
  279. EXTRACT_ALL = NO
  280. # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
  281. # will be included in the documentation.
  282. EXTRACT_PRIVATE = NO
  283. # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
  284. # scope will be included in the documentation.
  285. EXTRACT_PACKAGE = NO
  286. # If the EXTRACT_STATIC tag is set to YES all static members of a file
  287. # will be included in the documentation.
  288. EXTRACT_STATIC = NO
  289. # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
  290. # defined locally in source files will be included in the documentation.
  291. # If set to NO only classes defined in header files are included.
  292. EXTRACT_LOCAL_CLASSES = YES
  293. # This flag is only useful for Objective-C code. When set to YES local
  294. # methods, which are defined in the implementation section but not in
  295. # the interface are included in the documentation.
  296. # If set to NO (the default) only methods in the interface are included.
  297. EXTRACT_LOCAL_METHODS = NO
  298. # If this flag is set to YES, the members of anonymous namespaces will be
  299. # extracted and appear in the documentation as a namespace called
  300. # 'anonymous_namespace{file}', where file will be replaced with the base
  301. # name of the file that contains the anonymous namespace. By default
  302. # anonymous namespaces are hidden.
  303. EXTRACT_ANON_NSPACES = NO
  304. # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
  305. # undocumented members of documented classes, files or namespaces.
  306. # If set to NO (the default) these members will be included in the
  307. # various overviews, but no documentation section is generated.
  308. # This option has no effect if EXTRACT_ALL is enabled.
  309. HIDE_UNDOC_MEMBERS = NO
  310. # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
  311. # undocumented classes that are normally visible in the class hierarchy.
  312. # If set to NO (the default) these classes will be included in the various
  313. # overviews. This option has no effect if EXTRACT_ALL is enabled.
  314. HIDE_UNDOC_CLASSES = NO
  315. # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
  316. # friend (class|struct|union) declarations.
  317. # If set to NO (the default) these declarations will be included in the
  318. # documentation.
  319. HIDE_FRIEND_COMPOUNDS = NO
  320. # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
  321. # documentation blocks found inside the body of a function.
  322. # If set to NO (the default) these blocks will be appended to the
  323. # function's detailed documentation block.
  324. HIDE_IN_BODY_DOCS = NO
  325. # The INTERNAL_DOCS tag determines if documentation
  326. # that is typed after a \internal command is included. If the tag is set
  327. # to NO (the default) then the documentation will be excluded.
  328. # Set it to YES to include the internal documentation.
  329. INTERNAL_DOCS = NO
  330. # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
  331. # file names in lower-case letters. If set to YES upper-case letters are also
  332. # allowed. This is useful if you have classes or files whose names only differ
  333. # in case and if your file system supports case sensitive file names. Windows
  334. # and Mac users are advised to set this option to NO.
  335. CASE_SENSE_NAMES = NO
  336. # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
  337. # will show members with their full class and namespace scopes in the
  338. # documentation. If set to YES the scope will be hidden.
  339. HIDE_SCOPE_NAMES = YES
  340. # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
  341. # will put a list of the files that are included by a file in the documentation
  342. # of that file.
  343. SHOW_INCLUDE_FILES = YES
  344. # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
  345. # will list include files with double quotes in the documentation
  346. # rather than with sharp brackets.
  347. FORCE_LOCAL_INCLUDES = NO
  348. # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
  349. # is inserted in the documentation for inline members.
  350. INLINE_INFO = YES
  351. # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
  352. # will sort the (detailed) documentation of file and class members
  353. # alphabetically by member name. If set to NO the members will appear in
  354. # declaration order.
  355. SORT_MEMBER_DOCS = YES
  356. # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
  357. # brief documentation of file, namespace and class members alphabetically
  358. # by member name. If set to NO (the default) the members will appear in
  359. # declaration order.
  360. SORT_BRIEF_DOCS = NO
  361. # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
  362. # will sort the (brief and detailed) documentation of class members so that
  363. # constructors and destructors are listed first. If set to NO (the default)
  364. # the constructors will appear in the respective orders defined by
  365. # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
  366. # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
  367. # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
  368. SORT_MEMBERS_CTORS_1ST = NO
  369. # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
  370. # hierarchy of group names into alphabetical order. If set to NO (the default)
  371. # the group names will appear in their defined order.
  372. SORT_GROUP_NAMES = NO
  373. # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
  374. # sorted by fully-qualified names, including namespaces. If set to
  375. # NO (the default), the class list will be sorted only by class name,
  376. # not including the namespace part.
  377. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
  378. # Note: This option applies only to the class list, not to the
  379. # alphabetical list.
  380. SORT_BY_SCOPE_NAME = NO
  381. # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
  382. # do proper type resolution of all parameters of a function it will reject a
  383. # match between the prototype and the implementation of a member function even
  384. # if there is only one candidate or it is obvious which candidate to choose
  385. # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
  386. # will still accept a match between prototype and implementation in such cases.
  387. STRICT_PROTO_MATCHING = NO
  388. # The GENERATE_TODOLIST tag can be used to enable (YES) or
  389. # disable (NO) the todo list. This list is created by putting \todo
  390. # commands in the documentation.
  391. GENERATE_TODOLIST = YES
  392. # The GENERATE_TESTLIST tag can be used to enable (YES) or
  393. # disable (NO) the test list. This list is created by putting \test
  394. # commands in the documentation.
  395. GENERATE_TESTLIST = YES
  396. # The GENERATE_BUGLIST tag can be used to enable (YES) or
  397. # disable (NO) the bug list. This list is created by putting \bug
  398. # commands in the documentation.
  399. GENERATE_BUGLIST = YES
  400. # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
  401. # disable (NO) the deprecated list. This list is created by putting
  402. # \deprecated commands in the documentation.
  403. GENERATE_DEPRECATEDLIST= YES
  404. # The ENABLED_SECTIONS tag can be used to enable conditional
  405. # documentation sections, marked by \if sectionname ... \endif.
  406. ENABLED_SECTIONS =
  407. # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
  408. # the initial value of a variable or macro consists of for it to appear in
  409. # the documentation. If the initializer consists of more lines than specified
  410. # here it will be hidden. Use a value of 0 to hide initializers completely.
  411. # The appearance of the initializer of individual variables and macros in the
  412. # documentation can be controlled using \showinitializer or \hideinitializer
  413. # command in the documentation regardless of this setting.
  414. MAX_INITIALIZER_LINES = 30
  415. # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
  416. # at the bottom of the documentation of classes and structs. If set to YES the
  417. # list will mention the files that were used to generate the documentation.
  418. SHOW_USED_FILES = YES
  419. # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
  420. # This will remove the Files entry from the Quick Index and from the
  421. # Folder Tree View (if specified). The default is YES.
  422. SHOW_FILES = YES
  423. # Set the SHOW_NAMESPACES tag to NO to disable the generation of the
  424. # Namespaces page. This will remove the Namespaces entry from the Quick Index
  425. # and from the Folder Tree View (if specified). The default is YES.
  426. SHOW_NAMESPACES = YES
  427. # The FILE_VERSION_FILTER tag can be used to specify a program or script that
  428. # doxygen should invoke to get the current version for each file (typically from
  429. # the version control system). Doxygen will invoke the program by executing (via
  430. # popen()) the command <command> <input-file>, where <command> is the value of
  431. # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
  432. # provided by doxygen. Whatever the program writes to standard output
  433. # is used as the file version. See the manual for examples.
  434. FILE_VERSION_FILTER =
  435. # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
  436. # by doxygen. The layout file controls the global structure of the generated
  437. # output files in an output format independent way. To create the layout file
  438. # that represents doxygen's defaults, run doxygen with the -l option.
  439. # You can optionally specify a file name after the option, if omitted
  440. # DoxygenLayout.xml will be used as the name of the layout file.
  441. LAYOUT_FILE =
  442. # The CITE_BIB_FILES tag can be used to specify one or more bib files
  443. # containing the references data. This must be a list of .bib files. The
  444. # .bib extension is automatically appended if omitted. Using this command
  445. # requires the bibtex tool to be installed. See also
  446. # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
  447. # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
  448. # feature you need bibtex and perl available in the search path.
  449. CITE_BIB_FILES =
  450. #---------------------------------------------------------------------------
  451. # configuration options related to warning and progress messages
  452. #---------------------------------------------------------------------------
  453. # The QUIET tag can be used to turn on/off the messages that are generated
  454. # by doxygen. Possible values are YES and NO. If left blank NO is used.
  455. QUIET = NO
  456. # The WARNINGS tag can be used to turn on/off the warning messages that are
  457. # generated by doxygen. Possible values are YES and NO. If left blank
  458. # NO is used.
  459. WARNINGS = YES
  460. # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
  461. # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
  462. # automatically be disabled.
  463. WARN_IF_UNDOCUMENTED = YES
  464. # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
  465. # potential errors in the documentation, such as not documenting some
  466. # parameters in a documented function, or documenting parameters that
  467. # don't exist or using markup commands wrongly.
  468. WARN_IF_DOC_ERROR = YES
  469. # The WARN_NO_PARAMDOC option can be enabled to get warnings for
  470. # functions that are documented, but have no documentation for their parameters
  471. # or return value. If set to NO (the default) doxygen will only warn about
  472. # wrong or incomplete parameter documentation, but not about the absence of
  473. # documentation.
  474. WARN_NO_PARAMDOC = NO
  475. # The WARN_FORMAT tag determines the format of the warning messages that
  476. # doxygen can produce. The string should contain the $file, $line, and $text
  477. # tags, which will be replaced by the file and line number from which the
  478. # warning originated and the warning text. Optionally the format may contain
  479. # $version, which will be replaced by the version of the file (if it could
  480. # be obtained via FILE_VERSION_FILTER)
  481. WARN_FORMAT = "$file:$line: $text"
  482. # The WARN_LOGFILE tag can be used to specify a file to which warning
  483. # and error messages should be written. If left blank the output is written
  484. # to stderr.
  485. WARN_LOGFILE =
  486. #---------------------------------------------------------------------------
  487. # configuration options related to the input files
  488. #---------------------------------------------------------------------------
  489. # The INPUT tag can be used to specify the files and/or directories that contain
  490. # documented source files. You may enter file names like "myfile.cpp" or
  491. # directories like "/usr/src/myproject". Separate the files or directories
  492. # with spaces.
  493. INPUT = src
  494. # This tag can be used to specify the character encoding of the source files
  495. # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
  496. # also the default input encoding. Doxygen uses libiconv (or the iconv built
  497. # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
  498. # the list of possible encodings.
  499. INPUT_ENCODING = UTF-8
  500. # If the value of the INPUT tag contains directories, you can use the
  501. # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  502. # and *.h) to filter out the source-files in the directories. If left
  503. # blank the following patterns are tested:
  504. # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
  505. # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
  506. # *.f90 *.f *.for *.vhd *.vhdl
  507. FILE_PATTERNS = *.c \
  508. *.h
  509. # The RECURSIVE tag can be used to turn specify whether or not subdirectories
  510. # should be searched for input files as well. Possible values are YES and NO.
  511. # If left blank NO is used.
  512. RECURSIVE = NO
  513. # The EXCLUDE tag can be used to specify files and/or directories that should be
  514. # excluded from the INPUT source files. This way you can easily exclude a
  515. # subdirectory from a directory tree whose root is specified with the INPUT tag.
  516. # Note that relative paths are relative to the directory from which doxygen is
  517. # run.
  518. EXCLUDE =
  519. # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
  520. # directories that are symbolic links (a Unix file system feature) are excluded
  521. # from the input.
  522. EXCLUDE_SYMLINKS = NO
  523. # If the value of the INPUT tag contains directories, you can use the
  524. # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
  525. # certain files from those directories. Note that the wildcards are matched
  526. # against the file with absolute path, so to exclude all test directories
  527. # for example use the pattern */test/*
  528. EXCLUDE_PATTERNS =
  529. # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
  530. # (namespaces, classes, functions, etc.) that should be excluded from the
  531. # output. The symbol name can be a fully qualified name, a word, or if the
  532. # wildcard * is used, a substring. Examples: ANamespace, AClass,
  533. # AClass::ANamespace, ANamespace::*Test
  534. EXCLUDE_SYMBOLS =
  535. # The EXAMPLE_PATH tag can be used to specify one or more files or
  536. # directories that contain example code fragments that are included (see
  537. # the \include command).
  538. EXAMPLE_PATH =
  539. # If the value of the EXAMPLE_PATH tag contains directories, you can use the
  540. # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  541. # and *.h) to filter out the source-files in the directories. If left
  542. # blank all files are included.
  543. EXAMPLE_PATTERNS = *
  544. # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
  545. # searched for input files to be used with the \include or \dontinclude
  546. # commands irrespective of the value of the RECURSIVE tag.
  547. # Possible values are YES and NO. If left blank NO is used.
  548. EXAMPLE_RECURSIVE = NO
  549. # The IMAGE_PATH tag can be used to specify one or more files or
  550. # directories that contain image that are included in the documentation (see
  551. # the \image command).
  552. IMAGE_PATH =
  553. # The INPUT_FILTER tag can be used to specify a program that doxygen should
  554. # invoke to filter for each input file. Doxygen will invoke the filter program
  555. # by executing (via popen()) the command <filter> <input-file>, where <filter>
  556. # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
  557. # input file. Doxygen will then use the output that the filter program writes
  558. # to standard output. If FILTER_PATTERNS is specified, this tag will be
  559. # ignored.
  560. INPUT_FILTER =
  561. # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
  562. # basis. Doxygen will compare the file name with each pattern and apply the
  563. # filter if there is a match. The filters are a list of the form:
  564. # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
  565. # info on how filters are used. If FILTER_PATTERNS is empty or if
  566. # non of the patterns match the file name, INPUT_FILTER is applied.
  567. FILTER_PATTERNS =
  568. # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
  569. # INPUT_FILTER) will be used to filter the input files when producing source
  570. # files to browse (i.e. when SOURCE_BROWSER is set to YES).
  571. FILTER_SOURCE_FILES = NO
  572. # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
  573. # pattern. A pattern will override the setting for FILTER_PATTERN (if any)
  574. # and it is also possible to disable source filtering for a specific pattern
  575. # using *.ext= (so without naming a filter). This option only has effect when
  576. # FILTER_SOURCE_FILES is enabled.
  577. FILTER_SOURCE_PATTERNS =
  578. #---------------------------------------------------------------------------
  579. # configuration options related to source browsing
  580. #---------------------------------------------------------------------------
  581. # If the SOURCE_BROWSER tag is set to YES then a list of source files will
  582. # be generated. Documented entities will be cross-referenced with these sources.
  583. # Note: To get rid of all source code in the generated output, make sure also
  584. # VERBATIM_HEADERS is set to NO.
  585. SOURCE_BROWSER = NO
  586. # Setting the INLINE_SOURCES tag to YES will include the body
  587. # of functions and classes directly in the documentation.
  588. INLINE_SOURCES = NO
  589. # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
  590. # doxygen to hide any special comment blocks from generated source code
  591. # fragments. Normal C, C++ and Fortran comments will always remain visible.
  592. STRIP_CODE_COMMENTS = YES
  593. # If the REFERENCED_BY_RELATION tag is set to YES
  594. # then for each documented function all documented
  595. # functions referencing it will be listed.
  596. REFERENCED_BY_RELATION = NO
  597. # If the REFERENCES_RELATION tag is set to YES
  598. # then for each documented function all documented entities
  599. # called/used by that function will be listed.
  600. REFERENCES_RELATION = NO
  601. # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
  602. # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
  603. # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
  604. # link to the source code. Otherwise they will link to the documentation.
  605. REFERENCES_LINK_SOURCE = YES
  606. # If the USE_HTAGS tag is set to YES then the references to source code
  607. # will point to the HTML generated by the htags(1) tool instead of doxygen
  608. # built-in source browser. The htags tool is part of GNU's global source
  609. # tagging system (see http://www.gnu.org/software/global/global.html). You
  610. # will need version 4.8.6 or higher.
  611. USE_HTAGS = NO
  612. # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
  613. # will generate a verbatim copy of the header file for each class for
  614. # which an include is specified. Set to NO to disable this.
  615. VERBATIM_HEADERS = YES
  616. #---------------------------------------------------------------------------
  617. # configuration options related to the alphabetical class index
  618. #---------------------------------------------------------------------------
  619. # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
  620. # of all compounds will be generated. Enable this if the project
  621. # contains a lot of classes, structs, unions or interfaces.
  622. ALPHABETICAL_INDEX = YES
  623. # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
  624. # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
  625. # in which this list will be split (can be a number in the range [1..20])
  626. COLS_IN_ALPHA_INDEX = 5
  627. # In case all classes in a project start with a common prefix, all
  628. # classes will be put under the same header in the alphabetical index.
  629. # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
  630. # should be ignored while generating the index headers.
  631. IGNORE_PREFIX =
  632. #---------------------------------------------------------------------------
  633. # configuration options related to the HTML output
  634. #---------------------------------------------------------------------------
  635. # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
  636. # generate HTML output.
  637. GENERATE_HTML = YES
  638. # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
  639. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  640. # put in front of it. If left blank `html' will be used as the default path.
  641. HTML_OUTPUT = html
  642. # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
  643. # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
  644. # doxygen will generate files with .html extension.
  645. HTML_FILE_EXTENSION = .html
  646. # The HTML_HEADER tag can be used to specify a personal HTML header for
  647. # each generated HTML page. If it is left blank doxygen will generate a
  648. # standard header. Note that when using a custom header you are responsible
  649. # for the proper inclusion of any scripts and style sheets that doxygen
  650. # needs, which is dependent on the configuration options used.
  651. # It is advised to generate a default header using "doxygen -w html
  652. # header.html footer.html stylesheet.css YourConfigFile" and then modify
  653. # that header. Note that the header is subject to change so you typically
  654. # have to redo this when upgrading to a newer version of doxygen or when
  655. # changing the value of configuration settings such as GENERATE_TREEVIEW!
  656. HTML_HEADER =
  657. # The HTML_FOOTER tag can be used to specify a personal HTML footer for
  658. # each generated HTML page. If it is left blank doxygen will generate a
  659. # standard footer.
  660. HTML_FOOTER =
  661. # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
  662. # style sheet that is used by each HTML page. It can be used to
  663. # fine-tune the look of the HTML output. If the tag is left blank doxygen
  664. # will generate a default style sheet. Note that doxygen will try to copy
  665. # the style sheet file to the HTML output directory, so don't put your own
  666. # style sheet in the HTML output directory as well, or it will be erased!
  667. HTML_STYLESHEET =
  668. # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
  669. # other source files which should be copied to the HTML output directory. Note
  670. # that these files will be copied to the base HTML output directory. Use the
  671. # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
  672. # files. In the HTML_STYLESHEET file, use the file name only. Also note that
  673. # the files will be copied as-is; there are no commands or markers available.
  674. HTML_EXTRA_FILES =
  675. # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
  676. # Doxygen will adjust the colors in the style sheet and background images
  677. # according to this color. Hue is specified as an angle on a colorwheel,
  678. # see http://en.wikipedia.org/wiki/Hue for more information.
  679. # For instance the value 0 represents red, 60 is yellow, 120 is green,
  680. # 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
  681. # The allowed range is 0 to 359.
  682. HTML_COLORSTYLE_HUE = 220
  683. # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
  684. # the colors in the HTML output. For a value of 0 the output will use
  685. # grayscales only. A value of 255 will produce the most vivid colors.
  686. HTML_COLORSTYLE_SAT = 100
  687. # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
  688. # the luminance component of the colors in the HTML output. Values below
  689. # 100 gradually make the output lighter, whereas values above 100 make
  690. # the output darker. The value divided by 100 is the actual gamma applied,
  691. # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
  692. # and 100 does not change the gamma.
  693. HTML_COLORSTYLE_GAMMA = 80
  694. # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
  695. # page will contain the date and time when the page was generated. Setting
  696. # this to NO can help when comparing the output of multiple runs.
  697. HTML_TIMESTAMP = YES
  698. # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
  699. # documentation will contain sections that can be hidden and shown after the
  700. # page has loaded.
  701. HTML_DYNAMIC_SECTIONS = NO
  702. # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of
  703. # entries shown in the various tree structured indices initially; the user
  704. # can expand and collapse entries dynamically later on. Doxygen will expand
  705. # the tree to such a level that at most the specified number of entries are
  706. # visible (unless a fully collapsed tree already exceeds this amount).
  707. # So setting the number of entries 1 will produce a full collapsed tree by
  708. # default. 0 is a special value representing an infinite number of entries
  709. # and will result in a full expanded tree by default.
  710. HTML_INDEX_NUM_ENTRIES = 100
  711. # If the GENERATE_DOCSET tag is set to YES, additional index files
  712. # will be generated that can be used as input for Apple's Xcode 3
  713. # integrated development environment, introduced with OSX 10.5 (Leopard).
  714. # To create a documentation set, doxygen will generate a Makefile in the
  715. # HTML output directory. Running make will produce the docset in that
  716. # directory and running "make install" will install the docset in
  717. # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
  718. # it at startup.
  719. # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
  720. # for more information.
  721. GENERATE_DOCSET = NO
  722. # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
  723. # feed. A documentation feed provides an umbrella under which multiple
  724. # documentation sets from a single provider (such as a company or product suite)
  725. # can be grouped.
  726. DOCSET_FEEDNAME = "Doxygen generated docs"
  727. # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
  728. # should uniquely identify the documentation set bundle. This should be a
  729. # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
  730. # will append .docset to the name.
  731. DOCSET_BUNDLE_ID = org.doxygen.Project
  732. # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
  733. # the documentation publisher. This should be a reverse domain-name style
  734. # string, e.g. com.mycompany.MyDocSet.documentation.
  735. DOCSET_PUBLISHER_ID = org.doxygen.Publisher
  736. # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
  737. DOCSET_PUBLISHER_NAME = Publisher
  738. # If the GENERATE_HTMLHELP tag is set to YES, additional index files
  739. # will be generated that can be used as input for tools like the
  740. # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
  741. # of the generated HTML documentation.
  742. GENERATE_HTMLHELP = NO
  743. # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
  744. # be used to specify the file name of the resulting .chm file. You
  745. # can add a path in front of the file if the result should not be
  746. # written to the html output directory.
  747. CHM_FILE =
  748. # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
  749. # be used to specify the location (absolute path including file name) of
  750. # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
  751. # the HTML help compiler on the generated index.hhp.
  752. HHC_LOCATION =
  753. # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
  754. # controls if a separate .chi index file is generated (YES) or that
  755. # it should be included in the master .chm file (NO).
  756. GENERATE_CHI = NO
  757. # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
  758. # is used to encode HtmlHelp index (hhk), content (hhc) and project file
  759. # content.
  760. CHM_INDEX_ENCODING =
  761. # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
  762. # controls whether a binary table of contents is generated (YES) or a
  763. # normal table of contents (NO) in the .chm file.
  764. BINARY_TOC = NO
  765. # The TOC_EXPAND flag can be set to YES to add extra items for group members
  766. # to the contents of the HTML help documentation and to the tree view.
  767. TOC_EXPAND = NO
  768. # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
  769. # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
  770. # that can be used as input for Qt's qhelpgenerator to generate a
  771. # Qt Compressed Help (.qch) of the generated HTML documentation.
  772. GENERATE_QHP = NO
  773. # If the QHG_LOCATION tag is specified, the QCH_FILE tag can
  774. # be used to specify the file name of the resulting .qch file.
  775. # The path specified is relative to the HTML output folder.
  776. QCH_FILE =
  777. # The QHP_NAMESPACE tag specifies the namespace to use when generating
  778. # Qt Help Project output. For more information please see
  779. # http://doc.trolltech.com/qthelpproject.html#namespace
  780. QHP_NAMESPACE = org.doxygen.Project
  781. # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
  782. # Qt Help Project output. For more information please see
  783. # http://doc.trolltech.com/qthelpproject.html#virtual-folders
  784. QHP_VIRTUAL_FOLDER = doc
  785. # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
  786. # add. For more information please see
  787. # http://doc.trolltech.com/qthelpproject.html#custom-filters
  788. QHP_CUST_FILTER_NAME =
  789. # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
  790. # custom filter to add. For more information please see
  791. # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
  792. # Qt Help Project / Custom Filters</a>.
  793. QHP_CUST_FILTER_ATTRS =
  794. # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
  795. # project's
  796. # filter section matches.
  797. # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
  798. # Qt Help Project / Filter Attributes</a>.
  799. QHP_SECT_FILTER_ATTRS =
  800. # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
  801. # be used to specify the location of Qt's qhelpgenerator.
  802. # If non-empty doxygen will try to run qhelpgenerator on the generated
  803. # .qhp file.
  804. QHG_LOCATION =
  805. # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
  806. # will be generated, which together with the HTML files, form an Eclipse help
  807. # plugin. To install this plugin and make it available under the help contents
  808. # menu in Eclipse, the contents of the directory containing the HTML and XML
  809. # files needs to be copied into the plugins directory of eclipse. The name of
  810. # the directory within the plugins directory should be the same as
  811. # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
  812. # the help appears.
  813. GENERATE_ECLIPSEHELP = NO
  814. # A unique identifier for the eclipse help plugin. When installing the plugin
  815. # the directory name containing the HTML and XML files should also have
  816. # this name.
  817. ECLIPSE_DOC_ID = org.doxygen.Project
  818. # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)
  819. # at top of each HTML page. The value NO (the default) enables the index and
  820. # the value YES disables it. Since the tabs have the same information as the
  821. # navigation tree you can set this option to NO if you already set
  822. # GENERATE_TREEVIEW to YES.
  823. DISABLE_INDEX = NO
  824. # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
  825. # structure should be generated to display hierarchical information.
  826. # If the tag value is set to YES, a side panel will be generated
  827. # containing a tree-like index structure (just like the one that
  828. # is generated for HTML Help). For this to work a browser that supports
  829. # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
  830. # Windows users are probably better off using the HTML help feature.
  831. # Since the tree basically has the same information as the tab index you
  832. # could consider to set DISABLE_INDEX to NO when enabling this option.
  833. GENERATE_TREEVIEW = NO
  834. # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
  835. # (range [0,1..20]) that doxygen will group on one line in the generated HTML
  836. # documentation. Note that a value of 0 will completely suppress the enum
  837. # values from appearing in the overview section.
  838. ENUM_VALUES_PER_LINE = 4
  839. # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
  840. # used to set the initial width (in pixels) of the frame in which the tree
  841. # is shown.
  842. TREEVIEW_WIDTH = 250
  843. # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
  844. # links to external symbols imported via tag files in a separate window.
  845. EXT_LINKS_IN_WINDOW = NO
  846. # Use this tag to change the font size of Latex formulas included
  847. # as images in the HTML documentation. The default is 10. Note that
  848. # when you change the font size after a successful doxygen run you need
  849. # to manually remove any form_*.png images from the HTML output directory
  850. # to force them to be regenerated.
  851. FORMULA_FONTSIZE = 10
  852. # Use the FORMULA_TRANPARENT tag to determine whether or not the images
  853. # generated for formulas are transparent PNGs. Transparent PNGs are
  854. # not supported properly for IE 6.0, but are supported on all modern browsers.
  855. # Note that when changing this option you need to delete any form_*.png files
  856. # in the HTML output before the changes have effect.
  857. FORMULA_TRANSPARENT = YES
  858. # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
  859. # (see http://www.mathjax.org) which uses client side Javascript for the
  860. # rendering instead of using prerendered bitmaps. Use this if you do not
  861. # have LaTeX installed or if you want to formulas look prettier in the HTML
  862. # output. When enabled you may also need to install MathJax separately and
  863. # configure the path to it using the MATHJAX_RELPATH option.
  864. USE_MATHJAX = NO
  865. # When MathJax is enabled you need to specify the location relative to the
  866. # HTML output directory using the MATHJAX_RELPATH option. The destination
  867. # directory should contain the MathJax.js script. For instance, if the mathjax
  868. # directory is located at the same level as the HTML output directory, then
  869. # MATHJAX_RELPATH should be ../mathjax. The default value points to
  870. # the MathJax Content Delivery Network so you can quickly see the result without
  871. # installing MathJax. However, it is strongly recommended to install a local
  872. # copy of MathJax from http://www.mathjax.org before deployment.
  873. MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
  874. # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
  875. # names that should be enabled during MathJax rendering.
  876. MATHJAX_EXTENSIONS =
  877. # When the SEARCHENGINE tag is enabled doxygen will generate a search box
  878. # for the HTML output. The underlying search engine uses javascript
  879. # and DHTML and should work on any modern browser. Note that when using
  880. # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
  881. # (GENERATE_DOCSET) there is already a search function so this one should
  882. # typically be disabled. For large projects the javascript based search engine
  883. # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
  884. SEARCHENGINE = YES
  885. # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
  886. # implemented using a PHP enabled web server instead of at the web client
  887. # using Javascript. Doxygen will generate the search PHP script and index
  888. # file to put on the web server. The advantage of the server
  889. # based approach is that it scales better to large projects and allows
  890. # full text search. The disadvantages are that it is more difficult to setup
  891. # and does not have live searching capabilities.
  892. SERVER_BASED_SEARCH = NO
  893. #---------------------------------------------------------------------------
  894. # configuration options related to the LaTeX output
  895. #---------------------------------------------------------------------------
  896. # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
  897. # generate Latex output.
  898. GENERATE_LATEX = YES
  899. # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
  900. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  901. # put in front of it. If left blank `latex' will be used as the default path.
  902. LATEX_OUTPUT = latex
  903. # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
  904. # invoked. If left blank `latex' will be used as the default command name.
  905. # Note that when enabling USE_PDFLATEX this option is only used for
  906. # generating bitmaps for formulas in the HTML output, but not in the
  907. # Makefile that is written to the output directory.
  908. LATEX_CMD_NAME = latex
  909. # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
  910. # generate index for LaTeX. If left blank `makeindex' will be used as the
  911. # default command name.
  912. MAKEINDEX_CMD_NAME = makeindex
  913. # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
  914. # LaTeX documents. This may be useful for small projects and may help to
  915. # save some trees in general.
  916. COMPACT_LATEX = NO
  917. # The PAPER_TYPE tag can be used to set the paper type that is used
  918. # by the printer. Possible values are: a4, letter, legal and
  919. # executive. If left blank a4wide will be used.
  920. PAPER_TYPE = a4
  921. # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
  922. # packages that should be included in the LaTeX output.
  923. EXTRA_PACKAGES =
  924. # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
  925. # the generated latex document. The header should contain everything until
  926. # the first chapter. If it is left blank doxygen will generate a
  927. # standard header. Notice: only use this tag if you know what you are doing!
  928. LATEX_HEADER =
  929. # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
  930. # the generated latex document. The footer should contain everything after
  931. # the last chapter. If it is left blank doxygen will generate a
  932. # standard footer. Notice: only use this tag if you know what you are doing!
  933. LATEX_FOOTER =
  934. # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
  935. # is prepared for conversion to pdf (using ps2pdf). The pdf file will
  936. # contain links (just like the HTML output) instead of page references
  937. # This makes the output suitable for online browsing using a pdf viewer.
  938. PDF_HYPERLINKS = YES
  939. # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
  940. # plain latex in the generated Makefile. Set this option to YES to get a
  941. # higher quality PDF documentation.
  942. USE_PDFLATEX = YES
  943. # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
  944. # command to the generated LaTeX files. This will instruct LaTeX to keep
  945. # running if errors occur, instead of asking the user for help.
  946. # This option is also used when generating formulas in HTML.
  947. LATEX_BATCHMODE = NO
  948. # If LATEX_HIDE_INDICES is set to YES then doxygen will not
  949. # include the index chapters (such as File Index, Compound Index, etc.)
  950. # in the output.
  951. LATEX_HIDE_INDICES = NO
  952. # If LATEX_SOURCE_CODE is set to YES then doxygen will include
  953. # source code with syntax highlighting in the LaTeX output.
  954. # Note that which sources are shown also depends on other settings
  955. # such as SOURCE_BROWSER.
  956. LATEX_SOURCE_CODE = NO
  957. # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
  958. # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
  959. # http://en.wikipedia.org/wiki/BibTeX for more info.
  960. LATEX_BIB_STYLE = plain
  961. #---------------------------------------------------------------------------
  962. # configuration options related to the RTF output
  963. #---------------------------------------------------------------------------
  964. # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
  965. # The RTF output is optimized for Word 97 and may not look very pretty with
  966. # other RTF readers or editors.
  967. GENERATE_RTF = NO
  968. # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
  969. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  970. # put in front of it. If left blank `rtf' will be used as the default path.
  971. RTF_OUTPUT = rtf
  972. # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
  973. # RTF documents. This may be useful for small projects and may help to
  974. # save some trees in general.
  975. COMPACT_RTF = NO
  976. # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
  977. # will contain hyperlink fields. The RTF file will
  978. # contain links (just like the HTML output) instead of page references.
  979. # This makes the output suitable for online browsing using WORD or other
  980. # programs which support those fields.
  981. # Note: wordpad (write) and others do not support links.
  982. RTF_HYPERLINKS = NO
  983. # Load style sheet definitions from file. Syntax is similar to doxygen's
  984. # config file, i.e. a series of assignments. You only have to provide
  985. # replacements, missing definitions are set to their default value.
  986. RTF_STYLESHEET_FILE =
  987. # Set optional variables used in the generation of an rtf document.
  988. # Syntax is similar to doxygen's config file.
  989. RTF_EXTENSIONS_FILE =
  990. #---------------------------------------------------------------------------
  991. # configuration options related to the man page output
  992. #---------------------------------------------------------------------------
  993. # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
  994. # generate man pages
  995. GENERATE_MAN = NO
  996. # The MAN_OUTPUT tag is used to specify where the man pages will be put.
  997. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  998. # put in front of it. If left blank `man' will be used as the default path.
  999. MAN_OUTPUT = man
  1000. # The MAN_EXTENSION tag determines the extension that is added to
  1001. # the generated man pages (default is the subroutine's section .3)
  1002. MAN_EXTENSION = .3
  1003. # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
  1004. # then it will generate one additional man file for each entity
  1005. # documented in the real man page(s). These additional files
  1006. # only source the real man page, but without them the man command
  1007. # would be unable to find the correct page. The default is NO.
  1008. MAN_LINKS = NO
  1009. #---------------------------------------------------------------------------
  1010. # configuration options related to the XML output
  1011. #---------------------------------------------------------------------------
  1012. # If the GENERATE_XML tag is set to YES Doxygen will
  1013. # generate an XML file that captures the structure of
  1014. # the code including all documentation.
  1015. GENERATE_XML = NO
  1016. # The XML_OUTPUT tag is used to specify where the XML pages will be put.
  1017. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  1018. # put in front of it. If left blank `xml' will be used as the default path.
  1019. XML_OUTPUT = xml
  1020. # The XML_SCHEMA tag can be used to specify an XML schema,
  1021. # which can be used by a validating XML parser to check the
  1022. # syntax of the XML files.
  1023. XML_SCHEMA =
  1024. # The XML_DTD tag can be used to specify an XML DTD,
  1025. # which can be used by a validating XML parser to check the
  1026. # syntax of the XML files.
  1027. XML_DTD =
  1028. # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
  1029. # dump the program listings (including syntax highlighting
  1030. # and cross-referencing information) to the XML output. Note that
  1031. # enabling this will significantly increase the size of the XML output.
  1032. XML_PROGRAMLISTING = YES
  1033. #---------------------------------------------------------------------------
  1034. # configuration options for the AutoGen Definitions output
  1035. #---------------------------------------------------------------------------
  1036. # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
  1037. # generate an AutoGen Definitions (see autogen.sf.net) file
  1038. # that captures the structure of the code including all
  1039. # documentation. Note that this feature is still experimental
  1040. # and incomplete at the moment.
  1041. GENERATE_AUTOGEN_DEF = NO
  1042. #---------------------------------------------------------------------------
  1043. # configuration options related to the Perl module output
  1044. #---------------------------------------------------------------------------
  1045. # If the GENERATE_PERLMOD tag is set to YES Doxygen will
  1046. # generate a Perl module file that captures the structure of
  1047. # the code including all documentation. Note that this
  1048. # feature is still experimental and incomplete at the
  1049. # moment.
  1050. GENERATE_PERLMOD = NO
  1051. # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
  1052. # the necessary Makefile rules, Perl scripts and LaTeX code to be able
  1053. # to generate PDF and DVI output from the Perl module output.
  1054. PERLMOD_LATEX = NO
  1055. # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
  1056. # nicely formatted so it can be parsed by a human reader. This is useful
  1057. # if you want to understand what is going on. On the other hand, if this
  1058. # tag is set to NO the size of the Perl module output will be much smaller
  1059. # and Perl will parse it just the same.
  1060. PERLMOD_PRETTY = YES
  1061. # The names of the make variables in the generated doxyrules.make file
  1062. # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
  1063. # This is useful so different doxyrules.make files included by the same
  1064. # Makefile don't overwrite each other's variables.
  1065. PERLMOD_MAKEVAR_PREFIX =
  1066. #---------------------------------------------------------------------------
  1067. # Configuration options related to the preprocessor
  1068. #---------------------------------------------------------------------------
  1069. # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
  1070. # evaluate all C-preprocessor directives found in the sources and include
  1071. # files.
  1072. ENABLE_PREPROCESSING = YES
  1073. # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
  1074. # names in the source code. If set to NO (the default) only conditional
  1075. # compilation will be performed. Macro expansion can be done in a controlled
  1076. # way by setting EXPAND_ONLY_PREDEF to YES.
  1077. MACRO_EXPANSION = NO
  1078. # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
  1079. # then the macro expansion is limited to the macros specified with the
  1080. # PREDEFINED and EXPAND_AS_DEFINED tags.
  1081. EXPAND_ONLY_PREDEF = NO
  1082. # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
  1083. # pointed to by INCLUDE_PATH will be searched when a #include is found.
  1084. SEARCH_INCLUDES = YES
  1085. # The INCLUDE_PATH tag can be used to specify one or more directories that
  1086. # contain include files that are not input files but should be processed by
  1087. # the preprocessor.
  1088. INCLUDE_PATH =
  1089. # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
  1090. # patterns (like *.h and *.hpp) to filter out the header-files in the
  1091. # directories. If left blank, the patterns specified with FILE_PATTERNS will
  1092. # be used.
  1093. INCLUDE_FILE_PATTERNS =
  1094. # The PREDEFINED tag can be used to specify one or more macro names that
  1095. # are defined before the preprocessor is started (similar to the -D option of
  1096. # gcc). The argument of the tag is a list of macros of the form: name
  1097. # or name=definition (no spaces). If the definition and the = are
  1098. # omitted =1 is assumed. To prevent a macro definition from being
  1099. # undefined via #undef or recursively expanded use the := operator
  1100. # instead of the = operator.
  1101. PREDEFINED =
  1102. # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
  1103. # this tag can be used to specify a list of macro names that should be expanded.
  1104. # The macro definition that is found in the sources will be used.
  1105. # Use the PREDEFINED tag if you want to use a different macro definition that
  1106. # overrules the definition found in the source code.
  1107. EXPAND_AS_DEFINED =
  1108. # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
  1109. # doxygen's preprocessor will remove all references to function-like macros
  1110. # that are alone on a line, have an all uppercase name, and do not end with a
  1111. # semicolon, because these will confuse the parser if not removed.
  1112. SKIP_FUNCTION_MACROS = YES
  1113. #---------------------------------------------------------------------------
  1114. # Configuration::additions related to external references
  1115. #---------------------------------------------------------------------------
  1116. # The TAGFILES option can be used to specify one or more tagfiles. For each
  1117. # tag file the location of the external documentation should be added. The
  1118. # format of a tag file without this location is as follows:
  1119. # TAGFILES = file1 file2 ...
  1120. # Adding location for the tag files is done as follows:
  1121. # TAGFILES = file1=loc1 "file2 = loc2" ...
  1122. # where "loc1" and "loc2" can be relative or absolute paths
  1123. # or URLs. Note that each tag file must have a unique name (where the name does
  1124. # NOT include the path). If a tag file is not located in the directory in which
  1125. # doxygen is run, you must also specify the path to the tagfile here.
  1126. TAGFILES =
  1127. # When a file name is specified after GENERATE_TAGFILE, doxygen will create
  1128. # a tag file that is based on the input files it reads.
  1129. GENERATE_TAGFILE =
  1130. # If the ALLEXTERNALS tag is set to YES all external classes will be listed
  1131. # in the class index. If set to NO only the inherited external classes
  1132. # will be listed.
  1133. ALLEXTERNALS = NO
  1134. # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
  1135. # in the modules index. If set to NO, only the current project's groups will
  1136. # be listed.
  1137. EXTERNAL_GROUPS = YES
  1138. # The PERL_PATH should be the absolute path and name of the perl script
  1139. # interpreter (i.e. the result of `which perl').
  1140. PERL_PATH = /usr/bin/perl
  1141. #---------------------------------------------------------------------------
  1142. # Configuration options related to the dot tool
  1143. #---------------------------------------------------------------------------
  1144. # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
  1145. # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
  1146. # or super classes. Setting the tag to NO turns the diagrams off. Note that
  1147. # this option also works with HAVE_DOT disabled, but it is recommended to
  1148. # install and use dot, since it yields more powerful graphs.
  1149. CLASS_DIAGRAMS = YES
  1150. # You can define message sequence charts within doxygen comments using the \msc
  1151. # command. Doxygen will then run the mscgen tool (see
  1152. # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
  1153. # documentation. The MSCGEN_PATH tag allows you to specify the directory where
  1154. # the mscgen tool resides. If left empty the tool is assumed to be found in the
  1155. # default search path.
  1156. MSCGEN_PATH =
  1157. # If set to YES, the inheritance and collaboration graphs will hide
  1158. # inheritance and usage relations if the target is undocumented
  1159. # or is not a class.
  1160. HIDE_UNDOC_RELATIONS = YES
  1161. # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
  1162. # available from the path. This tool is part of Graphviz, a graph visualization
  1163. # toolkit from AT&T and Lucent Bell Labs. The other options in this section
  1164. # have no effect if this option is set to NO (the default)
  1165. HAVE_DOT = NO
  1166. # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
  1167. # allowed to run in parallel. When set to 0 (the default) doxygen will
  1168. # base this on the number of processors available in the system. You can set it
  1169. # explicitly to a value larger than 0 to get control over the balance
  1170. # between CPU load and processing speed.
  1171. DOT_NUM_THREADS = 0
  1172. # By default doxygen will use the Helvetica font for all dot files that
  1173. # doxygen generates. When you want a differently looking font you can specify
  1174. # the font name using DOT_FONTNAME. You need to make sure dot is able to find
  1175. # the font, which can be done by putting it in a standard location or by setting
  1176. # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
  1177. # directory containing the font.
  1178. DOT_FONTNAME = Helvetica
  1179. # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
  1180. # The default size is 10pt.
  1181. DOT_FONTSIZE = 10
  1182. # By default doxygen will tell dot to use the Helvetica font.
  1183. # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
  1184. # set the path where dot can find it.
  1185. DOT_FONTPATH =
  1186. # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
  1187. # will generate a graph for each documented class showing the direct and
  1188. # indirect inheritance relations. Setting this tag to YES will force the
  1189. # CLASS_DIAGRAMS tag to NO.
  1190. CLASS_GRAPH = YES
  1191. # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
  1192. # will generate a graph for each documented class showing the direct and
  1193. # indirect implementation dependencies (inheritance, containment, and
  1194. # class references variables) of the class with other documented classes.
  1195. COLLABORATION_GRAPH = YES
  1196. # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
  1197. # will generate a graph for groups, showing the direct groups dependencies
  1198. GROUP_GRAPHS = YES
  1199. # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
  1200. # collaboration diagrams in a style similar to the OMG's Unified Modeling
  1201. # Language.
  1202. UML_LOOK = NO
  1203. # If the UML_LOOK tag is enabled, the fields and methods are shown inside
  1204. # the class node. If there are many fields or methods and many nodes the
  1205. # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS
  1206. # threshold limits the number of items for each type to make the size more
  1207. # managable. Set this to 0 for no limit. Note that the threshold may be
  1208. # exceeded by 50% before the limit is enforced.
  1209. UML_LIMIT_NUM_FIELDS = 10
  1210. # If set to YES, the inheritance and collaboration graphs will show the
  1211. # relations between templates and their instances.
  1212. TEMPLATE_RELATIONS = NO
  1213. # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
  1214. # tags are set to YES then doxygen will generate a graph for each documented
  1215. # file showing the direct and indirect include dependencies of the file with
  1216. # other documented files.
  1217. INCLUDE_GRAPH = YES
  1218. # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
  1219. # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
  1220. # documented header file showing the documented files that directly or
  1221. # indirectly include this file.
  1222. INCLUDED_BY_GRAPH = YES
  1223. # If the CALL_GRAPH and HAVE_DOT options are set to YES then
  1224. # doxygen will generate a call dependency graph for every global function
  1225. # or class method. Note that enabling this option will significantly increase
  1226. # the time of a run. So in most cases it will be better to enable call graphs
  1227. # for selected functions only using the \callgraph command.
  1228. CALL_GRAPH = NO
  1229. # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
  1230. # doxygen will generate a caller dependency graph for every global function
  1231. # or class method. Note that enabling this option will significantly increase
  1232. # the time of a run. So in most cases it will be better to enable caller
  1233. # graphs for selected functions only using the \callergraph command.
  1234. CALLER_GRAPH = NO
  1235. # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
  1236. # will generate a graphical hierarchy of all classes instead of a textual one.
  1237. GRAPHICAL_HIERARCHY = YES
  1238. # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES
  1239. # then doxygen will show the dependencies a directory has on other directories
  1240. # in a graphical way. The dependency relations are determined by the #include
  1241. # relations between the files in the directories.
  1242. DIRECTORY_GRAPH = YES
  1243. # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
  1244. # generated by dot. Possible values are svg, png, jpg, or gif.
  1245. # If left blank png will be used. If you choose svg you need to set
  1246. # HTML_FILE_EXTENSION to xhtml in order to make the SVG files
  1247. # visible in IE 9+ (other browsers do not have this requirement).
  1248. DOT_IMAGE_FORMAT = png
  1249. # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
  1250. # enable generation of interactive SVG images that allow zooming and panning.
  1251. # Note that this requires a modern browser other than Internet Explorer.
  1252. # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
  1253. # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
  1254. # visible. Older versions of IE do not have SVG support.
  1255. INTERACTIVE_SVG = NO
  1256. # The tag DOT_PATH can be used to specify the path where the dot tool can be
  1257. # found. If left blank, it is assumed the dot tool can be found in the path.
  1258. DOT_PATH =
  1259. # The DOTFILE_DIRS tag can be used to specify one or more directories that
  1260. # contain dot files that are included in the documentation (see the
  1261. # \dotfile command).
  1262. DOTFILE_DIRS =
  1263. # The MSCFILE_DIRS tag can be used to specify one or more directories that
  1264. # contain msc files that are included in the documentation (see the
  1265. # \mscfile command).
  1266. MSCFILE_DIRS =
  1267. # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
  1268. # nodes that will be shown in the graph. If the number of nodes in a graph
  1269. # becomes larger than this value, doxygen will truncate the graph, which is
  1270. # visualized by representing a node as a red box. Note that doxygen if the
  1271. # number of direct children of the root node in a graph is already larger than
  1272. # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
  1273. # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
  1274. DOT_GRAPH_MAX_NODES = 50
  1275. # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
  1276. # graphs generated by dot. A depth value of 3 means that only nodes reachable
  1277. # from the root by following a path via at most 3 edges will be shown. Nodes
  1278. # that lay further from the root node will be omitted. Note that setting this
  1279. # option to 1 or 2 may greatly reduce the computation time needed for large
  1280. # code bases. Also note that the size of a graph can be further restricted by
  1281. # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
  1282. MAX_DOT_GRAPH_DEPTH = 0
  1283. # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
  1284. # background. This is disabled by default, because dot on Windows does not
  1285. # seem to support this out of the box. Warning: Depending on the platform used,
  1286. # enabling this option may lead to badly anti-aliased labels on the edges of
  1287. # a graph (i.e. they become hard to read).
  1288. DOT_TRANSPARENT = NO
  1289. # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
  1290. # files in one run (i.e. multiple -o and -T options on the command line). This
  1291. # makes dot run faster, but since only newer versions of dot (>1.8.10)
  1292. # support this, this feature is disabled by default.
  1293. DOT_MULTI_TARGETS = NO
  1294. # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
  1295. # generate a legend page explaining the meaning of the various boxes and
  1296. # arrows in the dot generated graphs.
  1297. GENERATE_LEGEND = YES
  1298. # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
  1299. # remove the intermediate dot files that are used to generate
  1300. # the various graphs.
  1301. DOT_CLEANUP = YES