1 # Doxyfile 1.5.4

     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           = "Flexible Timers API"

    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         = 0.1.1

    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       =

    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       = 

    89 

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

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

    92 # description.

    93 

    94 ALWAYS_DETAILED_SEC    = NO

    95 

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

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

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

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

   100 

   101 INLINE_INHERITED_MEMB  = NO

   102 

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

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

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

   106 

   107 FULL_PATH_NAMES        = YES

   108 

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

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

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

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

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

   114 # path to strip.

   115 

   116 STRIP_FROM_PATH        = 

   117 

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

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

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

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

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

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

   124 

   125 STRIP_FROM_INC_PATH    = 

   126 

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

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

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

   130 

   131 SHORT_NAMES            = NO

   132 

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

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

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

   136 # comments will behave just like regular Qt-style comments 

   137 # (thus requiring an explicit @brief command for a brief description.)

   138 

   139 JAVADOC_AUTOBRIEF      = YES

   140 

   141 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 

   142 # interpret the first line (until the first dot) of a Qt-style 

   143 # comment as the brief description. If set to NO, the comments 

   144 # will behave just like regular Qt-style comments (thus requiring 

   145 # an explicit \brief command for a brief description.)

   146 

   147 QT_AUTOBRIEF           = NO

   148 

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

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

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

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

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

   154 

   155 MULTILINE_CPP_IS_BRIEF = NO

   156 

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

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

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

   160 # documentation.

   161 

   162 DETAILS_AT_TOP         = 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                = "panic=\par \"Panic code:\" \e" \

   189                          "leave=\par \"Leave code:\" \e"

   190 

   191 

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

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

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

   195 # of all members will be omitted, etc.

   196 

   197 OPTIMIZE_OUTPUT_FOR_C  = NO

   198 

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

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

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

   202 # will look different, etc.

   203 

   204 OPTIMIZE_OUTPUT_JAVA   = NO

   205 

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

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

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

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

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

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

   212 

   213 BUILTIN_STL_SUPPORT    = NO

   214 

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

   216 # enable parsing support.

   217 

   218 CPP_CLI_SUPPORT        = NO

   219 

   220 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 

   221 # Doxygen will parse them like normal C++ but will assume all classes use public 

   222 # instead of private inheritance when no explicit protection keyword is present.

   223 

   224 SIP_SUPPORT            = NO

   225 

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

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

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

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

   230 

   231 DISTRIBUTE_GROUP_DOC   = NO

   232 

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

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

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

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

   237 # the \nosubgrouping command.

   238 

   239 SUBGROUPING            = YES

   240 

   241 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct (or union) is 

   242 # documented as struct with the name of the typedef. So 

   243 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct 

   244 # with name TypeT. When disabled the typedef will appear as a member of a file, 

   245 # namespace, or class. And the struct will be named TypeS. This can typically 

   246 # be useful for C code where the coding convention is that all structs are 

   247 # typedef'ed and only the typedef is referenced never the struct's name.

   248 

   249 TYPEDEF_HIDES_STRUCT   = NO

   250 

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

   252 # Build related configuration options

   253 #---------------------------------------------------------------------------

   254 

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

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

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

   258 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES

   259 

   260 EXTRACT_ALL            = NO

   261 

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

   263 # will be included in the documentation.

   264 

   265 EXTRACT_PRIVATE        = NO

   266 

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

   268 # will be included in the documentation.

   269 

   270 EXTRACT_STATIC         = NO

   271 

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

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

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

   275 

   276 EXTRACT_LOCAL_CLASSES  = YES

   277 

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

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

   280 # the interface are included in the documentation. 

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

   282 

   283 EXTRACT_LOCAL_METHODS  = NO

   284 

   285 # If this flag is set to YES, the members of anonymous namespaces will be extracted 

   286 # and appear in the documentation as a namespace called 'anonymous_namespace{file}', 

   287 # where file will be replaced with the base name of the file that contains the anonymous 

   288 # namespace. By default anonymous namespace are hidden.

   289 

   290 EXTRACT_ANON_NSPACES   = NO

   291 

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

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

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

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

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

   297 

   298 HIDE_UNDOC_MEMBERS     = NO

   299 

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

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

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

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

   304 

   305 HIDE_UNDOC_CLASSES     = NO

   306 

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

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

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

   310 # documentation.

   311 

   312 HIDE_FRIEND_COMPOUNDS  = NO

   313 

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

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

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

   317 # function's detailed documentation block.

   318 

   319 HIDE_IN_BODY_DOCS      = NO

   320 

   321 # The INTERNAL_DOCS tag determines if documentation 

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

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

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

   325 

   326 INTERNAL_DOCS          = NO

   327 

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

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

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

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

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

   333 

   334 CASE_SENSE_NAMES       = NO

   335 

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

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

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

   339 

   340 HIDE_SCOPE_NAMES       = NO

   341 

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

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

   344 # of that file.

   345 

   346 SHOW_INCLUDE_FILES     = YES

   347 

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

   349 # is inserted in the documentation for inline members.

   350 

   351 INLINE_INFO            = YES

   352 

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

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

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

   356 # declaration order.

   357 

   358 SORT_MEMBER_DOCS       = YES

   359 

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

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

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

   363 # declaration order.

   364 

   365 SORT_BRIEF_DOCS        = NO

   366 

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

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

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

   370 # not including the namespace part. 

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

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

   373 # alphabetical list.

   374 

   375 SORT_BY_SCOPE_NAME     = NO

   376 

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

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

   379 # commands in the documentation.

   380 

   381 GENERATE_TODOLIST      = YES

   382 

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

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

   385 # commands in the documentation.

   386 

   387 GENERATE_TESTLIST      = YES

   388 

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

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

   391 # commands in the documentation.

   392 

   393 GENERATE_BUGLIST       = YES

   394 

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

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

   397 # \deprecated commands in the documentation.

   398 

   399 GENERATE_DEPRECATEDLIST= YES

   400 

   401 # The ENABLED_SECTIONS tag can be used to enable conditional 

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

   403 

   404 ENABLED_SECTIONS       = 

   405 

   406 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 

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

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

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

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

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

   412 # command in the documentation regardless of this setting.

   413 

   414 MAX_INITIALIZER_LINES  = 30

   415 

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

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

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

   419 

   420 SHOW_USED_FILES        = NO

   421 

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

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

   424 # in the documentation. The default is NO.

   425 

   426 SHOW_DIRECTORIES       = NO

   427 

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

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

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

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

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

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

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

   435 

   436 FILE_VERSION_FILTER    = 

   437 

   438 #---------------------------------------------------------------------------

   439 # configuration options related to warning and progress messages

   440 #---------------------------------------------------------------------------

   441 

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

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

   444 

   445 QUIET                  = NO

   446 

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

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

   449 # NO is used.

   450 

   451 WARNINGS               = YES

   452 

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

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

   455 # automatically be disabled.

   456 

   457 WARN_IF_UNDOCUMENTED   = YES

   458 

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

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

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

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

   463 

   464 WARN_IF_DOC_ERROR      = YES

   465 

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

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

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

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

   470 # documentation.

   471 

   472 WARN_NO_PARAMDOC       = NO

   473 

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

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

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

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

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

   479 # be obtained via FILE_VERSION_FILTER)

   480 

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

   482 

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

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

   485 # to stderr.

   486 

   487 WARN_LOGFILE           = 

   488 

   489 #---------------------------------------------------------------------------

   490 # configuration options related to the input files

   491 #---------------------------------------------------------------------------

   492 

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

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

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

   496 # with spaces.

   497 

   498 INPUT                  = flextimer_for_clients.dox classesfordox.h ../client

   499 

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

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

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

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

   504 

   505 INPUT_ENCODING         = UTF-8

   506 

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

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

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

   510 # blank the following patterns are tested: 

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

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

   513 

   514 FILE_PATTERNS          = 

   515 

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

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

   518 # If left blank NO is used.

   519 

   520 RECURSIVE              = YES

   521 

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

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

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

   525 

   526 EXCLUDE                = .svn html

   527 

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

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

   530 # from the input.

   531 

   532 EXCLUDE_SYMLINKS       = NO

   533 

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

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

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

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

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

   539 

   540 EXCLUDE_PATTERNS       = */.svn/* */.svn */traces/*

   541 

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

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

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

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

   546 

   547 EXCLUDE_SYMBOLS        = CActive                        \

   548                          CBase                          \

   549                          CPeriodic                      \

   550                          CServer2                       \

   551                          CSession2                      \

   552                          CTimer                         \

   553                          RHandleBase                    \

   554                          RSessionBase                   \

   555                          RThread                        \

   556                          RTimer                         \

   557                          TCallBack                      \

   558                          TRequestStatus                 \

   559                          TTime                          \

   560                          TTimeIntervalMicroSeconds      \

   561                          TTimeIntervalMicroSeconds32    \

   562                          TVersion

   563 

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

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

   566 # the \include command).

   567 

   568 EXAMPLE_PATH           = 

   569 

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

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

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

   573 # blank all files are included.

   574 

   575 EXAMPLE_PATTERNS       = 

   576 

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

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

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

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

   581 

   582 EXAMPLE_RECURSIVE      = NO

   583 

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

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

   586 # the \image command).

   587 

   588 IMAGE_PATH             = ./pics

   589 

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

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

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

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

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

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

   596 # ignored.

   597 

   598 INPUT_FILTER           = 

   599 

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

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

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

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

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

   605 # is applied to all files.

   606 

   607 FILTER_PATTERNS        = 

   608 

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

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

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

   612 

   613 FILTER_SOURCE_FILES    = NO

   614 

   615 #---------------------------------------------------------------------------

   616 # configuration options related to source browsing

   617 #---------------------------------------------------------------------------

   618 

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

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

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

   622 # VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH 

   623 # then you must also enable this option. If you don't then doxygen will produce 

   624 # a warning and turn it on anyway

   625 

   626 SOURCE_BROWSER         = NO

   627 

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

   629 # of functions and classes directly in the documentation.

   630 

   631 INLINE_SOURCES         = NO

   632 

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

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

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

   636 

   637 STRIP_CODE_COMMENTS    = YES

   638 

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

   640 # then for each documented function all documented 

   641 # functions referencing it will be listed.

   642 

   643 REFERENCED_BY_RELATION = YES

   644 

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

   646 # then for each documented function all documented entities 

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

   648 

   649 REFERENCES_RELATION    = YES

   650 

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

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

   653 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will

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

   655 

   656 REFERENCES_LINK_SOURCE = YES

   657 

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

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

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

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

   662 # will need version 4.8.6 or higher.

   663 

   664 USE_HTAGS              = NO

   665 

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

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

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

   669 

   670 VERBATIM_HEADERS       = YES

   671 

   672 #---------------------------------------------------------------------------

   673 # configuration options related to the alphabetical class index

   674 #---------------------------------------------------------------------------

   675 

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

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

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

   679 

   680 ALPHABETICAL_INDEX     = NO

   681 

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

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

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

   685 

   686 COLS_IN_ALPHA_INDEX    = 5

   687 

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

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

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

   691 # should be ignored while generating the index headers.

   692 

   693 IGNORE_PREFIX          = 

   694 

   695 #---------------------------------------------------------------------------

   696 # configuration options related to the HTML output

   697 #---------------------------------------------------------------------------

   698 

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

   700 # generate HTML output.

   701 

   702 GENERATE_HTML          = YES

   703 

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

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

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

   707 

   708 HTML_OUTPUT            = html

   709 

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

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

   712 # doxygen will generate files with .html extension.

   713 

   714 HTML_FILE_EXTENSION    = .html

   715 

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

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

   718 # standard header.

   719 

   720 HTML_HEADER            = 

   721 

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

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

   724 # standard footer.

   725 

   726 HTML_FOOTER            = 

   727 

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

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

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

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

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

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

   734 

   735 HTML_STYLESHEET        = 

   736 

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

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

   739 # NO a bullet list will be used.

   740 

   741 HTML_ALIGN_MEMBERS     = YES

   742 

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

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

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

   746 # of the generated HTML documentation.

   747 

   748 GENERATE_HTMLHELP      = YES

   749 

   750 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 

   751 # documentation will contain sections that can be hidden and shown after the 

   752 # page has loaded. For this to work a browser that supports 

   753 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 

   754 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).

   755 

   756 HTML_DYNAMIC_SECTIONS  = NO

   757 

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

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

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

   761 # written to the html output directory.

   762 

   763 CHM_FILE               = 

   764 

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

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

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

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

   769 

   770 HHC_LOCATION           = "C:\Program Files\HTML Help Workshop\hhc.exe"

   771 

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

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

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

   775 

   776 GENERATE_CHI           = NO

   777 

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

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

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

   781 

   782 BINARY_TOC             = NO

   783 

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

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

   786 

   787 TOC_EXPAND             = NO

   788 

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

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

   791 # the value YES disables it.

   792 

   793 DISABLE_INDEX          = NO

   794 

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

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

   797 

   798 ENUM_VALUES_PER_LINE   = 4

   799 

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

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

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

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

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

   805 # probably better off using the HTML help feature.

   806 

   807 GENERATE_TREEVIEW      = NO

   808 

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

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

   811 # is shown.

   812 

   813 TREEVIEW_WIDTH         = 250

   814 

   815 #---------------------------------------------------------------------------

   816 # configuration options related to the LaTeX output

   817 #---------------------------------------------------------------------------

   818 

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

   820 # generate Latex output.

   821 

   822 GENERATE_LATEX         = NO

   823 

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

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

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

   827 

   828 LATEX_OUTPUT           = latex

   829 

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

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

   832 

   833 LATEX_CMD_NAME         = latex

   834 

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

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

   837 # default command name.

   838 

   839 MAKEINDEX_CMD_NAME     = makeindex

   840 

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

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

   843 # save some trees in general.

   844 

   845 COMPACT_LATEX          = NO

   846 

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

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

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

   850 

   851 PAPER_TYPE             = a4wide

   852 

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

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

   855 

   856 EXTRA_PACKAGES         = 

   857 

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

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

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

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

   862 

   863 LATEX_HEADER           = 

   864 

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

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

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

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

   869 

   870 PDF_HYPERLINKS         = NO

   871 

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

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

   874 # higher quality PDF documentation.

   875 

   876 USE_PDFLATEX           = NO

   877 

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

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

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

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

   882 

   883 LATEX_BATCHMODE        = NO

   884 

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

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

   887 # in the output.

   888 

   889 LATEX_HIDE_INDICES     = NO

   890 

   891 #---------------------------------------------------------------------------

   892 # configuration options related to the RTF output

   893 #---------------------------------------------------------------------------

   894 

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

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

   897 # other RTF readers or editors.

   898 

   899 GENERATE_RTF           = NO

   900 

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

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

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

   904 

   905 RTF_OUTPUT             = rtf

   906 

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

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

   909 # save some trees in general.

   910 

   911 COMPACT_RTF            = NO

   912 

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

   914 # will contain hyperlink fields. The RTF file will 

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

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

   917 # programs which support those fields. 

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

   919 

   920 RTF_HYPERLINKS         = NO

   921 

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

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

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

   925 

   926 RTF_STYLESHEET_FILE    = 

   927 

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

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

   930 

   931 RTF_EXTENSIONS_FILE    = 

   932 

   933 #---------------------------------------------------------------------------

   934 # configuration options related to the man page output

   935 #---------------------------------------------------------------------------

   936 

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

   938 # generate man pages

   939 

   940 GENERATE_MAN           = NO

   941 

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

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

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

   945 

   946 MAN_OUTPUT             = man

   947 

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

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

   950 

   951 MAN_EXTENSION          = .3

   952 

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

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

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

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

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

   958 

   959 MAN_LINKS              = NO

   960 

   961 #---------------------------------------------------------------------------

   962 # configuration options related to the XML output

   963 #---------------------------------------------------------------------------

   964 

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

   966 # generate an XML file that captures the structure of 

   967 # the code including all documentation.

   968 

   969 GENERATE_XML           = NO

   970 

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

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

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

   974 

   975 XML_OUTPUT             = xml

   976 

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

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

   979 # syntax of the XML files.

   980 

   981 XML_SCHEMA             = 

   982 

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

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

   985 # syntax of the XML files.

   986 

   987 XML_DTD                = 

   988 

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

   990 # dump the program listings (including syntax highlighting 

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

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

   993 

   994 XML_PROGRAMLISTING     = YES

   995 

   996 #---------------------------------------------------------------------------

   997 # configuration options for the AutoGen Definitions output

   998 #---------------------------------------------------------------------------

   999 

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

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

  1002 # that captures the structure of the code including all 

  1003 # documentation. Note that this feature is still experimental 

  1004 # and incomplete at the moment.

  1005 

  1006 GENERATE_AUTOGEN_DEF   = NO

  1007 

  1008 #---------------------------------------------------------------------------

  1009 # configuration options related to the Perl module output

  1010 #---------------------------------------------------------------------------

  1011 

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

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

  1014 # the code including all documentation. Note that this 

  1015 # feature is still experimental and incomplete at the 

  1016 # moment.

  1017 

  1018 GENERATE_PERLMOD       = NO

  1019 

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

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

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

  1023 

  1024 PERLMOD_LATEX          = NO

  1025 

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

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

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

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

  1030 # and Perl will parse it just the same.

  1031 

  1032 PERLMOD_PRETTY         = YES

  1033 

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

  1035 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 

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

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

  1038 

  1039 PERLMOD_MAKEVAR_PREFIX = 

  1040 

  1041 #---------------------------------------------------------------------------

  1042 # Configuration options related to the preprocessor   

  1043 #---------------------------------------------------------------------------

  1044 

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

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

  1047 # files.

  1048 

  1049 ENABLE_PREPROCESSING   = YES

  1050 

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

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

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

  1054 # way by setting EXPAND_ONLY_PREDEF to YES.

  1055 

  1056 MACRO_EXPANSION        = NO

  1057 

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

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

  1060 # PREDEFINED and EXPAND_AS_DEFINED tags.

  1061 

  1062 EXPAND_ONLY_PREDEF     = NO

  1063 

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

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

  1066 

  1067 SEARCH_INCLUDES        = YES

  1068 

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

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

  1071 # the preprocessor.

  1072 

  1073 INCLUDE_PATH           = 

  1074 

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

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

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

  1078 # be used.

  1079 

  1080 INCLUDE_FILE_PATTERNS  = 

  1081 

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

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

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

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

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

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

  1088 # instead of the = operator.

  1089 

  1090 PREDEFINED             = IMPORT_C= \

  1091                          EXPORT_C= \

  1092                          "NONSHARABLE_CLASS(name)=class name"

  1093 

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

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

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

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

  1098 

  1099 EXPAND_AS_DEFINED      = 

  1100 

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

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

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

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

  1105 # the parser if not removed.

  1106 

  1107 SKIP_FUNCTION_MACROS   = YES

  1108 

  1109 #---------------------------------------------------------------------------

  1110 # Configuration::additions related to external references   

  1111 #---------------------------------------------------------------------------

  1112 

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

  1114 # Optionally an initial location of the external documentation 

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

  1116 # this location is as follows: 

  1117 #   TAGFILES = file1 file2 ... 

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

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

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

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

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

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

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

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

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

  1127 

  1128 TAGFILES               = 

  1129 

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

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

  1132 

  1133 GENERATE_TAGFILE       = 

  1134