<doxygenconfig>

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

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

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

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

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

iconv built into libc) for the transcoding. See 

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

' defval='UTF-8'/>

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

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

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

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

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

This could be handy for archiving the generated documentation or 

if some version control system is used. 

' defval=''/>

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

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

base path where the generated documentation will be put. 

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

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

' defval=''/>

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

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

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

format and will distribute the generated files over these directories. 

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

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

otherwise cause performance problems for the file system. 

' defval='0'/>

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

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

documentation generated by doxygen is written. Doxygen will use this 

information to generate all constant output in the proper language. 

The default language is English, other supported languages are: 

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

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

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

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

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

Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 

'>

      <value name='Afrikaans'/>

      <value name='Arabic'/>

      <value name='Brazilian'/>

      <value name='Catalan'/>

      <value name='Chinese'/>

      <value name='Chinese-Traditional'/>

      <value name='Croatian'/>

      <value name='Czech'/>

      <value name='Danish'/>

      <value name='Dutch'/>

      <value name='English'/>

      <value name='Esperanto'/>

      <value name='Farsi'/>

      <value name='Finnish'/>

      <value name='French'/>

      <value name='German'/>

      <value name='Greek'/>

      <value name='Hungarian'/>

      <value name='Italian'/>

      <value name='Japanese'/>

      <value name='Japanese-en'/>

      <value name='Korean'/>

      <value name='Korean-en'/>

      <value name='Norwegian'/>

      <value name='Macedonian'/>

      <value name='Persian'/>

      <value name='Polish'/>

      <value name='Portuguese'/>

      <value name='Romanian'/>

      <value name='Russian'/>

      <value name='Serbian'/>

      <value name='Slovak'/>

      <value name='Slovene'/>

      <value name='Spanish'/>

      <value name='Swedish'/>

      <value name='Turkish'/>

      <value name='Ukrainian'/>

      <value name='Vietnamese'/>

    </option>

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

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

include brief member descriptions after the members that are listed in 

the file and class documentation (similar to JavaDoc). 

Set to NO to disable this. 

' defval='1'/>

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

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

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

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

brief descriptions will be completely suppressed. 

' defval='1'/>

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

This tag implements a quasi-intelligent brief description abbreviator 

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

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

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

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

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

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

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

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

'>

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

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

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

      <value name='is'/>

      <value name='provides'/>

      <value name='specifies'/>

      <value name='contains'/>

      <value name='represents'/>

      <value name='a'/>

      <value name='an'/>

      <value name='the'/>

    </option>

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

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

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

description. 

' defval='0'/>

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

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

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

members were ordinary class members. Constructors, destructors and assignment 

operators of the base classes will not be shown. 

' defval='0'/>

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

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

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

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

' defval='1'/>

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

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

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

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

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

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

path to strip. 

' depends='FULL_PATH_NAMES'>

      <value name=''/>

    </option>

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

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

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

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

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

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

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

'>

    </option>

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

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

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

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

' defval='0'/>

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

If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 

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

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

comments will behave just like regular Qt-style comments 

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

' defval='0'/>

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

If the QT_AUTOBRIEF tag is set to YES then Doxygen will 

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

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

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

an explicit \brief command for a brief description.) 

' defval='0'/>

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

The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 

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

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

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

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

' defval='0'/>

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

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

member inherits the documentation from any documented member that it 

re-implements. 

' defval='1'/>

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

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

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

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

' defval='0'/>

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

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

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

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

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

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

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

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

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

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

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

'>

    </option>

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

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

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

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

of all members will be omitted, etc. 

' defval='0'/>

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

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

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

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

scopes will look different, etc. 

' defval='0'/>

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

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

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

Fortran. 

' defval='0'/>

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

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

sources. Doxygen will then generate output that is tailored for 

VHDL. 

' defval='0'/>

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

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

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

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

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

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

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

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

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

FILE_PATTERNS otherwise the files are not read by doxygen.

'>

    </option>

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

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

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

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

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

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

