1 # Doxyfile 1.5.2

     2 

     3 # This file describes the settings to be used by the documentation system

     4 # doxygen (www.doxygen.org) for a project

     5 #

     6 # All text after a hash (#) is considered a comment and will be ignored

     7 # The format is:

     8 #       TAG = value [value, ...]

     9 # For lists items can also be appended using:

    10 #       TAG += value [value, ...]

    11 # Values that contain spaces should be placed between quotes (" ")

    12 

    13 #---------------------------------------------------------------------------

    14 # Project related configuration options

    15 #---------------------------------------------------------------------------

    16 

    17 # This tag specifies the encoding used for all characters in the config file that 

    18 # follow. The default is UTF-8 which is also the encoding used for all text before 

    19 # the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into 

    20 # libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of 

    21 # possible encodings.

    22 

    23 DOXYFILE_ENCODING      = UTF-8

    24 

    25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 

    26 # by quotes) that should identify the project.

    27 

    28 PROJECT_NAME           = "UI Accelerator Toolkit Operating System Neutrality Layer"

    29 

    30 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 

    31 # This could be handy for archiving the generated documentation or 

    32 # if some version control system is used.

    33 

    34 PROJECT_NUMBER         = 

    35 

    36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 

    37 # base path where the generated documentation will be put. 

    38 # If a relative path is entered, it will be relative to the location 

    39 # where doxygen was started. If left blank the current directory will be used.

    40 

    41 OUTPUT_DIRECTORY       = ../osn_apidoc

    42 

    43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 

    44 # 4096 sub-directories (in 2 levels) under the output directory of each output 

    45 # format and will distribute the generated files over these directories. 

    46 # Enabling this option can be useful when feeding doxygen a huge amount of 

    47 # source files, where putting all generated files in the same directory would 

    48 # otherwise cause performance problems for the file system.

    49 

    50 CREATE_SUBDIRS         = NO

    51 

    52 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 

    53 # documentation generated by doxygen is written. Doxygen will use this 

    54 # information to generate all constant output in the proper language. 

    55 # The default language is English, other supported languages are: 

    56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 

    57 # Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, 

    58 # Italian, Japanese, Japanese-en (Japanese with English messages), Korean, 

    59 # Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, 

    60 # Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.

    61 

    62 OUTPUT_LANGUAGE        = English

    63 

    64 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 

    65 # include brief member descriptions after the members that are listed in 

    66 # the file and class documentation (similar to JavaDoc). 

    67 # Set to NO to disable this.

    68 

    69 BRIEF_MEMBER_DESC      = YES

    70 

    71 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 

    72 # the brief description of a member or function before the detailed description. 

    73 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 

    74 # brief descriptions will be completely suppressed.

    75 

    76 REPEAT_BRIEF           = YES

    77 

    78 # This tag implements a quasi-intelligent brief description abbreviator 

    79 # that is used to form the text in various listings. Each string 

    80 # in this list, if found as the leading text of the brief description, will be 

    81 # stripped from the text and the result after processing the whole list, is 

    82 # used as the annotated text. Otherwise, the brief description is used as-is. 

    83 # If left blank, the following values are used ("$name" is automatically 

    84 # replaced with the name of the entity): "The $name class" "The $name widget" 

    85 # "The $name file" "is" "provides" "specifies" "contains" 

    86 # "represents" "a" "an" "the"

    87 

    88 ABBREVIATE_BRIEF       = "The $name class" \

    89                          "The $name widget" \

    90                          "The $name file" \

    91                          is \

    92                          provides \

    93                          specifies \

    94                          contains \

    95                          represents \

    96                          a \

    97                          an \

    98                          the

    99 

   100 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 

   101 # Doxygen will generate a detailed section even if there is only a brief 

   102 # description.

   103 

   104 ALWAYS_DETAILED_SEC    = NO

   105 

   106 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 

   107 # inherited members of a class in the documentation of that class as if those 

   108 # members were ordinary class members. Constructors, destructors and assignment 

   109 # operators of the base classes will not be shown.

   110 

   111 INLINE_INHERITED_MEMB  = NO

   112 

   113 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 

   114 # path before files name in the file list and in the header files. If set 

   115 # to NO the shortest path that makes the file name unique will be used.

   116 

   117 FULL_PATH_NAMES        = NO

   118 

   119 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 

   120 # can be used to strip a user-defined part of the path. Stripping is 

   121 # only done if one of the specified strings matches the left-hand part of 

   122 # the path. The tag can be used to show relative paths in the file list. 

   123 # If left blank the directory from which doxygen is run is used as the 

   124 # path to strip.

   125 

   126 STRIP_FROM_PATH        = 

   127 

   128 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 

   129 # the path mentioned in the documentation of a class, which tells 

   130 # the reader which header file to include in order to use a class. 

   131 # If left blank only the name of the header file containing the class 

   132 # definition is used. Otherwise one should specify the include paths that 

   133 # are normally passed to the compiler using the -I flag.

   134 

   135 STRIP_FROM_INC_PATH    = 

   136 

   137 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 

   138 # (but less readable) file names. This can be useful is your file systems 

   139 # doesn't support long names like on DOS, Mac, or CD-ROM.

   140 

   141 SHORT_NAMES            = NO

   142 

   143 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 

   144 # will interpret the first line (until the first dot) of a JavaDoc-style 

   145 # comment as the brief description. If set to NO, the JavaDoc 

   146 # comments will behave just like the Qt-style comments (thus requiring an 

   147 # explicit @brief command for a brief description.

   148 

   149 JAVADOC_AUTOBRIEF      = YES

   150 

   151 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 

   152 # treat a multi-line C++ special comment block (i.e. a block of //! or /// 

   153 # comments) as a brief description. This used to be the default behaviour. 

   154 # The new default is to treat a multi-line C++ comment block as a detailed 

   155 # description. Set this tag to YES if you prefer the old behaviour instead.

   156 

   157 MULTILINE_CPP_IS_BRIEF = NO

   158 

   159 # If the DETAILS_AT_TOP tag is set to YES then Doxygen 

   160 # will output the detailed description near the top, like JavaDoc.

   161 # If set to NO, the detailed description appears after the member 

   162 # documentation.

   163 

   164 DETAILS_AT_TOP         = YES

   165 

   166 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 

   167 # member inherits the documentation from any documented member that it 

   168 # re-implements.

   169 

   170 INHERIT_DOCS           = YES

   171 

   172 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 

   173 # a new page for each member. If set to NO, the documentation of a member will 

   174 # be part of the file/class/namespace that contains it.

   175 

   176 SEPARATE_MEMBER_PAGES  = NO

   177 

   178 # The TAB_SIZE tag can be used to set the number of spaces in a tab. 

   179 # Doxygen uses this value to replace tabs by spaces in code fragments.

   180 

   181 TAB_SIZE               = 4

   182 

   183 # This tag can be used to specify a number of aliases that acts 

   184 # as commands in the documentation. An alias has the form "name=value". 

   185 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 

   186 # put the command \sideeffect (or @sideeffect) in the documentation, which 

   187 # will result in a user-defined paragraph with heading "Side Effects:". 

   188 # You can put \n's in the value part of an alias to insert newlines.

   189 

   190 ALIASES                = panic=@exception \

   191                          leave=@exception \

   192                          "internalTechnology=@par Internal technology" \

   193                          "internalComponent=@par Internal component" \

   194                          "internalAll=@par Internal all" \

   195                          "publishedPartner=@par Published-partner" \

   196                          "publishedAll=@par Published-all" \

   197                          "prototype=@par Prototype" \

   198                          "interim=@par Interim" \

   199                          "released=@par Released" \

   200                          "removed=@par Removed" \

   201                          "test=@par Test" \

   202                          "realtime=@par Realtime" \

   203                          "beginAPI=@name Exported API\n @{" \

   204                          endAPI=@}

   205 

   206 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 

   207 # sources only. Doxygen will then generate output that is more tailored for C. 

   208 # For instance, some of the names that are used will be different. The list 

   209 # of all members will be omitted, etc.

   210 

   211 OPTIMIZE_OUTPUT_FOR_C  = NO

   212 

   213 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 

   214 # sources only. Doxygen will then generate output that is more tailored for Java. 

   215 # For instance, namespaces will be presented as packages, qualified scopes 

   216 # will look different, etc.

   217 

   218 OPTIMIZE_OUTPUT_JAVA   = NO

   219 

   220 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to 

   221 # include (a tag file for) the STL sources as input, then you should 

   222 # set this tag to YES in order to let doxygen match functions declarations and 

   223 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 

   224 # func(std::string) {}). This also make the inheritance and collaboration 

   225 # diagrams that involve STL classes more complete and accurate.

   226 

   227 BUILTIN_STL_SUPPORT    = NO

   228 

   229 # If you use Microsoft's C++/CLI language, you should set this option to YES to

   230 # enable parsing support.

   231 

   232 CPP_CLI_SUPPORT        = NO

   233 

   234 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 

   235 # tag is set to YES, then doxygen will reuse the documentation of the first 

   236 # member in the group (if any) for the other members of the group. By default 

   237 # all members of a group must be documented explicitly.

   238 

   239 DISTRIBUTE_GROUP_DOC   = NO

   240 

   241 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of 

   242 # the same type (for instance a group of public functions) to be put as a 

   243 # subgroup of that type (e.g. under the Public Functions section). Set it to 

   244 # NO to prevent subgrouping. Alternatively, this can be done per class using 

   245 # the \nosubgrouping command.

   246 

   247 SUBGROUPING            = YES

   248 

   249 #---------------------------------------------------------------------------

   250 # Build related configuration options

   251 #---------------------------------------------------------------------------

   252 

   253 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 

   254 # documentation are documented, even if no documentation was available. 

   255 # Private class members and static file members will be hidden unless 

   256 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES

   257 

   258 EXTRACT_ALL            = YES

   259 

   260 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 

   261 # will be included in the documentation.

   262 

   263 EXTRACT_PRIVATE        = YES

   264 

   265 # If the EXTRACT_STATIC tag is set to YES all static members of a file 

   266 # will be included in the documentation.

   267 

   268 EXTRACT_STATIC         = YES

   269 

   270 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 

   271 # defined locally in source files will be included in the documentation. 

   272 # If set to NO only classes defined in header files are included.

   273 

   274 EXTRACT_LOCAL_CLASSES  = YES

   275 

   276 # This flag is only useful for Objective-C code. When set to YES local 

   277 # methods, which are defined in the implementation section but not in 

   278 # the interface are included in the documentation. 

   279 # If set to NO (the default) only methods in the interface are included.

   280 

   281 EXTRACT_LOCAL_METHODS  = YES

   282 

   283 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 

   284 # undocumented members of documented classes, files or namespaces. 

   285 # If set to NO (the default) these members will be included in the 

   286 # various overviews, but no documentation section is generated. 

   287 # This option has no effect if EXTRACT_ALL is enabled.

   288 

   289 HIDE_UNDOC_MEMBERS     = NO

   290 

   291 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 

   292 # undocumented classes that are normally visible in the class hierarchy. 

   293 # If set to NO (the default) these classes will be included in the various 

   294 # overviews. This option has no effect if EXTRACT_ALL is enabled.

   295 

   296 HIDE_UNDOC_CLASSES     = NO

   297 

   298 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 

   299 # friend (class|struct|union) declarations. 

   300 # If set to NO (the default) these declarations will be included in the 

   301 # documentation.

   302 

   303 HIDE_FRIEND_COMPOUNDS  = NO

   304 

   305 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 

   306 # documentation blocks found inside the body of a function. 

   307 # If set to NO (the default) these blocks will be appended to the 

   308 # function's detailed documentation block.

   309 

   310 HIDE_IN_BODY_DOCS      = NO

   311 

   312 # The INTERNAL_DOCS tag determines if documentation 

   313 # that is typed after a \internal command is included. If the tag is set 

   314 # to NO (the default) then the documentation will be excluded. 

   315 # Set it to YES to include the internal documentation.

   316 

   317 INTERNAL_DOCS          = NO

   318 

   319 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 

   320 # file names in lower-case letters. If set to YES upper-case letters are also 

   321 # allowed. This is useful if you have classes or files whose names only differ 

   322 # in case and if your file system supports case sensitive file names. Windows 

   323 # and Mac users are advised to set this option to NO.

   324 

   325 CASE_SENSE_NAMES       = NO

   326 

   327 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 

   328 # will show members with their full class and namespace scopes in the 

   329 # documentation. If set to YES the scope will be hidden.

   330 

   331 HIDE_SCOPE_NAMES       = NO

   332 

   333 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 

   334 # will put a list of the files that are included by a file in the documentation 

   335 # of that file.

   336 

   337 SHOW_INCLUDE_FILES     = YES

   338 

   339 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 

   340 # is inserted in the documentation for inline members.

   341 

   342 INLINE_INFO            = YES

   343 

   344 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 

   345 # will sort the (detailed) documentation of file and class members 

   346 # alphabetically by member name. If set to NO the members will appear in 

   347 # declaration order.

   348 

   349 SORT_MEMBER_DOCS       = YES

   350 

   351 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 

   352 # brief documentation of file, namespace and class members alphabetically 

   353 # by member name. If set to NO (the default) the members will appear in 

   354 # declaration order.

   355 

   356 SORT_BRIEF_DOCS        = YES

   357 

   358 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 

   359 # sorted by fully-qualified names, including namespaces. If set to 

   360 # NO (the default), the class list will be sorted only by class name, 

   361 # not including the namespace part. 

   362 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.

   363 # Note: This option applies only to the class list, not to the 

   364 # alphabetical list.

   365 

   366 SORT_BY_SCOPE_NAME     = NO

   367 

   368 # The GENERATE_TODOLIST tag can be used to enable (YES) or 

   369 # disable (NO) the todo list. This list is created by putting \todo 

   370 # commands in the documentation.

   371 

   372 GENERATE_TODOLIST      = YES

   373 

   374 # The GENERATE_TESTLIST tag can be used to enable (YES) or 

   375 # disable (NO) the test list. This list is created by putting \test 

   376 # commands in the documentation.

   377 

   378 GENERATE_TESTLIST      = YES

   379 

   380 # The GENERATE_BUGLIST tag can be used to enable (YES) or 

   381 # disable (NO) the bug list. This list is created by putting \bug 

   382 # commands in the documentation.

   383 

   384 GENERATE_BUGLIST       = YES

   385 

   386 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 

   387 # disable (NO) the deprecated list. This list is created by putting 

   388 # \deprecated commands in the documentation.

   389 

   390 GENERATE_DEPRECATEDLIST= YES

   391 

   392 # The ENABLED_SECTIONS tag can be used to enable conditional 

   393 # documentation sections, marked by \if sectionname ... \endif.

   394 

   395 ENABLED_SECTIONS       = 

   396 

   397 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 

   398 # the initial value of a variable or define consists of for it to appear in 

   399 # the documentation. If the initializer consists of more lines than specified 

   400 # here it will be hidden. Use a value of 0 to hide initializers completely. 

   401 # The appearance of the initializer of individual variables and defines in the 

   402 # documentation can be controlled using \showinitializer or \hideinitializer 

   403 # command in the documentation regardless of this setting.

   404 

   405 MAX_INITIALIZER_LINES  = 30

   406 

   407 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 

   408 # at the bottom of the documentation of classes and structs. If set to YES the 

   409 # list will mention the files that were used to generate the documentation.

   410 

   411 SHOW_USED_FILES        = YES

   412 

   413 # If the sources in your project are distributed over multiple directories 

   414 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 

   415 # in the documentation. The default is NO.

   416 

   417 SHOW_DIRECTORIES       = YES

   418 

   419 # The FILE_VERSION_FILTER tag can be used to specify a program or script that 

   420 # doxygen should invoke to get the current version for each file (typically from the 

   421 # version control system). Doxygen will invoke the program by executing (via 

   422 # popen()) the command <command> <input-file>, where <command> is the value of 

   423 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 

   424 # provided by doxygen. Whatever the program writes to standard output 

   425 # is used as the file version. See the manual for examples.

   426 

   427 FILE_VERSION_FILTER    = 

   428 

   429 #---------------------------------------------------------------------------

   430 # configuration options related to warning and progress messages

   431 #---------------------------------------------------------------------------

   432 

   433 # The QUIET tag can be used to turn on/off the messages that are generated 

   434 # by doxygen. Possible values are YES and NO. If left blank NO is used.

   435 

   436 QUIET                  = NO

   437 

   438 # The WARNINGS tag can be used to turn on/off the warning messages that are 

   439 # generated by doxygen. Possible values are YES and NO. If left blank 

   440 # NO is used.

   441 

   442 WARNINGS               = YES

   443 

   444 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 

   445 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 

   446 # automatically be disabled.

   447 

   448 WARN_IF_UNDOCUMENTED   = YES

   449 

   450 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 

   451 # potential errors in the documentation, such as not documenting some 

   452 # parameters in a documented function, or documenting parameters that 

   453 # don't exist or using markup commands wrongly.

   454 

   455 WARN_IF_DOC_ERROR      = YES

   456 

   457 # This WARN_NO_PARAMDOC option can be abled to get warnings for 

   458 # functions that are documented, but have no documentation for their parameters 

   459 # or return value. If set to NO (the default) doxygen will only warn about 

   460 # wrong or incomplete parameter documentation, but not about the absence of 

   461 # documentation.

   462 

   463 WARN_NO_PARAMDOC       = NO

   464 

   465 # The WARN_FORMAT tag determines the format of the warning messages that 

   466 # doxygen can produce. The string should contain the $file, $line, and $text 

   467 # tags, which will be replaced by the file and line number from which the 

   468 # warning originated and the warning text. Optionally the format may contain 

   469 # $version, which will be replaced by the version of the file (if it could 

   470 # be obtained via FILE_VERSION_FILTER)

   471 

   472 WARN_FORMAT            = "$file:$line: $text"

   473 

   474 # The WARN_LOGFILE tag can be used to specify a file to which warning 

   475 # and error messages should be written. If left blank the output is written 

   476 # to stderr.

   477 

   478 WARN_LOGFILE           = 

   479 

   480 #---------------------------------------------------------------------------

   481 # configuration options related to the input files

   482 #---------------------------------------------------------------------------

   483 

   484 # The INPUT tag can be used to specify the files and/or directories that contain 

   485 # documented source files. You may enter file names like "myfile.cpp" or 

   486 # directories like "/usr/src/myproject". Separate the files or directories 

   487 # with spaces.

   488 

   489 INPUT                  = ../osn_container_api/inc/osn \

   490                          ../osn_exception_api/inc/osn \

   491                          ../osn_global_api/inc/osn \

   492                          ../osn_smartpointer_api/inc/osn \

   493                          ../osn_string_api/inc/osn

   494 

   495 # This tag can be used to specify the character encoding of the source files that 

   496 # doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default 

   497 # input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. 

   498 # See http://www.gnu.org/software/libiconv for the list of possible encodings.

   499 

   500 INPUT_ENCODING         = UTF-8

   501 

   502 # If the value of the INPUT tag contains directories, you can use the 

   503 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 

   504 # and *.h) to filter out the source-files in the directories. If left 

   505 # blank the following patterns are tested: 

   506 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 

   507 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py

   508 

   509 FILE_PATTERNS          = *.c \

   510                          *.cc \

   511                          *.cpp \

   512                          *.h \

   513                          *.inl \

   514                          *.hh \

   515                          *.hrh \

   516                          *.dox

   517 

   518 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 

   519 # should be searched for input files as well. Possible values are YES and NO. 

   520 # If left blank NO is used.

   521 

   522 RECURSIVE              = YES

   523 

   524 # The EXCLUDE tag can be used to specify files and/or directories that should 

   525 # excluded from the INPUT source files. This way you can easily exclude a 

   526 # subdirectory from a directory tree whose root is specified with the INPUT tag.

   527 

   528 EXCLUDE                = 

   529 

   530 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or 

   531 # directories that are symbolic links (a Unix filesystem feature) are excluded 

   532 # from the input.

   533 

   534 EXCLUDE_SYMLINKS       = NO

   535 

   536 # If the value of the INPUT tag contains directories, you can use the 

   537 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 

   538 # certain files from those directories. Note that the wildcards are matched 

   539 # against the file with absolute path, so to exclude all test directories 

   540 # for example use the pattern */test/*

   541 

   542 EXCLUDE_PATTERNS       = 

   543 

   544 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 

   545 # (namespaces, classes, functions, etc.) that should be excluded from the output. 

   546 # The symbol name can be a fully qualified name, a word, or if the wildcard * is used, 

   547 # a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test

   548 

   549 EXCLUDE_SYMBOLS        = 

   550 

   551 # The EXAMPLE_PATH tag can be used to specify one or more files or 

   552 # directories that contain example code fragments that are included (see 

   553 # the \include command).

   554 

   555 EXAMPLE_PATH           = 

   556 

   557 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 

   558 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 

   559 # and *.h) to filter out the source-files in the directories. If left 

   560 # blank all files are included.

   561 

   562 EXAMPLE_PATTERNS       = 

   563 

   564 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 

   565 # searched for input files to be used with the \include or \dontinclude 

   566 # commands irrespective of the value of the RECURSIVE tag. 

   567 # Possible values are YES and NO. If left blank NO is used.

   568 

   569 EXAMPLE_RECURSIVE      = NO

   570 

   571 # The IMAGE_PATH tag can be used to specify one or more files or 

   572 # directories that contain image that are included in the documentation (see 

   573 # the \image command).

   574 

   575 IMAGE_PATH             = 

   576 

   577 # The INPUT_FILTER tag can be used to specify a program that doxygen should 

   578 # invoke to filter for each input file. Doxygen will invoke the filter program 

   579 # by executing (via popen()) the command <filter> <input-file>, where <filter> 

   580 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an 

   581 # input file. Doxygen will then use the output that the filter program writes 

   582 # to standard output.  If FILTER_PATTERNS is specified, this tag will be 

   583 # ignored.

   584 

   585 INPUT_FILTER           = 

   586 

   587 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 

   588 # basis.  Doxygen will compare the file name with each pattern and apply the 

   589 # filter if there is a match.  The filters are a list of the form: 

   590 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 

   591 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 

   592 # is applied to all files.

   593 

   594 FILTER_PATTERNS        = 

   595 

   596 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 

   597 # INPUT_FILTER) will be used to filter the input files when producing source 

   598 # files to browse (i.e. when SOURCE_BROWSER is set to YES).

   599 

   600 FILTER_SOURCE_FILES    = NO

   601 

   602 #---------------------------------------------------------------------------

   603 # configuration options related to source browsing

   604 #---------------------------------------------------------------------------

   605 

   606 # If the SOURCE_BROWSER tag is set to YES then a list of source files will 

   607 # be generated. Documented entities will be cross-referenced with these sources. 

   608 # Note: To get rid of all source code in the generated output, make sure also 

   609 # VERBATIM_HEADERS is set to NO.

   610 

   611 SOURCE_BROWSER         = YES

   612 

   613 # Setting the INLINE_SOURCES tag to YES will include the body 

   614 # of functions and classes directly in the documentation.

   615 

   616 INLINE_SOURCES         = NO

   617 

   618 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 

   619 # doxygen to hide any special comment blocks from generated source code 

   620 # fragments. Normal C and C++ comments will always remain visible.

   621 

   622 STRIP_CODE_COMMENTS    = YES

   623 

   624 # If the REFERENCED_BY_RELATION tag is set to YES (the default) 

   625 # then for each documented function all documented 

   626 # functions referencing it will be listed.

   627 

   628 REFERENCED_BY_RELATION = YES

   629 

   630 # If the REFERENCES_RELATION tag is set to YES (the default) 

   631 # then for each documented function all documented entities 

   632 # called/used by that function will be listed.

   633 

   634 REFERENCES_RELATION    = YES

   635 

   636 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)

   637 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from

   638 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will

   639 # link to the source code.  Otherwise they will link to the documentstion.

   640 

   641 REFERENCES_LINK_SOURCE = YES

   642 

   643 # If the USE_HTAGS tag is set to YES then the references to source code 

   644 # will point to the HTML generated by the htags(1) tool instead of doxygen 

   645 # built-in source browser. The htags tool is part of GNU's global source 

   646 # tagging system (see http://www.gnu.org/software/global/global.html). You 

   647 # will need version 4.8.6 or higher.

   648 

   649 USE_HTAGS              = NO

   650 

   651 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 

   652 # will generate a verbatim copy of the header file for each class for 

   653 # which an include is specified. Set to NO to disable this.

   654 

   655 VERBATIM_HEADERS       = YES

   656 

   657 #---------------------------------------------------------------------------

   658 # configuration options related to the alphabetical class index

   659 #---------------------------------------------------------------------------

   660 

   661 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 

   662 # of all compounds will be generated. Enable this if the project 

   663 # contains a lot of classes, structs, unions or interfaces.

   664 

   665 ALPHABETICAL_INDEX     = YES

   666 

   667 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 

   668 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 

   669 # in which this list will be split (can be a number in the range [1..20])

   670 

   671 COLS_IN_ALPHA_INDEX    = 3

   672 

   673 # In case all classes in a project start with a common prefix, all 

   674 # classes will be put under the same header in the alphabetical index. 

   675 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 

   676 # should be ignored while generating the index headers.

   677 

   678 IGNORE_PREFIX          = TAlf \

   679                          SAlf \

   680                          CAlf \

   681                          RAlf \

   682                          MAlf \

   683                          Alf

   684 

   685 #---------------------------------------------------------------------------

   686 # configuration options related to the HTML output

   687 #---------------------------------------------------------------------------

   688 

   689 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 

   690 # generate HTML output.

   691 

   692 GENERATE_HTML          = YES

   693 

   694 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 

   695 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 

   696 # put in front of it. If left blank `html' will be used as the default path.

   697 

   698 HTML_OUTPUT            = html

   699 

   700 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 

   701 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 

   702 # doxygen will generate files with .html extension.

   703 

   704 HTML_FILE_EXTENSION    = .html

   705 

   706 # The HTML_HEADER tag can be used to specify a personal HTML header for 

   707 # each generated HTML page. If it is left blank doxygen will generate a 

   708 # standard header.

   709 

   710 HTML_HEADER            = 

   711 

   712 # The HTML_FOOTER tag can be used to specify a personal HTML footer for 

   713 # each generated HTML page. If it is left blank doxygen will generate a 

   714 # standard footer.

   715 

   716 HTML_FOOTER            = 

   717 

   718 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 

   719 # style sheet that is used by each HTML page. It can be used to 

   720 # fine-tune the look of the HTML output. If the tag is left blank doxygen 

   721 # will generate a default style sheet. Note that doxygen will try to copy 

   722 # the style sheet file to the HTML output directory, so don't put your own 

   723 # stylesheet in the HTML output directory as well, or it will be erased!

   724 

   725 HTML_STYLESHEET        = 

   726 

   727 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 

   728 # files or namespaces will be aligned in HTML using tables. If set to 

   729 # NO a bullet list will be used.

   730 

   731 HTML_ALIGN_MEMBERS     = YES

   732 

   733 # If the GENERATE_HTMLHELP tag is set to YES, additional index files 

   734 # will be generated that can be used as input for tools like the 

   735 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 

   736 # of the generated HTML documentation.

   737 

   738 GENERATE_HTMLHELP      = YES

   739 

   740 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 

   741 # be used to specify the file name of the resulting .chm file. You 

   742 # can add a path in front of the file if the result should not be 

   743 # written to the html output directory.

   744 

   745 CHM_FILE               = 

   746 

   747 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 

   748 # be used to specify the location (absolute path including file name) of 

   749 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 

   750 # the HTML help compiler on the generated index.hhp.

   751 

   752 HHC_LOCATION           = 

   753 

   754 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 

   755 # controls if a separate .chi index file is generated (YES) or that 

   756 # it should be included in the master .chm file (NO).

   757 

   758 GENERATE_CHI           = NO

   759 

   760 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 

   761 # controls whether a binary table of contents is generated (YES) or a 

   762 # normal table of contents (NO) in the .chm file.

   763 

   764 BINARY_TOC             = NO

   765 

   766 # The TOC_EXPAND flag can be set to YES to add extra items for group members 

   767 # to the contents of the HTML help documentation and to the tree view.

   768 

   769 TOC_EXPAND             = NO

   770 

   771 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at 

   772 # top of each HTML page. The value NO (the default) enables the index and 

   773 # the value YES disables it.

   774 

   775 DISABLE_INDEX          = NO

   776 

   777 # This tag can be used to set the number of enum values (range [1..20]) 

   778 # that doxygen will group on one line in the generated HTML documentation.

   779 

   780 ENUM_VALUES_PER_LINE   = 4

   781 

   782 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be

   783 # generated containing a tree-like index structure (just like the one that 

   784 # is generated for HTML Help). For this to work a browser that supports 

   785 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 

   786 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 

   787 # probably better off using the HTML help feature.

   788 

   789 GENERATE_TREEVIEW      = NO

   790 

   791 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 

   792 # used to set the initial width (in pixels) of the frame in which the tree 

   793 # is shown.

   794 

   795 TREEVIEW_WIDTH         = 250

   796 

   797 #---------------------------------------------------------------------------

   798 # configuration options related to the LaTeX output

   799 #---------------------------------------------------------------------------

   800 

   801 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 

   802 # generate Latex output.

   803 

   804 GENERATE_LATEX         = NO

   805 

   806 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 

   807 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 

   808 # put in front of it. If left blank `latex' will be used as the default path.

   809 

   810 LATEX_OUTPUT           = latex

   811 

   812 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 

   813 # invoked. If left blank `latex' will be used as the default command name.

   814 

   815 LATEX_CMD_NAME         = latex

   816 

   817 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 

   818 # generate index for LaTeX. If left blank `makeindex' will be used as the 

   819 # default command name.

   820 

   821 MAKEINDEX_CMD_NAME     = makeindex

   822 

   823 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 

   824 # LaTeX documents. This may be useful for small projects and may help to 

   825 # save some trees in general.

   826 

   827 COMPACT_LATEX          = NO

   828 

   829 # The PAPER_TYPE tag can be used to set the paper type that is used 

   830 # by the printer. Possible values are: a4, a4wide, letter, legal and 

   831 # executive. If left blank a4wide will be used.

   832 

   833 PAPER_TYPE             = a4wide

   834 

   835 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 

   836 # packages that should be included in the LaTeX output.

   837 

   838 EXTRA_PACKAGES         = 

   839 

   840 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 

   841 # the generated latex document. The header should contain everything until 

   842 # the first chapter. If it is left blank doxygen will generate a 

   843 # standard header. Notice: only use this tag if you know what you are doing!

   844 

   845 LATEX_HEADER           = 

   846 

   847 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 

   848 # is prepared for conversion to pdf (using ps2pdf). The pdf file will 

   849 # contain links (just like the HTML output) instead of page references 

   850 # This makes the output suitable for online browsing using a pdf viewer.

   851 

   852 PDF_HYPERLINKS         = NO

   853 

   854 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 

   855 # plain latex in the generated Makefile. Set this option to YES to get a 

   856 # higher quality PDF documentation.

   857 

   858 USE_PDFLATEX           = NO

   859 

   860 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 

   861 # command to the generated LaTeX files. This will instruct LaTeX to keep 

   862 # running if errors occur, instead of asking the user for help. 

   863 # This option is also used when generating formulas in HTML.

   864 

   865 LATEX_BATCHMODE        = NO

   866 

   867 # If LATEX_HIDE_INDICES is set to YES then doxygen will not 

   868 # include the index chapters (such as File Index, Compound Index, etc.) 

   869 # in the output.

   870 

   871 LATEX_HIDE_INDICES     = NO

   872 

   873 #---------------------------------------------------------------------------

   874 # configuration options related to the RTF output

   875 #---------------------------------------------------------------------------

   876 

   877 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 

   878 # The RTF output is optimized for Word 97 and may not look very pretty with 

   879 # other RTF readers or editors.

   880 

   881 GENERATE_RTF           = NO

   882 

   883 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 

   884 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 

   885 # put in front of it. If left blank `rtf' will be used as the default path.

   886 

   887 RTF_OUTPUT             = rtf

   888 

   889 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 

   890 # RTF documents. This may be useful for small projects and may help to 

   891 # save some trees in general.

   892 

   893 COMPACT_RTF            = NO

   894 

   895 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 

   896 # will contain hyperlink fields. The RTF file will 

   897 # contain links (just like the HTML output) instead of page references. 

   898 # This makes the output suitable for online browsing using WORD or other 

   899 # programs which support those fields. 

   900 # Note: wordpad (write) and others do not support links.

   901 

   902 RTF_HYPERLINKS         = NO

   903 

   904 # Load stylesheet definitions from file. Syntax is similar to doxygen's 

   905 # config file, i.e. a series of assignments. You only have to provide 

   906 # replacements, missing definitions are set to their default value.

   907 

   908 RTF_STYLESHEET_FILE    = 

   909 

   910 # Set optional variables used in the generation of an rtf document. 

   911 # Syntax is similar to doxygen's config file.

   912 

   913 RTF_EXTENSIONS_FILE    = 

   914 

   915 #---------------------------------------------------------------------------

   916 # configuration options related to the man page output

   917 #---------------------------------------------------------------------------

   918 

   919 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 

   920 # generate man pages

   921 

   922 GENERATE_MAN           = NO

   923 

   924 # The MAN_OUTPUT tag is used to specify where the man pages will be put. 

   925 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 

   926 # put in front of it. If left blank `man' will be used as the default path.

   927 

   928 MAN_OUTPUT             = man

   929 

   930 # The MAN_EXTENSION tag determines the extension that is added to 

   931 # the generated man pages (default is the subroutine's section .3)

   932 

   933 MAN_EXTENSION          = .3

   934 

   935 # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 

   936 # then it will generate one additional man file for each entity 

   937 # documented in the real man page(s). These additional files 

   938 # only source the real man page, but without them the man command 

   939 # would be unable to find the correct page. The default is NO.

   940 

   941 MAN_LINKS              = NO

   942 

   943 #---------------------------------------------------------------------------

   944 # configuration options related to the XML output

   945 #---------------------------------------------------------------------------

   946 

   947 # If the GENERATE_XML tag is set to YES Doxygen will 

   948 # generate an XML file that captures the structure of 

   949 # the code including all documentation.

   950 

   951 GENERATE_XML           = NO

   952 

   953 # The XML_OUTPUT tag is used to specify where the XML pages will be put. 

   954 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 

   955 # put in front of it. If left blank `xml' will be used as the default path.

   956 

   957 XML_OUTPUT             = xml

   958 

   959 # The XML_SCHEMA tag can be used to specify an XML schema, 

   960 # which can be used by a validating XML parser to check the 

   961 # syntax of the XML files.

   962 

   963 XML_SCHEMA             = 

   964 

   965 # The XML_DTD tag can be used to specify an XML DTD, 

   966 # which can be used by a validating XML parser to check the 

   967 # syntax of the XML files.

   968 

   969 XML_DTD                = 

   970 

   971 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will 

   972 # dump the program listings (including syntax highlighting 

   973 # and cross-referencing information) to the XML output. Note that 

   974 # enabling this will significantly increase the size of the XML output.

   975 

   976 XML_PROGRAMLISTING     = YES

   977 

   978 #---------------------------------------------------------------------------

   979 # configuration options for the AutoGen Definitions output

   980 #---------------------------------------------------------------------------

   981 

   982 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 

   983 # generate an AutoGen Definitions (see autogen.sf.net) file 

   984 # that captures the structure of the code including all 

   985 # documentation. Note that this feature is still experimental 

   986 # and incomplete at the moment.

   987 

   988 GENERATE_AUTOGEN_DEF   = NO

   989 

   990 #---------------------------------------------------------------------------

   991 # configuration options related to the Perl module output

   992 #---------------------------------------------------------------------------

   993 

   994 # If the GENERATE_PERLMOD tag is set to YES Doxygen will 

   995 # generate a Perl module file that captures the structure of 

   996 # the code including all documentation. Note that this 

   997 # feature is still experimental and incomplete at the 

   998 # moment.

   999 

  1000 GENERATE_PERLMOD       = NO

  1001 

  1002 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 

  1003 # the necessary Makefile rules, Perl scripts and LaTeX code to be able 

  1004 # to generate PDF and DVI output from the Perl module output.

  1005 

  1006 PERLMOD_LATEX          = NO

  1007 

  1008 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 

  1009 # nicely formatted so it can be parsed by a human reader.  This is useful 

  1010 # if you want to understand what is going on.  On the other hand, if this 

  1011 # tag is set to NO the size of the Perl module output will be much smaller 

  1012 # and Perl will parse it just the same.

  1013 

  1014 PERLMOD_PRETTY         = YES

  1015 

  1016 # The names of the make variables in the generated doxyrules.make file 

  1017 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 

  1018 # This is useful so different doxyrules.make files included by the same 

  1019 # Makefile don't overwrite each other's variables.

  1020 

  1021 PERLMOD_MAKEVAR_PREFIX = 

  1022 

  1023 #---------------------------------------------------------------------------

  1024 # Configuration options related to the preprocessor   

  1025 #---------------------------------------------------------------------------

  1026 

  1027 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 

  1028 # evaluate all C-preprocessor directives found in the sources and include 

  1029 # files.

  1030 

  1031 ENABLE_PREPROCESSING   = YES

  1032 

  1033 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 

  1034 # names in the source code. If set to NO (the default) only conditional 

  1035 # compilation will be performed. Macro expansion can be done in a controlled 

  1036 # way by setting EXPAND_ONLY_PREDEF to YES.

  1037 

  1038 MACRO_EXPANSION        = YES

  1039 

  1040 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 

  1041 # then the macro expansion is limited to the macros specified with the 

  1042 # PREDEFINED and EXPAND_AS_DEFINED tags.

  1043 

  1044 EXPAND_ONLY_PREDEF     = YES

  1045 

  1046 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 

  1047 # in the INCLUDE_PATH (see below) will be search if a #include is found.

  1048 

  1049 SEARCH_INCLUDES        = YES

  1050 

  1051 # The INCLUDE_PATH tag can be used to specify one or more directories that 

  1052 # contain include files that are not input files but should be processed by 

  1053 # the preprocessor.

  1054 

  1055 INCLUDE_PATH           = 

  1056 

  1057 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 

  1058 # patterns (like *.h and *.hpp) to filter out the header-files in the 

  1059 # directories. If left blank, the patterns specified with FILE_PATTERNS will 

  1060 # be used.

  1061 

  1062 INCLUDE_FILE_PATTERNS  = 

  1063 

  1064 # The PREDEFINED tag can be used to specify one or more macro names that 

  1065 # are defined before the preprocessor is started (similar to the -D option of 

  1066 # gcc). The argument of the tag is a list of macros of the form: name 

  1067 # or name=definition (no spaces). If the definition and the = are 

  1068 # omitted =1 is assumed. To prevent a macro definition from being 

  1069 # undefined via #undef or recursively expanded use the := operator 

  1070 # instead of the = operator.

  1071 

  1072 PREDEFINED             = "NONSHARABLE_CLASS(name)=class name" \

  1073                          "_LIT(name,string)=const static TLitC<sizeof(L##string)/2> name={sizeof(L##string)/2-1,L##string}"

  1074 

  1075 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 

  1076 # this tag can be used to specify a list of macro names that should be expanded. 

  1077 # The macro definition that is found in the sources will be used. 

  1078 # Use the PREDEFINED tag if you want to use a different macro definition.

  1079 

  1080 EXPAND_AS_DEFINED      = 

  1081 

  1082 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 

  1083 # doxygen's preprocessor will remove all function-like macros that are alone 

  1084 # on a line, have an all uppercase name, and do not end with a semicolon. Such 

  1085 # function macros are typically used for boiler-plate code, and will confuse 

  1086 # the parser if not removed.

  1087 

  1088 SKIP_FUNCTION_MACROS   = YES

  1089 

  1090 #---------------------------------------------------------------------------

  1091 # Configuration::additions related to external references   

  1092 #---------------------------------------------------------------------------

  1093 

  1094 # The TAGFILES option can be used to specify one or more tagfiles. 

  1095 # Optionally an initial location of the external documentation 

  1096 # can be added for each tagfile. The format of a tag file without 

  1097 # this location is as follows: 

  1098 #   TAGFILES = file1 file2 ... 

  1099 # Adding location for the tag files is done as follows: 

  1100 #   TAGFILES = file1=loc1 "file2 = loc2" ... 

  1101 # where "loc1" and "loc2" can be relative or absolute paths or 

  1102 # URLs. If a location is present for each tag, the installdox tool 

  1103 # does not have to be run to correct the links.

  1104 # Note that each tag file must have a unique name

  1105 # (where the name does NOT include the path)

  1106 # If a tag file is not located in the directory in which doxygen 

  1107 # is run, you must also specify the path to the tagfile here.

  1108 

  1109 TAGFILES               = 

  1110 

  1111 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 

  1112 # a tag file that is based on the input files it reads.

  1113 

  1114 GENERATE_TAGFILE       = 

  1115 

  1116 # If the ALLEXTERNALS tag is set to YES all external classes will be listed 

  1117 # in the class index. If set to NO only the inherited external classes 

  1118 # will be listed.

  1119 

  1120 ALLEXTERNALS           = NO

  1121 

  1122 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 

  1123 # in the modules index. If set to NO, only the current project's groups will 

  1124 # be listed.

  1125 

  1126 EXTERNAL_GROUPS        = YES

  1127 

  1128 # The PERL_PATH should be the absolute path and name of the perl script 

  1129 # interpreter (i.e. the result of `which perl').

  1130 

  1131 PERL_PATH              = /usr/bin/perl

  1132 

  1133 #---------------------------------------------------------------------------

  1134 # Configuration options related to the dot tool