Changeset 7282


Ignore:
Timestamp:
01/30/11 20:46:11 (2 years ago)
Author:
alanbach-guest
Message:
  • Updated 10_dbus-1.0.1-generate-xml-docs.patch to fix FTBFS errors
File:
1 edited

Legend:

Unmodified
Added
Removed

  • pkg/security/vinnie/main/dbus/trunk/debian/patches/10_dbus-1.0.1-generate-xml-docs.patch

    r7272 r7282  
    1 Index: dbus-1.2.14/Doxyfile.in 
    2 =================================================================== 
    3 --- dbus-1.2.14.orig/Doxyfile.in        2009-04-17 21:45:29.000000000 +0200 
    4 +++ dbus-1.2.14/Doxyfile.in     2009-05-07 00:19:57.000000000 +0200 
    5 @@ -133,7 +133,7 @@ 
     1diff -urN dbus-1.2.24/Doxyfile.in dbus-1.2.24.new//Doxyfile.in 
     2--- dbus-1.2.24/Doxyfile.in     2009-07-10 15:27:40.000000000 -0700 
     3+++ dbus-1.2.24.new//Doxyfile.in        2011-01-30 11:45:09.212767279 -0800 
     4@@ -1,181 +1,1653 @@ 
     5-# Doxyfile 0.1 
     6+# Doxyfile 1.7.1 
     7+ 
     8+# This file describes the settings to be used by the documentation system 
     9+# doxygen (www.doxygen.org) for a project 
     10+# 
     11+# All text after a hash (#) is considered a comment and will be ignored 
     12+# The format is: 
     13+#       TAG = value [value, ...] 
     14+# For lists items can also be appended using: 
     15+#       TAG += value [value, ...] 
     16+# Values that contain spaces should be placed between quotes (" ") 
     17  
     18 #--------------------------------------------------------------------------- 
     19-# General configuration options 
     20+# Project related configuration options 
     21 #--------------------------------------------------------------------------- 
     22+ 
     23+# This tag specifies the encoding used for all characters in the config file 
     24+# that follow. The default is UTF-8 which is also the encoding used for all 
     25+# text before the first occurrence of this tag. Doxygen uses libiconv (or the 
     26+# iconv built into libc) for the transcoding. See 
     27+# http://www.gnu.org/software/libiconv for the list of possible encodings. 
     28+ 
     29+DOXYFILE_ENCODING      = UTF-8 
     30+ 
     31+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
     32+# by quotes) that should identify the project. 
     33+ 
     34 PROJECT_NAME           = D-Bus 
     35+ 
     36+# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
     37+# This could be handy for archiving the generated documentation or 
     38+# if some version control system is used. 
     39+ 
     40 PROJECT_NUMBER         = @VERSION@ 
     41+ 
     42+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
     43+# base path where the generated documentation will be put. 
     44+# If a relative path is entered, it will be relative to the location 
     45+# where doxygen was started. If left blank the current directory will be used. 
     46+ 
     47 OUTPUT_DIRECTORY       = doc/api 
     48+ 
     49+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
     50+# 4096 sub-directories (in 2 levels) under the output directory of each output 
     51+# format and will distribute the generated files over these directories. 
     52+# Enabling this option can be useful when feeding doxygen a huge amount of 
     53+# source files, where putting all generated files in the same directory would 
     54+# otherwise cause performance problems for the file system. 
     55+ 
     56+CREATE_SUBDIRS         = NO 
     57+ 
     58+# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
     59+# documentation generated by doxygen is written. Doxygen will use this 
     60+# information to generate all constant output in the proper language. 
     61+# The default language is English, other supported languages are: 
     62+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
     63+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 
     64+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 
     65+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 
     66+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 
     67+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 
     68+ 
     69 OUTPUT_LANGUAGE        = English 
     70+ 
     71+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
     72+# include brief member descriptions after the members that are listed in 
     73+# the file and class documentation (similar to JavaDoc). 
     74+# Set to NO to disable this. 
     75+ 
     76+BRIEF_MEMBER_DESC      = YES 
     77+ 
     78+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
     79+# the brief description of a member or function before the detailed description. 
     80+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
     81+# brief descriptions will be completely suppressed. 
     82+ 
     83+REPEAT_BRIEF           = YES 
     84+ 
     85+# This tag implements a quasi-intelligent brief description abbreviator 
     86+# that is used to form the text in various listings. Each string 
     87+# in this list, if found as the leading text of the brief description, will be 
     88+# stripped from the text and the result after processing the whole list, is 
     89+# used as the annotated text. Otherwise, the brief description is used as-is. 
     90+# If left blank, the following values are used ("$name" is automatically 
     91+# replaced with the name of the entity): "The $name class" "The $name widget" 
     92+# "The $name file" "is" "provides" "specifies" "contains" 
     93+# "represents" "a" "an" "the" 
     94+ 
     95+ABBREVIATE_BRIEF       = 
     96+ 
     97+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
     98+# Doxygen will generate a detailed section even if there is only a brief 
     99+# description. 
     100+ 
     101+ALWAYS_DETAILED_SEC    = NO 
     102+ 
     103+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
     104+# inherited members of a class in the documentation of that class as if those 
     105+# members were ordinary class members. Constructors, destructors and assignment 
     106+# operators of the base classes will not be shown. 
     107+ 
     108+INLINE_INHERITED_MEMB  = NO 
     109+ 
     110+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
     111+# path before files name in the file list and in the header files. If set 
     112+# to NO the shortest path that makes the file name unique will be used. 
     113+ 
     114+FULL_PATH_NAMES        = NO 
     115+ 
     116+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
     117+# can be used to strip a user-defined part of the path. Stripping is 
     118+# only done if one of the specified strings matches the left-hand part of 
     119+# the path. The tag can be used to show relative paths in the file list. 
     120+# If left blank the directory from which doxygen is run is used as the 
     121+# path to strip. 
     122+ 
     123+STRIP_FROM_PATH        = 
     124+ 
     125+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
     126+# the path mentioned in the documentation of a class, which tells 
     127+# the reader which header file to include in order to use a class. 
     128+# If left blank only the name of the header file containing the class 
     129+# definition is used. Otherwise one should specify the include paths that 
     130+# are normally passed to the compiler using the -I flag. 
     131+ 
     132+STRIP_FROM_INC_PATH    = 
     133+ 
     134+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
     135+# (but less readable) file names. This can be useful is your file systems 
     136+# doesn't support long names like on DOS, Mac, or CD-ROM. 
     137+ 
     138+SHORT_NAMES            = NO 
     139+ 
     140+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
     141+# will interpret the first line (until the first dot) of a JavaDoc-style 
     142+# comment as the brief description. If set to NO, the JavaDoc 
     143+# comments will behave just like regular Qt-style comments 
     144+# (thus requiring an explicit @brief command for a brief description.) 
     145+ 
     146+JAVADOC_AUTOBRIEF      = YES 
     147+ 
     148+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
     149+# interpret the first line (until the first dot) of a Qt-style 
     150+# comment as the brief description. If set to NO, the comments 
     151+# will behave just like regular Qt-style comments (thus requiring 
     152+# an explicit \brief command for a brief description.) 
     153+ 
     154+QT_AUTOBRIEF           = NO 
     155+ 
     156+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
     157+# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
     158+# comments) as a brief description. This used to be the default behaviour. 
     159+# The new default is to treat a multi-line C++ comment block as a detailed 
     160+# description. Set this tag to YES if you prefer the old behaviour instead. 
     161+ 
     162+MULTILINE_CPP_IS_BRIEF = NO 
     163+ 
     164+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
     165+# member inherits the documentation from any documented member that it 
     166+# re-implements. 
     167+ 
     168+INHERIT_DOCS           = YES 
     169+ 
     170+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
     171+# a new page for each member. If set to NO, the documentation of a member will 
     172+# be part of the file/class/namespace that contains it. 
     173+ 
     174+SEPARATE_MEMBER_PAGES  = NO 
     175+ 
     176+# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
     177+# Doxygen uses this value to replace tabs by spaces in code fragments. 
     178+ 
     179+TAB_SIZE               = 8 
     180+ 
     181+# This tag can be used to specify a number of aliases that acts 
     182+# as commands in the documentation. An alias has the form "name=value". 
     183+# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
     184+# put the command \sideeffect (or @sideeffect) in the documentation, which 
     185+# will result in a user-defined paragraph with heading "Side Effects:". 
     186+# You can put \n's in the value part of an alias to insert newlines. 
     187+ 
     188+ALIASES                = 
     189+ 
     190+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
     191+# sources only. Doxygen will then generate output that is more tailored for C. 
     192+# For instance, some of the names that are used will be different. The list 
     193+# of all members will be omitted, etc. 
     194+ 
     195+OPTIMIZE_OUTPUT_FOR_C  = YES 
     196+ 
     197+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
     198+# sources only. Doxygen will then generate output that is more tailored for 
     199+# Java. For instance, namespaces will be presented as packages, qualified 
     200+# scopes will look different, etc. 
     201+ 
     202+OPTIMIZE_OUTPUT_JAVA   = NO 
     203+ 
     204+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 
     205+# sources only. Doxygen will then generate output that is more tailored for 
     206+# Fortran. 
     207+ 
     208+OPTIMIZE_FOR_FORTRAN   = NO 
     209+ 
     210+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 
     211+# sources. Doxygen will then generate output that is tailored for 
     212+# VHDL. 
     213+ 
     214+OPTIMIZE_OUTPUT_VHDL   = NO 
     215+ 
     216+# Doxygen selects the parser to use depending on the extension of the files it 
     217+# parses. With this tag you can assign which parser to use for a given extension. 
     218+# Doxygen has a built-in mapping, but you can override or extend it using this 
     219+# tag. The format is ext=language, where ext is a file extension, and language 
     220+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, 
     221+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make 
     222+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C 
     223+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions 
     224+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. 
     225+ 
     226+EXTENSION_MAPPING      = 
     227+ 
     228+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 
     229+# to include (a tag file for) the STL sources as input, then you should 
     230+# set this tag to YES in order to let doxygen match functions declarations and 
     231+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
     232+# func(std::string) {}). This also make the inheritance and collaboration 
     233+# diagrams that involve STL classes more complete and accurate. 
     234+ 
     235+BUILTIN_STL_SUPPORT    = NO 
     236+ 
     237+# If you use Microsoft's C++/CLI language, you should set this option to YES to 
     238+# enable parsing support. 
     239+ 
     240+CPP_CLI_SUPPORT        = NO 
     241+ 
     242+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 
     243+# Doxygen will parse them like normal C++ but will assume all classes use public 
     244+# instead of private inheritance when no explicit protection keyword is present. 
     245+ 
     246+SIP_SUPPORT            = NO 
     247+ 
     248+# For Microsoft's IDL there are propget and propput attributes to indicate getter 
     249+# and setter methods for a property. Setting this option to YES (the default) 
     250+# will make doxygen to replace the get and set methods by a property in the 
     251+# documentation. This will only work if the methods are indeed getting or 
     252+# setting a simple type. If this is not the case, or you want to show the 
     253+# methods anyway, you should set this option to NO. 
     254+ 
     255+IDL_PROPERTY_SUPPORT   = YES 
     256+ 
     257+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
     258+# tag is set to YES, then doxygen will reuse the documentation of the first 
     259+# member in the group (if any) for the other members of the group. By default 
     260+# all members of a group must be documented explicitly. 
     261+ 
     262+DISTRIBUTE_GROUP_DOC   = NO 
     263+ 
     264+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
     265+# the same type (for instance a group of public functions) to be put as a 
     266+# subgroup of that type (e.g. under the Public Functions section). Set it to 
     267+# NO to prevent subgrouping. Alternatively, this can be done per class using 
     268+# the \nosubgrouping command. 
     269+ 
     270+SUBGROUPING            = YES 
     271+ 
     272+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 
     273+# is documented as struct, union, or enum with the name of the typedef. So 
     274+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 
     275+# with name TypeT. When disabled the typedef will appear as a member of a file, 
     276+# namespace, or class. And the struct will be named TypeS. This can typically 
     277+# be useful for C code in case the coding convention dictates that all compound 
     278+# types are typedef'ed and only the typedef is referenced, never the tag name. 
     279+ 
     280+TYPEDEF_HIDES_STRUCT   = NO 
     281+ 
     282+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 
     283+# determine which symbols to keep in memory and which to flush to disk. 
     284+# When the cache is full, less often used symbols will be written to disk. 
     285+# For small to medium size projects (<1000 input files) the default value is 
     286+# probably good enough. For larger projects a too small cache size can cause 
     287+# doxygen to be busy swapping symbols to and from disk most of the time 
     288+# causing a significant performance penality. 
     289+# If the system has enough physical memory increasing the cache will improve the 
     290+# performance by keeping more symbols in memory. Note that the value works on 
     291+# a logarithmic scale so increasing the size by one will rougly double the 
     292+# memory usage. The cache size is given by this formula: 
     293+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 
     294+# corresponding to a cache size of 2^16 = 65536 symbols 
     295+ 
     296+SYMBOL_CACHE_SIZE      = 0 
     297+ 
     298+#--------------------------------------------------------------------------- 
     299+# Build related configuration options 
     300+#--------------------------------------------------------------------------- 
     301+ 
     302+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
     303+# documentation are documented, even if no documentation was available. 
     304+# Private class members and static file members will be hidden unless 
     305+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 
     306+ 
     307 EXTRACT_ALL            = NO 
     308+ 
     309+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
     310+# will be included in the documentation. 
     311+ 
     312 EXTRACT_PRIVATE        = NO 
     313+ 
     314+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
     315+# will be included in the documentation. 
     316+ 
     317 EXTRACT_STATIC         = NO 
     318+ 
     319+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
     320+# defined locally in source files will be included in the documentation. 
     321+# If set to NO only classes defined in header files are included. 
     322+ 
     323+EXTRACT_LOCAL_CLASSES  = YES 
     324+ 
     325+# This flag is only useful for Objective-C code. When set to YES local 
     326+# methods, which are defined in the implementation section but not in 
     327+# the interface are included in the documentation. 
     328+# If set to NO (the default) only methods in the interface are included. 
     329+ 
     330+EXTRACT_LOCAL_METHODS  = NO 
     331+ 
     332+# If this flag is set to YES, the members of anonymous namespaces will be 
     333+# extracted and appear in the documentation as a namespace called 
     334+# 'anonymous_namespace{file}', where file will be replaced with the base 
     335+# name of the file that contains the anonymous namespace. By default 
     336+# anonymous namespace are hidden. 
     337+ 
     338+EXTRACT_ANON_NSPACES   = NO 
     339+ 
     340+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
     341+# undocumented members of documented classes, files or namespaces. 
     342+# If set to NO (the default) these members will be included in the 
     343+# various overviews, but no documentation section is generated. 
     344+# This option has no effect if EXTRACT_ALL is enabled. 
     345+ 
     346 HIDE_UNDOC_MEMBERS     = NO 
     347+ 
     348+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
     349+# undocumented classes that are normally visible in the class hierarchy. 
     350+# If set to NO (the default) these classes will be included in the various 
     351+# overviews. This option has no effect if EXTRACT_ALL is enabled. 
     352+ 
     353 HIDE_UNDOC_CLASSES     = NO 
     354-BRIEF_MEMBER_DESC      = YES 
     355-REPEAT_BRIEF           = YES 
     356-ALWAYS_DETAILED_SEC    = NO 
     357-FULL_PATH_NAMES        = NO 
     358-STRIP_FROM_PATH        =  
     359+ 
     360+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
     361+# friend (class|struct|union) declarations. 
     362+# If set to NO (the default) these declarations will be included in the 
     363+# documentation. 
     364+ 
     365+HIDE_FRIEND_COMPOUNDS  = NO 
     366+ 
     367+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
     368+# documentation blocks found inside the body of a function. 
     369+# If set to NO (the default) these blocks will be appended to the 
     370+# function's detailed documentation block. 
     371+ 
     372+HIDE_IN_BODY_DOCS      = NO 
     373+ 
     374+# The INTERNAL_DOCS tag determines if documentation 
     375+# that is typed after a \internal command is included. If the tag is set 
     376+# to NO (the default) then the documentation will be excluded. 
     377+# Set it to YES to include the internal documentation. 
     378+ 
     379 INTERNAL_DOCS          = NO 
     380-STRIP_CODE_COMMENTS    = YES 
     381+ 
     382+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
     383+# file names in lower-case letters. If set to YES upper-case letters are also 
     384+# allowed. This is useful if you have classes or files whose names only differ 
     385+# in case and if your file system supports case sensitive file names. Windows 
     386+# and Mac users are advised to set this option to NO. 
     387+ 
     388 CASE_SENSE_NAMES       = YES 
     389-SHORT_NAMES            = NO 
     390+ 
     391+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
     392+# will show members with their full class and namespace scopes in the 
     393+# documentation. If set to YES the scope will be hidden. 
     394+ 
     395 HIDE_SCOPE_NAMES       = NO 
     396-VERBATIM_HEADERS       = YES 
     397+ 
     398+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
     399+# will put a list of the files that are included by a file in the documentation 
     400+# of that file. 
     401+ 
     402 SHOW_INCLUDE_FILES     = YES 
     403-JAVADOC_AUTOBRIEF      = YES 
     404-INHERIT_DOCS           = YES 
     405+ 
     406+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 
     407+# will list include files with double quotes in the documentation 
     408+# rather than with sharp brackets. 
     409+ 
     410+FORCE_LOCAL_INCLUDES   = NO 
     411+ 
     412+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
     413+# is inserted in the documentation for inline members. 
     414+ 
     415 INLINE_INFO            = YES 
     416+ 
     417+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
     418+# will sort the (detailed) documentation of file and class members 
     419+# alphabetically by member name. If set to NO the members will appear in 
     420+# declaration order. 
     421+ 
     422 SORT_MEMBER_DOCS       = YES 
     423-DISTRIBUTE_GROUP_DOC   = NO 
     424-TAB_SIZE               = 8 
     425+ 
     426+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
     427+# brief documentation of file, namespace and class members alphabetically 
     428+# by member name. If set to NO (the default) the members will appear in 
     429+# declaration order. 
     430+ 
     431+SORT_BRIEF_DOCS        = NO 
     432+ 
     433+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 
     434+# will sort the (brief and detailed) documentation of class members so that 
     435+# constructors and destructors are listed first. If set to NO (the default) 
     436+# the constructors will appear in the respective orders defined by 
     437+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 
     438+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 
     439+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 
     440+ 
     441+SORT_MEMBERS_CTORS_1ST = NO 
     442+ 
     443+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 
     444+# hierarchy of group names into alphabetical order. If set to NO (the default) 
     445+# the group names will appear in their defined order. 
     446+ 
     447+SORT_GROUP_NAMES       = NO 
     448+ 
     449+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
     450+# sorted by fully-qualified names, including namespaces. If set to 
     451+# NO (the default), the class list will be sorted only by class name, 
     452+# not including the namespace part. 
     453+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 
     454+# Note: This option applies only to the class list, not to the 
     455+# alphabetical list. 
     456+ 
     457+SORT_BY_SCOPE_NAME     = NO 
     458+ 
     459+# The GENERATE_TODOLIST tag can be used to enable (YES) or 
     460+# disable (NO) the todo list. This list is created by putting \todo 
     461+# commands in the documentation. 
     462+ 
     463 GENERATE_TODOLIST      = YES 
     464+ 
     465+# The GENERATE_TESTLIST tag can be used to enable (YES) or 
     466+# disable (NO) the test list. This list is created by putting \test 
     467+# commands in the documentation. 
     468+ 
     469 GENERATE_TESTLIST      = YES 
     470+ 
     471+# The GENERATE_BUGLIST tag can be used to enable (YES) or 
     472+# disable (NO) the bug list. This list is created by putting \bug 
     473+# commands in the documentation. 
     474+ 
     475 GENERATE_BUGLIST       = YES 
     476-ALIASES                =  
     477-ENABLED_SECTIONS       =  
     478+ 
     479+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
     480+# disable (NO) the deprecated list. This list is created by putting 
     481+# \deprecated commands in the documentation. 
     482+ 
     483+GENERATE_DEPRECATEDLIST= YES 
     484+ 
     485+# The ENABLED_SECTIONS tag can be used to enable conditional 
     486+# documentation sections, marked by \if sectionname ... \endif. 
     487+ 
     488+ENABLED_SECTIONS       = 
     489+ 
     490+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
     491+# the initial value of a variable or define consists of for it to appear in 
     492+# the documentation. If the initializer consists of more lines than specified 
     493+# here it will be hidden. Use a value of 0 to hide initializers completely. 
     494+# The appearance of the initializer of individual variables and defines in the 
     495+# documentation can be controlled using \showinitializer or \hideinitializer 
     496+# command in the documentation regardless of this setting. 
     497+ 
     498 MAX_INITIALIZER_LINES  = 30 
     499-OPTIMIZE_OUTPUT_FOR_C  = YES 
     500+ 
     501+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
     502+# at the bottom of the documentation of classes and structs. If set to YES the 
     503+# list will mention the files that were used to generate the documentation. 
     504+ 
     505 SHOW_USED_FILES        = YES 
     506+ 
     507+# If the sources in your project are distributed over multiple directories 
     508+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
     509+# in the documentation. The default is NO. 
     510+ 
     511+SHOW_DIRECTORIES       = NO 
     512+ 
     513+# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 
     514+# This will remove the Files entry from the Quick Index and from the 
     515+# Folder Tree View (if specified). The default is YES. 
     516+ 
     517+SHOW_FILES             = YES 
     518+ 
     519+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 
     520+# Namespaces page. 
     521+# This will remove the Namespaces entry from the Quick Index 
     522+# and from the Folder Tree View (if specified). The default is YES. 
     523+ 
     524+SHOW_NAMESPACES        = YES 
     525+ 
     526+# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
     527+# doxygen should invoke to get the current version for each file (typically from 
     528+# the version control system). Doxygen will invoke the program by executing (via 
     529+# popen()) the command <command> <input-file>, where <command> is the value of 
     530+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
     531+# provided by doxygen. Whatever the program writes to standard output 
     532+# is used as the file version. See the manual for examples. 
     533+ 
     534+FILE_VERSION_FILTER    = 
     535+ 
     536+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 
     537+# by doxygen. The layout file controls the global structure of the generated 
     538+# output files in an output format independent way. The create the layout file 
     539+# that represents doxygen's defaults, run doxygen with the -l option. 
     540+# You can optionally specify a file name after the option, if omitted 
     541+# DoxygenLayout.xml will be used as the name of the layout file. 
     542+ 
     543+LAYOUT_FILE            = 
     544+ 
     545 #--------------------------------------------------------------------------- 
     546 # configuration options related to warning and progress messages 
     547 #--------------------------------------------------------------------------- 
     548+ 
     549+# The QUIET tag can be used to turn on/off the messages that are generated 
     550+# by doxygen. Possible values are YES and NO. If left blank NO is used. 
     551+ 
     552 QUIET                  = YES 
     553+ 
     554+# The WARNINGS tag can be used to turn on/off the warning messages that are 
     555+# generated by doxygen. Possible values are YES and NO. If left blank 
     556+# NO is used. 
     557+ 
     558 WARNINGS               = YES 
     559+ 
     560+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
     561+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
     562+# automatically be disabled. 
     563+ 
     564 WARN_IF_UNDOCUMENTED   = YES 
     565-WARN_FORMAT            =  
     566-WARN_LOGFILE           =  
     567+ 
     568+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
     569+# potential errors in the documentation, such as not documenting some 
     570+# parameters in a documented function, or documenting parameters that 
     571+# don't exist or using markup commands wrongly. 
     572+ 
     573+WARN_IF_DOC_ERROR      = YES 
     574+ 
     575+# This WARN_NO_PARAMDOC option can be abled to get warnings for 
     576+# functions that are documented, but have no documentation for their parameters 
     577+# or return value. If set to NO (the default) doxygen will only warn about 
     578+# wrong or incomplete parameter documentation, but not about the absence of 
     579+# documentation. 
     580+ 
     581+WARN_NO_PARAMDOC       = NO 
     582+ 
     583+# The WARN_FORMAT tag determines the format of the warning messages that 
     584+# doxygen can produce. The string should contain the $file, $line, and $text 
     585+# tags, which will be replaced by the file and line number from which the 
     586+# warning originated and the warning text. Optionally the format may contain 
     587+# $version, which will be replaced by the version of the file (if it could 
     588+# be obtained via FILE_VERSION_FILTER) 
     589+ 
     590+WARN_FORMAT            = 
     591+ 
     592+# The WARN_LOGFILE tag can be used to specify a file to which warning 
     593+# and error messages should be written. If left blank the output is written 
     594+# to stderr. 
     595+ 
     596+WARN_LOGFILE           = 
     597+ 
     598 #--------------------------------------------------------------------------- 
     599 # configuration options related to the input files 
     600 #--------------------------------------------------------------------------- 
     601+ 
     602+# The INPUT tag can be used to specify the files and/or directories that contain 
     603+# documented source files. You may enter file names like "myfile.cpp" or 
     604+# directories like "/usr/src/myproject". Separate the files or directories 
     605+# with spaces. 
     606+ 
     607 INPUT                  = @top_srcdir@/dbus 
     608-FILE_PATTERNS          = *.c *.h 
     609+ 
     610+# This tag can be used to specify the character encoding of the source files 
     611+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 
     612+# also the default input encoding. Doxygen uses libiconv (or the iconv built 
     613+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 
     614+# the list of possible encodings. 
     615+ 
     616+INPUT_ENCODING         = UTF-8 
     617+ 
     618+# If the value of the INPUT tag contains directories, you can use the 
     619+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
     620+# and *.h) to filter out the source-files in the directories. If left 
     621+# blank the following patterns are tested: 
     622+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
     623+# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 
     624+ 
     625+FILE_PATTERNS          = *.c \ 
     626+                         *.h 
     627+ 
     628+# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
     629+# should be searched for input files as well. Possible values are YES and NO. 
     630+# If left blank NO is used. 
     631+ 
     632 RECURSIVE              = YES 
     633-#EXCLUDE                = test 
     634  
     635-# If the value of the INPUT tag contains directories, you can use the  
     636-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude  
     637-# certain files from those directories. 
     638- 
     639-EXCLUDE_PATTERNS       = Makefile.* ChangeLog CHANGES CHANGES.* README \ 
     640-                         README.* *.png AUTHORS DESIGN DESIGN.* *.desktop \ 
     641-                         DESKTOP* COMMENTS HOWTO magic NOTES TODO THANKS 
     642+# The EXCLUDE tag can be used to specify files and/or directories that should 
     643+# excluded from the INPUT source files. This way you can easily exclude a 
     644+# subdirectory from a directory tree whose root is specified with the INPUT tag. 
     645+ 
     646+EXCLUDE                = 
     647+ 
     648+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
     649+# directories that are symbolic links (a Unix filesystem feature) are excluded 
     650+# from the input. 
     651+ 
     652+EXCLUDE_SYMLINKS       = NO 
     653+ 
     654+# If the value of the INPUT tag contains directories, you can use the 
     655+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
     656+# certain files from those directories. Note that the wildcards are matched 
     657+# against the file with absolute path, so to exclude all test directories 
     658+# for example use the pattern */test/* 
     659+ 
     660+EXCLUDE_PATTERNS       = Makefile.* \ 
     661+                         ChangeLog \ 
     662+                         CHANGES \ 
     663+                         CHANGES.* \ 
     664+                         README \ 
     665+                         README.* \ 
     666+                         *.png \ 
     667+                         AUTHORS \ 
     668+                         DESIGN \ 
     669+                         DESIGN.* \ 
     670+                         *.desktop \ 
     671+                         DESKTOP* \ 
     672+                         COMMENTS \ 
     673+                         HOWTO \ 
     674+                         magic \ 
     675+                         NOTES \ 
     676+                         TODO \ 
     677+                         THANKS 
     678+ 
     679+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
     680+# (namespaces, classes, functions, etc.) that should be excluded from the 
     681+# output. The symbol name can be a fully qualified name, a word, or if the 
     682+# wildcard * is used, a substring. Examples: ANamespace, AClass, 
     683+# AClass::ANamespace, ANamespace::*Test 
     684  
     685-# The EXAMPLE_PATH tag can be used to specify one or more files or  
     686-# directories that contain example code fragments that are included (see  
     687+EXCLUDE_SYMBOLS        = 
     688+ 
     689+# The EXAMPLE_PATH tag can be used to specify one or more files or 
     690+# directories that contain example code fragments that are included (see 
     691 # the \include command). 
     692  
     693-EXAMPLE_PATH           =  
     694-EXAMPLE_PATTERNS       =  
     695+EXAMPLE_PATH           = 
     696+ 
     697+# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
     698+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
     699+# and *.h) to filter out the source-files in the directories. If left 
     700+# blank all files are included. 
     701+ 
     702+EXAMPLE_PATTERNS       = 
     703+ 
     704+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
     705+# searched for input files to be used with the \include or \dontinclude 
     706+# commands irrespective of the value of the RECURSIVE tag. 
     707+# Possible values are YES and NO. If left blank NO is used. 
     708+ 
     709 EXAMPLE_RECURSIVE      = NO 
     710-IMAGE_PATH             =  
     711-INPUT_FILTER           =  
     712+ 
     713+# The IMAGE_PATH tag can be used to specify one or more files or 
     714+# directories that contain image that are included in the documentation (see 
     715+# the \image command). 
     716+ 
     717+IMAGE_PATH             = 
     718+ 
     719+# The INPUT_FILTER tag can be used to specify a program that doxygen should 
     720+# invoke to filter for each input file. Doxygen will invoke the filter program 
     721+# by executing (via popen()) the command <filter> <input-file>, where <filter> 
     722+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
     723+# input file. Doxygen will then use the output that the filter program writes 
     724+# to standard output. 
     725+# If FILTER_PATTERNS is specified, this tag will be 
     726+# ignored. 
     727+ 
     728+INPUT_FILTER           = 
     729+ 
     730+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
     731+# basis. 
     732+# Doxygen will compare the file name with each pattern and apply the 
     733+# filter if there is a match. 
     734+# The filters are a list of the form: 
     735+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
     736+# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
     737+# is applied to all files. 
     738+ 
     739+FILTER_PATTERNS        = 
     740+ 
     741+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
     742+# INPUT_FILTER) will be used to filter the input files when producing source 
     743+# files to browse (i.e. when SOURCE_BROWSER is set to YES). 
     744+ 
     745 FILTER_SOURCE_FILES    = NO 
     746+ 
     747 #--------------------------------------------------------------------------- 
     748 # configuration options related to source browsing 
     749 #--------------------------------------------------------------------------- 
     750+ 
     751+# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
     752+# be generated. Documented entities will be cross-referenced with these sources. 
     753+# Note: To get rid of all source code in the generated output, make sure also 
     754+# VERBATIM_HEADERS is set to NO. 
     755+ 
     756 SOURCE_BROWSER         = YES 
     757+ 
     758+# Setting the INLINE_SOURCES tag to YES will include the body 
     759+# of functions and classes directly in the documentation. 
     760+ 
     761 INLINE_SOURCES         = NO 
     762+ 
     763+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
     764+# doxygen to hide any special comment blocks from generated source code 
     765+# fragments. Normal C and C++ comments will always remain visible. 
     766+ 
     767+STRIP_CODE_COMMENTS    = YES 
     768+ 
     769+# If the REFERENCED_BY_RELATION tag is set to YES 
     770+# then for each documented function all documented 
     771+# functions referencing it will be listed. 
     772+ 
     773 REFERENCED_BY_RELATION = YES 
     774+ 
     775+# If the REFERENCES_RELATION tag is set to YES 
     776+# then for each documented function all documented entities 
     777+# called/used by that function will be listed. 
     778+ 
     779 REFERENCES_RELATION    = YES 
     780+ 
     781+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 
     782+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 
     783+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 
     784+# link to the source code. 
     785+# Otherwise they will link to the documentation. 
     786+ 
     787+REFERENCES_LINK_SOURCE = YES 
     788+ 
     789+# If the USE_HTAGS tag is set to YES then the references to source code 
     790+# will point to the HTML generated by the htags(1) tool instead of doxygen 
     791+# built-in source browser. The htags tool is part of GNU's global source 
     792+# tagging system (see http://www.gnu.org/software/global/global.html). You 
     793+# will need version 4.8.6 or higher. 
     794+ 
     795+USE_HTAGS              = NO 
     796+ 
     797+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
     798+# will generate a verbatim copy of the header file for each class for 
     799+# which an include is specified. Set to NO to disable this. 
     800+ 
     801+VERBATIM_HEADERS       = YES 
     802+ 
     803 #--------------------------------------------------------------------------- 
     804 # configuration options related to the alphabetical class index 
     805 #--------------------------------------------------------------------------- 
     806+ 
     807+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
     808+# of all compounds will be generated. Enable this if the project 
     809+# contains a lot of classes, structs, unions or interfaces. 
     810+ 
     811 ALPHABETICAL_INDEX     = NO 
     812+ 
     813+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
     814+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
     815+# in which this list will be split (can be a number in the range [1..20]) 
     816+ 
     817 COLS_IN_ALPHA_INDEX    = 5 
     818-IGNORE_PREFIX          =  
     819+ 
     820+# In case all classes in a project start with a common prefix, all 
     821+# classes will be put under the same header in the alphabetical index. 
     822+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
     823+# should be ignored while generating the index headers. 
     824+ 
     825+IGNORE_PREFIX          = 
     826+ 
     827 #--------------------------------------------------------------------------- 
     828 # configuration options related to the HTML output 
     829 #--------------------------------------------------------------------------- 
     830+ 
     831+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
     832+# generate HTML output. 
     833+ 
     834 GENERATE_HTML          = YES 
     835-HTML_OUTPUT            =  
     836-HTML_HEADER            =  
     837-HTML_FOOTER            =  
     838-HTML_STYLESHEET        =  
     839+ 
     840+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
     841+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     842+# put in front of it. If left blank `html' will be used as the default path. 
     843+ 
     844+HTML_OUTPUT            = 
     845+ 
     846+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
     847+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
     848+# doxygen will generate files with .html extension. 
     849+ 
     850+HTML_FILE_EXTENSION    = .html 
     851+ 
     852+# The HTML_HEADER tag can be used to specify a personal HTML header for 
     853+# each generated HTML page. If it is left blank doxygen will generate a 
     854+# standard header. 
     855+ 
     856+HTML_HEADER            = 
     857+ 
     858+# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
     859+# each generated HTML page. If it is left blank doxygen will generate a 
     860+# standard footer. 
     861+ 
     862+HTML_FOOTER            = 
     863+ 
     864+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
     865+# style sheet that is used by each HTML page. It can be used to 
     866+# fine-tune the look of the HTML output. If the tag is left blank doxygen 
     867+# will generate a default style sheet. Note that doxygen will try to copy 
     868+# the style sheet file to the HTML output directory, so don't put your own 
     869+# stylesheet in the HTML output directory as well, or it will be erased! 
     870+ 
     871+HTML_STYLESHEET        = 
     872+ 
     873+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 
     874+# Doxygen will adjust the colors in the stylesheet and background images 
     875+# according to this color. Hue is specified as an angle on a colorwheel, 
     876+# see http://en.wikipedia.org/wiki/Hue for more information. 
     877+# For instance the value 0 represents red, 60 is yellow, 120 is green, 
     878+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 
     879+# The allowed range is 0 to 359. 
     880+ 
     881+HTML_COLORSTYLE_HUE    = 220 
     882+ 
     883+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 
     884+# the colors in the HTML output. For a value of 0 the output will use 
     885+# grayscales only. A value of 255 will produce the most vivid colors. 
     886+ 
     887+HTML_COLORSTYLE_SAT    = 100 
     888+ 
     889+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 
     890+# the luminance component of the colors in the HTML output. Values below 
     891+# 100 gradually make the output lighter, whereas values above 100 make 
     892+# the output darker. The value divided by 100 is the actual gamma applied, 
     893+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 
     894+# and 100 does not change the gamma. 
     895+ 
     896+HTML_COLORSTYLE_GAMMA  = 80 
     897+ 
     898+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 
     899+# page will contain the date and time when the page was generated. Setting 
     900+# this to NO can help when comparing the output of multiple runs. 
     901+ 
     902+HTML_TIMESTAMP         = YES 
     903+ 
     904+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
     905+# files or namespaces will be aligned in HTML using tables. If set to 
     906+# NO a bullet list will be used. 
     907+ 
     908 HTML_ALIGN_MEMBERS     = YES 
     909+ 
     910+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
     911+# documentation will contain sections that can be hidden and shown after the 
     912+# page has loaded. For this to work a browser that supports 
     913+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 
     914+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 
     915+ 
     916+HTML_DYNAMIC_SECTIONS  = NO 
     917+ 
     918+# If the GENERATE_DOCSET tag is set to YES, additional index files 
     919+# will be generated that can be used as input for Apple's Xcode 3 
     920+# integrated development environment, introduced with OSX 10.5 (Leopard). 
     921+# To create a documentation set, doxygen will generate a Makefile in the 
     922+# HTML output directory. Running make will produce the docset in that 
     923+# directory and running "make install" will install the docset in 
     924+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 
     925+# it at startup. 
     926+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 
     927+# for more information. 
     928+ 
     929+GENERATE_DOCSET        = NO 
     930+ 
     931+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 
     932+# feed. A documentation feed provides an umbrella under which multiple 
     933+# documentation sets from a single provider (such as a company or product suite) 
     934+# can be grouped. 
     935+ 
     936+DOCSET_FEEDNAME        = "Doxygen generated docs" 
     937+ 
     938+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 
     939+# should uniquely identify the documentation set bundle. This should be a 
     940+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 
     941+# will append .docset to the name. 
     942+ 
     943+DOCSET_BUNDLE_ID       = org.doxygen.Project 
     944+ 
     945+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify 
     946+# the documentation publisher. This should be a reverse domain-name style 
     947+# string, e.g. com.mycompany.MyDocSet.documentation. 
     948+ 
     949+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher 
     950+ 
     951+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. 
     952+ 
     953+DOCSET_PUBLISHER_NAME  = Publisher 
     954+ 
     955+# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
     956+# will be generated that can be used as input for tools like the 
     957+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 
     958+# of the generated HTML documentation. 
     959+ 
     960 GENERATE_HTMLHELP      = NO 
     961+ 
     962+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
     963+# be used to specify the file name of the resulting .chm file. You 
     964+# can add a path in front of the file if the result should not be 
     965+# written to the html output directory. 
     966+ 
     967+CHM_FILE               = 
     968+ 
     969+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
     970+# be used to specify the location (absolute path including file name) of 
     971+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
     972+# the HTML help compiler on the generated index.hhp. 
     973+ 
     974+HHC_LOCATION           = 
     975+ 
     976+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
     977+# controls if a separate .chi index file is generated (YES) or that 
     978+# it should be included in the master .chm file (NO). 
     979+ 
     980 GENERATE_CHI           = NO 
     981+ 
     982+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 
     983+# is used to encode HtmlHelp index (hhk), content (hhc) and project file 
     984+# content. 
     985+ 
     986+CHM_INDEX_ENCODING     = 
     987+ 
     988+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
     989+# controls whether a binary table of contents is generated (YES) or a 
     990+# normal table of contents (NO) in the .chm file. 
     991+ 
     992 BINARY_TOC             = NO 
     993+ 
     994+# The TOC_EXPAND flag can be set to YES to add extra items for group members 
     995+# to the contents of the HTML help documentation and to the tree view. 
     996+ 
     997 TOC_EXPAND             = NO 
     998+ 
     999+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 
     1000+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 
     1001+# that can be used as input for Qt's qhelpgenerator to generate a 
     1002+# Qt Compressed Help (.qch) of the generated HTML documentation. 
     1003+ 
     1004+GENERATE_QHP           = NO 
     1005+ 
     1006+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 
     1007+# be used to specify the file name of the resulting .qch file. 
     1008+# The path specified is relative to the HTML output folder. 
     1009+ 
     1010+QCH_FILE               = 
     1011+ 
     1012+# The QHP_NAMESPACE tag specifies the namespace to use when generating 
     1013+# Qt Help Project output. For more information please see 
     1014+# http://doc.trolltech.com/qthelpproject.html#namespace 
     1015+ 
     1016+QHP_NAMESPACE          = org.doxygen.Project 
     1017+ 
     1018+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 
     1019+# Qt Help Project output. For more information please see 
     1020+# http://doc.trolltech.com/qthelpproject.html#virtual-folders 
     1021+ 
     1022+QHP_VIRTUAL_FOLDER     = doc 
     1023+ 
     1024+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 
     1025+# add. For more information please see 
     1026+# http://doc.trolltech.com/qthelpproject.html#custom-filters 
     1027+ 
     1028+QHP_CUST_FILTER_NAME   = 
     1029+ 
     1030+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 
     1031+# custom filter to add. For more information please see 
     1032+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> 
     1033+# Qt Help Project / Custom Filters</a>. 
     1034+ 
     1035+QHP_CUST_FILTER_ATTRS  = 
     1036+ 
     1037+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 
     1038+# project's 
     1039+# filter section matches. 
     1040+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> 
     1041+# Qt Help Project / Filter Attributes</a>. 
     1042+ 
     1043+QHP_SECT_FILTER_ATTRS  = 
     1044+ 
     1045+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 
     1046+# be used to specify the location of Qt's qhelpgenerator. 
     1047+# If non-empty doxygen will try to run qhelpgenerator on the generated 
     1048+# .qhp file. 
     1049+ 
     1050+QHG_LOCATION           = 
     1051+ 
     1052+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files 
     1053+#  will be generated, which together with the HTML files, form an Eclipse help 
     1054+# plugin. To install this plugin and make it available under the help contents 
     1055+# menu in Eclipse, the contents of the directory containing the HTML and XML 
     1056+# files needs to be copied into the plugins directory of eclipse. The name of 
     1057+# the directory within the plugins directory should be the same as 
     1058+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 
     1059+# the help appears. 
     1060+ 
     1061+GENERATE_ECLIPSEHELP   = NO 
     1062+ 
     1063+# A unique identifier for the eclipse help plugin. When installing the plugin 
     1064+# the directory name containing the HTML and XML files should also have 
     1065+# this name. 
     1066+ 
     1067+ECLIPSE_DOC_ID         = org.doxygen.Project 
     1068+ 
     1069+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
     1070+# top of each HTML page. The value NO (the default) enables the index and 
     1071+# the value YES disables it. 
     1072+ 
     1073 DISABLE_INDEX          = NO 
     1074+ 
     1075+# This tag can be used to set the number of enum values (range [1..20]) 
     1076+# that doxygen will group on one line in the generated HTML documentation. 
     1077+ 
     1078 ENUM_VALUES_PER_LINE   = 4 
     1079+ 
     1080+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 
     1081+# structure should be generated to display hierarchical information. 
     1082+# If the tag value is set to YES, a side panel will be generated 
     1083+# containing a tree-like index structure (just like the one that 
     1084+# is generated for HTML Help). For this to work a browser that supports 
     1085+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 
     1086+# Windows users are probably better off using the HTML help feature. 
     1087+ 
     1088 GENERATE_TREEVIEW      = NO 
     1089+ 
     1090+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 
     1091+# and Class Hierarchy pages using a tree view instead of an ordered list. 
     1092+ 
     1093+USE_INLINE_TREES       = NO 
     1094+ 
     1095+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
     1096+# used to set the initial width (in pixels) of the frame in which the tree 
     1097+# is shown. 
     1098+ 
     1099 TREEVIEW_WIDTH         = 250 
     1100+ 
     1101+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 
     1102+# links to external symbols imported via tag files in a separate window. 
     1103+ 
     1104+EXT_LINKS_IN_WINDOW    = NO 
     1105+ 
     1106+# Use this tag to change the font size of Latex formulas included 
     1107+# as images in the HTML documentation. The default is 10. Note that 
     1108+# when you change the font size after a successful doxygen run you need 
     1109+# to manually remove any form_*.png images from the HTML output directory 
     1110+# to force them to be regenerated. 
     1111+ 
     1112+FORMULA_FONTSIZE       = 10 
     1113+ 
     1114+# Use the FORMULA_TRANPARENT tag to determine whether or not the images 
     1115+# generated for formulas are transparent PNGs. Transparent PNGs are 
     1116+# not supported properly for IE 6.0, but are supported on all modern browsers. 
     1117+# Note that when changing this option you need to delete any form_*.png files 
     1118+# in the HTML output before the changes have effect. 
     1119+ 
     1120+FORMULA_TRANSPARENT    = YES 
     1121+ 
     1122+# When the SEARCHENGINE tag is enabled doxygen will generate a search box 
     1123+# for the HTML output. The underlying search engine uses javascript 
     1124+# and DHTML and should work on any modern browser. Note that when using 
     1125+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 
     1126+# (GENERATE_DOCSET) there is already a search function so this one should 
     1127+# typically be disabled. For large projects the javascript based search engine 
     1128+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. 
     1129+ 
     1130+SEARCHENGINE           = NO 
     1131+ 
     1132+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be 
     1133+# implemented using a PHP enabled web server instead of at the web client 
     1134+# using Javascript. Doxygen will generate the search PHP script and index 
     1135+# file to put on the web server. The advantage of the server 
     1136+# based approach is that it scales better to large projects and allows 
     1137+# full text search. The disadvances is that it is more difficult to setup 
     1138+# and does not have live searching capabilities. 
     1139+ 
     1140+SERVER_BASED_SEARCH    = NO 
     1141+ 
     1142 #--------------------------------------------------------------------------- 
     1143 # configuration options related to the LaTeX output 
     1144 #--------------------------------------------------------------------------- 
     1145+ 
     1146+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
     1147+# generate Latex output. 
     1148+ 
     1149 GENERATE_LATEX         = NO 
     1150-LATEX_OUTPUT           =  
     1151+ 
     1152+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
     1153+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     1154+# put in front of it. If left blank `latex' will be used as the default path. 
     1155+ 
     1156+LATEX_OUTPUT           = 
     1157+ 
     1158+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
     1159+# invoked. If left blank `latex' will be used as the default command name. 
     1160+# Note that when enabling USE_PDFLATEX this option is only used for 
     1161+# generating bitmaps for formulas in the HTML output, but not in the 
     1162+# Makefile that is written to the output directory. 
     1163+ 
     1164+LATEX_CMD_NAME         = latex 
     1165+ 
     1166+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
     1167+# generate index for LaTeX. If left blank `makeindex' will be used as the 
     1168+# default command name. 
     1169+ 
     1170+MAKEINDEX_CMD_NAME     = makeindex 
     1171+ 
     1172+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
     1173+# LaTeX documents. This may be useful for small projects and may help to 
     1174+# save some trees in general. 
     1175+ 
     1176 COMPACT_LATEX          = NO 
     1177+ 
     1178+# The PAPER_TYPE tag can be used to set the paper type that is used 
     1179+# by the printer. Possible values are: a4, a4wide, letter, legal and 
     1180+# executive. If left blank a4wide will be used. 
     1181+ 
     1182 PAPER_TYPE             = a4wide 
     1183-EXTRA_PACKAGES         =  
     1184-LATEX_HEADER           =  
     1185+ 
     1186+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
     1187+# packages that should be included in the LaTeX output. 
     1188+ 
     1189+EXTRA_PACKAGES         = 
     1190+ 
     1191+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
     1192+# the generated latex document. The header should contain everything until 
     1193+# the first chapter. If it is left blank doxygen will generate a 
     1194+# standard header. Notice: only use this tag if you know what you are doing! 
     1195+ 
     1196+LATEX_HEADER           = 
     1197+ 
     1198+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
     1199+# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
     1200+# contain links (just like the HTML output) instead of page references 
     1201+# This makes the output suitable for online browsing using a pdf viewer. 
     1202+ 
     1203 PDF_HYPERLINKS         = NO 
     1204+ 
     1205+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
     1206+# plain latex in the generated Makefile. Set this option to YES to get a 
     1207+# higher quality PDF documentation. 
     1208+ 
     1209 USE_PDFLATEX           = NO 
     1210+ 
     1211+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
     1212+# command to the generated LaTeX files. This will instruct LaTeX to keep 
     1213+# running if errors occur, instead of asking the user for help. 
     1214+# This option is also used when generating formulas in HTML. 
     1215+ 
     1216 LATEX_BATCHMODE        = NO 
     1217+ 
     1218+# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
     1219+# include the index chapters (such as File Index, Compound Index, etc.) 
     1220+# in the output. 
     1221+ 
     1222+LATEX_HIDE_INDICES     = NO 
     1223+ 
     1224+# If LATEX_SOURCE_CODE is set to YES then doxygen will include 
     1225+# source code with syntax highlighting in the LaTeX output. 
     1226+# Note that which sources are shown also depends on other settings 
     1227+# such as SOURCE_BROWSER. 
     1228+ 
     1229+LATEX_SOURCE_CODE      = NO 
     1230+ 
     1231 #--------------------------------------------------------------------------- 
     1232 # configuration options related to the RTF output 
     1233 #--------------------------------------------------------------------------- 
     1234+ 
     1235+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
     1236+# The RTF output is optimized for Word 97 and may not look very pretty with 
     1237+# other RTF readers or editors. 
     1238+ 
     1239 GENERATE_RTF           = NO 
     1240-RTF_OUTPUT             =  
     1241+ 
     1242+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
     1243+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     1244+# put in front of it. If left blank `rtf' will be used as the default path. 
     1245+ 
     1246+RTF_OUTPUT             = 
     1247+ 
     1248+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
     1249+# RTF documents. This may be useful for small projects and may help to 
     1250+# save some trees in general. 
     1251+ 
     1252 COMPACT_RTF            = NO 
     1253+ 
     1254+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
     1255+# will contain hyperlink fields. The RTF file will 
     1256+# contain links (just like the HTML output) instead of page references. 
     1257+# This makes the output suitable for online browsing using WORD or other 
     1258+# programs which support those fields. 
     1259+# Note: wordpad (write) and others do not support links. 
     1260+ 
     1261 RTF_HYPERLINKS         = NO 
     1262-RTF_STYLESHEET_FILE    =  
     1263-RTF_EXTENSIONS_FILE    =  
     1264+ 
     1265+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
     1266+# config file, i.e. a series of assignments. You only have to provide 
     1267+# replacements, missing definitions are set to their default value. 
     1268+ 
     1269+RTF_STYLESHEET_FILE    = 
     1270+ 
     1271+# Set optional variables used in the generation of an rtf document. 
     1272+# Syntax is similar to doxygen's config file. 
     1273+ 
     1274+RTF_EXTENSIONS_FILE    = 
     1275+ 
     1276 #--------------------------------------------------------------------------- 
     1277 # configuration options related to the man page output 
     1278 #--------------------------------------------------------------------------- 
     1279+ 
     1280+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
     1281+# generate man pages 
     1282+ 
     1283 GENERATE_MAN           = YES 
     1284+ 
     1285+# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
     1286+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     1287+# put in front of it. If left blank `man' will be used as the default path. 
     1288+ 
     1289 MAN_OUTPUT             = man 
     1290+ 
     1291+# The MAN_EXTENSION tag determines the extension that is added to 
     1292+# the generated man pages (default is the subroutine's section .3) 
     1293+ 
     1294 MAN_EXTENSION          = .3dbus 
     1295+ 
     1296+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
     1297+# then it will generate one additional man file for each entity 
     1298+# documented in the real man page(s). These additional files 
     1299+# only source the real man page, but without them the man command 
     1300+# would be unable to find the correct page. The default is NO. 
     1301+ 
     1302 MAN_LINKS              = YES 
     1303+ 
    61304 #--------------------------------------------------------------------------- 
    71305 # configuration options related to the XML output 
    81306 #--------------------------------------------------------------------------- 
    91307-GENERATE_XML           = NO 
     1308+ 
     1309+# If the GENERATE_XML tag is set to YES Doxygen will 
     1310+# generate an XML file that captures the structure of 
     1311+# the code including all documentation. 
     1312+ 
    101313+GENERATE_XML           = YES 
     1314+ 
     1315+# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
     1316+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     1317+# put in front of it. If left blank `xml' will be used as the default path. 
     1318+ 
     1319+XML_OUTPUT             = xml 
     1320+ 
     1321+# The XML_SCHEMA tag can be used to specify an XML schema, 
     1322+# which can be used by a validating XML parser to check the 
     1323+# syntax of the XML files. 
     1324+ 
     1325+XML_SCHEMA             = 
     1326+ 
     1327+# The XML_DTD tag can be used to specify an XML DTD, 
     1328+# which can be used by a validating XML parser to check the 
     1329+# syntax of the XML files. 
     1330+ 
     1331+XML_DTD                = 
     1332+ 
     1333+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
     1334+# dump the program listings (including syntax highlighting 
     1335+# and cross-referencing information) to the XML output. Note that 
     1336+# enabling this will significantly increase the size of the XML output. 
     1337+ 
     1338+XML_PROGRAMLISTING     = YES 
     1339+ 
     1340+#--------------------------------------------------------------------------- 
     1341+# configuration options for the AutoGen Definitions output 
     1342+#--------------------------------------------------------------------------- 
     1343+ 
     1344+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
     1345+# generate an AutoGen Definitions (see autogen.sf.net) file 
     1346+# that captures the structure of the code including all 
     1347+# documentation. Note that this feature is still experimental 
     1348+# and incomplete at the moment. 
     1349+ 
     1350+GENERATE_AUTOGEN_DEF   = NO 
     1351+ 
     1352+#--------------------------------------------------------------------------- 
     1353+# configuration options related to the Perl module output 
     1354+#--------------------------------------------------------------------------- 
     1355+ 
     1356+# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
     1357+# generate a Perl module file that captures the structure of 
     1358+# the code including all documentation. Note that this 
     1359+# feature is still experimental and incomplete at the 
     1360+# moment. 
     1361+ 
     1362+GENERATE_PERLMOD       = NO 
     1363+ 
     1364+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
     1365+# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
     1366+# to generate PDF and DVI output from the Perl module output. 
     1367+ 
     1368+PERLMOD_LATEX          = NO 
     1369+ 
     1370+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
     1371+# nicely formatted so it can be parsed by a human reader. 
     1372+# This is useful 
     1373+# if you want to understand what is going on. 
     1374+# On the other hand, if this 
     1375+# tag is set to NO the size of the Perl module output will be much smaller 
     1376+# and Perl will parse it just the same. 
     1377+ 
     1378+PERLMOD_PRETTY         = YES 
     1379+ 
     1380+# The names of the make variables in the generated doxyrules.make file 
     1381+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
     1382+# This is useful so different doxyrules.make files included by the same 
     1383+# Makefile don't overwrite each other's variables. 
     1384+ 
     1385+PERLMOD_MAKEVAR_PREFIX = 
     1386+ 
    111387 #--------------------------------------------------------------------------- 
    12  # Configuration options related to the preprocessor    
     1388-# Configuration options related to the preprocessor    
     1389+# Configuration options related to the preprocessor 
    131390 #--------------------------------------------------------------------------- 
     1391+ 
     1392+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
     1393+# evaluate all C-preprocessor directives found in the sources and include 
     1394+# files. 
     1395+ 
     1396 ENABLE_PREPROCESSING   = YES 
     1397+ 
     1398+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
     1399+# names in the source code. If set to NO (the default) only conditional 
     1400+# compilation will be performed. Macro expansion can be done in a controlled 
     1401+# way by setting EXPAND_ONLY_PREDEF to YES. 
     1402+ 
     1403 MACRO_EXPANSION        = YES 
     1404+ 
     1405+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
     1406+# then the macro expansion is limited to the macros specified with the 
     1407+# PREDEFINED and EXPAND_AS_DEFINED tags. 
     1408+ 
     1409 EXPAND_ONLY_PREDEF     = YES 
     1410+ 
     1411+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
     1412+# in the INCLUDE_PATH (see below) will be search if a #include is found. 
     1413+ 
     1414 SEARCH_INCLUDES        = YES 
     1415-INCLUDE_PATH           =  
     1416-INCLUDE_FILE_PATTERNS  =  
     1417-PREDEFINED             = "DBUS_BEGIN_DECLS="                   \ 
     1418-                        "DBUS_END_DECLS="                      \ 
     1419-                        "DOXYGEN_SHOULD_SKIP_THIS"             \ 
     1420-                         "DBUS_GNUC_DEPRECATED="                \ 
     1421-                        "_DBUS_DEFINE_GLOBAL_LOCK(name)="      \ 
     1422-                        "_DBUS_GNUC_PRINTF(from,to)=" 
     1423+ 
     1424+# The INCLUDE_PATH tag can be used to specify one or more directories that 
     1425+# contain include files that are not input files but should be processed by 
     1426+# the preprocessor. 
     1427+ 
     1428+INCLUDE_PATH           = 
     1429+ 
     1430+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
     1431+# patterns (like *.h and *.hpp) to filter out the header-files in the 
     1432+# directories. If left blank, the patterns specified with FILE_PATTERNS will 
     1433+# be used. 
     1434+ 
     1435+INCLUDE_FILE_PATTERNS  = 
     1436+ 
     1437+# The PREDEFINED tag can be used to specify one or more macro names that 
     1438+# are defined before the preprocessor is started (similar to the -D option of 
     1439+# gcc). The argument of the tag is a list of macros of the form: name 
     1440+# or name=definition (no spaces). If the definition and the = are 
     1441+# omitted =1 is assumed. To prevent a macro definition from being 
     1442+# undefined via #undef or recursively expanded use the := operator 
     1443+# instead of the = operator. 
     1444+ 
     1445+PREDEFINED             = "DBUS_BEGIN_DECLS=" \ 
     1446+                         "DBUS_END_DECLS=" \ 
     1447+                         "DOXYGEN_SHOULD_SKIP_THIS" \ 
     1448+                         "DBUS_GNUC_DEPRECATED=" \ 
     1449+                         "_DBUS_DEFINE_GLOBAL_LOCK(name)=" \ 
     1450+                         "_DBUS_GNUC_PRINTF(from,to)=" 
     1451+ 
     1452+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
     1453+# this tag can be used to specify a list of macro names that should be expanded. 
     1454+# The macro definition that is found in the sources will be used. 
     1455+# Use the PREDEFINED tag if you want to use a different macro definition. 
     1456+ 
     1457+EXPAND_AS_DEFINED      = 
     1458+ 
     1459+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
     1460+# doxygen's preprocessor will remove all function-like macros that are alone 
     1461+# on a line, have an all uppercase name, and do not end with a semicolon. Such 
     1462+# function macros are typically used for boiler-plate code, and will confuse 
     1463+# the parser if not removed. 
     1464+ 
     1465 SKIP_FUNCTION_MACROS   = YES 
     1466+ 
     1467 #--------------------------------------------------------------------------- 
     1468-# Configuration::addtions related to external references    
     1469+# Configuration::additions related to external references 
     1470 #--------------------------------------------------------------------------- 
     1471-TAGFILES               =  
     1472-GENERATE_TAGFILE       =  
     1473+ 
     1474+# The TAGFILES option can be used to specify one or more tagfiles. 
     1475+# Optionally an initial location of the external documentation 
     1476+# can be added for each tagfile. The format of a tag file without 
     1477+# this location is as follows: 
     1478+# 
     1479+# TAGFILES = file1 file2 ... 
     1480+# Adding location for the tag files is done as follows: 
     1481+# 
     1482+# TAGFILES = file1=loc1 "file2 = loc2" ... 
     1483+# where "loc1" and "loc2" can be relative or absolute paths or 
     1484+# URLs. If a location is present for each tag, the installdox tool 
     1485+# does not have to be run to correct the links. 
     1486+# Note that each tag file must have a unique name 
     1487+# (where the name does NOT include the path) 
     1488+# If a tag file is not located in the directory in which doxygen 
     1489+# is run, you must also specify the path to the tagfile here. 
     1490+ 
     1491+TAGFILES               = 
     1492+ 
     1493+# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
     1494+# a tag file that is based on the input files it reads. 
     1495+ 
     1496+GENERATE_TAGFILE       = 
     1497+ 
     1498+# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
     1499+# in the class index. If set to NO only the inherited external classes 
     1500+# will be listed. 
     1501+ 
     1502 ALLEXTERNALS           = NO 
     1503-PERL_PATH              =  
     1504+ 
     1505+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
     1506+# in the modules index. If set to NO, only the current project's groups will 
     1507+# be listed. 
     1508+ 
     1509+EXTERNAL_GROUPS        = YES 
     1510+ 
     1511+# The PERL_PATH should be the absolute path and name of the perl script 
     1512+# interpreter (i.e. the result of `which perl'). 
     1513+ 
     1514+PERL_PATH              = 
     1515+ 
     1516 #--------------------------------------------------------------------------- 
     1517-# Configuration options related to the dot tool    
     1518+# Configuration options related to the dot tool 
     1519 #--------------------------------------------------------------------------- 
     1520+ 
     1521+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
     1522+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
     1523+# or super classes. Setting the tag to NO turns the diagrams off. Note that 
     1524+# this option is superseded by the HAVE_DOT option below. This is only a 
     1525+# fallback. It is recommended to install and use dot, since it yields more 
     1526+# powerful graphs. 
     1527+ 
     1528 CLASS_DIAGRAMS         = YES 
     1529+ 
     1530+# You can define message sequence charts within doxygen comments using the \msc 
     1531+# command. Doxygen will then run the mscgen tool (see 
     1532+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 
     1533+# documentation. The MSCGEN_PATH tag allows you to specify the directory where 
     1534+# the mscgen tool resides. If left empty the tool is assumed to be found in the 
     1535+# default search path. 
     1536+ 
     1537+MSCGEN_PATH            = 
     1538+ 
     1539+# If set to YES, the inheritance and collaboration graphs will hide 
     1540+# inheritance and usage relations if the target is undocumented 
     1541+# or is not a class. 
     1542+ 
     1543+HIDE_UNDOC_RELATIONS   = YES 
     1544+ 
     1545+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
     1546+# available from the path. This tool is part of Graphviz, a graph visualization 
     1547+# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
     1548+# have no effect if this option is set to NO (the default) 
     1549+ 
     1550 HAVE_DOT               = NO 
     1551+ 
     1552+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 
     1553+# allowed to run in parallel. When set to 0 (the default) doxygen will 
     1554+# base this on the number of processors available in the system. You can set it 
     1555+# explicitly to a value larger than 0 to get control over the balance 
     1556+# between CPU load and processing speed. 
     1557+ 
     1558+DOT_NUM_THREADS        = 0 
     1559+ 
     1560+# By default doxygen will write a font called FreeSans.ttf to the output 
     1561+# directory and reference it in all dot files that doxygen generates. This 
     1562+# font does not include all possible unicode characters however, so when you need 
     1563+# these (or just want a differently looking font) you can specify the font name 
     1564+# using DOT_FONTNAME. You need need to make sure dot is able to find the font, 
     1565+# which can be done by putting it in a standard location or by setting the 
     1566+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory 
     1567+# containing the font. 
     1568+ 
     1569+DOT_FONTNAME           = FreeSans.ttf 
     1570+ 
     1571+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 
     1572+# The default size is 10pt. 
     1573+ 
     1574+DOT_FONTSIZE           = 10 
     1575+ 
     1576+# By default doxygen will tell dot to use the output directory to look for the 
     1577+# FreeSans.ttf font (which doxygen will put there itself). If you specify a 
     1578+# different font using DOT_FONTNAME you can set the path where dot 
     1579+# can find it using this tag. 
     1580+ 
     1581+DOT_FONTPATH           = 
     1582+ 
     1583+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
     1584+# will generate a graph for each documented class showing the direct and 
     1585+# indirect inheritance relations. Setting this tag to YES will force the 
     1586+# the CLASS_DIAGRAMS tag to NO. 
     1587+ 
     1588 CLASS_GRAPH            = YES 
     1589+ 
     1590+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
     1591+# will generate a graph for each documented class showing the direct and 
     1592+# indirect implementation dependencies (inheritance, containment, and 
     1593+# class references variables) of the class with other documented classes. 
     1594+ 
     1595 COLLABORATION_GRAPH    = YES 
     1596+ 
     1597+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
     1598+# will generate a graph for groups, showing the direct groups dependencies 
     1599+ 
     1600+GROUP_GRAPHS           = YES 
     1601+ 
     1602+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
     1603+# collaboration diagrams in a style similar to the OMG's Unified Modeling 
     1604+# Language. 
     1605+ 
     1606+UML_LOOK               = NO 
     1607+ 
     1608+# If set to YES, the inheritance and collaboration graphs will show the 
     1609+# relations between templates and their instances. 
     1610+ 
     1611 TEMPLATE_RELATIONS     = YES 
     1612-HIDE_UNDOC_RELATIONS   = YES 
     1613+ 
     1614+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
     1615+# tags are set to YES then doxygen will generate a graph for each documented 
     1616+# file showing the direct and indirect include dependencies of the file with 
     1617+# other documented files. 
     1618+ 
     1619 INCLUDE_GRAPH          = YES 
     1620+ 
     1621+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
     1622+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
     1623+# documented header file showing the documented files that directly or 
     1624+# indirectly include this file. 
     1625+ 
     1626 INCLUDED_BY_GRAPH      = YES 
     1627+ 
     1628+# If the CALL_GRAPH and HAVE_DOT options are set to YES then 
     1629+# doxygen will generate a call dependency graph for every global function 
     1630+# or class method. Note that enabling this option will significantly increase 
     1631+# the time of a run. So in most cases it will be better to enable call graphs 
     1632+# for selected functions only using the \callgraph command. 
     1633+ 
     1634+CALL_GRAPH             = NO 
     1635+ 
     1636+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 
     1637+# doxygen will generate a caller dependency graph for every global function 
     1638+# or class method. Note that enabling this option will significantly increase 
     1639+# the time of a run. So in most cases it will be better to enable caller 
     1640+# graphs for selected functions only using the \callergraph command. 
     1641+ 
     1642+CALLER_GRAPH           = NO 
     1643+ 
     1644+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
     1645+# will graphical hierarchy of all classes instead of a textual one. 
     1646+ 
     1647 GRAPHICAL_HIERARCHY    = YES 
     1648-DOT_PATH               =  
     1649-DOTFILE_DIRS           =  
     1650-MAX_DOT_GRAPH_WIDTH    = 640 
     1651-MAX_DOT_GRAPH_HEIGHT   = 1024 
     1652+ 
     1653+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
     1654+# then doxygen will show the dependencies a directory has on other directories 
     1655+# in a graphical way. The dependency relations are determined by the #include 
     1656+# relations between the files in the directories. 
     1657+ 
     1658+DIRECTORY_GRAPH        = YES 
     1659+ 
     1660+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
     1661+# generated by dot. Possible values are png, jpg, or gif 
     1662+# If left blank png will be used. 
     1663+ 
     1664+DOT_IMAGE_FORMAT       = png 
     1665+ 
     1666+# The tag DOT_PATH can be used to specify the path where the dot tool can be 
     1667+# found. If left blank, it is assumed the dot tool can be found in the path. 
     1668+ 
     1669+DOT_PATH               = 
     1670+ 
     1671+# The DOTFILE_DIRS tag can be used to specify one or more directories that 
     1672+# contain dot files that are included in the documentation (see the 
     1673+# \dotfile command). 
     1674+ 
     1675+DOTFILE_DIRS           = 
     1676+ 
     1677+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 
     1678+# nodes that will be shown in the graph. If the number of nodes in a graph 
     1679+# becomes larger than this value, doxygen will truncate the graph, which is 
     1680+# visualized by representing a node as a red box. Note that doxygen if the 
     1681+# number of direct children of the root node in a graph is already larger than 
     1682+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 
     1683+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 
     1684+ 
     1685+DOT_GRAPH_MAX_NODES    = 50 
     1686+ 
     1687+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
     1688+# graphs generated by dot. A depth value of 3 means that only nodes reachable 
     1689+# from the root by following a path via at most 3 edges will be shown. Nodes 
     1690+# that lay further from the root node will be omitted. Note that setting this 
     1691+# option to 1 or 2 may greatly reduce the computation time needed for large 
     1692+# code bases. Also note that the size of a graph can be further restricted by 
     1693+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 
     1694+ 
     1695+MAX_DOT_GRAPH_DEPTH    = 0 
     1696+ 
     1697+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
     1698+# background. This is disabled by default, because dot on Windows does not 
     1699+# seem to support this out of the box. Warning: Depending on the platform used, 
     1700+# enabling this option may lead to badly anti-aliased labels on the edges of 
     1701+# a graph (i.e. they become hard to read). 
     1702+ 
     1703+DOT_TRANSPARENT        = NO 
     1704+ 
     1705+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
     1706+# files in one run (i.e. multiple -o and -T options on the command line). This 
     1707+# makes dot run faster, but since only newer versions of dot (>1.8.10) 
     1708+# support this, this feature is disabled by default. 
     1709+ 
     1710+DOT_MULTI_TARGETS      = YES 
     1711+ 
     1712+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
     1713+# generate a legend page explaining the meaning of the various boxes and 
     1714+# arrows in the dot generated graphs. 
     1715+ 
     1716 GENERATE_LEGEND        = YES 
     1717+ 
     1718+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
     1719+# remove the intermediate dot files that are used to generate 
     1720+# the various graphs. 
     1721+ 
     1722 DOT_CLEANUP            = YES 
     1723-#--------------------------------------------------------------------------- 
     1724-# Configuration::addtions related to the search engine    
     1725-#--------------------------------------------------------------------------- 
     1726-SEARCHENGINE           = NO 
     1727diff -urN dbus-1.2.24/Doxyfile.in.bak dbus-1.2.24.new//Doxyfile.in.bak 
     1728--- dbus-1.2.24/Doxyfile.in.bak 1969-12-31 16:00:00.000000000 -0800 
     1729+++ dbus-1.2.24.new//Doxyfile.in.bak    2011-01-30 11:44:55.678517012 -0800 
     1730@@ -0,0 +1,1653 @@ 
     1731+# Doxyfile 1.7.1 
     1732+ 
     1733+# This file describes the settings to be used by the documentation system 
     1734+# doxygen (www.doxygen.org) for a project 
     1735+# 
     1736+# All text after a hash (#) is considered a comment and will be ignored 
     1737+# The format is: 
     1738+#       TAG = value [value, ...] 
     1739+# For lists items can also be appended using: 
     1740+#       TAG += value [value, ...] 
     1741+# Values that contain spaces should be placed between quotes (" ") 
     1742+ 
     1743+#--------------------------------------------------------------------------- 
     1744+# Project related configuration options 
     1745+#--------------------------------------------------------------------------- 
     1746+ 
     1747+# This tag specifies the encoding used for all characters in the config file 
     1748+# that follow. The default is UTF-8 which is also the encoding used for all 
     1749+# text before the first occurrence of this tag. Doxygen uses libiconv (or the 
     1750+# iconv built into libc) for the transcoding. See 
     1751+# http://www.gnu.org/software/libiconv for the list of possible encodings. 
     1752+ 
     1753+DOXYFILE_ENCODING      = UTF-8 
     1754+ 
     1755+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
     1756+# by quotes) that should identify the project. 
     1757+ 
     1758+PROJECT_NAME           = D-Bus 
     1759+ 
     1760+# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
     1761+# This could be handy for archiving the generated documentation or 
     1762+# if some version control system is used. 
     1763+ 
     1764+PROJECT_NUMBER         = @VERSION@ 
     1765+ 
     1766+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
     1767+# base path where the generated documentation will be put. 
     1768+# If a relative path is entered, it will be relative to the location 
     1769+# where doxygen was started. If left blank the current directory will be used. 
     1770+ 
     1771+OUTPUT_DIRECTORY       = doc/api 
     1772+ 
     1773+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
     1774+# 4096 sub-directories (in 2 levels) under the output directory of each output 
     1775+# format and will distribute the generated files over these directories. 
     1776+# Enabling this option can be useful when feeding doxygen a huge amount of 
     1777+# source files, where putting all generated files in the same directory would 
     1778+# otherwise cause performance problems for the file system. 
     1779+ 
     1780+CREATE_SUBDIRS         = NO 
     1781+ 
     1782+# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
     1783+# documentation generated by doxygen is written. Doxygen will use this 
     1784+# information to generate all constant output in the proper language. 
     1785+# The default language is English, other supported languages are: 
     1786+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
     1787+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 
     1788+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 
     1789+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 
     1790+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 
     1791+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 
     1792+ 
     1793+OUTPUT_LANGUAGE        = English 
     1794+ 
     1795+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
     1796+# include brief member descriptions after the members that are listed in 
     1797+# the file and class documentation (similar to JavaDoc). 
     1798+# Set to NO to disable this. 
     1799+ 
     1800+BRIEF_MEMBER_DESC      = YES 
     1801+ 
     1802+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
     1803+# the brief description of a member or function before the detailed description. 
     1804+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
     1805+# brief descriptions will be completely suppressed. 
     1806+ 
     1807+REPEAT_BRIEF           = YES 
     1808+ 
     1809+# This tag implements a quasi-intelligent brief description abbreviator 
     1810+# that is used to form the text in various listings. Each string 
     1811+# in this list, if found as the leading text of the brief description, will be 
     1812+# stripped from the text and the result after processing the whole list, is 
     1813+# used as the annotated text. Otherwise, the brief description is used as-is. 
     1814+# If left blank, the following values are used ("$name" is automatically 
     1815+# replaced with the name of the entity): "The $name class" "The $name widget" 
     1816+# "The $name file" "is" "provides" "specifies" "contains" 
     1817+# "represents" "a" "an" "the" 
     1818+ 
     1819+ABBREVIATE_BRIEF       = 
     1820+ 
     1821+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
     1822+# Doxygen will generate a detailed section even if there is only a brief 
     1823+# description. 
     1824+ 
     1825+ALWAYS_DETAILED_SEC    = NO 
     1826+ 
     1827+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
     1828+# inherited members of a class in the documentation of that class as if those 
     1829+# members were ordinary class members. Constructors, destructors and assignment 
     1830+# operators of the base classes will not be shown. 
     1831+ 
     1832+INLINE_INHERITED_MEMB  = NO 
     1833+ 
     1834+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
     1835+# path before files name in the file list and in the header files. If set 
     1836+# to NO the shortest path that makes the file name unique will be used. 
     1837+ 
     1838+FULL_PATH_NAMES        = NO 
     1839+ 
     1840+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
     1841+# can be used to strip a user-defined part of the path. Stripping is 
     1842+# only done if one of the specified strings matches the left-hand part of 
     1843+# the path. The tag can be used to show relative paths in the file list. 
     1844+# If left blank the directory from which doxygen is run is used as the 
     1845+# path to strip. 
     1846+ 
     1847+STRIP_FROM_PATH        = 
     1848+ 
     1849+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
     1850+# the path mentioned in the documentation of a class, which tells 
     1851+# the reader which header file to include in order to use a class. 
     1852+# If left blank only the name of the header file containing the class 
     1853+# definition is used. Otherwise one should specify the include paths that 
     1854+# are normally passed to the compiler using the -I flag. 
     1855+ 
     1856+STRIP_FROM_INC_PATH    = 
     1857+ 
     1858+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
     1859+# (but less readable) file names. This can be useful is your file systems 
     1860+# doesn't support long names like on DOS, Mac, or CD-ROM. 
     1861+ 
     1862+SHORT_NAMES            = NO 
     1863+ 
     1864+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
     1865+# will interpret the first line (until the first dot) of a JavaDoc-style 
     1866+# comment as the brief description. If set to NO, the JavaDoc 
     1867+# comments will behave just like regular Qt-style comments 
     1868+# (thus requiring an explicit @brief command for a brief description.) 
     1869+ 
     1870+JAVADOC_AUTOBRIEF      = YES 
     1871+ 
     1872+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
     1873+# interpret the first line (until the first dot) of a Qt-style 
     1874+# comment as the brief description. If set to NO, the comments 
     1875+# will behave just like regular Qt-style comments (thus requiring 
     1876+# an explicit \brief command for a brief description.) 
     1877+ 
     1878+QT_AUTOBRIEF           = NO 
     1879+ 
     1880+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
     1881+# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
     1882+# comments) as a brief description. This used to be the default behaviour. 
     1883+# The new default is to treat a multi-line C++ comment block as a detailed 
     1884+# description. Set this tag to YES if you prefer the old behaviour instead. 
     1885+ 
     1886+MULTILINE_CPP_IS_BRIEF = NO 
     1887+ 
     1888+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
     1889+# member inherits the documentation from any documented member that it 
     1890+# re-implements. 
     1891+ 
     1892+INHERIT_DOCS           = YES 
     1893+ 
     1894+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
     1895+# a new page for each member. If set to NO, the documentation of a member will 
     1896+# be part of the file/class/namespace that contains it. 
     1897+ 
     1898+SEPARATE_MEMBER_PAGES  = NO 
     1899+ 
     1900+# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
     1901+# Doxygen uses this value to replace tabs by spaces in code fragments. 
     1902+ 
     1903+TAB_SIZE               = 8 
     1904+ 
     1905+# This tag can be used to specify a number of aliases that acts 
     1906+# as commands in the documentation. An alias has the form "name=value". 
     1907+# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
     1908+# put the command \sideeffect (or @sideeffect) in the documentation, which 
     1909+# will result in a user-defined paragraph with heading "Side Effects:". 
     1910+# You can put \n's in the value part of an alias to insert newlines. 
     1911+ 
     1912+ALIASES                = 
     1913+ 
     1914+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
     1915+# sources only. Doxygen will then generate output that is more tailored for C. 
     1916+# For instance, some of the names that are used will be different. The list 
     1917+# of all members will be omitted, etc. 
     1918+ 
     1919+OPTIMIZE_OUTPUT_FOR_C  = YES 
     1920+ 
     1921+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
     1922+# sources only. Doxygen will then generate output that is more tailored for 
     1923+# Java. For instance, namespaces will be presented as packages, qualified 
     1924+# scopes will look different, etc. 
     1925+ 
     1926+OPTIMIZE_OUTPUT_JAVA   = NO 
     1927+ 
     1928+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 
     1929+# sources only. Doxygen will then generate output that is more tailored for 
     1930+# Fortran. 
     1931+ 
     1932+OPTIMIZE_FOR_FORTRAN   = NO 
     1933+ 
     1934+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 
     1935+# sources. Doxygen will then generate output that is tailored for 
     1936+# VHDL. 
     1937+ 
     1938+OPTIMIZE_OUTPUT_VHDL   = NO 
     1939+ 
     1940+# Doxygen selects the parser to use depending on the extension of the files it 
     1941+# parses. With this tag you can assign which parser to use for a given extension. 
     1942+# Doxygen has a built-in mapping, but you can override or extend it using this 
     1943+# tag. The format is ext=language, where ext is a file extension, and language 
     1944+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, 
     1945+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make 
     1946+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C 
     1947+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions 
     1948+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. 
     1949+ 
     1950+EXTENSION_MAPPING      = 
     1951+ 
     1952+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 
     1953+# to include (a tag file for) the STL sources as input, then you should 
     1954+# set this tag to YES in order to let doxygen match functions declarations and 
     1955+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
     1956+# func(std::string) {}). This also make the inheritance and collaboration 
     1957+# diagrams that involve STL classes more complete and accurate. 
     1958+ 
     1959+BUILTIN_STL_SUPPORT    = NO 
     1960+ 
     1961+# If you use Microsoft's C++/CLI language, you should set this option to YES to 
     1962+# enable parsing support. 
     1963+ 
     1964+CPP_CLI_SUPPORT        = NO 
     1965+ 
     1966+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 
     1967+# Doxygen will parse them like normal C++ but will assume all classes use public 
     1968+# instead of private inheritance when no explicit protection keyword is present. 
     1969+ 
     1970+SIP_SUPPORT            = NO 
     1971+ 
     1972+# For Microsoft's IDL there are propget and propput attributes to indicate getter 
     1973+# and setter methods for a property. Setting this option to YES (the default) 
     1974+# will make doxygen to replace the get and set methods by a property in the 
     1975+# documentation. This will only work if the methods are indeed getting or 
     1976+# setting a simple type. If this is not the case, or you want to show the 
     1977+# methods anyway, you should set this option to NO. 
     1978+ 
     1979+IDL_PROPERTY_SUPPORT   = YES 
     1980+ 
     1981+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
     1982+# tag is set to YES, then doxygen will reuse the documentation of the first 
     1983+# member in the group (if any) for the other members of the group. By default 
     1984+# all members of a group must be documented explicitly. 
     1985+ 
     1986+DISTRIBUTE_GROUP_DOC   = NO 
     1987+ 
     1988+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
     1989+# the same type (for instance a group of public functions) to be put as a 
     1990+# subgroup of that type (e.g. under the Public Functions section). Set it to 
     1991+# NO to prevent subgrouping. Alternatively, this can be done per class using 
     1992+# the \nosubgrouping command. 
     1993+ 
     1994+SUBGROUPING            = YES 
     1995+ 
     1996+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 
     1997+# is documented as struct, union, or enum with the name of the typedef. So 
     1998+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 
     1999+# with name TypeT. When disabled the typedef will appear as a member of a file, 
     2000+# namespace, or class. And the struct will be named TypeS. This can typically 
     2001+# be useful for C code in case the coding convention dictates that all compound 
     2002+# types are typedef'ed and only the typedef is referenced, never the tag name. 
     2003+ 
     2004+TYPEDEF_HIDES_STRUCT   = NO 
     2005+ 
     2006+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 
     2007+# determine which symbols to keep in memory and which to flush to disk. 
     2008+# When the cache is full, less often used symbols will be written to disk. 
     2009+# For small to medium size projects (<1000 input files) the default value is 
     2010+# probably good enough. For larger projects a too small cache size can cause 
     2011+# doxygen to be busy swapping symbols to and from disk most of the time 
     2012+# causing a significant performance penality. 
     2013+# If the system has enough physical memory increasing the cache will improve the 
     2014+# performance by keeping more symbols in memory. Note that the value works on 
     2015+# a logarithmic scale so increasing the size by one will rougly double the 
     2016+# memory usage. The cache size is given by this formula: 
     2017+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 
     2018+# corresponding to a cache size of 2^16 = 65536 symbols 
     2019+ 
     2020+SYMBOL_CACHE_SIZE      = 0 
     2021+ 
     2022+#--------------------------------------------------------------------------- 
     2023+# Build related configuration options 
     2024+#--------------------------------------------------------------------------- 
     2025+ 
     2026+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
     2027+# documentation are documented, even if no documentation was available. 
     2028+# Private class members and static file members will be hidden unless 
     2029+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 
     2030+ 
     2031+EXTRACT_ALL            = NO 
     2032+ 
     2033+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
     2034+# will be included in the documentation. 
     2035+ 
     2036+EXTRACT_PRIVATE        = NO 
     2037+ 
     2038+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
     2039+# will be included in the documentation. 
     2040+ 
     2041+EXTRACT_STATIC         = NO 
     2042+ 
     2043+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
     2044+# defined locally in source files will be included in the documentation. 
     2045+# If set to NO only classes defined in header files are included. 
     2046+ 
     2047+EXTRACT_LOCAL_CLASSES  = YES 
     2048+ 
     2049+# This flag is only useful for Objective-C code. When set to YES local 
     2050+# methods, which are defined in the implementation section but not in 
     2051+# the interface are included in the documentation. 
     2052+# If set to NO (the default) only methods in the interface are included. 
     2053+ 
     2054+EXTRACT_LOCAL_METHODS  = NO 
     2055+ 
     2056+# If this flag is set to YES, the members of anonymous namespaces will be 
     2057+# extracted and appear in the documentation as a namespace called 
     2058+# 'anonymous_namespace{file}', where file will be replaced with the base 
     2059+# name of the file that contains the anonymous namespace. By default 
     2060+# anonymous namespace are hidden. 
     2061+ 
     2062+EXTRACT_ANON_NSPACES   = NO 
     2063+ 
     2064+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
     2065+# undocumented members of documented classes, files or namespaces. 
     2066+# If set to NO (the default) these members will be included in the 
     2067+# various overviews, but no documentation section is generated. 
     2068+# This option has no effect if EXTRACT_ALL is enabled. 
     2069+ 
     2070+HIDE_UNDOC_MEMBERS     = NO 
     2071+ 
     2072+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
     2073+# undocumented classes that are normally visible in the class hierarchy. 
     2074+# If set to NO (the default) these classes will be included in the various 
     2075+# overviews. This option has no effect if EXTRACT_ALL is enabled. 
     2076+ 
     2077+HIDE_UNDOC_CLASSES     = NO 
     2078+ 
     2079+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
     2080+# friend (class|struct|union) declarations. 
     2081+# If set to NO (the default) these declarations will be included in the 
     2082+# documentation. 
     2083+ 
     2084+HIDE_FRIEND_COMPOUNDS  = NO 
     2085+ 
     2086+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
     2087+# documentation blocks found inside the body of a function. 
     2088+# If set to NO (the default) these blocks will be appended to the 
     2089+# function's detailed documentation block. 
     2090+ 
     2091+HIDE_IN_BODY_DOCS      = NO 
     2092+ 
     2093+# The INTERNAL_DOCS tag determines if documentation 
     2094+# that is typed after a \internal command is included. If the tag is set 
     2095+# to NO (the default) then the documentation will be excluded. 
     2096+# Set it to YES to include the internal documentation. 
     2097+ 
     2098+INTERNAL_DOCS          = NO 
     2099+ 
     2100+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
     2101+# file names in lower-case letters. If set to YES upper-case letters are also 
     2102+# allowed. This is useful if you have classes or files whose names only differ 
     2103+# in case and if your file system supports case sensitive file names. Windows 
     2104+# and Mac users are advised to set this option to NO. 
     2105+ 
     2106+CASE_SENSE_NAMES       = YES 
     2107+ 
     2108+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
     2109+# will show members with their full class and namespace scopes in the 
     2110+# documentation. If set to YES the scope will be hidden. 
     2111+ 
     2112+HIDE_SCOPE_NAMES       = NO 
     2113+ 
     2114+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
     2115+# will put a list of the files that are included by a file in the documentation 
     2116+# of that file. 
     2117+ 
     2118+SHOW_INCLUDE_FILES     = YES 
     2119+ 
     2120+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 
     2121+# will list include files with double quotes in the documentation 
     2122+# rather than with sharp brackets. 
     2123+ 
     2124+FORCE_LOCAL_INCLUDES   = NO 
     2125+ 
     2126+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
     2127+# is inserted in the documentation for inline members. 
     2128+ 
     2129+INLINE_INFO            = YES 
     2130+ 
     2131+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
     2132+# will sort the (detailed) documentation of file and class members 
     2133+# alphabetically by member name. If set to NO the members will appear in 
     2134+# declaration order. 
     2135+ 
     2136+SORT_MEMBER_DOCS       = YES 
     2137+ 
     2138+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
     2139+# brief documentation of file, namespace and class members alphabetically 
     2140+# by member name. If set to NO (the default) the members will appear in 
     2141+# declaration order. 
     2142+ 
     2143+SORT_BRIEF_DOCS        = NO 
     2144+ 
     2145+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 
     2146+# will sort the (brief and detailed) documentation of class members so that 
     2147+# constructors and destructors are listed first. If set to NO (the default) 
     2148+# the constructors will appear in the respective orders defined by 
     2149+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 
     2150+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 
     2151+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 
     2152+ 
     2153+SORT_MEMBERS_CTORS_1ST = NO 
     2154+ 
     2155+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 
     2156+# hierarchy of group names into alphabetical order. If set to NO (the default) 
     2157+# the group names will appear in their defined order. 
     2158+ 
     2159+SORT_GROUP_NAMES       = NO 
     2160+ 
     2161+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
     2162+# sorted by fully-qualified names, including namespaces. If set to 
     2163+# NO (the default), the class list will be sorted only by class name, 
     2164+# not including the namespace part. 
     2165+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 
     2166+# Note: This option applies only to the class list, not to the 
     2167+# alphabetical list. 
     2168+ 
     2169+SORT_BY_SCOPE_NAME     = NO 
     2170+ 
     2171+# The GENERATE_TODOLIST tag can be used to enable (YES) or 
     2172+# disable (NO) the todo list. This list is created by putting \todo 
     2173+# commands in the documentation. 
     2174+ 
     2175+GENERATE_TODOLIST      = YES 
     2176+ 
     2177+# The GENERATE_TESTLIST tag can be used to enable (YES) or 
     2178+# disable (NO) the test list. This list is created by putting \test 
     2179+# commands in the documentation. 
     2180+ 
     2181+GENERATE_TESTLIST      = YES 
     2182+ 
     2183+# The GENERATE_BUGLIST tag can be used to enable (YES) or 
     2184+# disable (NO) the bug list. This list is created by putting \bug 
     2185+# commands in the documentation. 
     2186+ 
     2187+GENERATE_BUGLIST       = YES 
     2188+ 
     2189+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
     2190+# disable (NO) the deprecated list. This list is created by putting 
     2191+# \deprecated commands in the documentation. 
     2192+ 
     2193+GENERATE_DEPRECATEDLIST= YES 
     2194+ 
     2195+# The ENABLED_SECTIONS tag can be used to enable conditional 
     2196+# documentation sections, marked by \if sectionname ... \endif. 
     2197+ 
     2198+ENABLED_SECTIONS       = 
     2199+ 
     2200+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
     2201+# the initial value of a variable or define consists of for it to appear in 
     2202+# the documentation. If the initializer consists of more lines than specified 
     2203+# here it will be hidden. Use a value of 0 to hide initializers completely. 
     2204+# The appearance of the initializer of individual variables and defines in the 
     2205+# documentation can be controlled using \showinitializer or \hideinitializer 
     2206+# command in the documentation regardless of this setting. 
     2207+ 
     2208+MAX_INITIALIZER_LINES  = 30 
     2209+ 
     2210+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
     2211+# at the bottom of the documentation of classes and structs. If set to YES the 
     2212+# list will mention the files that were used to generate the documentation. 
     2213+ 
     2214+SHOW_USED_FILES        = YES 
     2215+ 
     2216+# If the sources in your project are distributed over multiple directories 
     2217+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
     2218+# in the documentation. The default is NO. 
     2219+ 
     2220+SHOW_DIRECTORIES       = NO 
     2221+ 
     2222+# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 
     2223+# This will remove the Files entry from the Quick Index and from the 
     2224+# Folder Tree View (if specified). The default is YES. 
     2225+ 
     2226+SHOW_FILES             = YES 
     2227+ 
     2228+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 
     2229+# Namespaces page. 
     2230+# This will remove the Namespaces entry from the Quick Index 
     2231+# and from the Folder Tree View (if specified). The default is YES. 
     2232+ 
     2233+SHOW_NAMESPACES        = YES 
     2234+ 
     2235+# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
     2236+# doxygen should invoke to get the current version for each file (typically from 
     2237+# the version control system). Doxygen will invoke the program by executing (via 
     2238+# popen()) the command <command> <input-file>, where <command> is the value of 
     2239+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
     2240+# provided by doxygen. Whatever the program writes to standard output 
     2241+# is used as the file version. See the manual for examples. 
     2242+ 
     2243+FILE_VERSION_FILTER    = 
     2244+ 
     2245+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 
     2246+# by doxygen. The layout file controls the global structure of the generated 
     2247+# output files in an output format independent way. The create the layout file 
     2248+# that represents doxygen's defaults, run doxygen with the -l option. 
     2249+# You can optionally specify a file name after the option, if omitted 
     2250+# DoxygenLayout.xml will be used as the name of the layout file. 
     2251+ 
     2252+LAYOUT_FILE            = 
     2253+ 
     2254+#--------------------------------------------------------------------------- 
     2255+# configuration options related to warning and progress messages 
     2256+#--------------------------------------------------------------------------- 
     2257+ 
     2258+# The QUIET tag can be used to turn on/off the messages that are generated 
     2259+# by doxygen. Possible values are YES and NO. If left blank NO is used. 
     2260+ 
     2261+QUIET                  = YES 
     2262+ 
     2263+# The WARNINGS tag can be used to turn on/off the warning messages that are 
     2264+# generated by doxygen. Possible values are YES and NO. If left blank 
     2265+# NO is used. 
     2266+ 
     2267+WARNINGS               = YES 
     2268+ 
     2269+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
     2270+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
     2271+# automatically be disabled. 
     2272+ 
     2273+WARN_IF_UNDOCUMENTED   = YES 
     2274+ 
     2275+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
     2276+# potential errors in the documentation, such as not documenting some 
     2277+# parameters in a documented function, or documenting parameters that 
     2278+# don't exist or using markup commands wrongly. 
     2279+ 
     2280+WARN_IF_DOC_ERROR      = YES 
     2281+ 
     2282+# This WARN_NO_PARAMDOC option can be abled to get warnings for 
     2283+# functions that are documented, but have no documentation for their parameters 
     2284+# or return value. If set to NO (the default) doxygen will only warn about 
     2285+# wrong or incomplete parameter documentation, but not about the absence of 
     2286+# documentation. 
     2287+ 
     2288+WARN_NO_PARAMDOC       = NO 
     2289+ 
     2290+# The WARN_FORMAT tag determines the format of the warning messages that 
     2291+# doxygen can produce. The string should contain the $file, $line, and $text 
     2292+# tags, which will be replaced by the file and line number from which the 
     2293+# warning originated and the warning text. Optionally the format may contain 
     2294+# $version, which will be replaced by the version of the file (if it could 
     2295+# be obtained via FILE_VERSION_FILTER) 
     2296+ 
     2297+WARN_FORMAT            = 
     2298+ 
     2299+# The WARN_LOGFILE tag can be used to specify a file to which warning 
     2300+# and error messages should be written. If left blank the output is written 
     2301+# to stderr. 
     2302+ 
     2303+WARN_LOGFILE           = 
     2304+ 
     2305+#--------------------------------------------------------------------------- 
     2306+# configuration options related to the input files 
     2307+#--------------------------------------------------------------------------- 
     2308+ 
     2309+# The INPUT tag can be used to specify the files and/or directories that contain 
     2310+# documented source files. You may enter file names like "myfile.cpp" or 
     2311+# directories like "/usr/src/myproject". Separate the files or directories 
     2312+# with spaces. 
     2313+ 
     2314+INPUT                  = @top_srcdir@/dbus 
     2315+ 
     2316+# This tag can be used to specify the character encoding of the source files 
     2317+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 
     2318+# also the default input encoding. Doxygen uses libiconv (or the iconv built 
     2319+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 
     2320+# the list of possible encodings. 
     2321+ 
     2322+INPUT_ENCODING         = UTF-8 
     2323+ 
     2324+# If the value of the INPUT tag contains directories, you can use the 
     2325+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
     2326+# and *.h) to filter out the source-files in the directories. If left 
     2327+# blank the following patterns are tested: 
     2328+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
     2329+# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 
     2330+ 
     2331+FILE_PATTERNS          = *.c \ 
     2332+                         *.h 
     2333+ 
     2334+# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
     2335+# should be searched for input files as well. Possible values are YES and NO. 
     2336+# If left blank NO is used. 
     2337+ 
     2338+RECURSIVE              = YES 
     2339+ 
     2340+# The EXCLUDE tag can be used to specify files and/or directories that should 
     2341+# excluded from the INPUT source files. This way you can easily exclude a 
     2342+# subdirectory from a directory tree whose root is specified with the INPUT tag. 
     2343+ 
     2344+EXCLUDE                = 
     2345+ 
     2346+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
     2347+# directories that are symbolic links (a Unix filesystem feature) are excluded 
     2348+# from the input. 
     2349+ 
     2350+EXCLUDE_SYMLINKS       = NO 
     2351+ 
     2352+# If the value of the INPUT tag contains directories, you can use the 
     2353+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
     2354+# certain files from those directories. Note that the wildcards are matched 
     2355+# against the file with absolute path, so to exclude all test directories 
     2356+# for example use the pattern */test/* 
     2357+ 
     2358+EXCLUDE_PATTERNS       = Makefile.* \ 
     2359+                         ChangeLog \ 
     2360+                         CHANGES \ 
     2361+                         CHANGES.* \ 
     2362+                         README \ 
     2363+                         README.* \ 
     2364+                         *.png \ 
     2365+                         AUTHORS \ 
     2366+                         DESIGN \ 
     2367+                         DESIGN.* \ 
     2368+                         *.desktop \ 
     2369+                         DESKTOP* \ 
     2370+                         COMMENTS \ 
     2371+                         HOWTO \ 
     2372+                         magic \ 
     2373+                         NOTES \ 
     2374+                         TODO \ 
     2375+                         THANKS 
     2376+ 
     2377+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
     2378+# (namespaces, classes, functions, etc.) that should be excluded from the 
     2379+# output. The symbol name can be a fully qualified name, a word, or if the 
     2380+# wildcard * is used, a substring. Examples: ANamespace, AClass, 
     2381+# AClass::ANamespace, ANamespace::*Test 
     2382+ 
     2383+EXCLUDE_SYMBOLS        = 
     2384+ 
     2385+# The EXAMPLE_PATH tag can be used to specify one or more files or 
     2386+# directories that contain example code fragments that are included (see 
     2387+# the \include command). 
     2388+ 
     2389+EXAMPLE_PATH           = 
     2390+ 
     2391+# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
     2392+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
     2393+# and *.h) to filter out the source-files in the directories. If left 
     2394+# blank all files are included. 
     2395+ 
     2396+EXAMPLE_PATTERNS       = 
     2397+ 
     2398+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
     2399+# searched for input files to be used with the \include or \dontinclude 
     2400+# commands irrespective of the value of the RECURSIVE tag. 
     2401+# Possible values are YES and NO. If left blank NO is used. 
     2402+ 
     2403+EXAMPLE_RECURSIVE      = NO 
     2404+ 
     2405+# The IMAGE_PATH tag can be used to specify one or more files or 
     2406+# directories that contain image that are included in the documentation (see 
     2407+# the \image command). 
     2408+ 
     2409+IMAGE_PATH             = 
     2410+ 
     2411+# The INPUT_FILTER tag can be used to specify a program that doxygen should 
     2412+# invoke to filter for each input file. Doxygen will invoke the filter program 
     2413+# by executing (via popen()) the command <filter> <input-file>, where <filter> 
     2414+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
     2415+# input file. Doxygen will then use the output that the filter program writes 
     2416+# to standard output. 
     2417+# If FILTER_PATTERNS is specified, this tag will be 
     2418+# ignored. 
     2419+ 
     2420+INPUT_FILTER           = 
     2421+ 
     2422+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
     2423+# basis. 
     2424+# Doxygen will compare the file name with each pattern and apply the 
     2425+# filter if there is a match. 
     2426+# The filters are a list of the form: 
     2427+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
     2428+# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
     2429+# is applied to all files. 
     2430+ 
     2431+FILTER_PATTERNS        = 
     2432+ 
     2433+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
     2434+# INPUT_FILTER) will be used to filter the input files when producing source 
     2435+# files to browse (i.e. when SOURCE_BROWSER is set to YES). 
     2436+ 
     2437+FILTER_SOURCE_FILES    = NO 
     2438+ 
     2439+#--------------------------------------------------------------------------- 
     2440+# configuration options related to source browsing 
     2441+#--------------------------------------------------------------------------- 
     2442+ 
     2443+# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
     2444+# be generated. Documented entities will be cross-referenced with these sources. 
     2445+# Note: To get rid of all source code in the generated output, make sure also 
     2446+# VERBATIM_HEADERS is set to NO. 
     2447+ 
     2448+SOURCE_BROWSER         = YES 
     2449+ 
     2450+# Setting the INLINE_SOURCES tag to YES will include the body 
     2451+# of functions and classes directly in the documentation. 
     2452+ 
     2453+INLINE_SOURCES         = NO 
     2454+ 
     2455+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
     2456+# doxygen to hide any special comment blocks from generated source code 
     2457+# fragments. Normal C and C++ comments will always remain visible. 
     2458+ 
     2459+STRIP_CODE_COMMENTS    = YES 
     2460+ 
     2461+# If the REFERENCED_BY_RELATION tag is set to YES 
     2462+# then for each documented function all documented 
     2463+# functions referencing it will be listed. 
     2464+ 
     2465+REFERENCED_BY_RELATION = YES 
     2466+ 
     2467+# If the REFERENCES_RELATION tag is set to YES 
     2468+# then for each documented function all documented entities 
     2469+# called/used by that function will be listed. 
     2470+ 
     2471+REFERENCES_RELATION    = YES 
     2472+ 
     2473+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 
     2474+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 
     2475+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 
     2476+# link to the source code. 
     2477+# Otherwise they will link to the documentation. 
     2478+ 
     2479+REFERENCES_LINK_SOURCE = YES 
     2480+ 
     2481+# If the USE_HTAGS tag is set to YES then the references to source code 
     2482+# will point to the HTML generated by the htags(1) tool instead of doxygen 
     2483+# built-in source browser. The htags tool is part of GNU's global source 
     2484+# tagging system (see http://www.gnu.org/software/global/global.html). You 
     2485+# will need version 4.8.6 or higher. 
     2486+ 
     2487+USE_HTAGS              = NO 
     2488+ 
     2489+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
     2490+# will generate a verbatim copy of the header file for each class for 
     2491+# which an include is specified. Set to NO to disable this. 
     2492+ 
     2493+VERBATIM_HEADERS       = YES 
     2494+ 
     2495+#--------------------------------------------------------------------------- 
     2496+# configuration options related to the alphabetical class index 
     2497+#--------------------------------------------------------------------------- 
     2498+ 
     2499+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
     2500+# of all compounds will be generated. Enable this if the project 
     2501+# contains a lot of classes, structs, unions or interfaces. 
     2502+ 
     2503+ALPHABETICAL_INDEX     = NO 
     2504+ 
     2505+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
     2506+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
     2507+# in which this list will be split (can be a number in the range [1..20]) 
     2508+ 
     2509+COLS_IN_ALPHA_INDEX    = 5 
     2510+ 
     2511+# In case all classes in a project start with a common prefix, all 
     2512+# classes will be put under the same header in the alphabetical index. 
     2513+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
     2514+# should be ignored while generating the index headers. 
     2515+ 
     2516+IGNORE_PREFIX          = 
     2517+ 
     2518+#--------------------------------------------------------------------------- 
     2519+# configuration options related to the HTML output 
     2520+#--------------------------------------------------------------------------- 
     2521+ 
     2522+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
     2523+# generate HTML output. 
     2524+ 
     2525+GENERATE_HTML          = YES 
     2526+ 
     2527+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
     2528+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     2529+# put in front of it. If left blank `html' will be used as the default path. 
     2530+ 
     2531+HTML_OUTPUT            = 
     2532+ 
     2533+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
     2534+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
     2535+# doxygen will generate files with .html extension. 
     2536+ 
     2537+HTML_FILE_EXTENSION    = .html 
     2538+ 
     2539+# The HTML_HEADER tag can be used to specify a personal HTML header for 
     2540+# each generated HTML page. If it is left blank doxygen will generate a 
     2541+# standard header. 
     2542+ 
     2543+HTML_HEADER            = 
     2544+ 
     2545+# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
     2546+# each generated HTML page. If it is left blank doxygen will generate a 
     2547+# standard footer. 
     2548+ 
     2549+HTML_FOOTER            = 
     2550+ 
     2551+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
     2552+# style sheet that is used by each HTML page. It can be used to 
     2553+# fine-tune the look of the HTML output. If the tag is left blank doxygen 
     2554+# will generate a default style sheet. Note that doxygen will try to copy 
     2555+# the style sheet file to the HTML output directory, so don't put your own 
     2556+# stylesheet in the HTML output directory as well, or it will be erased! 
     2557+ 
     2558+HTML_STYLESHEET        = 
     2559+ 
     2560+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 
     2561+# Doxygen will adjust the colors in the stylesheet and background images 
     2562+# according to this color. Hue is specified as an angle on a colorwheel, 
     2563+# see http://en.wikipedia.org/wiki/Hue for more information. 
     2564+# For instance the value 0 represents red, 60 is yellow, 120 is green, 
     2565+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 
     2566+# The allowed range is 0 to 359. 
     2567+ 
     2568+HTML_COLORSTYLE_HUE    = 220 
     2569+ 
     2570+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 
     2571+# the colors in the HTML output. For a value of 0 the output will use 
     2572+# grayscales only. A value of 255 will produce the most vivid colors. 
     2573+ 
     2574+HTML_COLORSTYLE_SAT    = 100 
     2575+ 
     2576+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 
     2577+# the luminance component of the colors in the HTML output. Values below 
     2578+# 100 gradually make the output lighter, whereas values above 100 make 
     2579+# the output darker. The value divided by 100 is the actual gamma applied, 
     2580+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 
     2581+# and 100 does not change the gamma. 
     2582+ 
     2583+HTML_COLORSTYLE_GAMMA  = 80 
     2584+ 
     2585+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 
     2586+# page will contain the date and time when the page was generated. Setting 
     2587+# this to NO can help when comparing the output of multiple runs. 
     2588+ 
     2589+HTML_TIMESTAMP         = YES 
     2590+ 
     2591+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
     2592+# files or namespaces will be aligned in HTML using tables. If set to 
     2593+# NO a bullet list will be used. 
     2594+ 
     2595+HTML_ALIGN_MEMBERS     = YES 
     2596+ 
     2597+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
     2598+# documentation will contain sections that can be hidden and shown after the 
     2599+# page has loaded. For this to work a browser that supports 
     2600+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 
     2601+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 
     2602+ 
     2603+HTML_DYNAMIC_SECTIONS  = NO 
     2604+ 
     2605+# If the GENERATE_DOCSET tag is set to YES, additional index files 
     2606+# will be generated that can be used as input for Apple's Xcode 3 
     2607+# integrated development environment, introduced with OSX 10.5 (Leopard). 
     2608+# To create a documentation set, doxygen will generate a Makefile in the 
     2609+# HTML output directory. Running make will produce the docset in that 
     2610+# directory and running "make install" will install the docset in 
     2611+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 
     2612+# it at startup. 
     2613+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 
     2614+# for more information. 
     2615+ 
     2616+GENERATE_DOCSET        = NO 
     2617+ 
     2618+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 
     2619+# feed. A documentation feed provides an umbrella under which multiple 
     2620+# documentation sets from a single provider (such as a company or product suite) 
     2621+# can be grouped. 
     2622+ 
     2623+DOCSET_FEEDNAME        = "Doxygen generated docs" 
     2624+ 
     2625+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 
     2626+# should uniquely identify the documentation set bundle. This should be a 
     2627+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 
     2628+# will append .docset to the name. 
     2629+ 
     2630+DOCSET_BUNDLE_ID       = org.doxygen.Project 
     2631+ 
     2632+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify 
     2633+# the documentation publisher. This should be a reverse domain-name style 
     2634+# string, e.g. com.mycompany.MyDocSet.documentation. 
     2635+ 
     2636+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher 
     2637+ 
     2638+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. 
     2639+ 
     2640+DOCSET_PUBLISHER_NAME  = Publisher 
     2641+ 
     2642+# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
     2643+# will be generated that can be used as input for tools like the 
     2644+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 
     2645+# of the generated HTML documentation. 
     2646+ 
     2647+GENERATE_HTMLHELP      = NO 
     2648+ 
     2649+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
     2650+# be used to specify the file name of the resulting .chm file. You 
     2651+# can add a path in front of the file if the result should not be 
     2652+# written to the html output directory. 
     2653+ 
     2654+CHM_FILE               = 
     2655+ 
     2656+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
     2657+# be used to specify the location (absolute path including file name) of 
     2658+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
     2659+# the HTML help compiler on the generated index.hhp. 
     2660+ 
     2661+HHC_LOCATION           = 
     2662+ 
     2663+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
     2664+# controls if a separate .chi index file is generated (YES) or that 
     2665+# it should be included in the master .chm file (NO). 
     2666+ 
     2667+GENERATE_CHI           = NO 
     2668+ 
     2669+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 
     2670+# is used to encode HtmlHelp index (hhk), content (hhc) and project file 
     2671+# content. 
     2672+ 
     2673+CHM_INDEX_ENCODING     = 
     2674+ 
     2675+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
     2676+# controls whether a binary table of contents is generated (YES) or a 
     2677+# normal table of contents (NO) in the .chm file. 
     2678+ 
     2679+BINARY_TOC             = NO 
     2680+ 
     2681+# The TOC_EXPAND flag can be set to YES to add extra items for group members 
     2682+# to the contents of the HTML help documentation and to the tree view. 
     2683+ 
     2684+TOC_EXPAND             = NO 
     2685+ 
     2686+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 
     2687+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 
     2688+# that can be used as input for Qt's qhelpgenerator to generate a 
     2689+# Qt Compressed Help (.qch) of the generated HTML documentation. 
     2690+ 
     2691+GENERATE_QHP           = NO 
     2692+ 
     2693+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 
     2694+# be used to specify the file name of the resulting .qch file. 
     2695+# The path specified is relative to the HTML output folder. 
     2696+ 
     2697+QCH_FILE               = 
     2698+ 
     2699+# The QHP_NAMESPACE tag specifies the namespace to use when generating 
     2700+# Qt Help Project output. For more information please see 
     2701+# http://doc.trolltech.com/qthelpproject.html#namespace 
     2702+ 
     2703+QHP_NAMESPACE          = org.doxygen.Project 
     2704+ 
     2705+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 
     2706+# Qt Help Project output. For more information please see 
     2707+# http://doc.trolltech.com/qthelpproject.html#virtual-folders 
     2708+ 
     2709+QHP_VIRTUAL_FOLDER     = doc 
     2710+ 
     2711+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 
     2712+# add. For more information please see 
     2713+# http://doc.trolltech.com/qthelpproject.html#custom-filters 
     2714+ 
     2715+QHP_CUST_FILTER_NAME   = 
     2716+ 
     2717+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 
     2718+# custom filter to add. For more information please see 
     2719+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> 
     2720+# Qt Help Project / Custom Filters</a>. 
     2721+ 
     2722+QHP_CUST_FILTER_ATTRS  = 
     2723+ 
     2724+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 
     2725+# project's 
     2726+# filter section matches. 
     2727+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> 
     2728+# Qt Help Project / Filter Attributes</a>. 
     2729+ 
     2730+QHP_SECT_FILTER_ATTRS  = 
     2731+ 
     2732+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 
     2733+# be used to specify the location of Qt's qhelpgenerator. 
     2734+# If non-empty doxygen will try to run qhelpgenerator on the generated 
     2735+# .qhp file. 
     2736+ 
     2737+QHG_LOCATION           = 
     2738+ 
     2739+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files 
     2740+#  will be generated, which together with the HTML files, form an Eclipse help 
     2741+# plugin. To install this plugin and make it available under the help contents 
     2742+# menu in Eclipse, the contents of the directory containing the HTML and XML 
     2743+# files needs to be copied into the plugins directory of eclipse. The name of 
     2744+# the directory within the plugins directory should be the same as 
     2745+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 
     2746+# the help appears. 
     2747+ 
     2748+GENERATE_ECLIPSEHELP   = NO 
     2749+ 
     2750+# A unique identifier for the eclipse help plugin. When installing the plugin 
     2751+# the directory name containing the HTML and XML files should also have 
     2752+# this name. 
     2753+ 
     2754+ECLIPSE_DOC_ID         = org.doxygen.Project 
     2755+ 
     2756+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
     2757+# top of each HTML page. The value NO (the default) enables the index and 
     2758+# the value YES disables it. 
     2759+ 
     2760+DISABLE_INDEX          = NO 
     2761+ 
     2762+# This tag can be used to set the number of enum values (range [1..20]) 
     2763+# that doxygen will group on one line in the generated HTML documentation. 
     2764+ 
     2765+ENUM_VALUES_PER_LINE   = 4 
     2766+ 
     2767+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 
     2768+# structure should be generated to display hierarchical information. 
     2769+# If the tag value is set to YES, a side panel will be generated 
     2770+# containing a tree-like index structure (just like the one that 
     2771+# is generated for HTML Help). For this to work a browser that supports 
     2772+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 
     2773+# Windows users are probably better off using the HTML help feature. 
     2774+ 
     2775+GENERATE_TREEVIEW      = NO 
     2776+ 
     2777+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 
     2778+# and Class Hierarchy pages using a tree view instead of an ordered list. 
     2779+ 
     2780+USE_INLINE_TREES       = NO 
     2781+ 
     2782+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
     2783+# used to set the initial width (in pixels) of the frame in which the tree 
     2784+# is shown. 
     2785+ 
     2786+TREEVIEW_WIDTH         = 250 
     2787+ 
     2788+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 
     2789+# links to external symbols imported via tag files in a separate window. 
     2790+ 
     2791+EXT_LINKS_IN_WINDOW    = NO 
     2792+ 
     2793+# Use this tag to change the font size of Latex formulas included 
     2794+# as images in the HTML documentation. The default is 10. Note that 
     2795+# when you change the font size after a successful doxygen run you need 
     2796+# to manually remove any form_*.png images from the HTML output directory 
     2797+# to force them to be regenerated. 
     2798+ 
     2799+FORMULA_FONTSIZE       = 10 
     2800+ 
     2801+# Use the FORMULA_TRANPARENT tag to determine whether or not the images 
     2802+# generated for formulas are transparent PNGs. Transparent PNGs are 
     2803+# not supported properly for IE 6.0, but are supported on all modern browsers. 
     2804+# Note that when changing this option you need to delete any form_*.png files 
     2805+# in the HTML output before the changes have effect. 
     2806+ 
     2807+FORMULA_TRANSPARENT    = YES 
     2808+ 
     2809+# When the SEARCHENGINE tag is enabled doxygen will generate a search box 
     2810+# for the HTML output. The underlying search engine uses javascript 
     2811+# and DHTML and should work on any modern browser. Note that when using 
     2812+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 
     2813+# (GENERATE_DOCSET) there is already a search function so this one should 
     2814+# typically be disabled. For large projects the javascript based search engine 
     2815+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. 
     2816+ 
     2817+SEARCHENGINE           = NO 
     2818+ 
     2819+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be 
     2820+# implemented using a PHP enabled web server instead of at the web client 
     2821+# using Javascript. Doxygen will generate the search PHP script and index 
     2822+# file to put on the web server. The advantage of the server 
     2823+# based approach is that it scales better to large projects and allows 
     2824+# full text search. The disadvances is that it is more difficult to setup 
     2825+# and does not have live searching capabilities. 
     2826+ 
     2827+SERVER_BASED_SEARCH    = NO 
     2828+ 
     2829+#--------------------------------------------------------------------------- 
     2830+# configuration options related to the LaTeX output 
     2831+#--------------------------------------------------------------------------- 
     2832+ 
     2833+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
     2834+# generate Latex output. 
     2835+ 
     2836+GENERATE_LATEX         = NO 
     2837+ 
     2838+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
     2839+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     2840+# put in front of it. If left blank `latex' will be used as the default path. 
     2841+ 
     2842+LATEX_OUTPUT           = 
     2843+ 
     2844+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
     2845+# invoked. If left blank `latex' will be used as the default command name. 
     2846+# Note that when enabling USE_PDFLATEX this option is only used for 
     2847+# generating bitmaps for formulas in the HTML output, but not in the 
     2848+# Makefile that is written to the output directory. 
     2849+ 
     2850+LATEX_CMD_NAME         = latex 
     2851+ 
     2852+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
     2853+# generate index for LaTeX. If left blank `makeindex' will be used as the 
     2854+# default command name. 
     2855+ 
     2856+MAKEINDEX_CMD_NAME     = makeindex 
     2857+ 
     2858+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
     2859+# LaTeX documents. This may be useful for small projects and may help to 
     2860+# save some trees in general. 
     2861+ 
     2862+COMPACT_LATEX          = NO 
     2863+ 
     2864+# The PAPER_TYPE tag can be used to set the paper type that is used 
     2865+# by the printer. Possible values are: a4, a4wide, letter, legal and 
     2866+# executive. If left blank a4wide will be used. 
     2867+ 
     2868+PAPER_TYPE             = a4wide 
     2869+ 
     2870+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
     2871+# packages that should be included in the LaTeX output. 
     2872+ 
     2873+EXTRA_PACKAGES         = 
     2874+ 
     2875+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
     2876+# the generated latex document. The header should contain everything until 
     2877+# the first chapter. If it is left blank doxygen will generate a 
     2878+# standard header. Notice: only use this tag if you know what you are doing! 
     2879+ 
     2880+LATEX_HEADER           = 
     2881+ 
     2882+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
     2883+# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
     2884+# contain links (just like the HTML output) instead of page references 
     2885+# This makes the output suitable for online browsing using a pdf viewer. 
     2886+ 
     2887+PDF_HYPERLINKS         = NO 
     2888+ 
     2889+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
     2890+# plain latex in the generated Makefile. Set this option to YES to get a 
     2891+# higher quality PDF documentation. 
     2892+ 
     2893+USE_PDFLATEX           = NO 
     2894+ 
     2895+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
     2896+# command to the generated LaTeX files. This will instruct LaTeX to keep 
     2897+# running if errors occur, instead of asking the user for help. 
     2898+# This option is also used when generating formulas in HTML. 
     2899+ 
     2900+LATEX_BATCHMODE        = NO 
     2901+ 
     2902+# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
     2903+# include the index chapters (such as File Index, Compound Index, etc.) 
     2904+# in the output. 
     2905+ 
     2906+LATEX_HIDE_INDICES     = NO 
     2907+ 
     2908+# If LATEX_SOURCE_CODE is set to YES then doxygen will include 
     2909+# source code with syntax highlighting in the LaTeX output. 
     2910+# Note that which sources are shown also depends on other settings 
     2911+# such as SOURCE_BROWSER. 
     2912+ 
     2913+LATEX_SOURCE_CODE      = NO 
     2914+ 
     2915+#--------------------------------------------------------------------------- 
     2916+# configuration options related to the RTF output 
     2917+#--------------------------------------------------------------------------- 
     2918+ 
     2919+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
     2920+# The RTF output is optimized for Word 97 and may not look very pretty with 
     2921+# other RTF readers or editors. 
     2922+ 
     2923+GENERATE_RTF           = NO 
     2924+ 
     2925+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
     2926+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     2927+# put in front of it. If left blank `rtf' will be used as the default path. 
     2928+ 
     2929+RTF_OUTPUT             = 
     2930+ 
     2931+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
     2932+# RTF documents. This may be useful for small projects and may help to 
     2933+# save some trees in general. 
     2934+ 
     2935+COMPACT_RTF            = NO 
     2936+ 
     2937+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
     2938+# will contain hyperlink fields. The RTF file will 
     2939+# contain links (just like the HTML output) instead of page references. 
     2940+# This makes the output suitable for online browsing using WORD or other 
     2941+# programs which support those fields. 
     2942+# Note: wordpad (write) and others do not support links. 
     2943+ 
     2944+RTF_HYPERLINKS         = NO 
     2945+ 
     2946+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
     2947+# config file, i.e. a series of assignments. You only have to provide 
     2948+# replacements, missing definitions are set to their default value. 
     2949+ 
     2950+RTF_STYLESHEET_FILE    = 
     2951+ 
     2952+# Set optional variables used in the generation of an rtf document. 
     2953+# Syntax is similar to doxygen's config file. 
     2954+ 
     2955+RTF_EXTENSIONS_FILE    = 
     2956+ 
     2957+#--------------------------------------------------------------------------- 
     2958+# configuration options related to the man page output 
     2959+#--------------------------------------------------------------------------- 
     2960+ 
     2961+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
     2962+# generate man pages 
     2963+ 
     2964+GENERATE_MAN           = YES 
     2965+ 
     2966+# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
     2967+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     2968+# put in front of it. If left blank `man' will be used as the default path. 
     2969+ 
     2970+MAN_OUTPUT             = man 
     2971+ 
     2972+# The MAN_EXTENSION tag determines the extension that is added to 
     2973+# the generated man pages (default is the subroutine's section .3) 
     2974+ 
     2975+MAN_EXTENSION          = .3dbus 
     2976+ 
     2977+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
     2978+# then it will generate one additional man file for each entity 
     2979+# documented in the real man page(s). These additional files 
     2980+# only source the real man page, but without them the man command 
     2981+# would be unable to find the correct page. The default is NO. 
     2982+ 
     2983+MAN_LINKS              = YES 
     2984+ 
     2985+#--------------------------------------------------------------------------- 
     2986+# configuration options related to the XML output 
     2987+#--------------------------------------------------------------------------- 
     2988+ 
     2989+# If the GENERATE_XML tag is set to YES Doxygen will 
     2990+# generate an XML file that captures the structure of 
     2991+# the code including all documentation. 
     2992+ 
     2993+GENERATE_XML           = YES 
     2994+ 
     2995+# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
     2996+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
     2997+# put in front of it. If left blank `xml' will be used as the default path. 
     2998+ 
     2999+XML_OUTPUT             = xml 
     3000+ 
     3001+# The XML_SCHEMA tag can be used to specify an XML schema, 
     3002+# which can be used by a validating XML parser to check the 
     3003+# syntax of the XML files. 
     3004+ 
     3005+XML_SCHEMA             = 
     3006+ 
     3007+# The XML_DTD tag can be used to specify an XML DTD, 
     3008+# which can be used by a validating XML parser to check the 
     3009+# syntax of the XML files. 
     3010+ 
     3011+XML_DTD                = 
     3012+ 
     3013+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
     3014+# dump the program listings (including syntax highlighting 
     3015+# and cross-referencing information) to the XML output. Note that 
     3016+# enabling this will significantly increase the size of the XML output. 
     3017+ 
     3018+XML_PROGRAMLISTING     = YES 
     3019+ 
     3020+#--------------------------------------------------------------------------- 
     3021+# configuration options for the AutoGen Definitions output 
     3022+#--------------------------------------------------------------------------- 
     3023+ 
     3024+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
     3025+# generate an AutoGen Definitions (see autogen.sf.net) file 
     3026+# that captures the structure of the code including all 
     3027+# documentation. Note that this feature is still experimental 
     3028+# and incomplete at the moment. 
     3029+ 
     3030+GENERATE_AUTOGEN_DEF   = NO 
     3031+ 
     3032+#--------------------------------------------------------------------------- 
     3033+# configuration options related to the Perl module output 
     3034+#--------------------------------------------------------------------------- 
     3035+ 
     3036+# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
     3037+# generate a Perl module file that captures the structure of 
     3038+# the code including all documentation. Note that this 
     3039+# feature is still experimental and incomplete at the 
     3040+# moment. 
     3041+ 
     3042+GENERATE_PERLMOD       = NO 
     3043+ 
     3044+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
     3045+# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
     3046+# to generate PDF and DVI output from the Perl module output. 
     3047+ 
     3048+PERLMOD_LATEX          = NO 
     3049+ 
     3050+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
     3051+# nicely formatted so it can be parsed by a human reader. 
     3052+# This is useful 
     3053+# if you want to understand what is going on. 
     3054+# On the other hand, if this 
     3055+# tag is set to NO the size of the Perl module output will be much smaller 
     3056+# and Perl will parse it just the same. 
     3057+ 
     3058+PERLMOD_PRETTY         = YES 
     3059+ 
     3060+# The names of the make variables in the generated doxyrules.make file 
     3061+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
     3062+# This is useful so different doxyrules.make files included by the same 
     3063+# Makefile don't overwrite each other's variables. 
     3064+ 
     3065+PERLMOD_MAKEVAR_PREFIX = 
     3066+ 
     3067+#--------------------------------------------------------------------------- 
     3068+# Configuration options related to the preprocessor 
     3069+#--------------------------------------------------------------------------- 
     3070+ 
     3071+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
     3072+# evaluate all C-preprocessor directives found in the sources and include 
     3073+# files. 
     3074+ 
     3075+ENABLE_PREPROCESSING   = YES 
     3076+ 
     3077+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
     3078+# names in the source code. If set to NO (the default) only conditional 
     3079+# compilation will be performed. Macro expansion can be done in a controlled 
     3080+# way by setting EXPAND_ONLY_PREDEF to YES. 
     3081+ 
     3082+MACRO_EXPANSION        = YES 
     3083+ 
     3084+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
     3085+# then the macro expansion is limited to the macros specified with the 
     3086+# PREDEFINED and EXPAND_AS_DEFINED tags. 
     3087+ 
     3088+EXPAND_ONLY_PREDEF     = YES 
     3089+ 
     3090+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
     3091+# in the INCLUDE_PATH (see below) will be search if a #include is found. 
     3092+ 
     3093+SEARCH_INCLUDES        = YES 
     3094+ 
     3095+# The INCLUDE_PATH tag can be used to specify one or more directories that 
     3096+# contain include files that are not input files but should be processed by 
     3097+# the preprocessor. 
     3098+ 
     3099+INCLUDE_PATH           = 
     3100+ 
     3101+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
     3102+# patterns (like *.h and *.hpp) to filter out the header-files in the 
     3103+# directories. If left blank, the patterns specified with FILE_PATTERNS will 
     3104+# be used. 
     3105+ 
     3106+INCLUDE_FILE_PATTERNS  = 
     3107+ 
     3108+# The PREDEFINED tag can be used to specify one or more macro names that 
     3109+# are defined before the preprocessor is started (similar to the -D option of 
     3110+# gcc). The argument of the tag is a list of macros of the form: name 
     3111+# or name=definition (no spaces). If the definition and the = are 
     3112+# omitted =1 is assumed. To prevent a macro definition from being 
     3113+# undefined via #undef or recursively expanded use the := operator 
     3114+# instead of the = operator. 
     3115+ 
     3116+PREDEFINED             = "DBUS_BEGIN_DECLS=" \ 
     3117+                         "DBUS_END_DECLS=" \ 
     3118+                         "DOXYGEN_SHOULD_SKIP_THIS" \ 
     3119+                         "DBUS_GNUC_DEPRECATED=" \ 
     3120+                         "_DBUS_DEFINE_GLOBAL_LOCK(name)=" \ 
     3121+                         "_DBUS_GNUC_PRINTF(from,to)=" 
     3122+ 
     3123+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
     3124+# this tag can be used to specify a list of macro names that should be expanded. 
     3125+# The macro definition that is found in the sources will be used. 
     3126+# Use the PREDEFINED tag if you want to use a different macro definition. 
     3127+ 
     3128+EXPAND_AS_DEFINED      = 
     3129+ 
     3130+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
     3131+# doxygen's preprocessor will remove all function-like macros that are alone 
     3132+# on a line, have an all uppercase name, and do not end with a semicolon. Such 
     3133+# function macros are typically used for boiler-plate code, and will confuse 
     3134+# the parser if not removed. 
     3135+ 
     3136+SKIP_FUNCTION_MACROS   = YES 
     3137+ 
     3138+#--------------------------------------------------------------------------- 
     3139+# Configuration::additions related to external references 
     3140+#--------------------------------------------------------------------------- 
     3141+ 
     3142+# The TAGFILES option can be used to specify one or more tagfiles. 
     3143+# Optionally an initial location of the external documentation 
     3144+# can be added for each tagfile. The format of a tag file without 
     3145+# this location is as follows: 
     3146+# 
     3147+# TAGFILES = file1 file2 ... 
     3148+# Adding location for the tag files is done as follows: 
     3149+# 
     3150+# TAGFILES = file1=loc1 "file2 = loc2" ... 
     3151+# where "loc1" and "loc2" can be relative or absolute paths or 
     3152+# URLs. If a location is present for each tag, the installdox tool 
     3153+# does not have to be run to correct the links. 
     3154+# Note that each tag file must have a unique name 
     3155+# (where the name does NOT include the path) 
     3156+# If a tag file is not located in the directory in which doxygen 
     3157+# is run, you must also specify the path to the tagfile here. 
     3158+ 
     3159+TAGFILES               = 
     3160+ 
     3161+# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
     3162+# a tag file that is based on the input files it reads. 
     3163+ 
     3164+GENERATE_TAGFILE       = 
     3165+ 
     3166+# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
     3167+# in the class index. If set to NO only the inherited external classes 
     3168+# will be listed. 
     3169+ 
     3170+ALLEXTERNALS           = NO 
     3171+ 
     3172+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
     3173+# in the modules index. If set to NO, only the current project's groups will 
     3174+# be listed. 
     3175+ 
     3176+EXTERNAL_GROUPS        = YES 
     3177+ 
     3178+# The PERL_PATH should be the absolute path and name of the perl script 
     3179+# interpreter (i.e. the result of `which perl'). 
     3180+ 
     3181+PERL_PATH              = 
     3182+ 
     3183+#--------------------------------------------------------------------------- 
     3184+# Configuration options related to the dot tool 
     3185+#--------------------------------------------------------------------------- 
     3186+ 
     3187+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
     3188+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
     3189+# or super classes. Setting the tag to NO turns the diagrams off. Note that 
     3190+# this option is superseded by the HAVE_DOT option below. This is only a 
     3191+# fallback. It is recommended to install and use dot, since it yields more 
     3192+# powerful graphs. 
     3193+ 
     3194+CLASS_DIAGRAMS         = YES 
     3195+ 
     3196+# You can define message sequence charts within doxygen comments using the \msc 
     3197+# command. Doxygen will then run the mscgen tool (see 
     3198+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 
     3199+# documentation. The MSCGEN_PATH tag allows you to specify the directory where 
     3200+# the mscgen tool resides. If left empty the tool is assumed to be found in the 
     3201+# default search path. 
     3202+ 
     3203+MSCGEN_PATH            = 
     3204+ 
     3205+# If set to YES, the inheritance and collaboration graphs will hide 
     3206+# inheritance and usage relations if the target is undocumented 
     3207+# or is not a class. 
     3208+ 
     3209+HIDE_UNDOC_RELATIONS   = YES 
     3210+ 
     3211+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
     3212+# available from the path. This tool is part of Graphviz, a graph visualization 
     3213+# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
     3214+# have no effect if this option is set to NO (the default) 
     3215+ 
     3216+HAVE_DOT               = NO 
     3217+ 
     3218+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 
     3219+# allowed to run in parallel. When set to 0 (the default) doxygen will 
     3220+# base this on the number of processors available in the system. You can set it 
     3221+# explicitly to a value larger than 0 to get control over the balance 
     3222+# between CPU load and processing speed. 
     3223+ 
     3224+DOT_NUM_THREADS        = 0 
     3225+ 
     3226+# By default doxygen will write a font called FreeSans.ttf to the output 
     3227+# directory and reference it in all dot files that doxygen generates. This 
     3228+# font does not include all possible unicode characters however, so when you need 
     3229+# these (or just want a differently looking font) you can specify the font name 
     3230+# using DOT_FONTNAME. You need need to make sure dot is able to find the font, 
     3231+# which can be done by putting it in a standard location or by setting the 
     3232+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory 
     3233+# containing the font. 
     3234+ 
     3235+DOT_FONTNAME           = FreeSans.ttf 
     3236+ 
     3237+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 
     3238+# The default size is 10pt. 
     3239+ 
     3240+DOT_FONTSIZE           = 10 
     3241+ 
     3242+# By default doxygen will tell dot to use the output directory to look for the 
     3243+# FreeSans.ttf font (which doxygen will put there itself). If you specify a 
     3244+# different font using DOT_FONTNAME you can set the path where dot 
     3245+# can find it using this tag. 
     3246+ 
     3247+DOT_FONTPATH           = 
     3248+ 
     3249+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
     3250+# will generate a graph for each documented class showing the direct and 
     3251+# indirect inheritance relations. Setting this tag to YES will force the 
     3252+# the CLASS_DIAGRAMS tag to NO. 
     3253+ 
     3254+CLASS_GRAPH            = YES 
     3255+ 
     3256+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
     3257+# will generate a graph for each documented class showing the direct and 
     3258+# indirect implementation dependencies (inheritance, containment, and 
     3259+# class references variables) of the class with other documented classes. 
     3260+ 
     3261+COLLABORATION_GRAPH    = YES 
     3262+ 
     3263+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
     3264+# will generate a graph for groups, showing the direct groups dependencies 
     3265+ 
     3266+GROUP_GRAPHS           = YES 
     3267+ 
     3268+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
     3269+# collaboration diagrams in a style similar to the OMG's Unified Modeling 
     3270+# Language. 
     3271+ 
     3272+UML_LOOK               = NO 
     3273+ 
     3274+# If set to YES, the inheritance and collaboration graphs will show the 
     3275+# relations between templates and their instances. 
     3276+ 
     3277+TEMPLATE_RELATIONS     = YES 
     3278+ 
     3279+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
     3280+# tags are set to YES then doxygen will generate a graph for each documented 
     3281+# file showing the direct and indirect include dependencies of the file with 
     3282+# other documented files. 
     3283+ 
     3284+INCLUDE_GRAPH          = YES 
     3285+ 
     3286+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
     3287+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
     3288+# documented header file showing the documented files that directly or 
     3289+# indirectly include this file. 
     3290+ 
     3291+INCLUDED_BY_GRAPH      = YES 
     3292+ 
     3293+# If the CALL_GRAPH and HAVE_DOT options are set to YES then 
     3294+# doxygen will generate a call dependency graph for every global function 
     3295+# or class method. Note that enabling this option will significantly increase 
     3296+# the time of a run. So in most cases it will be better to enable call graphs 
     3297+# for selected functions only using the \callgraph command. 
     3298+ 
     3299+CALL_GRAPH             = NO 
     3300+ 
     3301+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 
     3302+# doxygen will generate a caller dependency graph for every global function 
     3303+# or class method. Note that enabling this option will significantly increase 
     3304+# the time of a run. So in most cases it will be better to enable caller 
     3305+# graphs for selected functions only using the \callergraph command. 
     3306+ 
     3307+CALLER_GRAPH           = NO 
     3308+ 
     3309+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
     3310+# will graphical hierarchy of all classes instead of a textual one. 
     3311+ 
     3312+GRAPHICAL_HIERARCHY    = YES 
     3313+ 
     3314+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
     3315+# then doxygen will show the dependencies a directory has on other directories 
     3316+# in a graphical way. The dependency relations are determined by the #include 
     3317+# relations between the files in the directories. 
     3318+ 
     3319+DIRECTORY_GRAPH        = YES 
     3320+ 
     3321+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
     3322+# generated by dot. Possible values are png, jpg, or gif 
     3323+# If left blank png will be used. 
     3324+ 
     3325+DOT_IMAGE_FORMAT       = png 
     3326+ 
     3327+# The tag DOT_PATH can be used to specify the path where the dot tool can be 
     3328+# found. If left blank, it is assumed the dot tool can be found in the path. 
     3329+ 
     3330+DOT_PATH               = 
     3331+ 
     3332+# The DOTFILE_DIRS tag can be used to specify one or more directories that 
     3333+# contain dot files that are included in the documentation (see the 
     3334+# \dotfile command). 
     3335+ 
     3336+DOTFILE_DIRS           = 
     3337+ 
     3338+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 
     3339+# nodes that will be shown in the graph. If the number of nodes in a graph 
     3340+# becomes larger than this value, doxygen will truncate the graph, which is 
     3341+# visualized by representing a node as a red box. Note that doxygen if the 
     3342+# number of direct children of the root node in a graph is already larger than 
     3343+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 
     3344+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 
     3345+ 
     3346+DOT_GRAPH_MAX_NODES    = 50 
     3347+ 
     3348+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
     3349+# graphs generated by dot. A depth value of 3 means that only nodes reachable 
     3350+# from the root by following a path via at most 3 edges will be shown. Nodes 
     3351+# that lay further from the root node will be omitted. Note that setting this 
     3352+# option to 1 or 2 may greatly reduce the computation time needed for large 
     3353+# code bases. Also note that the size of a graph can be further restricted by 
     3354+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 
     3355+ 
     3356+MAX_DOT_GRAPH_DEPTH    = 0 
     3357+ 
     3358+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
     3359+# background. This is disabled by default, because dot on Windows does not 
     3360+# seem to support this out of the box. Warning: Depending on the platform used, 
     3361+# enabling this option may lead to badly anti-aliased labels on the edges of 
     3362+# a graph (i.e. they become hard to read). 
     3363+ 
     3364+DOT_TRANSPARENT        = NO 
     3365+ 
     3366+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
     3367+# files in one run (i.e. multiple -o and -T options on the command line). This 
     3368+# makes dot run faster, but since only newer versions of dot (>1.8.10) 
     3369+# support this, this feature is disabled by default. 
     3370+ 
     3371+DOT_MULTI_TARGETS      = YES 
     3372+ 
     3373+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
     3374+# generate a legend page explaining the meaning of the various boxes and 
     3375+# arrows in the dot generated graphs. 
     3376+ 
     3377+GENERATE_LEGEND        = YES 
     3378+ 
     3379+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
     3380+# remove the intermediate dot files that are used to generate 
     3381+# the various graphs. 
     3382+ 
     3383+DOT_CLEANUP            = YES 
Note: See TracChangeset for help on using the changeset viewer.