KOffice – TDE office suite
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.

Doxyfile 46KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153
  1. # Doxyfile 1.3.6
  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. # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
  15. # by quotes) that should identify the project.
  16. PROJECT_NAME =
  17. # The PROJECT_NUMBER tag can be used to enter a project or revision number.
  18. # This could be handy for archiving the generated documentation or
  19. # if some version control system is used.
  20. PROJECT_NUMBER =
  21. # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
  22. # base path where the generated documentation will be put.
  23. # If a relative path is entered, it will be relative to the location
  24. # where doxygen was started. If left blank the current directory will be used.
  25. OUTPUT_DIRECTORY = ../apidocs/
  26. # The OUTPUT_LANGUAGE tag is used to specify the language in which all
  27. # documentation generated by doxygen is written. Doxygen will use this
  28. # information to generate all constant output in the proper language.
  29. # The default language is English, other supported languages are:
  30. # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
  31. # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
  32. # (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese,
  33. # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
  34. OUTPUT_LANGUAGE = English
  35. # This tag can be used to specify the encoding used in the generated output.
  36. # The encoding is not always determined by the language that is chosen,
  37. # but also whether or not the output is meant for Windows or non-Windows users.
  38. # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
  39. # forces the Windows encoding (this is the default for the Windows binary),
  40. # whereas setting the tag to NO uses a Unix-style encoding (the default for
  41. # all platforms other than Windows).
  42. USE_WINDOWS_ENCODING = NO
  43. # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
  44. # include brief member descriptions after the members that are listed in
  45. # the file and class documentation (similar to JavaDoc).
  46. # Set to NO to disable this.
  47. BRIEF_MEMBER_DESC = NO
  48. # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
  49. # the brief description of a member or function before the detailed description.
  50. # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
  51. # brief descriptions will be completely suppressed.
  52. REPEAT_BRIEF = YES
  53. # This tag implements a quasi-intelligent brief description abbreviator
  54. # that is used to form the text in various listings. Each string
  55. # in this list, if found as the leading text of the brief description, will be
  56. # stripped from the text and the result after processing the whole list, is used
  57. # as the annotated text. Otherwise, the brief description is used as-is. If left
  58. # blank, the following values are used ("$name" is automatically replaced with the
  59. # name of the entity): "The $name class" "The $name widget" "The $name file"
  60. # "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
  61. ABBREVIATE_BRIEF =
  62. # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
  63. # Doxygen will generate a detailed section even if there is only a brief
  64. # description.
  65. ALWAYS_DETAILED_SEC = YES
  66. # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
  67. # members of a class in the documentation of that class as if those members were
  68. # ordinary class members. Constructors, destructors and assignment operators of
  69. # the base classes will not be shown.
  70. INLINE_INHERITED_MEMB = NO
  71. # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
  72. # path before files name in the file list and in the header files. If set
  73. # to NO the shortest path that makes the file name unique will be used.
  74. FULL_PATH_NAMES = NO
  75. # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
  76. # can be used to strip a user-defined part of the path. Stripping is
  77. # only done if one of the specified strings matches the left-hand part of
  78. # the path. It is allowed to use relative paths in the argument list.
  79. # If left blank the directory from which doxygen is run is used as the
  80. # path to strip.
  81. STRIP_FROM_PATH =
  82. # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
  83. # (but less readable) file names. This can be useful is your file systems
  84. # doesn't support long names like on DOS, Mac, or CD-ROM.
  85. SHORT_NAMES = NO
  86. # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
  87. # will interpret the first line (until the first dot) of a JavaDoc-style
  88. # comment as the brief description. If set to NO, the JavaDoc
  89. # comments will behave just like the Qt-style comments (thus requiring an
  90. # explicit @brief command for a brief description.
  91. JAVADOC_AUTOBRIEF = YES
  92. # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
  93. # treat a multi-line C++ special comment block (i.e. a block of //! or ///
  94. # comments) as a brief description. This used to be the default behaviour.
  95. # The new default is to treat a multi-line C++ comment block as a detailed
  96. # description. Set this tag to YES if you prefer the old behaviour instead.
  97. MULTILINE_CPP_IS_BRIEF = NO
  98. # If the DETAILS_AT_TOP tag is set to YES then Doxygen
  99. # will output the detailed description near the top, like JavaDoc.
  100. # If set to NO, the detailed description appears after the member
  101. # documentation.
  102. DETAILS_AT_TOP = NO
  103. # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
  104. # member inherits the documentation from any documented member that it
  105. # re-implements.
  106. INHERIT_DOCS = YES
  107. # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
  108. # tag is set to YES, then doxygen will reuse the documentation of the first
  109. # member in the group (if any) for the other members of the group. By default
  110. # all members of a group must be documented explicitly.
  111. DISTRIBUTE_GROUP_DOC = NO
  112. # The TAB_SIZE tag can be used to set the number of spaces in a tab.
  113. # Doxygen uses this value to replace tabs by spaces in code fragments.
  114. TAB_SIZE = 4
  115. # This tag can be used to specify a number of aliases that acts
  116. # as commands in the documentation. An alias has the form "name=value".
  117. # For example adding "sideeffect=\par Side Effects:\n" will allow you to
  118. # put the command \sideeffect (or @sideeffect) in the documentation, which
  119. # will result in a user-defined paragraph with heading "Side Effects:".
  120. # You can put \n's in the value part of an alias to insert newlines.
  121. ALIASES = obsolete=@deprecated
  122. # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
  123. # only. Doxygen will then generate output that is more tailored for C.
  124. # For instance, some of the names that are used will be different. The list
  125. # of all members will be omitted, etc.
  126. OPTIMIZE_OUTPUT_FOR_C = NO
  127. # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
  128. # only. Doxygen will then generate output that is more tailored for Java.
  129. # For instance, namespaces will be presented as packages, qualified scopes
  130. # will look different, etc.
  131. OPTIMIZE_OUTPUT_JAVA = NO
  132. # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
  133. # the same type (for instance a group of public functions) to be put as a
  134. # subgroup of that type (e.g. under the Public Functions section). Set it to
  135. # NO to prevent subgrouping. Alternatively, this can be done per class using
  136. # the \nosubgrouping command.
  137. SUBGROUPING = YES
  138. #---------------------------------------------------------------------------
  139. # Build related configuration options
  140. #---------------------------------------------------------------------------
  141. # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
  142. # documentation are documented, even if no documentation was available.
  143. # Private class members and static file members will be hidden unless
  144. # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
  145. EXTRACT_ALL = NO
  146. # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
  147. # will be included in the documentation.
  148. EXTRACT_PRIVATE = NO
  149. # If the EXTRACT_STATIC tag is set to YES all static members of a file
  150. # will be included in the documentation.
  151. EXTRACT_STATIC = YES
  152. # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
  153. # defined locally in source files will be included in the documentation.
  154. # If set to NO only classes defined in header files are included.
  155. EXTRACT_LOCAL_CLASSES = NO
  156. # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
  157. # undocumented members of documented classes, files or namespaces.
  158. # If set to NO (the default) these members will be included in the
  159. # various overviews, but no documentation section is generated.
  160. # This option has no effect if EXTRACT_ALL is enabled.
  161. HIDE_UNDOC_MEMBERS = NO
  162. # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
  163. # undocumented classes that are normally visible in the class hierarchy.
  164. # If set to NO (the default) these classes will be included in the various
  165. # overviews. This option has no effect if EXTRACT_ALL is enabled.
  166. HIDE_UNDOC_CLASSES = YES
  167. # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
  168. # friend (class|struct|union) declarations.
  169. # If set to NO (the default) these declarations will be included in the
  170. # documentation.
  171. HIDE_FRIEND_COMPOUNDS = NO
  172. # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
  173. # documentation blocks found inside the body of a function.
  174. # If set to NO (the default) these blocks will be appended to the
  175. # function's detailed documentation block.
  176. HIDE_IN_BODY_DOCS = NO
  177. # The INTERNAL_DOCS tag determines if documentation
  178. # that is typed after a \internal command is included. If the tag is set
  179. # to NO (the default) then the documentation will be excluded.
  180. # Set it to YES to include the internal documentation.
  181. INTERNAL_DOCS = NO
  182. # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
  183. # file names in lower-case letters. If set to YES upper-case letters are also
  184. # allowed. This is useful if you have classes or files whose names only differ
  185. # in case and if your file system supports case sensitive file names. Windows
  186. # users are advised to set this option to NO.
  187. CASE_SENSE_NAMES = YES
  188. # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
  189. # will show members with their full class and namespace scopes in the
  190. # documentation. If set to YES the scope will be hidden.
  191. HIDE_SCOPE_NAMES = NO
  192. # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
  193. # will put a list of the files that are included by a file in the documentation
  194. # of that file.
  195. SHOW_INCLUDE_FILES = YES
  196. # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
  197. # is inserted in the documentation for inline members.
  198. INLINE_INFO = YES
  199. # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
  200. # will sort the (detailed) documentation of file and class members
  201. # alphabetically by member name. If set to NO the members will appear in
  202. # declaration order.
  203. SORT_MEMBER_DOCS = NO
  204. # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
  205. # brief documentation of file, namespace and class members alphabetically
  206. # by member name. If set to NO (the default) the members will appear in
  207. # declaration order.
  208. SORT_BRIEF_DOCS = NO
  209. # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
  210. # sorted by fully-qualified names, including namespaces. If set to
  211. # NO (the default), the class list will be sorted only by class name,
  212. # not including the namespace part.
  213. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
  214. # Note: This option applies only to the class list, not to the
  215. # alphabetical list.
  216. SORT_BY_SCOPE_NAME = NO
  217. # The GENERATE_TODOLIST tag can be used to enable (YES) or
  218. # disable (NO) the todo list. This list is created by putting \todo
  219. # commands in the documentation.
  220. GENERATE_TODOLIST = NO
  221. # The GENERATE_TESTLIST tag can be used to enable (YES) or
  222. # disable (NO) the test list. This list is created by putting \test
  223. # commands in the documentation.
  224. GENERATE_TESTLIST = NO
  225. # The GENERATE_BUGLIST tag can be used to enable (YES) or
  226. # disable (NO) the bug list. This list is created by putting \bug
  227. # commands in the documentation.
  228. GENERATE_BUGLIST = YES
  229. # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
  230. # disable (NO) the deprecated list. This list is created by putting
  231. # \deprecated commands in the documentation.
  232. GENERATE_DEPRECATEDLIST= YES
  233. # The ENABLED_SECTIONS tag can be used to enable conditional
  234. # documentation sections, marked by \if sectionname ... \endif.
  235. ENABLED_SECTIONS =
  236. # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
  237. # the initial value of a variable or define consists of for it to appear in
  238. # the documentation. If the initializer consists of more lines than specified
  239. # here it will be hidden. Use a value of 0 to hide initializers completely.
  240. # The appearance of the initializer of individual variables and defines in the
  241. # documentation can be controlled using \showinitializer or \hideinitializer
  242. # command in the documentation regardless of this setting.
  243. MAX_INITIALIZER_LINES = 30
  244. # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
  245. # at the bottom of the documentation of classes and structs. If set to YES the
  246. # list will mention the files that were used to generate the documentation.
  247. SHOW_USED_FILES = YES
  248. #---------------------------------------------------------------------------
  249. # configuration options related to warning and progress messages
  250. #---------------------------------------------------------------------------
  251. # The QUIET tag can be used to turn on/off the messages that are generated
  252. # by doxygen. Possible values are YES and NO. If left blank NO is used.
  253. QUIET = YES
  254. # The WARNINGS tag can be used to turn on/off the warning messages that are
  255. # generated by doxygen. Possible values are YES and NO. If left blank
  256. # NO is used.
  257. WARNINGS = NO
  258. # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
  259. # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
  260. # automatically be disabled.
  261. WARN_IF_UNDOCUMENTED = NO
  262. # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
  263. # potential errors in the documentation, such as not documenting some
  264. # parameters in a documented function, or documenting parameters that
  265. # don't exist or using markup commands wrongly.
  266. WARN_IF_DOC_ERROR = YES
  267. # The WARN_FORMAT tag determines the format of the warning messages that
  268. # doxygen can produce. The string should contain the $file, $line, and $text
  269. # tags, which will be replaced by the file and line number from which the
  270. # warning originated and the warning text.
  271. WARN_FORMAT =
  272. # The WARN_LOGFILE tag can be used to specify a file to which warning
  273. # and error messages should be written. If left blank the output is written
  274. # to stderr.
  275. WARN_LOGFILE =
  276. #---------------------------------------------------------------------------
  277. # configuration options related to the input files
  278. #---------------------------------------------------------------------------
  279. # The INPUT tag can be used to specify the files and/or directories that contain
  280. # documented source files. You may enter file names like "myfile.cpp" or
  281. # directories like "/usr/src/myproject". Separate the files or directories
  282. # with spaces.
  283. INPUT =
  284. # If the value of the INPUT tag contains directories, you can use the
  285. # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  286. # and *.h) to filter out the source-files in the directories. If left
  287. # blank the following patterns are tested:
  288. # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
  289. # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
  290. FILE_PATTERNS = *.h \
  291. *.cpp \
  292. *.cc \
  293. *.hpp \
  294. *.dox \
  295. *.c++ \
  296. *.cxx \
  297. *.h++ \
  298. *.hh
  299. # The RECURSIVE tag can be used to turn specify whether or not subdirectories
  300. # should be searched for input files as well. Possible values are YES and NO.
  301. # If left blank NO is used.
  302. RECURSIVE = YES
  303. # The EXCLUDE tag can be used to specify files and/or directories that should
  304. # excluded from the INPUT source files. This way you can easily exclude a
  305. # subdirectory from a directory tree whose root is specified with the INPUT tag.
  306. EXCLUDE =
  307. # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
  308. # that are symbolic links (a Unix filesystem feature) are excluded from the input.
  309. EXCLUDE_SYMLINKS = NO
  310. # If the value of the INPUT tag contains directories, you can use the
  311. # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
  312. # certain files from those directories.
  313. EXCLUDE_PATTERNS = *.tqmoc.* \
  314. tqmoc* \
  315. *.all_cpp.* \
  316. *unload.* \
  317. */test/* \
  318. */tests/* \
  319. *_p.h
  320. # The EXAMPLE_PATH tag can be used to specify one or more files or
  321. # directories that contain example code fragments that are included (see
  322. # the \include command).
  323. EXAMPLE_PATH =
  324. # If the value of the EXAMPLE_PATH tag contains directories, you can use the
  325. # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  326. # and *.h) to filter out the source-files in the directories. If left
  327. # blank all files are included.
  328. EXAMPLE_PATTERNS =
  329. # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
  330. # searched for input files to be used with the \include or \dontinclude
  331. # commands irrespective of the value of the RECURSIVE tag.
  332. # Possible values are YES and NO. If left blank NO is used.
  333. EXAMPLE_RECURSIVE = NO
  334. # The IMAGE_PATH tag can be used to specify one or more files or
  335. # directories that contain image that are included in the documentation (see
  336. # the \image command).
  337. IMAGE_PATH =
  338. # The INPUT_FILTER tag can be used to specify a program that doxygen should
  339. # invoke to filter for each input file. Doxygen will invoke the filter program
  340. # by executing (via popen()) the command <filter> <input-file>, where <filter>
  341. # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
  342. # input file. Doxygen will then use the output that the filter program writes
  343. # to standard output.
  344. INPUT_FILTER =
  345. # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
  346. # INPUT_FILTER) will be used to filter the input files when producing source
  347. # files to browse (i.e. when SOURCE_BROWSER is set to YES).
  348. FILTER_SOURCE_FILES = NO
  349. #---------------------------------------------------------------------------
  350. # configuration options related to source browsing
  351. #---------------------------------------------------------------------------
  352. # If the SOURCE_BROWSER tag is set to YES then a list of source files will
  353. # be generated. Documented entities will be cross-referenced with these sources.
  354. # Note: To get rid of all source code in the generated output, make sure also
  355. # VERBATIM_HEADERS is set to NO.
  356. SOURCE_BROWSER = YES
  357. # Setting the INLINE_SOURCES tag to YES will include the body
  358. # of functions and classes directly in the documentation.
  359. INLINE_SOURCES = NO
  360. # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
  361. # doxygen to hide any special comment blocks from generated source code
  362. # fragments. Normal C and C++ comments will always remain visible.
  363. STRIP_CODE_COMMENTS = YES
  364. # If the REFERENCED_BY_RELATION tag is set to YES (the default)
  365. # then for each documented function all documented
  366. # functions referencing it will be listed.
  367. REFERENCED_BY_RELATION = YES
  368. # If the REFERENCES_RELATION tag is set to YES (the default)
  369. # then for each documented function all documented entities
  370. # called/used by that function will be listed.
  371. REFERENCES_RELATION = YES
  372. # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
  373. # will generate a verbatim copy of the header file for each class for
  374. # which an include is specified. Set to NO to disable this.
  375. VERBATIM_HEADERS = YES
  376. #---------------------------------------------------------------------------
  377. # configuration options related to the alphabetical class index
  378. #---------------------------------------------------------------------------
  379. # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
  380. # of all compounds will be generated. Enable this if the project
  381. # contains a lot of classes, structs, unions or interfaces.
  382. ALPHABETICAL_INDEX = YES
  383. # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
  384. # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
  385. # in which this list will be split (can be a number in the range [1..20])
  386. COLS_IN_ALPHA_INDEX = 3
  387. # In case all classes in a project start with a common prefix, all
  388. # classes will be put under the same header in the alphabetical index.
  389. # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
  390. # should be ignored while generating the index headers.
  391. IGNORE_PREFIX = K
  392. #---------------------------------------------------------------------------
  393. # configuration options related to the HTML output
  394. #---------------------------------------------------------------------------
  395. # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
  396. # generate HTML output.
  397. GENERATE_HTML = NO
  398. # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
  399. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  400. # put in front of it. If left blank `html' will be used as the default path.
  401. HTML_OUTPUT =
  402. # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
  403. # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
  404. # doxygen will generate files with .html extension.
  405. HTML_FILE_EXTENSION = .html
  406. # The HTML_HEADER tag can be used to specify a personal HTML header for
  407. # each generated HTML page. If it is left blank doxygen will generate a
  408. # standard header.
  409. HTML_HEADER = ../apidocs/common/header.html
  410. # The HTML_FOOTER tag can be used to specify a personal HTML footer for
  411. # each generated HTML page. If it is left blank doxygen will generate a
  412. # standard footer.
  413. HTML_FOOTER = ../apidocs/common/footer.html
  414. # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
  415. # style sheet that is used by each HTML page. It can be used to
  416. # fine-tune the look of the HTML output. If the tag is left blank doxygen
  417. # will generate a default style sheet. Note that doxygen will try to copy
  418. # the style sheet file to the HTML output directory, so don't put your own
  419. # stylesheet in the HTML output directory as well, or it will be erased!
  420. HTML_STYLESHEET = ../apidocs/common/doxygen.css
  421. # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
  422. # files or namespaces will be aligned in HTML using tables. If set to
  423. # NO a bullet list will be used.
  424. HTML_ALIGN_MEMBERS = YES
  425. # If the GENERATE_HTMLHELP tag is set to YES, additional index files
  426. # will be generated that can be used as input for tools like the
  427. # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
  428. # of the generated HTML documentation.
  429. GENERATE_HTMLHELP = NO
  430. # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
  431. # be used to specify the file name of the resulting .chm file. You
  432. # can add a path in front of the file if the result should not be
  433. # written to the html output directory.
  434. CHM_FILE =
  435. # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
  436. # be used to specify the location (absolute path including file name) of
  437. # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
  438. # the HTML help compiler on the generated index.hhp.
  439. HHC_LOCATION =
  440. # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
  441. # controls if a separate .chi index file is generated (YES) or that
  442. # it should be included in the master .chm file (NO).
  443. GENERATE_CHI = NO
  444. # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
  445. # controls whether a binary table of contents is generated (YES) or a
  446. # normal table of contents (NO) in the .chm file.
  447. BINARY_TOC = NO
  448. # The TOC_EXPAND flag can be set to YES to add extra items for group members
  449. # to the contents of the HTML help documentation and to the tree view.
  450. TOC_EXPAND = NO
  451. # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
  452. # top of each HTML page. The value NO (the default) enables the index and
  453. # the value YES disables it.
  454. DISABLE_INDEX = YES
  455. # This tag can be used to set the number of enum values (range [1..20])
  456. # that doxygen will group on one line in the generated HTML documentation.
  457. ENUM_VALUES_PER_LINE = 4
  458. # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
  459. # generated containing a tree-like index structure (just like the one that
  460. # is generated for HTML Help). For this to work a browser that supports
  461. # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
  462. # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
  463. # probably better off using the HTML help feature.
  464. GENERATE_TREEVIEW = NO
  465. # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
  466. # used to set the initial width (in pixels) of the frame in which the tree
  467. # is shown.
  468. TREEVIEW_WIDTH = 250
  469. #---------------------------------------------------------------------------
  470. # configuration options related to the LaTeX output
  471. #---------------------------------------------------------------------------
  472. # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
  473. # generate Latex output.
  474. GENERATE_LATEX = NO
  475. # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
  476. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  477. # put in front of it. If left blank `latex' will be used as the default path.
  478. LATEX_OUTPUT =
  479. # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
  480. # invoked. If left blank `latex' will be used as the default command name.
  481. LATEX_CMD_NAME = latex
  482. # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
  483. # generate index for LaTeX. If left blank `makeindex' will be used as the
  484. # default command name.
  485. MAKEINDEX_CMD_NAME = makeindex
  486. # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
  487. # LaTeX documents. This may be useful for small projects and may help to
  488. # save some trees in general.
  489. COMPACT_LATEX = NO
  490. # The PAPER_TYPE tag can be used to set the paper type that is used
  491. # by the printer. Possible values are: a4, a4wide, letter, legal and
  492. # executive. If left blank a4wide will be used.
  493. PAPER_TYPE = a4wide
  494. # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
  495. # packages that should be included in the LaTeX output.
  496. EXTRA_PACKAGES =
  497. # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
  498. # the generated latex document. The header should contain everything until
  499. # the first chapter. If it is left blank doxygen will generate a
  500. # standard header. Notice: only use this tag if you know what you are doing!
  501. LATEX_HEADER =
  502. # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
  503. # is prepared for conversion to pdf (using ps2pdf). The pdf file will
  504. # contain links (just like the HTML output) instead of page references
  505. # This makes the output suitable for online browsing using a pdf viewer.
  506. PDF_HYPERLINKS = NO
  507. # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
  508. # plain latex in the generated Makefile. Set this option to YES to get a
  509. # higher quality PDF documentation.
  510. USE_PDFLATEX = NO
  511. # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
  512. # command to the generated LaTeX files. This will instruct LaTeX to keep
  513. # running if errors occur, instead of asking the user for help.
  514. # This option is also used when generating formulas in HTML.
  515. LATEX_BATCHMODE = NO
  516. # If LATEX_HIDE_INDICES is set to YES then doxygen will not
  517. # include the index chapters (such as File Index, Compound Index, etc.)
  518. # in the output.
  519. LATEX_HIDE_INDICES = NO
  520. #---------------------------------------------------------------------------
  521. # configuration options related to the RTF output
  522. #---------------------------------------------------------------------------
  523. # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
  524. # The RTF output is optimized for Word 97 and may not look very pretty with
  525. # other RTF readers or editors.
  526. GENERATE_RTF = NO
  527. # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
  528. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  529. # put in front of it. If left blank `rtf' will be used as the default path.
  530. RTF_OUTPUT =
  531. # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
  532. # RTF documents. This may be useful for small projects and may help to
  533. # save some trees in general.
  534. COMPACT_RTF = NO
  535. # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
  536. # will contain hyperlink fields. The RTF file will
  537. # contain links (just like the HTML output) instead of page references.
  538. # This makes the output suitable for online browsing using WORD or other
  539. # programs which support those fields.
  540. # Note: wordpad (write) and others do not support links.
  541. RTF_HYPERLINKS = NO
  542. # Load stylesheet definitions from file. Syntax is similar to doxygen's
  543. # config file, i.e. a series of assignments. You only have to provide
  544. # replacements, missing definitions are set to their default value.
  545. RTF_STYLESHEET_FILE =
  546. # Set optional variables used in the generation of an rtf document.
  547. # Syntax is similar to doxygen's config file.
  548. RTF_EXTENSIONS_FILE =
  549. #---------------------------------------------------------------------------
  550. # configuration options related to the man page output
  551. #---------------------------------------------------------------------------
  552. # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
  553. # generate man pages
  554. GENERATE_MAN = NO
  555. # The MAN_OUTPUT tag is used to specify where the man pages will be put.
  556. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  557. # put in front of it. If left blank `man' will be used as the default path.
  558. MAN_OUTPUT =
  559. # The MAN_EXTENSION tag determines the extension that is added to
  560. # the generated man pages (default is the subroutine's section .3)
  561. MAN_EXTENSION = .trinity
  562. # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
  563. # then it will generate one additional man file for each entity
  564. # documented in the real man page(s). These additional files
  565. # only source the real man page, but without them the man command
  566. # would be unable to find the correct page. The default is NO.
  567. MAN_LINKS = YES
  568. #---------------------------------------------------------------------------
  569. # configuration options related to the XML output
  570. #---------------------------------------------------------------------------
  571. # If the GENERATE_XML tag is set to YES Doxygen will
  572. # generate an XML file that captures the structure of
  573. # the code including all documentation.
  574. GENERATE_XML = NO
  575. # The XML_OUTPUT tag is used to specify where the XML pages will be put.
  576. # If a relative path is entered the value of OUTPUT_DIRECTORY will be
  577. # put in front of it. If left blank `xml' will be used as the default path.
  578. XML_OUTPUT = xml
  579. # The XML_SCHEMA tag can be used to specify an XML schema,
  580. # which can be used by a validating XML parser to check the
  581. # syntax of the XML files.
  582. XML_SCHEMA =
  583. # The XML_DTD tag can be used to specify an XML DTD,
  584. # which can be used by a validating XML parser to check the
  585. # syntax of the XML files.
  586. XML_DTD =
  587. # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
  588. # dump the program listings (including syntax highlighting
  589. # and cross-referencing information) to the XML output. Note that
  590. # enabling this will significantly increase the size of the XML output.
  591. XML_PROGRAMLISTING = NO
  592. #---------------------------------------------------------------------------
  593. # configuration options for the AutoGen Definitions output
  594. #---------------------------------------------------------------------------
  595. # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
  596. # generate an AutoGen Definitions (see autogen.sf.net) file
  597. # that captures the structure of the code including all
  598. # documentation. Note that this feature is still experimental
  599. # and incomplete at the moment.
  600. GENERATE_AUTOGEN_DEF = NO
  601. #---------------------------------------------------------------------------
  602. # configuration options related to the Perl module output
  603. #---------------------------------------------------------------------------
  604. # If the GENERATE_PERLMOD tag is set to YES Doxygen will
  605. # generate a Perl module file that captures the structure of
  606. # the code including all documentation. Note that this
  607. # feature is still experimental and incomplete at the
  608. # moment.
  609. GENERATE_PERLMOD = NO
  610. # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
  611. # the necessary Makefile rules, Perl scripts and LaTeX code to be able
  612. # to generate PDF and DVI output from the Perl module output.
  613. PERLMOD_LATEX = NO
  614. # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
  615. # nicely formatted so it can be parsed by a human reader. This is useful
  616. # if you want to understand what is going on. On the other hand, if this
  617. # tag is set to NO the size of the Perl module output will be much smaller
  618. # and Perl will parse it just the same.
  619. PERLMOD_PRETTY = YES
  620. # The names of the make variables in the generated doxyrules.make file
  621. # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
  622. # This is useful so different doxyrules.make files included by the same
  623. # Makefile don't overwrite each other's variables.
  624. PERLMOD_MAKEVAR_PREFIX =
  625. #---------------------------------------------------------------------------
  626. # Configuration options related to the preprocessor
  627. #---------------------------------------------------------------------------
  628. # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
  629. # evaluate all C-preprocessor directives found in the sources and include
  630. # files.
  631. ENABLE_PREPROCESSING = YES
  632. # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
  633. # names in the source code. If set to NO (the default) only conditional
  634. # compilation will be performed. Macro expansion can be done in a controlled
  635. # way by setting EXPAND_ONLY_PREDEF to YES.
  636. MACRO_EXPANSION = NO
  637. # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
  638. # then the macro expansion is limited to the macros specified with the
  639. # PREDEFINED and EXPAND_AS_PREDEFINED tags.
  640. EXPAND_ONLY_PREDEF = NO
  641. # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
  642. # in the INCLUDE_PATH (see below) will be search if a #include is found.
  643. SEARCH_INCLUDES = YES
  644. # The INCLUDE_PATH tag can be used to specify one or more directories that
  645. # contain include files that are not input files but should be processed by
  646. # the preprocessor.
  647. INCLUDE_PATH =
  648. # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
  649. # patterns (like *.h and *.hpp) to filter out the header-files in the
  650. # directories. If left blank, the patterns specified with FILE_PATTERNS will
  651. # be used.
  652. INCLUDE_FILE_PATTERNS =
  653. # The PREDEFINED tag can be used to specify one or more macro names that
  654. # are defined before the preprocessor is started (similar to the -D option of
  655. # gcc). The argument of the tag is a list of macros of the form: name
  656. # or name=definition (no spaces). If the definition and the = are
  657. # omitted =1 is assumed.
  658. PREDEFINED = QT_VERSION=320 \
  659. __cplusplus \
  660. Q_WS_X11
  661. # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
  662. # this tag can be used to specify a list of macro names that should be expanded.
  663. # The macro definition that is found in the sources will be used.
  664. # Use the PREDEFINED tag if you want to use a different macro definition.
  665. EXPAND_AS_DEFINED =
  666. # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
  667. # doxygen's preprocessor will remove all function-like macros that are alone
  668. # on a line, have an all uppercase name, and do not end with a semicolon. Such
  669. # function macros are typically used for boiler-plate code, and will confuse the
  670. # parser if not removed.
  671. SKIP_FUNCTION_MACROS = YES
  672. #---------------------------------------------------------------------------
  673. # Configuration::additions related to external references
  674. #---------------------------------------------------------------------------
  675. # The TAGFILES option can be used to specify one or more tagfiles.
  676. # Optionally an initial location of the external documentation
  677. # can be added for each tagfile. The format of a tag file without
  678. # this location is as follows:
  679. # TAGFILES = file1 file2 ...
  680. # Adding location for the tag files is done as follows:
  681. # TAGFILES = file1=loc1 "file2 = loc2" ...
  682. # where "loc1" and "loc2" can be relative or absolute paths or
  683. # URLs. If a location is present for each tag, the installdox tool
  684. # does not have to be run to correct the links.
  685. # Note that each tag file must have a unique name
  686. # (where the name does NOT include the path)
  687. # If a tag file is not located in the directory in which doxygen
  688. # is run, you must also specify the path to the tagfile here.
  689. TAGFILES =
  690. # When a file name is specified after GENERATE_TAGFILE, doxygen will create
  691. # a tag file that is based on the input files it reads.
  692. GENERATE_TAGFILE =
  693. # If the ALLEXTERNALS tag is set to YES all external classes will be listed
  694. # in the class index. If set to NO only the inherited external classes
  695. # will be listed.
  696. ALLEXTERNALS = NO
  697. # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
  698. # in the modules index. If set to NO, only the current project's groups will
  699. # be listed.
  700. EXTERNAL_GROUPS = NO
  701. # The PERL_PATH should be the absolute path and name of the perl script
  702. # interpreter (i.e. the result of `which perl').
  703. PERL_PATH =
  704. #---------------------------------------------------------------------------
  705. # Configuration options related to the dot tool
  706. #---------------------------------------------------------------------------
  707. # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
  708. # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
  709. # super classes. Setting the tag to NO turns the diagrams off. Note that this
  710. # option is superseded by the HAVE_DOT option below. This is only a fallback. It is
  711. # recommended to install and use dot, since it yields more powerful graphs.
  712. CLASS_DIAGRAMS = YES
  713. # If set to YES, the inheritance and collaboration graphs will hide
  714. # inheritance and usage relations if the target is undocumented
  715. # or is not a class.
  716. HIDE_UNDOC_RELATIONS = NO
  717. # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
  718. # available from the path. This tool is part of Graphviz, a graph visualization
  719. # toolkit from AT&T and Lucent Bell Labs. The other options in this section
  720. # have no effect if this option is set to NO (the default)
  721. HAVE_DOT = NO
  722. # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
  723. # will generate a graph for each documented class showing the direct and
  724. # indirect inheritance relations. Setting this tag to YES will force the
  725. # the CLASS_DIAGRAMS tag to NO.
  726. CLASS_GRAPH = YES
  727. # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
  728. # will generate a graph for each documented class showing the direct and
  729. # indirect implementation dependencies (inheritance, containment, and
  730. # class references variables) of the class with other documented classes.
  731. COLLABORATION_GRAPH = YES
  732. # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
  733. # collaboration diagrams in a style similar to the OMG's Unified Modeling
  734. # Language.
  735. UML_LOOK = NO
  736. # If set to YES, the inheritance and collaboration graphs will show the
  737. # relations between templates and their instances.
  738. TEMPLATE_RELATIONS = YES
  739. # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
  740. # tags are set to YES then doxygen will generate a graph for each documented
  741. # file showing the direct and indirect include dependencies of the file with
  742. # other documented files.
  743. INCLUDE_GRAPH = YES
  744. # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
  745. # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
  746. # documented header file showing the documented files that directly or
  747. # indirectly include this file.
  748. INCLUDED_BY_GRAPH = YES
  749. # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
  750. # generate a call dependency graph for every global function or class method.
  751. # Note that enabling this option will significantly increase the time of a run.
  752. # So in most cases it will be better to enable call graphs for selected
  753. # functions only using the \callgraph command.
  754. CALL_GRAPH = NO
  755. # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
  756. # will graphical hierarchy of all classes instead of a textual one.
  757. GRAPHICAL_HIERARCHY = YES
  758. # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
  759. # generated by dot. Possible values are png, jpg, or gif
  760. # If left blank png will be used.
  761. DOT_IMAGE_FORMAT = png
  762. # The tag DOT_PATH can be used to specify the path where the dot tool can be
  763. # found. If left blank, it is assumed the dot tool can be found on the path.
  764. DOT_PATH =
  765. # The DOTFILE_DIRS tag can be used to specify one or more directories that
  766. # contain dot files that are included in the documentation (see the
  767. # \dotfile command).
  768. DOTFILE_DIRS =
  769. # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
  770. # (in pixels) of the graphs generated by dot. If a graph becomes larger than
  771. # this value, doxygen will try to truncate the graph, so that it fits within
  772. # the specified constraint. Beware that most browsers cannot cope with very
  773. # large images.
  774. MAX_DOT_GRAPH_WIDTH = 800
  775. # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
  776. # (in pixels) of the graphs generated by dot. If a graph becomes larger than
  777. # this value, doxygen will try to truncate the graph, so that it fits within
  778. # the specified constraint. Beware that most browsers cannot cope with very
  779. # large images.
  780. MAX_DOT_GRAPH_HEIGHT = 1024
  781. # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
  782. # graphs generated by dot. A depth value of 3 means that only nodes reachable
  783. # from the root by following a path via at most 3 edges will be shown. Nodes that
  784. # lay further from the root node will be omitted. Note that setting this option to
  785. # 1 or 2 may greatly reduce the computation time needed for large code bases. Also
  786. # note that a graph may be further truncated if the graph's image dimensions are
  787. # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
  788. # If 0 is used for the depth value (the default), the graph is not depth-constrained.
  789. MAX_DOT_GRAPH_DEPTH = 0
  790. # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
  791. # generate a legend page explaining the meaning of the various boxes and
  792. # arrows in the dot generated graphs.
  793. GENERATE_LEGEND = YES
  794. # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
  795. # remove the intermediate dot files that are used to generate
  796. # the various graphs.
  797. DOT_CLEANUP = YES
  798. #---------------------------------------------------------------------------
  799. # Configuration::additions related to the search engine
  800. #---------------------------------------------------------------------------
  801. # The SEARCHENGINE tag specifies whether or not a search engine should be
  802. # used. If set to NO the values of all tags below this one will be ignored.
  803. SEARCHENGINE = NO
  804. PROJECT_NAME = "kspread Library"
  805. PROJECT_NUMBER = "Version 1.3post"
  806. INPUT = .
  807. IMAGE_PATH = ../doc/api
  808. OUTPUT_DIRECTORY = ../apidocs
  809. HTML_OUTPUT = kspread/html
  810. HTML_HEADER = ../apidocs/common/header.html
  811. HTML_FOOTER = ../apidocs/common/footer.html
  812. HTML_STYLESHEET = ../apidocs/common/doxygen.css
  813. LATEX_OUTPUT = kspread/latex
  814. RTF_OUTPUT = kspread/rtf
  815. MAN_OUTPUT = kspread/man
  816. GENERATE_HTML =
  817. GENERATE_MAN =
  818. GENERATE_LATEX =
  819. TAGFILES = \
  820. /usr/local/trinity/share/doc/HTML/en/kdelibs-apidocs/qt/qt.tag=/usr/local/qt-copy/doc/html
  821. GENERATE_TAGFILE = ../apidocs/kspread/kspread.tag
  822. IGNORE_PREFIX = K
  823. HAVE_DOT = YES