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.

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