🛠️🐜 Antkeeper superbuild with dependencies included https://antkeeper.com
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.

1558 lines
64 KiB

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