1 <doxygenconfig>

     2   <group name='Project' docs='Project related configuration options'>

     3     <option type='string' id='DOXYFILE_ENCODING' format='string' docs='

     4 This tag specifies the encoding used for all characters in the config file 

     5 that follow. The default is UTF-8 which is also the encoding used for all 

     6 text before the first occurrence of this tag. Doxygen uses libiconv (or the 

     7 iconv built into libc) for the transcoding. See 

     8 http://www.gnu.org/software/libiconv for the list of possible encodings. 

     9 ' defval='UTF-8'/>

    10     <option type='string' id='PROJECT_NAME' format='string' docs='

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

    12 by quotes) that should identify the project. ' defval=''/>

    13     <option type='string' id='PROJECT_NUMBER' format='string' docs='

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

    15 This could be handy for archiving the generated documentation or 

    16 if some version control system is used. 

    17 ' defval=''/>

    18     <option type='string' id='OUTPUT_DIRECTORY' format='dir' docs='

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

    20 base path where the generated documentation will be put. 

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

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

    23 ' defval=''/>

    24     <option type='bool' id='CREATE_SUBDIRS' docs='

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

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

    27 format and will distribute the generated files over these directories. 

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

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

    30 otherwise cause performance problems for the file system. 

    31 ' defval='0'/>

    32     <option type='enum' id='OUTPUT_LANGUAGE' defval='English' docs='

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

    34 documentation generated by doxygen is written. Doxygen will use this 

    35 information to generate all constant output in the proper language. 

    36 The default language is English, other supported languages are: 

    37 Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 

    38 Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 

    39 Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 

    40 messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 

    41 Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 

    42 Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 

    43 '>

    44       <value name='Afrikaans'/>

    45       <value name='Arabic'/>

    46       <value name='Brazilian'/>

    47       <value name='Catalan'/>

    48       <value name='Chinese'/>

    49       <value name='Chinese-Traditional'/>

    50       <value name='Croatian'/>

    51       <value name='Czech'/>

    52       <value name='Danish'/>

    53       <value name='Dutch'/>

    54       <value name='English'/>

    55       <value name='Esperanto'/>

    56       <value name='Farsi'/>

    57       <value name='Finnish'/>

    58       <value name='French'/>

    59       <value name='German'/>

    60       <value name='Greek'/>

    61       <value name='Hungarian'/>

    62       <value name='Italian'/>

    63       <value name='Japanese'/>

    64       <value name='Japanese-en'/>

    65       <value name='Korean'/>

    66       <value name='Korean-en'/>

    67       <value name='Norwegian'/>

    68       <value name='Macedonian'/>

    69       <value name='Persian'/>

    70       <value name='Polish'/>

    71       <value name='Portuguese'/>

    72       <value name='Romanian'/>

    73       <value name='Russian'/>

    74       <value name='Serbian'/>

    75       <value name='Slovak'/>

    76       <value name='Slovene'/>

    77       <value name='Spanish'/>

    78       <value name='Swedish'/>

    79       <value name='Turkish'/>

    80       <value name='Ukrainian'/>

    81       <value name='Vietnamese'/>

    82     </option>

    83     <option type='bool' id='BRIEF_MEMBER_DESC' docs='

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

    85 include brief member descriptions after the members that are listed in 

    86 the file and class documentation (similar to JavaDoc). 

    87 Set to NO to disable this. 

    88 ' defval='1'/>

    89     <option type='bool' id='REPEAT_BRIEF' docs='

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

    91 the brief description of a member or function before the detailed description. 

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

    93 brief descriptions will be completely suppressed. 

    94 ' defval='1'/>

    95     <option type='list' id='ABBREVIATE_BRIEF' format='string' docs='

    96 This tag implements a quasi-intelligent brief description abbreviator 

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

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

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

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

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

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

   103 "The $name file" "is" "provides" "specifies" "contains" 

   104 "represents" "a" "an" "the" 

   105 '>

   106       <value name='The $name class'/>

   107       <value name='The $name widget'/>

   108       <value name='The $name file'/>

   109       <value name='is'/>

   110       <value name='provides'/>

   111       <value name='specifies'/>

   112       <value name='contains'/>

   113       <value name='represents'/>

   114       <value name='a'/>

   115       <value name='an'/>

   116       <value name='the'/>

   117     </option>

   118     <option type='bool' id='ALWAYS_DETAILED_SEC' docs='

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

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

   121 description. 

   122 ' defval='0'/>

   123     <option type='bool' id='INLINE_INHERITED_MEMB' docs='

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

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

   126 members were ordinary class members. Constructors, destructors and assignment 

   127 operators of the base classes will not be shown. 

   128 ' defval='0'/>

   129     <option type='bool' id='FULL_PATH_NAMES' docs='

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

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

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

   133 ' defval='1'/>

   134     <option type='list' id='STRIP_FROM_PATH' format='string' docs='

   135 If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 

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

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

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

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

   140 path to strip. 

   141 ' depends='FULL_PATH_NAMES'>

   142       <value name=''/>

   143     </option>

   144     <option type='list' id='STRIP_FROM_INC_PATH' format='string' docs='

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

   146 the path mentioned in the documentation of a class, which tells 

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

   148 If left blank only the name of the header file containing the class 

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

   150 are normally passed to the compiler using the -I flag. 

   151 '>

   152     </option>

   153     <option type='bool' id='SHORT_NAMES' docs='

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

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

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

   157 ' defval='0'/>

   158     <option type='bool' id='JAVADOC_AUTOBRIEF' docs='

   159 If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 

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

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

   162 comments will behave just like regular Qt-style comments 

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

   164 ' defval='0'/>

   165     <option type='bool' id='QT_AUTOBRIEF' docs='

   166 If the QT_AUTOBRIEF tag is set to YES then Doxygen will 

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

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

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

   170 an explicit \brief command for a brief description.) 

   171 ' defval='0'/>

   172     <option type='bool' id='MULTILINE_CPP_IS_BRIEF' docs='

   173 The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 

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

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

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

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

   178 ' defval='0'/>

   179     <option type='bool' id='INHERIT_DOCS' docs='

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

   181 member inherits the documentation from any documented member that it 

   182 re-implements. 

   183 ' defval='1'/>

   184     <option type='bool' id='SEPARATE_MEMBER_PAGES' docs='

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

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

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

   188 ' defval='0'/>

   189     <option type='int' id='TAB_SIZE' docs='

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

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

   192 ' minval='1' maxval='16' defval='8'/>

   193     <option type='list' id='ALIASES' format='string' docs='

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

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

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

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

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

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

   200 '>

   201     </option>

   202     <option type='bool' id='OPTIMIZE_OUTPUT_FOR_C' docs='

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

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

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

   206 of all members will be omitted, etc. 

   207 ' defval='0'/>

   208     <option type='bool' id='OPTIMIZE_OUTPUT_JAVA' docs='

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

   210 sources only. Doxygen will then generate output that is more tailored for 

   211 Java. For instance, namespaces will be presented as packages, qualified 

   212 scopes will look different, etc. 

   213 ' defval='0'/>

   214     <option type='bool' id='OPTIMIZE_FOR_FORTRAN' docs='

   215 Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 

   216 sources only. Doxygen will then generate output that is more tailored for 

   217 Fortran. 

   218 ' defval='0'/>

   219     <option type='bool' id='OPTIMIZE_OUTPUT_VHDL' docs='

   220 Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 

   221 sources. Doxygen will then generate output that is tailored for 

   222 VHDL. 

   223 ' defval='0'/>

   224     <option type='list' id='EXTENSION_MAPPING' format='string' docs='

   225 Doxygen selects the parser to use depending on the extension of the files it parses. 

   226 With this tag you can assign which parser to use for a given extension. 

   227 Doxygen has a built-in mapping, but you can override or extend it using this tag. 

   228 The format is ext=language, where ext is a file extension, and language is one of 

   229 the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, 

   230 Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat 

   231 .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), 

   232 use: inc=Fortran f=C. Note that for custom extensions you also need to set

   233 FILE_PATTERNS otherwise the files are not read by doxygen.

   234 '>

   235     </option>

   236     <option type='bool' id='BUILTIN_STL_SUPPORT' docs='

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

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

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

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

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

   242 diagrams that involve STL classes more complete and accurate. 

   243 ' defval='0'/>

   244     <option type='bool' id='CPP_CLI_SUPPORT' docs='

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

   246 enable parsing support. 

   247 ' defval='0'/>

   248     <option type='bool' id='SIP_SUPPORT' docs='

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

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

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

   252 ' defval='0'/>

   253     <option type='bool' id='IDL_PROPERTY_SUPPORT' docs='

   254 For Microsoft's IDL there are propget and propput attributes to indicate getter 

   255 and setter methods for a property. Setting this option to YES (the default) 

   256 will make doxygen to replace the get and set methods by a property in the 

   257 documentation. This will only work if the methods are indeed getting or 

   258 setting a simple type. If this is not the case, or you want to show the 

   259 methods anyway, you should set this option to NO. 

   260 ' defval='1'/>

   261     <option type='bool' id='DISTRIBUTE_GROUP_DOC' docs='

   262 If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 

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

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

   265 all members of a group must be documented explicitly. 

   266 ' defval='0'/>

   267     <option type='bool' id='SUBGROUPING' docs='

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

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

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

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

   272 the \nosubgrouping command. 

   273 ' defval='1'/>

   274     <option type='bool' id='TYPEDEF_HIDES_STRUCT' docs='

   275 When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 

   276 is documented as struct, union, or enum with the name of the typedef. So 

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

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

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

   280 be useful for C code in case the coding convention dictates that all compound 

   281 types are typedef'ed and only the typedef is referenced, never the tag name. 

   282 ' defval='0'/>

   283     <option type='int' id='SYMBOL_CACHE_SIZE' docs='

   284 The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 

   285 determine which symbols to keep in memory and which to flush to disk. 

   286 When the cache is full, less often used symbols will be written to disk. 

   287 For small to medium size projects (<1000 input files) the default value is 

   288 probably good enough. For larger projects a too small cache size can cause 

   289 doxygen to be busy swapping symbols to and from disk most of the time 

   290 causing a significant performance penality. 

   291 If the system has enough physical memory increasing the cache will improve the 

   292 performance by keeping more symbols in memory. Note that the value works on 

   293 a logarithmic scale so increasing the size by one will rougly double the 

   294 memory usage. The cache size is given by this formula: 

   295 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 

   296 corresponding to a cache size of 2^16 = 65536 symbols 

   297 ' minval='0' maxval='9' defval='0'/>

   298   </group>

   299   <group name='Build' docs='Build related configuration options'>

   300     <option type='bool' id='EXTRACT_ALL' docs='

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

   302 documentation are documented, even if no documentation was available. 

   303 Private class members and static file members will be hidden unless 

   304 the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 

   305 ' defval='0'/>

   306     <option type='bool' id='EXTRACT_PRIVATE' docs='

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

   308 will be included in the documentation. 

   309 ' defval='0'/>

   310     <option type='bool' id='EXTRACT_STATIC' docs='

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

   312 will be included in the documentation. 

   313 ' defval='0'/>

   314     <option type='bool' id='EXTRACT_LOCAL_CLASSES' docs='

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

   316 defined locally in source files will be included in the documentation. 

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

   318 ' defval='1'/>

   319     <option type='bool' id='EXTRACT_LOCAL_METHODS' docs='

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

   321 methods, which are defined in the implementation section but not in 

   322 the interface are included in the documentation. 

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

   324 ' defval='0'/>

   325     <option type='bool' id='EXTRACT_ANON_NSPACES' docs='

   326 If this flag is set to YES, the members of anonymous namespaces will be 

   327 extracted and appear in the documentation as a namespace called 

   328 'anonymous_namespace{file}', where file will be replaced with the base 

   329 name of the file that contains the anonymous namespace. By default 

   330 anonymous namespace are hidden. 

   331 ' defval='0'/>

   332     <option type='bool' id='HIDE_UNDOC_MEMBERS' docs='

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

   334 undocumented members of documented classes, files or namespaces. 

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

   336 various overviews, but no documentation section is generated. 

   337 This option has no effect if EXTRACT_ALL is enabled. 

   338 ' defval='0'/>

   339     <option type='bool' id='HIDE_UNDOC_CLASSES' docs='

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

   341 undocumented classes that are normally visible in the class hierarchy. 

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

   343 overviews. This option has no effect if EXTRACT_ALL is enabled. 

   344 ' defval='0'/>

   345     <option type='bool' id='HIDE_FRIEND_COMPOUNDS' docs='

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

   347 friend (class|struct|union) declarations. 

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

   349 documentation. 

   350 ' defval='0'/>

   351     <option type='bool' id='HIDE_IN_BODY_DOCS' docs='

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

   353 documentation blocks found inside the body of a function. 

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

   355 function's detailed documentation block. 

   356 ' defval='0'/>

   357     <option type='bool' id='INTERNAL_DOCS' docs='

   358 The INTERNAL_DOCS tag determines if documentation 

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

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

   361 Set it to YES to include the internal documentation. 

   362 ' defval='0'/>

   363     <option type='bool' id='CASE_SENSE_NAMES' docs='

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

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

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

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

   368 and Mac users are advised to set this option to NO. 

   369 ' defval='0' altdefval='portable_fileSystemIsCaseSensitive()'/>

   370     <option type='bool' id='HIDE_SCOPE_NAMES' docs='

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

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

   373 documentation. If set to YES the scope will be hidden. 

   374 ' defval='0'/>

   375     <option type='bool' id='SHOW_INCLUDE_FILES' docs='

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

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

   378 of that file. 

   379 ' defval='1'/>

   380     <option type='bool' id='FORCE_LOCAL_INCLUDES' docs='

   381 If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 

   382 will list include files with double quotes in the documentation 

   383 rather than with sharp brackets.

   384 ' defval='0'/>

   385     <option type='bool' id='INLINE_INFO' docs='

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

   387 is inserted in the documentation for inline members. 

   388 ' defval='1'/>

   389     <option type='bool' id='SORT_MEMBER_DOCS' docs='

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

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

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

   393 declaration order. 

   394 ' defval='1'/>

   395     <option type='bool' id='SORT_BRIEF_DOCS' docs='

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

   397 brief documentation of file, namespace and class members alphabetically 

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

   399 declaration order. 

   400 ' defval='0'/>

   401     <option type='bool' id='SORT_MEMBERS_CTORS_1ST' docs='

   402 If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen

   403 will sort the (brief and detailed) documentation of class members so that

   404 constructors and destructors are listed first. If set to NO (the default)

   405 the constructors will appear in the respective orders defined by

   406 SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.

   407 This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO

   408 and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.' defval='0'/>

   409     <option type='bool' id='SORT_GROUP_NAMES' docs='

   410 If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 

   411 hierarchy of group names into alphabetical order. If set to NO (the default) 

   412 the group names will appear in their defined order. 

   413 ' defval='0'/>

   414     <option type='bool' id='SORT_BY_SCOPE_NAME' docs='

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

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

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

   418 not including the namespace part. 

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

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

   421 alphabetical list. 

   422 ' defval='0'/>

   423     <option type='bool' id='GENERATE_TODOLIST' docs='

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

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

   426 commands in the documentation. 

   427 ' defval='1'/>

   428     <option type='bool' id='GENERATE_TESTLIST' docs='

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

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

   431 commands in the documentation. 

   432 ' defval='1'/>

   433     <option type='bool' id='GENERATE_BUGLIST' docs='

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

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

   436 commands in the documentation. 

   437 ' defval='1'/>

   438     <option type='bool' id='GENERATE_DEPRECATEDLIST' docs='

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

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

   441 \deprecated commands in the documentation. 

   442 ' defval='1'/>

   443     <option type='list' id='ENABLED_SECTIONS' format='string' docs='

   444 The ENABLED_SECTIONS tag can be used to enable conditional 

   445 documentation sections, marked by \if sectionname ... \endif. 

   446 '>

   447     </option>

   448     <option type='int' id='MAX_INITIALIZER_LINES' docs='

   449 The MAX_INITIALIZER_LINES tag determines the maximum number of lines 

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

   451 the documentation. If the initializer consists of more lines than specified 

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

   453 The appearance of the initializer of individual variables and defines in the 

   454 documentation can be controlled using \showinitializer or \hideinitializer 

   455 command in the documentation regardless of this setting. 

   456 ' minval='0' maxval='10000' defval='30'/>

   457     <option type='bool' id='SHOW_USED_FILES' docs='

   458 Set the SHOW_USED_FILES tag to NO to disable the list of files generated 

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

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

   461 ' defval='1'/>

   462     <option type='bool' id='SHOW_DIRECTORIES' docs='

   463 If the sources in your project are distributed over multiple directories 

   464 then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 

   465 in the documentation. The default is NO. 

   466 ' defval='0'/>

   467     <option type='bool' id='SHOW_FILES' docs='

   468 Set the SHOW_FILES tag to NO to disable the generation of the Files page. 

   469 This will remove the Files entry from the Quick Index and from the 

   470 Folder Tree View (if specified). The default is YES. 

   471 ' defval='1'/>

   472     <option type='bool' id='SHOW_NAMESPACES' docs='

   473 Set the SHOW_NAMESPACES tag to NO to disable the generation of the 

   474 Namespaces page.  This will remove the Namespaces entry from the Quick Index 

   475 and from the Folder Tree View (if specified). The default is YES. 

   476 ' defval='1'/>

   477     <option type='string' id='FILE_VERSION_FILTER' format='file' docs='

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

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

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

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

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

   483 provided by doxygen. Whatever the program writes to standard output 

   484 is used as the file version. See the manual for examples. 

   485 ' defval=''/>

   486     <option type='string' id='LAYOUT_FILE' format='file' docs='

   487 The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by 

   488 doxygen. The layout file controls the global structure of the generated output files 

   489 in an output format independent way. The create the layout file that represents 

   490 doxygen's defaults, run doxygen with the -l option. You can optionally specify a 

   491 file name after the option, if omitted DoxygenLayout.xml will be used as the name 

   492 of the layout file. 

   493 ' defval=''/>

   494     <option type='bool' id='OUTPUT_INCLUDES' docs='

   495 If set this will write out documentation for #included files so that links can be 

   496 made from INPUT files to them. 

   497 if PREPROCESS_INCLUDES is not set then this has no effect.

   498 You are strongly advised to have EXTRACT_ALL = YES, if not some include files 

   499 may not be linkable to.

   500 ' defval='0'/>

   501   </group>

   502   <group name='Messages' docs='configuration options related to warning and progress messages'>

   503     <option type='bool' id='QUIET' docs='

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

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

   506 ' defval='0'/>

   507     <option type='bool' id='WARNINGS' docs='

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

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

   510 NO is used. 

   511 ' defval='1'/>

   512     <option type='bool' id='WARN_IF_UNDOCUMENTED' docs='

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

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

   515 automatically be disabled. 

   516 ' defval='1'/>

   517     <option type='bool' id='WARN_IF_DOC_ERROR' docs='

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

   519 potential errors in the documentation, such as not documenting some 

   520 parameters in a documented function, or documenting parameters that 

   521 don't exist or using markup commands wrongly. 

   522 ' defval='1'/>

   523     <option type='bool' id='WARN_NO_PARAMDOC' docs='

   524 This WARN_NO_PARAMDOC option can be abled to get warnings for 

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

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

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

   528 documentation. 

   529 ' defval='0'/>

   530     <option type='string' id='WARN_FORMAT' format='string' docs='

   531 The WARN_FORMAT tag determines the format of the warning messages that 

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

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

   534 warning originated and the warning text. Optionally the format may contain 

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

   536 be obtained via FILE_VERSION_FILTER) 

   537 ' defval='$file:$line: $text'/>

   538     <option type='string' id='WARN_LOGFILE' format='file' docs='

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

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

   541 to stderr. 

   542 ' defval=''/>

   543   </group>

   544   <group name='Input' docs='configuration options related to the input files'>

   545     <option type='list' id='INPUT' format='filedir' docs='

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

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

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

   549 with spaces. 

   550 '>

   551       <value name=''/>

   552     </option>

   553     <option type='string' id='INPUT_ENCODING' format='string' docs='

   554 This tag can be used to specify the character encoding of the source files 

   555 that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 

   556 also the default input encoding. Doxygen uses libiconv (or the iconv built 

   557 into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 

   558 the list of possible encodings. 

   559 ' defval='UTF-8'/>

   560     <option type='list' id='FILE_PATTERNS' format='string' docs='

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

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

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

   564 blank the following patterns are tested: 

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

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

   567 '>

   568       <value name='*.c'/>

   569       <value name='*.cc'/>

   570       <value name='*.cxx'/>

   571       <value name='*.cpp'/>

   572       <value name='*.c++'/>

   573       <value name='*.d'/>

   574       <value name='*.java'/>

   575       <value name='*.ii'/>

   576       <value name='*.ixx'/>

   577       <value name='*.ipp'/>

   578       <value name='*.i++'/>

   579       <value name='*.inl'/>

   580       <value name='*.h'/>

   581       <value name='*.hh'/>

   582       <value name='*.hxx'/>

   583       <value name='*.hpp'/>

   584       <value name='*.h++'/>

   585       <value name='*.idl'/>

   586       <value name='*.odl'/>

   587       <value name='*.cs'/>

   588       <value name='*.php'/>

   589       <value name='*.php3'/>

   590       <value name='*.inc'/>

   591       <value name='*.m'/>

   592       <value name='*.mm'/>

   593       <value name='*.dox'/>

   594       <value name='*.py'/>

   595       <value name='*.f90'/>

   596       <value name='*.f'/>

   597       <value name='*.vhd'/>

   598       <value name='*.vhdl'/>

   599     </option>

   600     <option type='bool' id='RECURSIVE' docs='

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

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

   603 If left blank NO is used. 

   604 ' defval='0'/>

   605     <option type='list' id='EXCLUDE' format='filedir' docs='

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

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

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

   609 '>

   610     </option>

   611     <option type='bool' id='EXCLUDE_SYMLINKS' docs='

   612 The EXCLUDE_SYMLINKS tag can be used select whether or not files or 

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

   614 from the input. 

   615 ' defval='0'/>

   616     <option type='list' id='EXCLUDE_PATTERNS' format='string' docs='

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

   618 EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 

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

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

   621 for example use the pattern */test/* 

   622 '>

   623     </option>

   624     <option type='list' id='EXCLUDE_SYMBOLS' format='string' docs='

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

   626 (namespaces, classes, functions, etc.) that should be excluded from the 

   627 output. The symbol name can be a fully qualified name, a word, or if the 

   628 wildcard * is used, a substring. Examples: ANamespace, AClass, 

   629 AClass::ANamespace, ANamespace::*Test 

   630 '>

   631     </option>

   632     <option type='list' id='EXAMPLE_PATH' format='dir' docs='

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

   634 directories that contain example code fragments that are included (see 

   635 the \include command). 

   636 '>

   637     </option>

   638     <option type='list' id='EXAMPLE_PATTERNS' format='string' docs='

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

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

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

   642 blank all files are included. 

   643 '>

   644       <value name='*'/>

   645     </option>

   646     <option type='bool' id='EXAMPLE_RECURSIVE' docs='

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

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

   649 commands irrespective of the value of the RECURSIVE tag. 

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

   651 ' defval='0'/>

   652     <option type='list' id='IMAGE_PATH' format='dir' docs='

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

   654 directories that contain image that are included in the documentation (see 

   655 the \image command). 

   656 '>

   657     </option>

   658     <option type='string' id='INPUT_FILTER' format='file' docs='

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

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

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

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

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

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

   665 ignored. 

   666 ' defval=''/>

   667     <option type='list' id='FILTER_PATTERNS' format='file' docs='

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

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

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

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

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

   673 is applied to all files. 

   674 '>

   675     </option>

   676     <option type='bool' id='FILTER_SOURCE_FILES' docs='

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

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

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

   680 ' defval='0'/>

   681   </group>

   682   <group name='Source Browser' docs='configuration options related to source browsing'>

   683     <option type='bool' id='SOURCE_BROWSER' docs='

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

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

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

   687 VERBATIM_HEADERS is set to NO. 

   688 ' defval='0'/>

   689     <option type='bool' id='INLINE_SOURCES' docs='

   690 Setting the INLINE_SOURCES tag to YES will include the body 

   691 of functions and classes directly in the documentation. 

   692 ' defval='0'/>

   693     <option type='bool' id='STRIP_CODE_COMMENTS' docs='

   694 Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 

   695 doxygen to hide any special comment blocks from generated source code 

   696 fragments. Normal C and C++ comments will always remain visible. 

   697 ' defval='1'/>

   698     <option type='bool' id='REFERENCED_BY_RELATION' docs='

   699 If the REFERENCED_BY_RELATION tag is set to YES 

   700 then for each documented function all documented 

   701 functions referencing it will be listed. 

   702 ' defval='0'/>

   703     <option type='bool' id='REFERENCES_RELATION' docs='

   704 If the REFERENCES_RELATION tag is set to YES 

   705 then for each documented function all documented entities 

   706 called/used by that function will be listed. 

   707 ' defval='0'/>

   708     <option type='bool' id='REFERENCES_LINK_SOURCE' docs='

   709 If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 

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

   711 functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 

   712 link to the source code.  Otherwise they will link to the documentation. 

   713 ' defval='1'/>

   714     <option type='bool' id='USE_HTAGS' docs='

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

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

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

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

   719 will need version 4.8.6 or higher. 

   720 ' defval='0' depends='SOURCE_BROWSER'/>

   721     <option type='bool' id='VERBATIM_HEADERS' docs='

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

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

   724 which an include is specified. Set to NO to disable this. 

   725 ' defval='1'/>

   726   </group>

   727   <group name='Index' docs='configuration options related to the alphabetical class index'>

   728     <option type='bool' id='ALPHABETICAL_INDEX' docs='

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

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

   731 contains a lot of classes, structs, unions or interfaces. 

   732 ' defval='0'/>

   733     <option type='int' id='COLS_IN_ALPHA_INDEX' docs='

   734 If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 

   735 the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 

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

   737 ' minval='1' maxval='20' defval='5'/>

   738     <option type='list' id='IGNORE_PREFIX' format='string' docs='

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

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

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

   742 should be ignored while generating the index headers. 

   743 '>

   744     </option>

   745   </group>

   746   <group name='HTML' docs='configuration options related to the HTML output'>

   747     <option type='bool' id='GENERATE_HTML' docs='

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

   749 generate HTML output. 

   750 ' defval='1'/>

   751     <option type='string' id='HTML_OUTPUT' format='dir' docs='

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

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

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

   755 ' defval='html' depends='GENERATE_HTML'/>

   756     <option type='string' id='HTML_FILE_EXTENSION' format='string' docs='

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

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

   759 doxygen will generate files with .html extension. 

   760 ' defval='.html' depends='GENERATE_HTML'/>

   761     <option type='string' id='HTML_HEADER' format='file' docs='

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

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

   764 standard header. 

   765 ' defval='' depends='GENERATE_HTML'/>

   766     <option type='string' id='HTML_FOOTER' format='file' docs='

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

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

   769 standard footer. 

   770 ' defval='' depends='GENERATE_HTML'/>

   771     <option type='string' id='HTML_STYLESHEET' format='file' docs='

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

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

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

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

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

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

   778 ' defval='' depends='GENERATE_HTML'/>

   779     <option type='bool' id='HTML_TIMESTAMP' docs='

   780 If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 

   781 page will contain the date and time when the page was generated. Setting 

   782 this to NO can help when comparing the output of multiple runs.

   783 ' defval='0' depends='GENERATE_HTML'/>

   784     <option type='bool' id='HTML_ALIGN_MEMBERS' docs='

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

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

   787 NO a bullet list will be used. 

   788 ' defval='1' depends='GENERATE_HTML'/>

   789     <option type='bool' id='HTML_DYNAMIC_SECTIONS' docs='

   790 If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 

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

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

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

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

   795 ' defval='0' depends='GENERATE_HTML'/>

   796     <option type='bool' id='GENERATE_DOCSET' docs='

   797 If the GENERATE_DOCSET tag is set to YES, additional index files 

   798 will be generated that can be used as input for Apple's Xcode 3 

   799 integrated development environment, introduced with OSX 10.5 (Leopard). 

   800 To create a documentation set, doxygen will generate a Makefile in the 

   801 HTML output directory. Running make will produce the docset in that 

   802 directory and running "make install" will install the docset in 

   803 ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 

   804 it at startup. 

   805 See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. 

   806 ' defval='0' depends='GENERATE_HTML'/>

   807     <option type='string' id='DOCSET_FEEDNAME' format='string' docs='

   808 When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 

   809 feed. A documentation feed provides an umbrella under which multiple 

   810 documentation sets from a single provider (such as a company or product suite) 

   811 can be grouped. 

   812 ' defval='Doxygen generated docs' depends='GENERATE_DOCSET'/>

   813     <option type='string' id='DOCSET_BUNDLE_ID' format='string' docs='

   814 When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 

   815 should uniquely identify the documentation set bundle. This should be a 

   816 reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 

   817 will append .docset to the name. 

   818 ' defval='org.doxygen.Project' depends='GENERATE_DOCSET'/>

   819     <option type='bool' id='GENERATE_HTMLHELP' docs='

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

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

   822 Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 

   823 of the generated HTML documentation. 

   824 ' defval='0' depends='GENERATE_HTML'/>

   825     <option type='string' id='CHM_FILE' format='file' docs='

   826 If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 

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

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

   829 written to the html output directory. 

   830 ' defval='' depends='GENERATE_HTMLHELP'/>

   831     <option type='string' id='HHC_LOCATION' format='file' docs='

   832 If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 

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

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

   835 the HTML help compiler on the generated index.hhp. 

   836 ' defval='' depends='GENERATE_HTMLHELP' abspath='1'/>

   837     <option type='bool' id='GENERATE_CHI' docs='

   838 If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 

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

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

   841 ' defval='0' depends='GENERATE_HTMLHELP'/>

   842     <option type='string' id='CHM_INDEX_ENCODING' format='string' docs='

   843 If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 

   844 is used to encode HtmlHelp index (hhk), content (hhc) and project file 

   845 content. 

   846 ' defval='' depends='GENERATE_HTMLHELP'/>

   847     <option type='bool' id='BINARY_TOC' docs='

   848 If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 

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

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

   851 ' defval='0' depends='GENERATE_HTMLHELP'/>

   852     <option type='bool' id='TOC_EXPAND' docs='

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

   854 to the contents of the HTML help documentation and to the tree view. 

   855 ' defval='0' depends='GENERATE_HTMLHELP'/>

   856     <option type='bool' id='GENERATE_QHP' docs='

   857 If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER 

   858 are set, an additional index file will be generated that can be used as input for 

   859 Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated 

   860 HTML documentation. 

   861 ' defval='0' depends='GENERATE_HTML'/>

   862     <option type='string' id='QCH_FILE' format='file' docs='

   863 If the QHG_LOCATION tag is specified, the QCH_FILE tag can 

   864 be used to specify the file name of the resulting .qch file. 

   865 The path specified is relative to the HTML output folder. 

   866 ' defval='' depends='GENERATE_QHP'/>

   867     <option type='string' id='QHP_NAMESPACE' format='string' docs='

   868 The QHP_NAMESPACE tag specifies the namespace to use when generating 

   869 Qt Help Project output. For more information please see 

   870 http://doc.trolltech.com/qthelpproject.html#namespace 

   871 ' defval='org.doxygen.Project' depends='GENERATE_QHP'/>

   872     <option type='string' id='QHP_VIRTUAL_FOLDER' format='string' docs='

   873 The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 

   874 Qt Help Project output. For more information please see 

   875 http://doc.trolltech.com/qthelpproject.html#virtual-folders 

   876 ' defval='doc' depends='GENERATE_QHP'/>

   877     <option type='string' id='QHP_CUST_FILTER_NAME' format='string' docs='

   878 If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. 

   879 For more information please see 

   880 http://doc.trolltech.com/qthelpproject.html#custom-filters 

   881 ' defval='' depends='GENERATE_QHP'/>

   882     <option type='string' id='QHP_CUST_FILTER_ATTRS' format='string' docs='

   883 The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see 

   884 <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>. 

   885 ' defval='' depends='GENERATE_QHP'/>

   886     <option type='string' id='QHP_SECT_FILTER_ATTRS' format='string' docs='

   887 The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's 

   888 filter section matches. 

   889 <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>. 

   890 ' defval='' depends='GENERATE_QHP'/>

   891     <option type='string' id='QHG_LOCATION' format='file' docs='

   892 If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 

   893 be used to specify the location of Qt's qhelpgenerator. 

   894 If non-empty doxygen will try to run qhelpgenerator on the generated 

   895 .qhp file. 

   896 ' defval='' depends='GENERATE_QHP'/>

   897     <option type='bool' id='GENERATE_ECLIPSEHELP' docs='

   898 If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files  

   899 will be generated, which together with the HTML files, form an Eclipse help  

   900 plugin. To install this plugin and make it available under the help contents 

   901 menu in Eclipse, the contents of the directory containing the HTML and XML 

   902 files needs to be copied into the plugins directory of eclipse. The name of 

   903 the directory within the plugins directory should be the same as 

   904 the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before

   905 the help appears.

   906 ' defval='0' depends='GENERATE_HTML'/>

   907     <option type='string' id='ECLIPSE_DOC_ID' docs='

   908 A unique identifier for the eclipse help plugin. When installing the plugin 

   909 the directory name containing the HTML and XML files should also have 

   910 this name.

   911 ' defval='org.doxygen.Project' depends='GENERATE_ECLIPSEHELP'/>

   912     <option type='bool' id='DISABLE_INDEX' docs='

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

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

   915 the value YES disables it. 

   916 ' defval='0' depends='GENERATE_HTML'/>

   917     <option type='int' id='ENUM_VALUES_PER_LINE' docs='

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

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

   920 ' minval='1' maxval='20' defval='4' depends='GENERATE_HTML'/>

   921     <option type='bool' id='GENERATE_TREEVIEW' defval='0' docs='

   922 The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 

   923 structure should be generated to display hierarchical information. 

   924 If the tag value is set to YES, a side panel will be generated 

   925 containing a tree-like index structure (just like the one that 

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

   927 JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 

   928 Windows users are probably better off using the HTML help feature.

   929 ' depends='GENERATE_HTML'/>

   930     <option type='bool' id='USE_INLINE_TREES' defval='0' docs='

   931 By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 

   932 and Class Hierarchy pages using a tree view instead of an ordered list.

   933 ' depends='GENERATE_HTML'/>

   934     <option type='int' id='TREEVIEW_WIDTH' docs='

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

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

   937 is shown. 

   938 ' minval='0' maxval='1500' defval='250' depends='GENERATE_HTML'/>

   939     <option type='int' id='FORMULA_FONTSIZE' docs='

   940 Use this tag to change the font size of Latex formulas included 

   941 as images in the HTML documentation. The default is 10. Note that 

   942 when you change the font size after a successful doxygen run you need 

   943 to manually remove any form_*.png images from the HTML output directory 

   944 to force them to be regenerated. 

   945 ' minval='8' maxval='50' defval='10' depends='GENERATE_HTML'/>

   946     <option type='bool' id='SEARCHENGINE' docs='

   947 When the SEARCHENGINE tag is enabled doxygen will generate a search box

   948 for the HTML output. The underlying search engine uses javascript 

   949 and DHTML and should work on any modern browser. Note that when using

   950 HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets

   951 (GENERATE_DOCSET) there is already a search function so this one should 

   952 typically be disabled. For large projects the javascript based search engine 

   953 can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.

   954 ' defval='1' depends='GENERATE_HTML'/>

   955     <option type='bool' id='SERVER_BASED_SEARCH' docs='

   956 When the SERVER_BASED_SEARCH tag is enabled the search engine will be

   957 implemented using a PHP enabled web server instead of at the web client

   958 using Javascript. Doxygen will generate the search PHP script and index 

   959 file to put on the web server. The advantage of the server

   960 based approach is that it scales better to large projects and allows

   961 full text search. The disadvances is that it is more difficult to setup 

   962 and does not have live searching capabilities.

   963 ' defval='0' depends='SEARCHENGINE'/>

   964   </group>

   965   <group name='LaTeX' docs='configuration options related to the LaTeX output'>

   966     <option type='bool' id='GENERATE_LATEX' docs='

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

   968 generate Latex output. 

   969 ' defval='1'/>

   970     <option type='string' id='LATEX_OUTPUT' format='dir' docs='

   971 The LATEX_OUTPUT tag is used to specify where the LaTeX docs 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 `latex' will be used as the default path. 

   974 ' defval='latex' depends='GENERATE_LATEX'/>

   975     <option type='string' id='LATEX_CMD_NAME' format='file' docs='

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

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

   978 Note that when enabling USE_PDFLATEX this option is only used for 

   979 generating bitmaps for formulas in the HTML output, but not in the 

   980 Makefile that is written to the output directory.

   981 ' defval='latex' depends='GENERATE_LATEX'/>

   982     <option type='string' id='MAKEINDEX_CMD_NAME' format='file' docs='

   983 The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 

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

   985 default command name. 

   986 ' defval='makeindex' depends='GENERATE_LATEX'/>

   987     <option type='bool' id='COMPACT_LATEX' docs='

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

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

   990 save some trees in general. 

   991 ' defval='0' depends='GENERATE_LATEX'/>

   992     <option type='enum' id='PAPER_TYPE' defval='a4wide' docs='

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

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

   995 executive. If left blank a4wide will be used. 

   996 ' depends='GENERATE_LATEX'>

   997       <value name='a4'/>

   998       <value name='a4wide'/>

   999       <value name='letter'/>

  1000       <value name='legal'/>

  1001       <value name='executive'/>

  1002     </option>

  1003     <option type='list' id='EXTRA_PACKAGES' format='string' docs='

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

  1005 packages that should be included in the LaTeX output. 

  1006 ' depends='GENERATE_LATEX'>

  1007     </option>

  1008     <option type='string' id='LATEX_HEADER' format='file' docs='

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

  1010 the generated latex document. The header should contain everything until 

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

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

  1013 ' defval='' depends='GENERATE_LATEX'/>

  1014     <option type='bool' id='PDF_HYPERLINKS' docs='

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

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

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

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

  1019 ' defval='1' depends='GENERATE_LATEX'/>

  1020     <option type='bool' id='USE_PDFLATEX' docs='

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

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

  1023 higher quality PDF documentation. 

  1024 ' defval='1' depends='GENERATE_LATEX'/>

  1025     <option type='bool' id='LATEX_BATCHMODE' docs='

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

  1027 command to the generated LaTeX files. This will instruct LaTeX to keep 

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

  1029 This option is also used when generating formulas in HTML. 

  1030 ' defval='0' depends='GENERATE_LATEX'/>

  1031     <option type='bool' id='LATEX_HIDE_INDICES' docs='

  1032 If LATEX_HIDE_INDICES is set to YES then doxygen will not 

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

  1034 in the output. 

  1035 ' defval='0' depends='GENERATE_LATEX'/>

  1036     <option type='bool' id='LATEX_SOURCE_CODE' docs='

  1037 If LATEX_SOURCE_CODE is set to YES then doxygen will include

  1038 source code with syntax highlighting in the LaTeX output.

  1039 Note that which sources are shown also depends on other settings

  1040 such as SOURCE_BROWSER.

  1041 ' defval='0' depends='GENERATE_LATEX'/>

  1042   </group>

  1043   <group name='RTF' docs='configuration options related to the RTF output'>

  1044     <option type='bool' id='GENERATE_RTF' docs='

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

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

  1047 other RTF readers or editors. 

  1048 ' defval='0'/>

  1049     <option type='string' id='RTF_OUTPUT' format='dir' docs='

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

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

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

  1053 ' defval='rtf' depends='GENERATE_RTF'/>

  1054     <option type='bool' id='COMPACT_RTF' docs='

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

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

  1057 save some trees in general. 

  1058 ' defval='0' depends='GENERATE_RTF'/>

  1059     <option type='bool' id='RTF_HYPERLINKS' docs='

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

  1061 will contain hyperlink fields. The RTF file will 

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

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

  1064 programs which support those fields. 

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

  1066 ' defval='0' depends='GENERATE_RTF'/>

  1067     <option type='string' id='RTF_STYLESHEET_FILE' format='file' docs='

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

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

  1070 replacements, missing definitions are set to their default value. 

  1071 ' defval='' depends='GENERATE_RTF'/>

  1072     <option type='string' id='RTF_EXTENSIONS_FILE' format='file' docs='

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

  1074 Syntax is similar to doxygen's config file. 

  1075 ' defval='' depends='GENERATE_RTF'/>

  1076   </group>

  1077   <group name='Man' docs='configuration options related to the man page output'>

  1078     <option type='bool' id='GENERATE_MAN' docs='

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

  1080 generate man pages 

  1081 ' defval='0'/>

  1082     <option type='string' id='MAN_OUTPUT' format='dir' docs='

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

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

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

  1086 ' defval='man' depends='GENERATE_MAN'/>

  1087     <option type='string' id='MAN_EXTENSION' format='string' docs='

  1088 The MAN_EXTENSION tag determines the extension that is added to 

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

  1090 ' defval='.3' depends='GENERATE_MAN'/>

  1091     <option type='bool' id='MAN_LINKS' docs='

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

  1093 then it will generate one additional man file for each entity 

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

  1095 only source the real man page, but without them the man command 

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

  1097 ' defval='0' depends='GENERATE_MAN'/>

  1098   </group>

  1099   <group name='XML' docs='configuration options related to the XML output'>

  1100     <option type='bool' id='GENERATE_XML' docs='

  1101 If the GENERATE_XML tag is set to YES Doxygen will 

  1102 generate an XML file that captures the structure of 

  1103 the code including all documentation. 

  1104 ' defval='0'/>

  1105     <option type='string' id='XML_OUTPUT' format='dir' docs='

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

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

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

  1109 ' defval='xml' depends='GENERATE_XML'/>

  1110     <option type='string' id='XML_SCHEMA' format='string' docs='

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

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

  1113 syntax of the XML files. 

  1114 ' defval='' depends='GENERATE_XML'/>

  1115     <option type='string' id='XML_DTD' format='string' docs='

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

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

  1118 syntax of the XML files. 

  1119 ' defval='' depends='GENERATE_XML'/>

  1120     <option type='bool' id='XML_PROGRAMLISTING' docs='

  1121 If the XML_PROGRAMLISTING tag is set to YES Doxygen will 

  1122 dump the program listings (including syntax highlighting 

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

  1124 enabling this will significantly increase the size of the XML output. 

  1125 ' defval='1' depends='GENERATE_XML'/>

  1126   </group>

  1127   <group name='DITA' docs='configuration options related to DITA XML output'>

  1128     <option type='bool' id='GENERATE_XML_DITA' docs='

  1129 If the GENERATE_XML_DITA tag is set to YES Doxygen will 

  1130 generate DITA XML files that captures the structure of 

  1131 the code including all documentation. 

  1132 See: http://www.oasis-open.org/committees/dita/

  1133 ' defval='0'/>

  1134     <option type='string' id='XML_DITA_OUTPUT' format='dir' docs='