1# Doxyfile 1.7.5.1 2 3# This file describes the settings to be used by the documentation system 4# doxygen (www.doxygen.org) for a project. 5# 6# All text after a hash (#) is considered a comment and will be ignored. 7# The format is: 8# TAG = value [value, ...] 9# For lists items can also be appended using: 10# TAG += value [value, ...] 11# Values that contain spaces should be placed between quotes (" "). 12 13#--------------------------------------------------------------------------- 14# Project related configuration options 15#--------------------------------------------------------------------------- 16 17# This tag specifies the encoding used for all characters in the config file 18# that follow. The default is UTF-8 which is also the encoding used for all 19# text before the first occurrence of this tag. Doxygen uses libiconv (or the 20# iconv built into libc) for the transcoding. See 21# http://www.gnu.org/software/libiconv for the list of possible encodings. 22 23DOXYFILE_ENCODING = UTF-8 24 25# The PROJECT_NAME tag is a single word (or sequence of words) that should 26# identify the project. Note that if you do not use Doxywizard you need 27# to put quotes around the project name if it contains spaces. 28 29PROJECT_NAME = "The Haiku Book" 30 31# The PROJECT_NUMBER tag can be used to enter a project or revision number. 32# This could be handy for archiving the generated documentation or 33# if some version control system is used. 34 35PROJECT_NUMBER = pre-R1 36 37# Using the PROJECT_BRIEF tag one can provide an optional one line description 38# for a project that appears at the top of each page and should give viewer 39# a quick idea about the purpose of the project. Keep the description short. 40 41PROJECT_BRIEF = 42 43# With the PROJECT_LOGO tag one can specify an logo or icon that is 44# included in the documentation. The maximum height of the logo should not 45# exceed 55 pixels and the maximum width should not exceed 200 pixels. 46# Doxygen will copy the logo to the output directory. 47 48PROJECT_LOGO = 49 50# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 51# base path where the generated documentation will be put. 52# If a relative path is entered, it will be relative to the location 53# where doxygen was started. If left blank the current directory will be used. 54 55OUTPUT_DIRECTORY = ../../generated/doxygen 56 57# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 58# 4096 sub-directories (in 2 levels) under the output directory of each output 59# format and will distribute the generated files over these directories. 60# Enabling this option can be useful when feeding doxygen a huge amount of 61# source files, where putting all generated files in the same directory would 62# otherwise cause performance problems for the file system. 63 64CREATE_SUBDIRS = NO 65 66# The OUTPUT_LANGUAGE tag is used to specify the language in which all 67# documentation generated by doxygen is written. Doxygen will use this 68# information to generate all constant output in the proper language. 69# The default language is English, other supported languages are: 70# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 71# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 72# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 73# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 74# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, 75# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 76 77OUTPUT_LANGUAGE = English 78 79# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 80# include brief member descriptions after the members that are listed in 81# the file and class documentation (similar to JavaDoc). 82# Set to NO to disable this. 83 84BRIEF_MEMBER_DESC = YES 85 86# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 87# the brief description of a member or function before the detailed description. 88# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 89# brief descriptions will be completely suppressed. 90 91REPEAT_BRIEF = YES 92 93# This tag implements a quasi-intelligent brief description abbreviator 94# that is used to form the text in various listings. Each string 95# in this list, if found as the leading text of the brief description, will be 96# stripped from the text and the result after processing the whole list, is 97# used as the annotated text. Otherwise, the brief description is used as-is. 98# If left blank, the following values are used ("$name" is automatically 99# replaced with the name of the entity): "The $name class" "The $name widget" 100# "The $name file" "is" "provides" "specifies" "contains" 101# "represents" "a" "an" "the" 102 103ABBREVIATE_BRIEF = 104 105# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 106# Doxygen will generate a detailed section even if there is only a brief 107# description. 108 109ALWAYS_DETAILED_SEC = NO 110 111# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 112# inherited members of a class in the documentation of that class as if those 113# members were ordinary class members. Constructors, destructors and assignment 114# operators of the base classes will not be shown. 115 116INLINE_INHERITED_MEMB = YES 117 118# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 119# path before files name in the file list and in the header files. If set 120# to NO the shortest path that makes the file name unique will be used. 121 122FULL_PATH_NAMES = NO 123 124# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 125# can be used to strip a user-defined part of the path. Stripping is 126# only done if one of the specified strings matches the left-hand part of 127# the path. The tag can be used to show relative paths in the file list. 128# If left blank the directory from which doxygen is run is used as the 129# path to strip. 130 131STRIP_FROM_PATH = 132 133# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 134# the path mentioned in the documentation of a class, which tells 135# the reader which header file to include in order to use a class. 136# If left blank only the name of the header file containing the class 137# definition is used. Otherwise one should specify the include paths that 138# are normally passed to the compiler using the -I flag. 139 140STRIP_FROM_INC_PATH = 141 142# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 143# (but less readable) file names. This can be useful if your file system 144# doesn't support long names like on DOS, Mac, or CD-ROM. 145 146SHORT_NAMES = NO 147 148# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 149# will interpret the first line (until the first dot) of a JavaDoc-style 150# comment as the brief description. If set to NO, the JavaDoc 151# comments will behave just like regular Qt-style comments 152# (thus requiring an explicit @brief command for a brief description.) 153 154JAVADOC_AUTOBRIEF = NO 155 156# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 157# interpret the first line (until the first dot) of a Qt-style 158# comment as the brief description. If set to NO, the comments 159# will behave just like regular Qt-style comments (thus requiring 160# an explicit \brief command for a brief description.) 161 162QT_AUTOBRIEF = NO 163 164# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 165# treat a multi-line C++ special comment block (i.e. a block of //! or /// 166# comments) as a brief description. This used to be the default behaviour. 167# The new default is to treat a multi-line C++ comment block as a detailed 168# description. Set this tag to YES if you prefer the old behaviour instead. 169 170MULTILINE_CPP_IS_BRIEF = NO 171 172# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 173# member inherits the documentation from any documented member that it 174# re-implements. 175 176INHERIT_DOCS = YES 177 178# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 179# a new page for each member. If set to NO, the documentation of a member will 180# be part of the file/class/namespace that contains it. 181 182SEPARATE_MEMBER_PAGES = NO 183 184# The TAB_SIZE tag can be used to set the number of spaces in a tab. 185# Doxygen uses this value to replace tabs by spaces in code fragments. 186 187TAB_SIZE = 4 188 189# This tag can be used to specify a number of aliases that acts 190# as commands in the documentation. An alias has the form "name=value". 191# For example adding "sideeffect=\par Side Effects:\n" will allow you to 192# put the command \sideeffect (or @sideeffect) in the documentation, which 193# will result in a user-defined paragraph with heading "Side Effects:". 194# You can put \n's in the value part of an alias to insert newlines. 195 196ALIASES = "key{1}=<span class=\"keycap\">\1</span>" 197 198# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 199# sources only. Doxygen will then generate output that is more tailored for C. 200# For instance, some of the names that are used will be different. The list 201# of all members will be omitted, etc. 202 203OPTIMIZE_OUTPUT_FOR_C = NO 204 205# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 206# sources only. Doxygen will then generate output that is more tailored for 207# Java. For instance, namespaces will be presented as packages, qualified 208# scopes will look different, etc. 209 210OPTIMIZE_OUTPUT_JAVA = NO 211 212# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 213# sources only. Doxygen will then generate output that is more tailored for 214# Fortran. 215 216OPTIMIZE_FOR_FORTRAN = NO 217 218# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 219# sources. Doxygen will then generate output that is tailored for 220# VHDL. 221 222OPTIMIZE_OUTPUT_VHDL = NO 223 224# Doxygen selects the parser to use depending on the extension of the files it 225# parses. With this tag you can assign which parser to use for a given extension. 226# Doxygen has a built-in mapping, but you can override or extend it using this 227# tag. The format is ext=language, where ext is a file extension, and language 228# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, 229# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make 230# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C 231# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions 232# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. 233 234EXTENSION_MAPPING = 235 236# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 237# to include (a tag file for) the STL sources as input, then you should 238# set this tag to YES in order to let doxygen match functions declarations and 239# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 240# func(std::string) {}). This also makes the inheritance and collaboration 241# diagrams that involve STL classes more complete and accurate. 242 243BUILTIN_STL_SUPPORT = NO 244 245# If you use Microsoft's C++/CLI language, you should set this option to YES to 246# enable parsing support. 247 248CPP_CLI_SUPPORT = NO 249 250# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 251# Doxygen will parse them like normal C++ but will assume all classes use public 252# instead of private inheritance when no explicit protection keyword is present. 253 254SIP_SUPPORT = NO 255 256# For Microsoft's IDL there are propget and propput attributes to indicate getter 257# and setter methods for a property. Setting this option to YES (the default) 258# will make doxygen replace the get and set methods by a property in the 259# documentation. This will only work if the methods are indeed getting or 260# setting a simple type. If this is not the case, or you want to show the 261# methods anyway, you should set this option to NO. 262 263IDL_PROPERTY_SUPPORT = YES 264 265# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 266# tag is set to YES, then doxygen will reuse the documentation of the first 267# member in the group (if any) for the other members of the group. By default 268# all members of a group must be documented explicitly. 269 270DISTRIBUTE_GROUP_DOC = NO 271 272# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 273# the same type (for instance a group of public functions) to be put as a 274# subgroup of that type (e.g. under the Public Functions section). Set it to 275# NO to prevent subgrouping. Alternatively, this can be done per class using 276# the \nosubgrouping command. 277 278SUBGROUPING = YES 279 280# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and 281# unions are shown inside the group in which they are included (e.g. using 282# @ingroup) instead of on a separate page (for HTML and Man pages) or 283# section (for LaTeX and RTF). 284 285INLINE_GROUPED_CLASSES = NO 286 287# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and 288# unions with only public data fields will be shown inline in the documentation 289# of the scope in which they are defined (i.e. file, namespace, or group 290# documentation), provided this scope is documented. If set to NO (the default), 291# structs, classes, and unions are shown on a separate page (for HTML and Man 292# pages) or section (for LaTeX and RTF). 293 294INLINE_SIMPLE_STRUCTS = NO 295 296# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 297# is documented as struct, union, or enum with the name of the typedef. So 298# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 299# with name TypeT. When disabled the typedef will appear as a member of a file, 300# namespace, or class. And the struct will be named TypeS. This can typically 301# be useful for C code in case the coding convention dictates that all compound 302# types are typedef'ed and only the typedef is referenced, never the tag name. 303 304TYPEDEF_HIDES_STRUCT = NO 305 306# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 307# determine which symbols to keep in memory and which to flush to disk. 308# When the cache is full, less often used symbols will be written to disk. 309# For small to medium size projects (<1000 input files) the default value is 310# probably good enough. For larger projects a too small cache size can cause 311# doxygen to be busy swapping symbols to and from disk most of the time 312# causing a significant performance penalty. 313# If the system has enough physical memory increasing the cache will improve the 314# performance by keeping more symbols in memory. Note that the value works on 315# a logarithmic scale so increasing the size by one will roughly double the 316# memory usage. The cache size is given by this formula: 317# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 318# corresponding to a cache size of 2^16 = 65536 symbols 319 320SYMBOL_CACHE_SIZE = 0 321 322#--------------------------------------------------------------------------- 323# Build related configuration options 324#--------------------------------------------------------------------------- 325 326# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 327# documentation are documented, even if no documentation was available. 328# Private class members and static file members will be hidden unless 329# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 330 331EXTRACT_ALL = NO 332 333# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 334# will be included in the documentation. 335 336EXTRACT_PRIVATE = NO 337 338# If the EXTRACT_STATIC tag is set to YES all static members of a file 339# will be included in the documentation. 340 341EXTRACT_STATIC = YES 342 343# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 344# defined locally in source files will be included in the documentation. 345# If set to NO only classes defined in header files are included. 346 347EXTRACT_LOCAL_CLASSES = NO 348 349# This flag is only useful for Objective-C code. When set to YES local 350# methods, which are defined in the implementation section but not in 351# the interface are included in the documentation. 352# If set to NO (the default) only methods in the interface are included. 353 354EXTRACT_LOCAL_METHODS = NO 355 356# If this flag is set to YES, the members of anonymous namespaces will be 357# extracted and appear in the documentation as a namespace called 358# 'anonymous_namespace{file}', where file will be replaced with the base 359# name of the file that contains the anonymous namespace. By default 360# anonymous namespaces are hidden. 361 362EXTRACT_ANON_NSPACES = NO 363 364# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 365# undocumented members of documented classes, files or namespaces. 366# If set to NO (the default) these members will be included in the 367# various overviews, but no documentation section is generated. 368# This option has no effect if EXTRACT_ALL is enabled. 369 370HIDE_UNDOC_MEMBERS = YES 371 372# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 373# undocumented classes that are normally visible in the class hierarchy. 374# If set to NO (the default) these classes will be included in the various 375# overviews. This option has no effect if EXTRACT_ALL is enabled. 376 377HIDE_UNDOC_CLASSES = YES 378 379# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 380# friend (class|struct|union) declarations. 381# If set to NO (the default) these declarations will be included in the 382# documentation. 383 384HIDE_FRIEND_COMPOUNDS = YES 385 386# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 387# documentation blocks found inside the body of a function. 388# If set to NO (the default) these blocks will be appended to the 389# function's detailed documentation block. 390 391HIDE_IN_BODY_DOCS = NO 392 393# The INTERNAL_DOCS tag determines if documentation 394# that is typed after a \internal command is included. If the tag is set 395# to NO (the default) then the documentation will be excluded. 396# Set it to YES to include the internal documentation. 397 398INTERNAL_DOCS = NO 399 400# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 401# file names in lower-case letters. If set to YES upper-case letters are also 402# allowed. This is useful if you have classes or files whose names only differ 403# in case and if your file system supports case sensitive file names. Windows 404# and Mac users are advised to set this option to NO. 405 406CASE_SENSE_NAMES = YES 407 408# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 409# will show members with their full class and namespace scopes in the 410# documentation. If set to YES the scope will be hidden. 411 412HIDE_SCOPE_NAMES = NO 413 414# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 415# will put a list of the files that are included by a file in the documentation 416# of that file. 417 418SHOW_INCLUDE_FILES = NO 419 420# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 421# will list include files with double quotes in the documentation 422# rather than with sharp brackets. 423 424FORCE_LOCAL_INCLUDES = NO 425 426# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 427# is inserted in the documentation for inline members. 428 429INLINE_INFO = YES 430 431# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 432# will sort the (detailed) documentation of file and class members 433# alphabetically by member name. If set to NO the members will appear in 434# declaration order. 435 436SORT_MEMBER_DOCS = YES 437 438# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 439# brief documentation of file, namespace and class members alphabetically 440# by member name. If set to NO (the default) the members will appear in 441# declaration order. 442 443SORT_BRIEF_DOCS = YES 444 445# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 446# will sort the (brief and detailed) documentation of class members so that 447# constructors and destructors are listed first. If set to NO (the default) 448# the constructors will appear in the respective orders defined by 449# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 450# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 451# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 452 453SORT_MEMBERS_CTORS_1ST = YES 454 455# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 456# hierarchy of group names into alphabetical order. If set to NO (the default) 457# the group names will appear in their defined order. 458 459SORT_GROUP_NAMES = NO 460 461# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 462# sorted by fully-qualified names, including namespaces. If set to 463# NO (the default), the class list will be sorted only by class name, 464# not including the namespace part. 465# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 466# Note: This option applies only to the class list, not to the 467# alphabetical list. 468 469SORT_BY_SCOPE_NAME = NO 470 471# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to 472# do proper type resolution of all parameters of a function it will reject a 473# match between the prototype and the implementation of a member function even 474# if there is only one candidate or it is obvious which candidate to choose 475# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen 476# will still accept a match between prototype and implementation in such cases. 477 478STRICT_PROTO_MATCHING = NO 479 480# The GENERATE_TODOLIST tag can be used to enable (YES) or 481# disable (NO) the todo list. This list is created by putting \todo 482# commands in the documentation. 483 484GENERATE_TODOLIST = NO 485 486# The GENERATE_TESTLIST tag can be used to enable (YES) or 487# disable (NO) the test list. This list is created by putting \test 488# commands in the documentation. 489 490GENERATE_TESTLIST = NO 491 492# The GENERATE_BUGLIST tag can be used to enable (YES) or 493# disable (NO) the bug list. This list is created by putting \bug 494# commands in the documentation. 495 496GENERATE_BUGLIST = NO 497 498# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 499# disable (NO) the deprecated list. This list is created by putting 500# \deprecated commands in the documentation. 501 502GENERATE_DEPRECATEDLIST= NO 503 504# The ENABLED_SECTIONS tag can be used to enable conditional 505# documentation sections, marked by \if sectionname ... \endif. 506 507ENABLED_SECTIONS = 508 509# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 510# the initial value of a variable or macro consists of for it to appear in 511# the documentation. If the initializer consists of more lines than specified 512# here it will be hidden. Use a value of 0 to hide initializers completely. 513# The appearance of the initializer of individual variables and macros in the 514# documentation can be controlled using \showinitializer or \hideinitializer 515# command in the documentation regardless of this setting. 516 517MAX_INITIALIZER_LINES = 30 518 519# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 520# at the bottom of the documentation of classes and structs. If set to YES the 521# list will mention the files that were used to generate the documentation. 522 523SHOW_USED_FILES = NO 524 525# If the sources in your project are distributed over multiple directories 526# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 527# in the documentation. The default is NO. 528 529SHOW_DIRECTORIES = NO 530 531# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 532# This will remove the Files entry from the Quick Index and from the 533# Folder Tree View (if specified). The default is YES. 534 535SHOW_FILES = YES 536 537# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 538# Namespaces page. 539# This will remove the Namespaces entry from the Quick Index 540# and from the Folder Tree View (if specified). The default is YES. 541 542SHOW_NAMESPACES = YES 543 544# The FILE_VERSION_FILTER tag can be used to specify a program or script that 545# doxygen should invoke to get the current version for each file (typically from 546# the version control system). Doxygen will invoke the program by executing (via 547# popen()) the command <command> <input-file>, where <command> is the value of 548# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 549# provided by doxygen. Whatever the program writes to standard output 550# is used as the file version. See the manual for examples. 551 552FILE_VERSION_FILTER = 553 554# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 555# by doxygen. The layout file controls the global structure of the generated 556# output files in an output format independent way. The create the layout file 557# that represents doxygen's defaults, run doxygen with the -l option. 558# You can optionally specify a file name after the option, if omitted 559# DoxygenLayout.xml will be used as the name of the layout file. 560 561LAYOUT_FILE = 562 563# The CITE_BIB_FILES tag can be used to specify one or more bib files 564# containing the references data. This must be a list of .bib files. The 565# .bib extension is automatically appended if omitted. Using this command 566# requires the bibtex tool to be installed. See also 567# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style 568# of the bibliography can be controlled using LATEX_BIB_STYLE. 569 570CITE_BIB_FILES = 571 572#--------------------------------------------------------------------------- 573# configuration options related to warning and progress messages 574#--------------------------------------------------------------------------- 575 576# The QUIET tag can be used to turn on/off the messages that are generated 577# by doxygen. Possible values are YES and NO. If left blank NO is used. 578 579QUIET = YES 580 581# The WARNINGS tag can be used to turn on/off the warning messages that are 582# generated by doxygen. Possible values are YES and NO. If left blank 583# NO is used. 584 585WARNINGS = YES 586 587# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 588# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 589# automatically be disabled. 590 591WARN_IF_UNDOCUMENTED = YES 592 593# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 594# potential errors in the documentation, such as not documenting some 595# parameters in a documented function, or documenting parameters that 596# don't exist or using markup commands wrongly. 597 598WARN_IF_DOC_ERROR = YES 599 600# The WARN_NO_PARAMDOC option can be enabled to get warnings for 601# functions that are documented, but have no documentation for their parameters 602# or return value. If set to NO (the default) doxygen will only warn about 603# wrong or incomplete parameter documentation, but not about the absence of 604# documentation. 605 606WARN_NO_PARAMDOC = NO 607 608# The WARN_FORMAT tag determines the format of the warning messages that 609# doxygen can produce. The string should contain the $file, $line, and $text 610# tags, which will be replaced by the file and line number from which the 611# warning originated and the warning text. Optionally the format may contain 612# $version, which will be replaced by the version of the file (if it could 613# be obtained via FILE_VERSION_FILTER) 614 615WARN_FORMAT = "$file:$line: $text" 616 617# The WARN_LOGFILE tag can be used to specify a file to which warning 618# and error messages should be written. If left blank the output is written 619# to stderr. 620 621WARN_LOGFILE = 622 623#--------------------------------------------------------------------------- 624# configuration options related to the input files 625#--------------------------------------------------------------------------- 626 627# The INPUT tag can be used to specify the files and/or directories that contain 628# documented source files. You may enter file names like "myfile.cpp" or 629# directories like "/usr/src/myproject". Separate the files or directories 630# with spaces. 631 632INPUT = . \ 633 app \ 634 drivers \ 635 game \ 636 interface \ 637 keyboard \ 638 locale \ 639 media \ 640 midi \ 641 midi2 \ 642 storage \ 643 support \ 644 translation \ 645 ../../headers/os/app \ 646 ../../headers/os/drivers/fs_interface.h \ 647 ../../headers/os/drivers/USB3.h \ 648 ../../headers/os/drivers/USB_spec.h \ 649 ../../headers/os/game \ 650 ../../headers/os/interface \ 651 ../../headers/os/locale \ 652 ../../headers/os/media \ 653 ../../headers/os/midi2 \ 654 ../../headers/os/storage \ 655 ../../headers/os/support \ 656 ../../headers/os/translation \ 657 ../../headers/posix/syslog.h \ 658 ../../src/kits/game/GameProducer.h 659 660# This tag can be used to specify the character encoding of the source files 661# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 662# also the default input encoding. Doxygen uses libiconv (or the iconv built 663# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 664# the list of possible encodings. 665 666INPUT_ENCODING = UTF-8 667 668# If the value of the INPUT tag contains directories, you can use the 669# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 670# and *.h) to filter out the source-files in the directories. If left 671# blank the following patterns are tested: 672# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh 673# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py 674# *.f90 *.f *.for *.vhd *.vhdl 675 676FILE_PATTERNS = *.dox \ 677 *.h \ 678 *.c \ 679 *.cpp 680 681# The RECURSIVE tag can be used to turn specify whether or not subdirectories 682# should be searched for input files as well. Possible values are YES and NO. 683# If left blank NO is used. 684 685RECURSIVE = NO 686 687# The EXCLUDE tag can be used to specify files and/or directories that should 688# excluded from the INPUT source files. This way you can easily exclude a 689# subdirectory from a directory tree whose root is specified with the INPUT tag. 690# Note that relative paths are relative to directory from which doxygen is run. 691 692EXCLUDE = 693 694# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 695# directories that are symbolic links (a Unix file system feature) are excluded 696# from the input. 697 698EXCLUDE_SYMLINKS = NO 699 700# If the value of the INPUT tag contains directories, you can use the 701# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 702# certain files from those directories. Note that the wildcards are matched 703# against the file with absolute path, so to exclude all test directories 704# for example use the pattern */test/* 705 706EXCLUDE_PATTERNS = */libkernelppp/_KPPP* 707 708# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 709# (namespaces, classes, functions, etc.) that should be excluded from the 710# output. The symbol name can be a fully qualified name, a word, or if the 711# wildcard * is used, a substring. Examples: ANamespace, AClass, 712# AClass::ANamespace, ANamespace::*Test 713 714EXCLUDE_SYMBOLS = 715 716# The EXAMPLE_PATH tag can be used to specify one or more files or 717# directories that contain example code fragments that are included (see 718# the \include command). 719 720EXAMPLE_PATH = 721 722# If the value of the EXAMPLE_PATH tag contains directories, you can use the 723# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 724# and *.h) to filter out the source-files in the directories. If left 725# blank all files are included. 726 727EXAMPLE_PATTERNS = 728 729# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 730# searched for input files to be used with the \include or \dontinclude 731# commands irrespective of the value of the RECURSIVE tag. 732# Possible values are YES and NO. If left blank NO is used. 733 734EXAMPLE_RECURSIVE = NO 735 736# The IMAGE_PATH tag can be used to specify one or more files or 737# directories that contain image that are included in the documentation (see 738# the \image command). 739 740IMAGE_PATH = . \ 741 interface \ 742 keyboard \ 743 midi2 \ 744 storage 745 746# The INPUT_FILTER tag can be used to specify a program that doxygen should 747# invoke to filter for each input file. Doxygen will invoke the filter program 748# by executing (via popen()) the command <filter> <input-file>, where <filter> 749# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 750# input file. Doxygen will then use the output that the filter program writes 751# to standard output. 752# If FILTER_PATTERNS is specified, this tag will be 753# ignored. 754 755INPUT_FILTER = 756 757# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 758# basis. 759# Doxygen will compare the file name with each pattern and apply the 760# filter if there is a match. 761# The filters are a list of the form: 762# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 763# info on how filters are used. If FILTER_PATTERNS is empty or if 764# non of the patterns match the file name, INPUT_FILTER is applied. 765 766FILTER_PATTERNS = 767 768# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 769# INPUT_FILTER) will be used to filter the input files when producing source 770# files to browse (i.e. when SOURCE_BROWSER is set to YES). 771 772FILTER_SOURCE_FILES = NO 773 774# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 775# pattern. A pattern will override the setting for FILTER_PATTERN (if any) 776# and it is also possible to disable source filtering for a specific pattern 777# using *.ext= (so without naming a filter). This option only has effect when 778# FILTER_SOURCE_FILES is enabled. 779 780FILTER_SOURCE_PATTERNS = 781 782#--------------------------------------------------------------------------- 783# configuration options related to source browsing 784#--------------------------------------------------------------------------- 785 786# If the SOURCE_BROWSER tag is set to YES then a list of source files will 787# be generated. Documented entities will be cross-referenced with these sources. 788# Note: To get rid of all source code in the generated output, make sure also 789# VERBATIM_HEADERS is set to NO. 790 791SOURCE_BROWSER = NO 792 793# Setting the INLINE_SOURCES tag to YES will include the body 794# of functions and classes directly in the documentation. 795 796INLINE_SOURCES = NO 797 798# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 799# doxygen to hide any special comment blocks from generated source code 800# fragments. Normal C and C++ comments will always remain visible. 801 802STRIP_CODE_COMMENTS = YES 803 804# If the REFERENCED_BY_RELATION tag is set to YES 805# then for each documented function all documented 806# functions referencing it will be listed. 807 808REFERENCED_BY_RELATION = YES 809 810# If the REFERENCES_RELATION tag is set to YES 811# then for each documented function all documented entities 812# called/used by that function will be listed. 813 814REFERENCES_RELATION = YES 815 816# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 817# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 818# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 819# link to the source code. 820# Otherwise they will link to the documentation. 821 822REFERENCES_LINK_SOURCE = NO 823 824# If the USE_HTAGS tag is set to YES then the references to source code 825# will point to the HTML generated by the htags(1) tool instead of doxygen 826# built-in source browser. The htags tool is part of GNU's global source 827# tagging system (see http://www.gnu.org/software/global/global.html). You 828# will need version 4.8.6 or higher. 829 830USE_HTAGS = NO 831 832# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 833# will generate a verbatim copy of the header file for each class for 834# which an include is specified. Set to NO to disable this. 835 836VERBATIM_HEADERS = NO 837 838#--------------------------------------------------------------------------- 839# configuration options related to the alphabetical class index 840#--------------------------------------------------------------------------- 841 842# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 843# of all compounds will be generated. Enable this if the project 844# contains a lot of classes, structs, unions or interfaces. 845 846ALPHABETICAL_INDEX = NO 847 848# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 849# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 850# in which this list will be split (can be a number in the range [1..20]) 851 852COLS_IN_ALPHA_INDEX = 5 853 854# In case all classes in a project start with a common prefix, all 855# classes will be put under the same header in the alphabetical index. 856# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 857# should be ignored while generating the index headers. 858 859IGNORE_PREFIX = 860 861#--------------------------------------------------------------------------- 862# configuration options related to the HTML output 863#--------------------------------------------------------------------------- 864 865# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 866# generate HTML output. 867 868GENERATE_HTML = YES 869 870# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 871# If a relative path is entered the value of OUTPUT_DIRECTORY will be 872# put in front of it. If left blank `html' will be used as the default path. 873 874HTML_OUTPUT = html 875 876# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 877# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 878# doxygen will generate files with .html extension. 879 880HTML_FILE_EXTENSION = .html 881 882# The HTML_HEADER tag can be used to specify a personal HTML header for 883# each generated HTML page. If it is left blank doxygen will generate a 884# standard header. Note that when using a custom header you are responsible 885# for the proper inclusion of any scripts and style sheets that doxygen 886# needs, which is dependent on the configuration options used. 887# It is adviced to generate a default header using "doxygen -w html 888# header.html footer.html stylesheet.css YourConfigFile" and then modify 889# that header. Note that the header is subject to change so you typically 890# have to redo this when upgrading to a newer version of doxygen or when 891# changing the value of configuration settings such as GENERATE_TREEVIEW! 892 893HTML_HEADER = header.html 894 895# The HTML_FOOTER tag can be used to specify a personal HTML footer for 896# each generated HTML page. If it is left blank doxygen will generate a 897# standard footer. 898 899HTML_FOOTER = footer.html 900 901# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 902# style sheet that is used by each HTML page. It can be used to 903# fine-tune the look of the HTML output. If the tag is left blank doxygen 904# will generate a default style sheet. Note that doxygen will try to copy 905# the style sheet file to the HTML output directory, so don't put your own 906# stylesheet in the HTML output directory as well, or it will be erased! 907 908HTML_STYLESHEET = book.css 909 910# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 911# other source files which should be copied to the HTML output directory. Note 912# that these files will be copied to the base HTML output directory. Use the 913# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 914# files. In the HTML_STYLESHEET file, use the file name only. Also note that 915# the files will be copied as-is; there are no commands or markers available. 916 917HTML_EXTRA_FILES = 918 919# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 920# Doxygen will adjust the colors in the stylesheet and background images 921# according to this color. Hue is specified as an angle on a colorwheel, 922# see http://en.wikipedia.org/wiki/Hue for more information. 923# For instance the value 0 represents red, 60 is yellow, 120 is green, 924# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 925# The allowed range is 0 to 359. 926 927HTML_COLORSTYLE_HUE = 220 928 929# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 930# the colors in the HTML output. For a value of 0 the output will use 931# grayscales only. A value of 255 will produce the most vivid colors. 932 933HTML_COLORSTYLE_SAT = 100 934 935# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 936# the luminance component of the colors in the HTML output. Values below 937# 100 gradually make the output lighter, whereas values above 100 make 938# the output darker. The value divided by 100 is the actual gamma applied, 939# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 940# and 100 does not change the gamma. 941 942HTML_COLORSTYLE_GAMMA = 80 943 944# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 945# page will contain the date and time when the page was generated. Setting 946# this to NO can help when comparing the output of multiple runs. 947 948HTML_TIMESTAMP = YES 949 950# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 951# files or namespaces will be aligned in HTML using tables. If set to 952# NO a bullet list will be used. 953 954HTML_ALIGN_MEMBERS = YES 955 956# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 957# documentation will contain sections that can be hidden and shown after the 958# page has loaded. For this to work a browser that supports 959# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 960# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 961 962HTML_DYNAMIC_SECTIONS = NO 963 964# If the GENERATE_DOCSET tag is set to YES, additional index files 965# will be generated that can be used as input for Apple's Xcode 3 966# integrated development environment, introduced with OSX 10.5 (Leopard). 967# To create a documentation set, doxygen will generate a Makefile in the 968# HTML output directory. Running make will produce the docset in that 969# directory and running "make install" will install the docset in 970# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 971# it at startup. 972# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 973# for more information. 974 975GENERATE_DOCSET = NO 976 977# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 978# feed. A documentation feed provides an umbrella under which multiple 979# documentation sets from a single provider (such as a company or product suite) 980# can be grouped. 981 982DOCSET_FEEDNAME = "Doxygen generated docs" 983 984# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 985# should uniquely identify the documentation set bundle. This should be a 986# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 987# will append .docset to the name. 988 989DOCSET_BUNDLE_ID = org.doxygen.Project 990 991# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify 992# the documentation publisher. This should be a reverse domain-name style 993# string, e.g. com.mycompany.MyDocSet.documentation. 994 995DOCSET_PUBLISHER_ID = org.doxygen.Publisher 996 997# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. 998 999DOCSET_PUBLISHER_NAME = Publisher 1000 1001# If the GENERATE_HTMLHELP tag is set to YES, additional index files 1002# will be generated that can be used as input for tools like the 1003# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 1004# of the generated HTML documentation. 1005 1006GENERATE_HTMLHELP = NO 1007 1008# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 1009# be used to specify the file name of the resulting .chm file. You 1010# can add a path in front of the file if the result should not be 1011# written to the html output directory. 1012 1013CHM_FILE = 1014 1015# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 1016# be used to specify the location (absolute path including file name) of 1017# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 1018# the HTML help compiler on the generated index.hhp. 1019 1020HHC_LOCATION = 1021 1022# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 1023# controls if a separate .chi index file is generated (YES) or that 1024# it should be included in the master .chm file (NO). 1025 1026GENERATE_CHI = NO 1027 1028# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 1029# is used to encode HtmlHelp index (hhk), content (hhc) and project file 1030# content. 1031 1032CHM_INDEX_ENCODING = 1033 1034# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 1035# controls whether a binary table of contents is generated (YES) or a 1036# normal table of contents (NO) in the .chm file. 1037 1038BINARY_TOC = NO 1039 1040# The TOC_EXPAND flag can be set to YES to add extra items for group members 1041# to the contents of the HTML help documentation and to the tree view. 1042 1043TOC_EXPAND = NO 1044 1045# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 1046# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 1047# that can be used as input for Qt's qhelpgenerator to generate a 1048# Qt Compressed Help (.qch) of the generated HTML documentation. 1049 1050GENERATE_QHP = NO 1051 1052# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 1053# be used to specify the file name of the resulting .qch file. 1054# The path specified is relative to the HTML output folder. 1055 1056QCH_FILE = 1057 1058# The QHP_NAMESPACE tag specifies the namespace to use when generating 1059# Qt Help Project output. For more information please see 1060# http://doc.trolltech.com/qthelpproject.html#namespace 1061 1062QHP_NAMESPACE = org.doxygen.Project 1063 1064# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 1065# Qt Help Project output. For more information please see 1066# http://doc.trolltech.com/qthelpproject.html#virtual-folders 1067 1068QHP_VIRTUAL_FOLDER = doc 1069 1070# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 1071# add. For more information please see 1072# http://doc.trolltech.com/qthelpproject.html#custom-filters 1073 1074QHP_CUST_FILTER_NAME = 1075 1076# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 1077# custom filter to add. For more information please see 1078# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> 1079# Qt Help Project / Custom Filters</a>. 1080 1081QHP_CUST_FILTER_ATTRS = 1082 1083# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 1084# project's 1085# filter section matches. 1086# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> 1087# Qt Help Project / Filter Attributes</a>. 1088 1089QHP_SECT_FILTER_ATTRS = 1090 1091# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 1092# be used to specify the location of Qt's qhelpgenerator. 1093# If non-empty doxygen will try to run qhelpgenerator on the generated 1094# .qhp file. 1095 1096QHG_LOCATION = 1097 1098# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files 1099# will be generated, which together with the HTML files, form an Eclipse help 1100# plugin. To install this plugin and make it available under the help contents 1101# menu in Eclipse, the contents of the directory containing the HTML and XML 1102# files needs to be copied into the plugins directory of eclipse. The name of 1103# the directory within the plugins directory should be the same as 1104# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 1105# the help appears. 1106 1107GENERATE_ECLIPSEHELP = NO 1108 1109# A unique identifier for the eclipse help plugin. When installing the plugin 1110# the directory name containing the HTML and XML files should also have 1111# this name. 1112 1113ECLIPSE_DOC_ID = org.doxygen.Project 1114 1115# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 1116# top of each HTML page. The value NO (the default) enables the index and 1117# the value YES disables it. 1118 1119DISABLE_INDEX = NO 1120 1121# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values 1122# (range [0,1..20]) that doxygen will group on one line in the generated HTML 1123# documentation. Note that a value of 0 will completely suppress the enum 1124# values from appearing in the overview section. 1125 1126ENUM_VALUES_PER_LINE = 1 1127 1128# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 1129# structure should be generated to display hierarchical information. 1130# If the tag value is set to YES, a side panel will be generated 1131# containing a tree-like index structure (just like the one that 1132# is generated for HTML Help). For this to work a browser that supports 1133# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 1134# Windows users are probably better off using the HTML help feature. 1135 1136GENERATE_TREEVIEW = NO 1137 1138# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 1139# and Class Hierarchy pages using a tree view instead of an ordered list. 1140 1141USE_INLINE_TREES = NO 1142 1143# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 1144# used to set the initial width (in pixels) of the frame in which the tree 1145# is shown. 1146 1147TREEVIEW_WIDTH = 250 1148 1149# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 1150# links to external symbols imported via tag files in a separate window. 1151 1152EXT_LINKS_IN_WINDOW = NO 1153 1154# Use this tag to change the font size of Latex formulas included 1155# as images in the HTML documentation. The default is 10. Note that 1156# when you change the font size after a successful doxygen run you need 1157# to manually remove any form_*.png images from the HTML output directory 1158# to force them to be regenerated. 1159 1160FORMULA_FONTSIZE = 10 1161 1162# Use the FORMULA_TRANPARENT tag to determine whether or not the images 1163# generated for formulas are transparent PNGs. Transparent PNGs are 1164# not supported properly for IE 6.0, but are supported on all modern browsers. 1165# Note that when changing this option you need to delete any form_*.png files 1166# in the HTML output before the changes have effect. 1167 1168FORMULA_TRANSPARENT = YES 1169 1170# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax 1171# (see http://www.mathjax.org) which uses client side Javascript for the 1172# rendering instead of using prerendered bitmaps. Use this if you do not 1173# have LaTeX installed or if you want to formulas look prettier in the HTML 1174# output. When enabled you also need to install MathJax separately and 1175# configure the path to it using the MATHJAX_RELPATH option. 1176 1177USE_MATHJAX = NO 1178 1179# When MathJax is enabled you need to specify the location relative to the 1180# HTML output directory using the MATHJAX_RELPATH option. The destination 1181# directory should contain the MathJax.js script. For instance, if the mathjax 1182# directory is located at the same level as the HTML output directory, then 1183# MATHJAX_RELPATH should be ../mathjax. The default value points to the 1184# mathjax.org site, so you can quickly see the result without installing 1185# MathJax, but it is strongly recommended to install a local copy of MathJax 1186# before deployment. 1187 1188MATHJAX_RELPATH = http://www.mathjax.org/mathjax 1189 1190# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension 1191# names that should be enabled during MathJax rendering. 1192 1193MATHJAX_EXTENSIONS = 1194 1195# When the SEARCHENGINE tag is enabled doxygen will generate a search box 1196# for the HTML output. The underlying search engine uses javascript 1197# and DHTML and should work on any modern browser. Note that when using 1198# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 1199# (GENERATE_DOCSET) there is already a search function so this one should 1200# typically be disabled. For large projects the javascript based search engine 1201# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. 1202 1203SEARCHENGINE = NO 1204 1205# When the SERVER_BASED_SEARCH tag is enabled the search engine will be 1206# implemented using a PHP enabled web server instead of at the web client 1207# using Javascript. Doxygen will generate the search PHP script and index 1208# file to put on the web server. The advantage of the server 1209# based approach is that it scales better to large projects and allows 1210# full text search. The disadvantages are that it is more difficult to setup 1211# and does not have live searching capabilities. 1212 1213SERVER_BASED_SEARCH = NO 1214 1215#--------------------------------------------------------------------------- 1216# configuration options related to the LaTeX output 1217#--------------------------------------------------------------------------- 1218 1219# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 1220# generate Latex output. 1221 1222GENERATE_LATEX = NO 1223 1224# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 1225# If a relative path is entered the value of OUTPUT_DIRECTORY will be 1226# put in front of it. If left blank `latex' will be used as the default path. 1227 1228LATEX_OUTPUT = latex 1229 1230# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 1231# invoked. If left blank `latex' will be used as the default command name. 1232# Note that when enabling USE_PDFLATEX this option is only used for 1233# generating bitmaps for formulas in the HTML output, but not in the 1234# Makefile that is written to the output directory. 1235 1236LATEX_CMD_NAME = latex 1237 1238# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 1239# generate index for LaTeX. If left blank `makeindex' will be used as the 1240# default command name. 1241 1242MAKEINDEX_CMD_NAME = makeindex 1243 1244# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 1245# LaTeX documents. This may be useful for small projects and may help to 1246# save some trees in general. 1247 1248COMPACT_LATEX = NO 1249 1250# The PAPER_TYPE tag can be used to set the paper type that is used 1251# by the printer. Possible values are: a4, letter, legal and 1252# executive. If left blank a4wide will be used. 1253 1254PAPER_TYPE = a4wide 1255 1256# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 1257# packages that should be included in the LaTeX output. 1258 1259EXTRA_PACKAGES = 1260 1261# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 1262# the generated latex document. The header should contain everything until 1263# the first chapter. If it is left blank doxygen will generate a 1264# standard header. Notice: only use this tag if you know what you are doing! 1265 1266LATEX_HEADER = 1267 1268# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for 1269# the generated latex document. The footer should contain everything after 1270# the last chapter. If it is left blank doxygen will generate a 1271# standard footer. Notice: only use this tag if you know what you are doing! 1272 1273LATEX_FOOTER = 1274 1275# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 1276# is prepared for conversion to pdf (using ps2pdf). The pdf file will 1277# contain links (just like the HTML output) instead of page references 1278# This makes the output suitable for online browsing using a pdf viewer. 1279 1280PDF_HYPERLINKS = NO 1281 1282# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 1283# plain latex in the generated Makefile. Set this option to YES to get a 1284# higher quality PDF documentation. 1285 1286USE_PDFLATEX = NO 1287 1288# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 1289# command to the generated LaTeX files. This will instruct LaTeX to keep 1290# running if errors occur, instead of asking the user for help. 1291# This option is also used when generating formulas in HTML. 1292 1293LATEX_BATCHMODE = NO 1294 1295# If LATEX_HIDE_INDICES is set to YES then doxygen will not 1296# include the index chapters (such as File Index, Compound Index, etc.) 1297# in the output. 1298 1299LATEX_HIDE_INDICES = NO 1300 1301# If LATEX_SOURCE_CODE is set to YES then doxygen will include 1302# source code with syntax highlighting in the LaTeX output. 1303# Note that which sources are shown also depends on other settings 1304# such as SOURCE_BROWSER. 1305 1306LATEX_SOURCE_CODE = NO 1307 1308# The LATEX_BIB_STYLE tag can be used to specify the style to use for the 1309# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See 1310# http://en.wikipedia.org/wiki/BibTeX for more info. 1311 1312LATEX_BIB_STYLE = plain 1313 1314#--------------------------------------------------------------------------- 1315# configuration options related to the RTF output 1316#--------------------------------------------------------------------------- 1317 1318# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 1319# The RTF output is optimized for Word 97 and may not look very pretty with 1320# other RTF readers or editors. 1321 1322GENERATE_RTF = NO 1323 1324# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 1325# If a relative path is entered the value of OUTPUT_DIRECTORY will be 1326# put in front of it. If left blank `rtf' will be used as the default path. 1327 1328RTF_OUTPUT = rtf 1329 1330# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 1331# RTF documents. This may be useful for small projects and may help to 1332# save some trees in general. 1333 1334COMPACT_RTF = NO 1335 1336# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 1337# will contain hyperlink fields. The RTF file will 1338# contain links (just like the HTML output) instead of page references. 1339# This makes the output suitable for online browsing using WORD or other 1340# programs which support those fields. 1341# Note: wordpad (write) and others do not support links. 1342 1343RTF_HYPERLINKS = NO 1344 1345# Load stylesheet definitions from file. Syntax is similar to doxygen's 1346# config file, i.e. a series of assignments. You only have to provide 1347# replacements, missing definitions are set to their default value. 1348 1349RTF_STYLESHEET_FILE = 1350 1351# Set optional variables used in the generation of an rtf document. 1352# Syntax is similar to doxygen's config file. 1353 1354RTF_EXTENSIONS_FILE = 1355 1356#--------------------------------------------------------------------------- 1357# configuration options related to the man page output 1358#--------------------------------------------------------------------------- 1359 1360# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 1361# generate man pages 1362 1363GENERATE_MAN = NO 1364 1365# The MAN_OUTPUT tag is used to specify where the man pages will be put. 1366# If a relative path is entered the value of OUTPUT_DIRECTORY will be 1367# put in front of it. If left blank `man' will be used as the default path. 1368 1369MAN_OUTPUT = man 1370 1371# The MAN_EXTENSION tag determines the extension that is added to 1372# the generated man pages (default is the subroutine's section .3) 1373 1374MAN_EXTENSION = .3 1375 1376# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 1377# then it will generate one additional man file for each entity 1378# documented in the real man page(s). These additional files 1379# only source the real man page, but without them the man command 1380# would be unable to find the correct page. The default is NO. 1381 1382MAN_LINKS = NO 1383 1384#--------------------------------------------------------------------------- 1385# configuration options related to the XML output 1386#--------------------------------------------------------------------------- 1387 1388# If the GENERATE_XML tag is set to YES Doxygen will 1389# generate an XML file that captures the structure of 1390# the code including all documentation. 1391 1392GENERATE_XML = YES 1393 1394# The XML_OUTPUT tag is used to specify where the XML pages will be put. 1395# If a relative path is entered the value of OUTPUT_DIRECTORY will be 1396# put in front of it. If left blank `xml' will be used as the default path. 1397 1398XML_OUTPUT = xml 1399 1400# The XML_SCHEMA tag can be used to specify an XML schema, 1401# which can be used by a validating XML parser to check the 1402# syntax of the XML files. 1403 1404XML_SCHEMA = 1405 1406# The XML_DTD tag can be used to specify an XML DTD, 1407# which can be used by a validating XML parser to check the 1408# syntax of the XML files. 1409 1410XML_DTD = 1411 1412# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 1413# dump the program listings (including syntax highlighting 1414# and cross-referencing information) to the XML output. Note that 1415# enabling this will significantly increase the size of the XML output. 1416 1417XML_PROGRAMLISTING = YES 1418 1419#--------------------------------------------------------------------------- 1420# configuration options for the AutoGen Definitions output 1421#--------------------------------------------------------------------------- 1422 1423# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 1424# generate an AutoGen Definitions (see autogen.sf.net) file 1425# that captures the structure of the code including all 1426# documentation. Note that this feature is still experimental 1427# and incomplete at the moment. 1428 1429GENERATE_AUTOGEN_DEF = NO 1430 1431#--------------------------------------------------------------------------- 1432# configuration options related to the Perl module output 1433#--------------------------------------------------------------------------- 1434 1435# If the GENERATE_PERLMOD tag is set to YES Doxygen will 1436# generate a Perl module file that captures the structure of 1437# the code including all documentation. Note that this 1438# feature is still experimental and incomplete at the 1439# moment. 1440 1441GENERATE_PERLMOD = NO 1442 1443# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 1444# the necessary Makefile rules, Perl scripts and LaTeX code to be able 1445# to generate PDF and DVI output from the Perl module output. 1446 1447PERLMOD_LATEX = NO 1448 1449# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 1450# nicely formatted so it can be parsed by a human reader. 1451# This is useful 1452# if you want to understand what is going on. 1453# On the other hand, if this 1454# tag is set to NO the size of the Perl module output will be much smaller 1455# and Perl will parse it just the same. 1456 1457PERLMOD_PRETTY = YES 1458 1459# The names of the make variables in the generated doxyrules.make file 1460# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 1461# This is useful so different doxyrules.make files included by the same 1462# Makefile don't overwrite each other's variables. 1463 1464PERLMOD_MAKEVAR_PREFIX = 1465 1466#--------------------------------------------------------------------------- 1467# Configuration options related to the preprocessor 1468#--------------------------------------------------------------------------- 1469 1470# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 1471# evaluate all C-preprocessor directives found in the sources and include 1472# files. 1473 1474ENABLE_PREPROCESSING = YES 1475 1476# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 1477# names in the source code. If set to NO (the default) only conditional 1478# compilation will be performed. Macro expansion can be done in a controlled 1479# way by setting EXPAND_ONLY_PREDEF to YES. 1480 1481MACRO_EXPANSION = NO 1482 1483# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 1484# then the macro expansion is limited to the macros specified with the 1485# PREDEFINED and EXPAND_AS_DEFINED tags. 1486 1487EXPAND_ONLY_PREDEF = NO 1488 1489# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 1490# pointed to by INCLUDE_PATH will be searched when a #include is found. 1491 1492SEARCH_INCLUDES = YES 1493 1494# The INCLUDE_PATH tag can be used to specify one or more directories that 1495# contain include files that are not input files but should be processed by 1496# the preprocessor. 1497 1498INCLUDE_PATH = 1499 1500# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 1501# patterns (like *.h and *.hpp) to filter out the header-files in the 1502# directories. If left blank, the patterns specified with FILE_PATTERNS will 1503# be used. 1504 1505INCLUDE_FILE_PATTERNS = 1506 1507# The PREDEFINED tag can be used to specify one or more macro names that 1508# are defined before the preprocessor is started (similar to the -D option of 1509# gcc). The argument of the tag is a list of macros of the form: name 1510# or name=definition (no spaces). If the definition and the = are 1511# omitted =1 is assumed. To prevent a macro definition from being 1512# undefined via #undef or recursively expanded use the := operator 1513# instead of the = operator. 1514 1515PREDEFINED = __cplusplus \ 1516 _SYS_TYPES_H 1517 1518# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 1519# this tag can be used to specify a list of macro names that should be expanded. 1520# The macro definition that is found in the sources will be used. 1521# Use the PREDEFINED tag if you want to use a different macro definition that 1522# overrules the definition found in the source code. 1523 1524EXPAND_AS_DEFINED = 1525 1526# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 1527# doxygen's preprocessor will remove all references to function-like macros 1528# that are alone on a line, have an all uppercase name, and do not end with a 1529# semicolon, because these will confuse the parser if not removed. 1530 1531SKIP_FUNCTION_MACROS = YES 1532 1533#--------------------------------------------------------------------------- 1534# Configuration::additions related to external references 1535#--------------------------------------------------------------------------- 1536 1537# The TAGFILES option can be used to specify one or more tagfiles. 1538# Optionally an initial location of the external documentation 1539# can be added for each tagfile. The format of a tag file without 1540# this location is as follows: 1541# 1542# TAGFILES = file1 file2 ... 1543# Adding location for the tag files is done as follows: 1544# 1545# TAGFILES = file1=loc1 "file2 = loc2" ... 1546# where "loc1" and "loc2" can be relative or absolute paths or 1547# URLs. If a location is present for each tag, the installdox tool 1548# does not have to be run to correct the links. 1549# Note that each tag file must have a unique name 1550# (where the name does NOT include the path) 1551# If a tag file is not located in the directory in which doxygen 1552# is run, you must also specify the path to the tagfile here. 1553 1554TAGFILES = 1555 1556# When a file name is specified after GENERATE_TAGFILE, doxygen will create 1557# a tag file that is based on the input files it reads. 1558 1559GENERATE_TAGFILE = 1560 1561# If the ALLEXTERNALS tag is set to YES all external classes will be listed 1562# in the class index. If set to NO only the inherited external classes 1563# will be listed. 1564 1565ALLEXTERNALS = NO 1566 1567# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 1568# in the modules index. If set to NO, only the current project's groups will 1569# be listed. 1570 1571EXTERNAL_GROUPS = YES 1572 1573# The PERL_PATH should be the absolute path and name of the perl script 1574# interpreter (i.e. the result of `which perl'). 1575 1576PERL_PATH = /boot/home/config/bin/perl 1577 1578#--------------------------------------------------------------------------- 1579# Configuration options related to the dot tool 1580#--------------------------------------------------------------------------- 1581 1582# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 1583# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 1584# or super classes. Setting the tag to NO turns the diagrams off. Note that 1585# this option also works with HAVE_DOT disabled, but it is recommended to 1586# install and use dot, since it yields more powerful graphs. 1587 1588CLASS_DIAGRAMS = YES 1589 1590# You can define message sequence charts within doxygen comments using the \msc 1591# command. Doxygen will then run the mscgen tool (see 1592# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 1593# documentation. The MSCGEN_PATH tag allows you to specify the directory where 1594# the mscgen tool resides. If left empty the tool is assumed to be found in the 1595# default search path. 1596 1597MSCGEN_PATH = 1598 1599# If set to YES, the inheritance and collaboration graphs will hide 1600# inheritance and usage relations if the target is undocumented 1601# or is not a class. 1602 1603HIDE_UNDOC_RELATIONS = YES 1604 1605# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 1606# available from the path. This tool is part of Graphviz, a graph visualization 1607# toolkit from AT&T and Lucent Bell Labs. The other options in this section 1608# have no effect if this option is set to NO (the default) 1609 1610HAVE_DOT = NO 1611 1612# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 1613# allowed to run in parallel. When set to 0 (the default) doxygen will 1614# base this on the number of processors available in the system. You can set it 1615# explicitly to a value larger than 0 to get control over the balance 1616# between CPU load and processing speed. 1617 1618DOT_NUM_THREADS = 0 1619 1620# By default doxygen will use the Helvetica font for all dot files that 1621# doxygen generates. When you want a differently looking font you can specify 1622# the font name using DOT_FONTNAME. You need to make sure dot is able to find 1623# the font, which can be done by putting it in a standard location or by setting 1624# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the 1625# directory containing the font. 1626 1627DOT_FONTNAME = Helvetica 1628 1629# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 1630# The default size is 10pt. 1631 1632DOT_FONTSIZE = 10 1633 1634# By default doxygen will tell dot to use the Helvetica font. 1635# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to 1636# set the path where dot can find it. 1637 1638DOT_FONTPATH = 1639 1640# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 1641# will generate a graph for each documented class showing the direct and 1642# indirect inheritance relations. Setting this tag to YES will force the 1643# the CLASS_DIAGRAMS tag to NO. 1644 1645CLASS_GRAPH = YES 1646 1647# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 1648# will generate a graph for each documented class showing the direct and 1649# indirect implementation dependencies (inheritance, containment, and 1650# class references variables) of the class with other documented classes. 1651 1652COLLABORATION_GRAPH = YES 1653 1654# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 1655# will generate a graph for groups, showing the direct groups dependencies 1656 1657GROUP_GRAPHS = YES 1658 1659# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 1660# collaboration diagrams in a style similar to the OMG's Unified Modeling 1661# Language. 1662 1663UML_LOOK = NO 1664 1665# If set to YES, the inheritance and collaboration graphs will show the 1666# relations between templates and their instances. 1667 1668TEMPLATE_RELATIONS = YES 1669 1670# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 1671# tags are set to YES then doxygen will generate a graph for each documented 1672# file showing the direct and indirect include dependencies of the file with 1673# other documented files. 1674 1675INCLUDE_GRAPH = NO 1676 1677# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 1678# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 1679# documented header file showing the documented files that directly or 1680# indirectly include this file. 1681 1682INCLUDED_BY_GRAPH = NO 1683 1684# If the CALL_GRAPH and HAVE_DOT options are set to YES then 1685# doxygen will generate a call dependency graph for every global function 1686# or class method. Note that enabling this option will significantly increase 1687# the time of a run. So in most cases it will be better to enable call graphs 1688# for selected functions only using the \callgraph command. 1689 1690CALL_GRAPH = NO 1691 1692# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 1693# doxygen will generate a caller dependency graph for every global function 1694# or class method. Note that enabling this option will significantly increase 1695# the time of a run. So in most cases it will be better to enable caller 1696# graphs for selected functions only using the \callergraph command. 1697 1698CALLER_GRAPH = NO 1699 1700# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 1701# will generate a graphical hierarchy of all classes instead of a textual one. 1702 1703GRAPHICAL_HIERARCHY = YES 1704 1705# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 1706# then doxygen will show the dependencies a directory has on other directories 1707# in a graphical way. The dependency relations are determined by the #include 1708# relations between the files in the directories. 1709 1710DIRECTORY_GRAPH = YES 1711 1712# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 1713# generated by dot. Possible values are svg, png, jpg, or gif. 1714# If left blank png will be used. If you choose svg you need to set 1715# HTML_FILE_EXTENSION to xhtml in order to make the SVG files 1716# visible in IE 9+ (other browsers do not have this requirement). 1717 1718DOT_IMAGE_FORMAT = png 1719 1720# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to 1721# enable generation of interactive SVG images that allow zooming and panning. 1722# Note that this requires a modern browser other than Internet Explorer. 1723# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you 1724# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files 1725# visible. Older versions of IE do not have SVG support. 1726 1727INTERACTIVE_SVG = NO 1728 1729# The tag DOT_PATH can be used to specify the path where the dot tool can be 1730# found. If left blank, it is assumed the dot tool can be found in the path. 1731 1732DOT_PATH = 1733 1734# The DOTFILE_DIRS tag can be used to specify one or more directories that 1735# contain dot files that are included in the documentation (see the 1736# \dotfile command). 1737 1738DOTFILE_DIRS = 1739 1740# The MSCFILE_DIRS tag can be used to specify one or more directories that 1741# contain msc files that are included in the documentation (see the 1742# \mscfile command). 1743 1744MSCFILE_DIRS = 1745 1746# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 1747# nodes that will be shown in the graph. If the number of nodes in a graph 1748# becomes larger than this value, doxygen will truncate the graph, which is 1749# visualized by representing a node as a red box. Note that doxygen if the 1750# number of direct children of the root node in a graph is already larger than 1751# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 1752# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 1753 1754DOT_GRAPH_MAX_NODES = 50 1755 1756# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 1757# graphs generated by dot. A depth value of 3 means that only nodes reachable 1758# from the root by following a path via at most 3 edges will be shown. Nodes 1759# that lay further from the root node will be omitted. Note that setting this 1760# option to 1 or 2 may greatly reduce the computation time needed for large 1761# code bases. Also note that the size of a graph can be further restricted by 1762# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 1763 1764MAX_DOT_GRAPH_DEPTH = 0 1765 1766# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 1767# background. This is disabled by default, because dot on Windows does not 1768# seem to support this out of the box. Warning: Depending on the platform used, 1769# enabling this option may lead to badly anti-aliased labels on the edges of 1770# a graph (i.e. they become hard to read). 1771 1772DOT_TRANSPARENT = NO 1773 1774# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 1775# files in one run (i.e. multiple -o and -T options on the command line). This 1776# makes dot run faster, but since only newer versions of dot (>1.8.10) 1777# support this, this feature is disabled by default. 1778 1779DOT_MULTI_TARGETS = NO 1780 1781# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 1782# generate a legend page explaining the meaning of the various boxes and 1783# arrows in the dot generated graphs. 1784 1785GENERATE_LEGEND = YES 1786 1787# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 1788# remove the intermediate dot files that are used to generate 1789# the various graphs. 1790 1791DOT_CLEANUP = YES 1792