diagrams that involve STL classes more complete and accurate. 

' defval='0'/>

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

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

enable parsing support. 

' defval='0'/>

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

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

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

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

' defval='0'/>

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

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

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

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

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

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

methods anyway, you should set this option to NO. 

' defval='1'/>

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

If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 

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

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

all members of a group must be documented explicitly. 

' defval='0'/>

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

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

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

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

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

the \nosubgrouping command. 

' defval='1'/>

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

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

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

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

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

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

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

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

' defval='0'/>

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

The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 

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

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

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

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

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

causing a significant performance penality. 

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

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

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

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

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

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

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

  </group>

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

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

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

documentation are documented, even if no documentation was available. 

Private class members and static file members will be hidden unless 

the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 

' defval='0'/>

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

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

will be included in the documentation. 

' defval='0'/>

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

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

will be included in the documentation. 

' defval='0'/>

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

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

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

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

' defval='1'/>

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

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

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

the interface are included in the documentation. 

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

' defval='0'/>

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

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

extracted and appear in the documentation as a namespace called 

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

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

anonymous namespace are hidden. 

' defval='0'/>

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

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

undocumented members of documented classes, files or namespaces. 

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

various overviews, but no documentation section is generated. 

This option has no effect if EXTRACT_ALL is enabled. 

' defval='0'/>

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

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

undocumented classes that are normally visible in the class hierarchy. 

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

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

' defval='0'/>

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

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

friend (class|struct|union) declarations. 

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

documentation. 

' defval='0'/>

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

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

documentation blocks found inside the body of a function. 

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

function's detailed documentation block. 

' defval='0'/>

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

The INTERNAL_DOCS tag determines if documentation 

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

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

Set it to YES to include the internal documentation. 

' defval='0'/>

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

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

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

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

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

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

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

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

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

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

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

' defval='0'/>

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

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

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

of that file. 

' defval='1'/>

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

If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 

will list include files with double quotes in the documentation 

rather than with sharp brackets.

' defval='0'/>

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

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

is inserted in the documentation for inline members. 

' defval='1'/>

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

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

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

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

declaration order. 

' defval='1'/>

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

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

brief documentation of file, namespace and class members alphabetically 

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

declaration order. 

' defval='0'/>

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

If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen

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

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

the constructors will appear in the respective orders defined by

SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.

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

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

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

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

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

the group names will appear in their defined order. 

' defval='0'/>

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

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

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

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

not including the namespace part. 

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

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

alphabetical list. 

' defval='0'/>

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

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

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

commands in the documentation. 

' defval='1'/>

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

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

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

commands in the documentation. 

' defval='1'/>

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

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

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

commands in the documentation. 

' defval='1'/>

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

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

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

\deprecated commands in the documentation. 

' defval='1'/>

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

The ENABLED_SECTIONS tag can be used to enable conditional 

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

'>

    </option>

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

The MAX_INITIALIZER_LINES tag determines the maximum number of lines 

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

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

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

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

documentation can be controlled using \showinitializer or \hideinitializer 

command in the documentation regardless of this setting. 

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

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

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

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

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

' defval='1'/>

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

If the sources in your project are distributed over multiple directories 

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

in the documentation. The default is NO. 

' defval='0'/>

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

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

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

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

' defval='1'/>

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

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

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

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

' defval='1'/>

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

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

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

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

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

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

provided by doxygen. Whatever the program writes to standard output 

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

' defval=''/>

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

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

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

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

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

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

of the layout file. 

' defval=''/>

  </group>

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

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

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

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

' defval='0'/>

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

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

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

NO is used. 

' defval='1'/>

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

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

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

automatically be disabled. 

' defval='1'/>

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

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

potential errors in the documentation, such as not documenting some 

parameters in a documented function, or documenting parameters that 

don't exist or using markup commands wrongly. 

' defval='1'/>

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

This WARN_NO_PARAMDOC option can be abled to get warnings for 

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

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

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

documentation.