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.
 
 
 
 
 
 

1365 lines
55 KiB

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