doxygen.cfg 75 KB

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