🛠️🐜 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.

1561 lines
64 KiB

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