mbed TLS upgraded to 2.6.0

Fork of mbedtls by Mark Radbourne

Committer:
Jasper Wallace
Date:
Fri Sep 29 19:50:30 2017 +0100
Revision:
2:bbdeda018a3c
Parent:
1:9ebc941037d5
Update to mbedtls 2.6.0, many changes.

Changes to mbedtls sources made:

in include/mbedtls/config.h comment out:

#define MBEDTLS_FS_IO
#define MBEDTLS_NET_C
#define MBEDTLS_TIMING_C

uncomment:

#define MBEDTLS_NO_PLATFORM_ENTROPY

remove the following directorys:

programs
yotta
visualc

Who changed what in which revision?

UserRevisionLine numberNew contents of line
markrad 0:cdf462088d13 1 # Doxyfile 1.8.4
markrad 0:cdf462088d13 2
markrad 0:cdf462088d13 3 # This file describes the settings to be used by the documentation system
markrad 0:cdf462088d13 4 # doxygen (www.doxygen.org) for a project.
markrad 0:cdf462088d13 5 #
markrad 0:cdf462088d13 6 # All text after a double hash (##) is considered a comment and is placed
markrad 0:cdf462088d13 7 # in front of the TAG it is preceding .
markrad 0:cdf462088d13 8 # All text after a hash (#) is considered a comment and will be ignored.
markrad 0:cdf462088d13 9 # The format is:
markrad 0:cdf462088d13 10 # TAG = value [value, ...]
markrad 0:cdf462088d13 11 # For lists items can also be appended using:
markrad 0:cdf462088d13 12 # TAG += value [value, ...]
markrad 0:cdf462088d13 13 # Values that contain spaces should be placed between quotes (" ").
markrad 0:cdf462088d13 14
markrad 0:cdf462088d13 15 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 16 # Project related configuration options
markrad 0:cdf462088d13 17 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 18
markrad 0:cdf462088d13 19 # This tag specifies the encoding used for all characters in the config file
markrad 0:cdf462088d13 20 # that follow. The default is UTF-8 which is also the encoding used for all
markrad 0:cdf462088d13 21 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
markrad 0:cdf462088d13 22 # iconv built into libc) for the transcoding. See
markrad 0:cdf462088d13 23 # http://www.gnu.org/software/libiconv for the list of possible encodings.
markrad 0:cdf462088d13 24
markrad 0:cdf462088d13 25 DOXYFILE_ENCODING = UTF-8
markrad 0:cdf462088d13 26
markrad 0:cdf462088d13 27 # The PROJECT_NAME tag is a single word (or sequence of words) that should
markrad 0:cdf462088d13 28 # identify the project. Note that if you do not use Doxywizard you need
markrad 0:cdf462088d13 29 # to put quotes around the project name if it contains spaces.
markrad 0:cdf462088d13 30
Jasper Wallace 2:bbdeda018a3c 31 PROJECT_NAME = "mbed TLS v2.6.0"
markrad 0:cdf462088d13 32
markrad 0:cdf462088d13 33 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
markrad 0:cdf462088d13 34 # This could be handy for archiving the generated documentation or
markrad 0:cdf462088d13 35 # if some version control system is used.
markrad 0:cdf462088d13 36
markrad 0:cdf462088d13 37 PROJECT_NUMBER =
markrad 0:cdf462088d13 38
markrad 0:cdf462088d13 39 # Using the PROJECT_BRIEF tag one can provide an optional one line description
markrad 0:cdf462088d13 40 # for a project that appears at the top of each page and should give viewer
markrad 0:cdf462088d13 41 # a quick idea about the purpose of the project. Keep the description short.
markrad 0:cdf462088d13 42
markrad 0:cdf462088d13 43 PROJECT_BRIEF =
markrad 0:cdf462088d13 44
markrad 0:cdf462088d13 45 # With the PROJECT_LOGO tag one can specify an logo or icon that is
markrad 0:cdf462088d13 46 # included in the documentation. The maximum height of the logo should not
markrad 0:cdf462088d13 47 # exceed 55 pixels and the maximum width should not exceed 200 pixels.
markrad 0:cdf462088d13 48 # Doxygen will copy the logo to the output directory.
markrad 0:cdf462088d13 49
markrad 0:cdf462088d13 50 PROJECT_LOGO =
markrad 0:cdf462088d13 51
markrad 0:cdf462088d13 52 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
markrad 0:cdf462088d13 53 # base path where the generated documentation will be put.
markrad 0:cdf462088d13 54 # If a relative path is entered, it will be relative to the location
markrad 0:cdf462088d13 55 # where doxygen was started. If left blank the current directory will be used.
markrad 0:cdf462088d13 56
markrad 0:cdf462088d13 57 OUTPUT_DIRECTORY = apidoc/
markrad 0:cdf462088d13 58
markrad 0:cdf462088d13 59 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
markrad 0:cdf462088d13 60 # 4096 sub-directories (in 2 levels) under the output directory of each output
markrad 0:cdf462088d13 61 # format and will distribute the generated files over these directories.
markrad 0:cdf462088d13 62 # Enabling this option can be useful when feeding doxygen a huge amount of
markrad 0:cdf462088d13 63 # source files, where putting all generated files in the same directory would
markrad 0:cdf462088d13 64 # otherwise cause performance problems for the file system.
markrad 0:cdf462088d13 65
markrad 0:cdf462088d13 66 CREATE_SUBDIRS = NO
markrad 0:cdf462088d13 67
markrad 0:cdf462088d13 68 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
markrad 0:cdf462088d13 69 # documentation generated by doxygen is written. Doxygen will use this
markrad 0:cdf462088d13 70 # information to generate all constant output in the proper language.
markrad 0:cdf462088d13 71 # The default language is English, other supported languages are:
markrad 0:cdf462088d13 72 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
markrad 0:cdf462088d13 73 # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
markrad 0:cdf462088d13 74 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
markrad 0:cdf462088d13 75 # messages), Korean, Korean-en, Latvian, Lithuanian, Norwegian, Macedonian,
markrad 0:cdf462088d13 76 # Persian, Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic,
markrad 0:cdf462088d13 77 # Slovak, Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
markrad 0:cdf462088d13 78
markrad 0:cdf462088d13 79 OUTPUT_LANGUAGE = English
markrad 0:cdf462088d13 80
markrad 0:cdf462088d13 81 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 82 # include brief member descriptions after the members that are listed in
markrad 0:cdf462088d13 83 # the file and class documentation (similar to JavaDoc).
markrad 0:cdf462088d13 84 # Set to NO to disable this.
markrad 0:cdf462088d13 85
markrad 0:cdf462088d13 86 BRIEF_MEMBER_DESC = YES
markrad 0:cdf462088d13 87
markrad 0:cdf462088d13 88 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
markrad 0:cdf462088d13 89 # the brief description of a member or function before the detailed description.
markrad 0:cdf462088d13 90 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
markrad 0:cdf462088d13 91 # brief descriptions will be completely suppressed.
markrad 0:cdf462088d13 92
markrad 0:cdf462088d13 93 REPEAT_BRIEF = YES
markrad 0:cdf462088d13 94
markrad 0:cdf462088d13 95 # This tag implements a quasi-intelligent brief description abbreviator
markrad 0:cdf462088d13 96 # that is used to form the text in various listings. Each string
markrad 0:cdf462088d13 97 # in this list, if found as the leading text of the brief description, will be
markrad 0:cdf462088d13 98 # stripped from the text and the result after processing the whole list, is
markrad 0:cdf462088d13 99 # used as the annotated text. Otherwise, the brief description is used as-is.
markrad 0:cdf462088d13 100 # If left blank, the following values are used ("$name" is automatically
markrad 0:cdf462088d13 101 # replaced with the name of the entity): "The $name class" "The $name widget"
markrad 0:cdf462088d13 102 # "The $name file" "is" "provides" "specifies" "contains"
markrad 0:cdf462088d13 103 # "represents" "a" "an" "the"
markrad 0:cdf462088d13 104
markrad 0:cdf462088d13 105 ABBREVIATE_BRIEF = "The $name class" \
markrad 0:cdf462088d13 106 "The $name widget" \
markrad 0:cdf462088d13 107 "The $name file" \
markrad 0:cdf462088d13 108 is \
markrad 0:cdf462088d13 109 provides \
markrad 0:cdf462088d13 110 specifies \
markrad 0:cdf462088d13 111 contains \
markrad 0:cdf462088d13 112 represents \
markrad 0:cdf462088d13 113 a \
markrad 0:cdf462088d13 114 an \
markrad 0:cdf462088d13 115 the
markrad 0:cdf462088d13 116
markrad 0:cdf462088d13 117 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
markrad 0:cdf462088d13 118 # Doxygen will generate a detailed section even if there is only a brief
markrad 0:cdf462088d13 119 # description.
markrad 0:cdf462088d13 120
markrad 0:cdf462088d13 121 ALWAYS_DETAILED_SEC = NO
markrad 0:cdf462088d13 122
markrad 0:cdf462088d13 123 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
markrad 0:cdf462088d13 124 # inherited members of a class in the documentation of that class as if those
markrad 0:cdf462088d13 125 # members were ordinary class members. Constructors, destructors and assignment
markrad 0:cdf462088d13 126 # operators of the base classes will not be shown.
markrad 0:cdf462088d13 127
markrad 0:cdf462088d13 128 INLINE_INHERITED_MEMB = NO
markrad 0:cdf462088d13 129
markrad 0:cdf462088d13 130 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
markrad 0:cdf462088d13 131 # path before files name in the file list and in the header files. If set
markrad 0:cdf462088d13 132 # to NO the shortest path that makes the file name unique will be used.
markrad 0:cdf462088d13 133
markrad 0:cdf462088d13 134 FULL_PATH_NAMES = NO
markrad 0:cdf462088d13 135
markrad 0:cdf462088d13 136 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
markrad 0:cdf462088d13 137 # can be used to strip a user-defined part of the path. Stripping is
markrad 0:cdf462088d13 138 # only done if one of the specified strings matches the left-hand part of
markrad 0:cdf462088d13 139 # the path. The tag can be used to show relative paths in the file list.
markrad 0:cdf462088d13 140 # If left blank the directory from which doxygen is run is used as the
markrad 0:cdf462088d13 141 # path to strip. Note that you specify absolute paths here, but also
markrad 0:cdf462088d13 142 # relative paths, which will be relative from the directory where doxygen is
markrad 0:cdf462088d13 143 # started.
markrad 0:cdf462088d13 144
markrad 0:cdf462088d13 145 STRIP_FROM_PATH =
markrad 0:cdf462088d13 146
markrad 0:cdf462088d13 147 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
markrad 0:cdf462088d13 148 # the path mentioned in the documentation of a class, which tells
markrad 0:cdf462088d13 149 # the reader which header file to include in order to use a class.
markrad 0:cdf462088d13 150 # If left blank only the name of the header file containing the class
markrad 0:cdf462088d13 151 # definition is used. Otherwise one should specify the include paths that
markrad 0:cdf462088d13 152 # are normally passed to the compiler using the -I flag.
markrad 0:cdf462088d13 153
markrad 0:cdf462088d13 154 STRIP_FROM_INC_PATH =
markrad 0:cdf462088d13 155
markrad 0:cdf462088d13 156 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
markrad 0:cdf462088d13 157 # (but less readable) file names. This can be useful if your file system
markrad 0:cdf462088d13 158 # doesn't support long names like on DOS, Mac, or CD-ROM.
markrad 0:cdf462088d13 159
markrad 0:cdf462088d13 160 SHORT_NAMES = NO
markrad 0:cdf462088d13 161
markrad 0:cdf462088d13 162 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
markrad 0:cdf462088d13 163 # will interpret the first line (until the first dot) of a JavaDoc-style
markrad 0:cdf462088d13 164 # comment as the brief description. If set to NO, the JavaDoc
markrad 0:cdf462088d13 165 # comments will behave just like regular Qt-style comments
markrad 0:cdf462088d13 166 # (thus requiring an explicit @brief command for a brief description.)
markrad 0:cdf462088d13 167
markrad 0:cdf462088d13 168 JAVADOC_AUTOBRIEF = YES
markrad 0:cdf462088d13 169
markrad 0:cdf462088d13 170 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
markrad 0:cdf462088d13 171 # interpret the first line (until the first dot) of a Qt-style
markrad 0:cdf462088d13 172 # comment as the brief description. If set to NO, the comments
markrad 0:cdf462088d13 173 # will behave just like regular Qt-style comments (thus requiring
markrad 0:cdf462088d13 174 # an explicit \brief command for a brief description.)
markrad 0:cdf462088d13 175
markrad 0:cdf462088d13 176 QT_AUTOBRIEF = NO
markrad 0:cdf462088d13 177
markrad 0:cdf462088d13 178 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
markrad 0:cdf462088d13 179 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
markrad 0:cdf462088d13 180 # comments) as a brief description. This used to be the default behaviour.
markrad 0:cdf462088d13 181 # The new default is to treat a multi-line C++ comment block as a detailed
markrad 0:cdf462088d13 182 # description. Set this tag to YES if you prefer the old behaviour instead.
markrad 0:cdf462088d13 183
markrad 0:cdf462088d13 184 MULTILINE_CPP_IS_BRIEF = NO
markrad 0:cdf462088d13 185
markrad 0:cdf462088d13 186 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
markrad 0:cdf462088d13 187 # member inherits the documentation from any documented member that it
markrad 0:cdf462088d13 188 # re-implements.
markrad 0:cdf462088d13 189
markrad 0:cdf462088d13 190 INHERIT_DOCS = YES
markrad 0:cdf462088d13 191
markrad 0:cdf462088d13 192 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
markrad 0:cdf462088d13 193 # a new page for each member. If set to NO, the documentation of a member will
markrad 0:cdf462088d13 194 # be part of the file/class/namespace that contains it.
markrad 0:cdf462088d13 195
markrad 0:cdf462088d13 196 SEPARATE_MEMBER_PAGES = NO
markrad 0:cdf462088d13 197
markrad 0:cdf462088d13 198 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
markrad 0:cdf462088d13 199 # Doxygen uses this value to replace tabs by spaces in code fragments.
markrad 0:cdf462088d13 200
markrad 0:cdf462088d13 201 TAB_SIZE = 8
markrad 0:cdf462088d13 202
markrad 0:cdf462088d13 203 # This tag can be used to specify a number of aliases that acts
markrad 0:cdf462088d13 204 # as commands in the documentation. An alias has the form "name=value".
markrad 0:cdf462088d13 205 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
markrad 0:cdf462088d13 206 # put the command \sideeffect (or @sideeffect) in the documentation, which
markrad 0:cdf462088d13 207 # will result in a user-defined paragraph with heading "Side Effects:".
markrad 0:cdf462088d13 208 # You can put \n's in the value part of an alias to insert newlines.
markrad 0:cdf462088d13 209
markrad 0:cdf462088d13 210 ALIASES =
markrad 0:cdf462088d13 211
markrad 0:cdf462088d13 212 # This tag can be used to specify a number of word-keyword mappings (TCL only).
markrad 0:cdf462088d13 213 # A mapping has the form "name=value". For example adding
markrad 0:cdf462088d13 214 # "class=itcl::class" will allow you to use the command class in the
markrad 0:cdf462088d13 215 # itcl::class meaning.
markrad 0:cdf462088d13 216
markrad 0:cdf462088d13 217 TCL_SUBST =
markrad 0:cdf462088d13 218
markrad 0:cdf462088d13 219 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
markrad 0:cdf462088d13 220 # sources only. Doxygen will then generate output that is more tailored for C.
markrad 0:cdf462088d13 221 # For instance, some of the names that are used will be different. The list
markrad 0:cdf462088d13 222 # of all members will be omitted, etc.
markrad 0:cdf462088d13 223
markrad 0:cdf462088d13 224 OPTIMIZE_OUTPUT_FOR_C = YES
markrad 0:cdf462088d13 225
markrad 0:cdf462088d13 226 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
markrad 0:cdf462088d13 227 # sources only. Doxygen will then generate output that is more tailored for
markrad 0:cdf462088d13 228 # Java. For instance, namespaces will be presented as packages, qualified
markrad 0:cdf462088d13 229 # scopes will look different, etc.
markrad 0:cdf462088d13 230
markrad 0:cdf462088d13 231 OPTIMIZE_OUTPUT_JAVA = NO
markrad 0:cdf462088d13 232
markrad 0:cdf462088d13 233 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
markrad 0:cdf462088d13 234 # sources only. Doxygen will then generate output that is more tailored for
markrad 0:cdf462088d13 235 # Fortran.
markrad 0:cdf462088d13 236
markrad 0:cdf462088d13 237 OPTIMIZE_FOR_FORTRAN = NO
markrad 0:cdf462088d13 238
markrad 0:cdf462088d13 239 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
markrad 0:cdf462088d13 240 # sources. Doxygen will then generate output that is tailored for
markrad 0:cdf462088d13 241 # VHDL.
markrad 0:cdf462088d13 242
markrad 0:cdf462088d13 243 OPTIMIZE_OUTPUT_VHDL = NO
markrad 0:cdf462088d13 244
markrad 0:cdf462088d13 245 # Doxygen selects the parser to use depending on the extension of the files it
markrad 0:cdf462088d13 246 # parses. With this tag you can assign which parser to use for a given
markrad 0:cdf462088d13 247 # extension. Doxygen has a built-in mapping, but you can override or extend it
markrad 0:cdf462088d13 248 # using this tag. The format is ext=language, where ext is a file extension,
markrad 0:cdf462088d13 249 # and language is one of the parsers supported by doxygen: IDL, Java,
markrad 0:cdf462088d13 250 # Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C,
markrad 0:cdf462088d13 251 # C++. For instance to make doxygen treat .inc files as Fortran files (default
markrad 0:cdf462088d13 252 # is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note
markrad 0:cdf462088d13 253 # that for custom extensions you also need to set FILE_PATTERNS otherwise the
markrad 0:cdf462088d13 254 # files are not read by doxygen.
markrad 0:cdf462088d13 255
markrad 0:cdf462088d13 256 EXTENSION_MAPPING =
markrad 0:cdf462088d13 257
markrad 0:cdf462088d13 258 # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all
markrad 0:cdf462088d13 259 # comments according to the Markdown format, which allows for more readable
markrad 0:cdf462088d13 260 # documentation. See http://daringfireball.net/projects/markdown/ for details.
markrad 0:cdf462088d13 261 # The output of markdown processing is further processed by doxygen, so you
markrad 0:cdf462088d13 262 # can mix doxygen, HTML, and XML commands with Markdown formatting.
markrad 0:cdf462088d13 263 # Disable only in case of backward compatibilities issues.
markrad 0:cdf462088d13 264
markrad 0:cdf462088d13 265 MARKDOWN_SUPPORT = YES
markrad 0:cdf462088d13 266
markrad 0:cdf462088d13 267 # When enabled doxygen tries to link words that correspond to documented
markrad 0:cdf462088d13 268 # classes, or namespaces to their corresponding documentation. Such a link can
markrad 0:cdf462088d13 269 # be prevented in individual cases by by putting a % sign in front of the word
markrad 0:cdf462088d13 270 # or globally by setting AUTOLINK_SUPPORT to NO.
markrad 0:cdf462088d13 271
markrad 0:cdf462088d13 272 AUTOLINK_SUPPORT = YES
markrad 0:cdf462088d13 273
markrad 0:cdf462088d13 274 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
markrad 0:cdf462088d13 275 # to include (a tag file for) the STL sources as input, then you should
markrad 0:cdf462088d13 276 # set this tag to YES in order to let doxygen match functions declarations and
markrad 0:cdf462088d13 277 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
markrad 0:cdf462088d13 278 # func(std::string) {}). This also makes the inheritance and collaboration
markrad 0:cdf462088d13 279 # diagrams that involve STL classes more complete and accurate.
markrad 0:cdf462088d13 280
markrad 0:cdf462088d13 281 BUILTIN_STL_SUPPORT = NO
markrad 0:cdf462088d13 282
markrad 0:cdf462088d13 283 # If you use Microsoft's C++/CLI language, you should set this option to YES to
markrad 0:cdf462088d13 284 # enable parsing support.
markrad 0:cdf462088d13 285
markrad 0:cdf462088d13 286 CPP_CLI_SUPPORT = NO
markrad 0:cdf462088d13 287
markrad 0:cdf462088d13 288 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
markrad 0:cdf462088d13 289 # Doxygen will parse them like normal C++ but will assume all classes use public
markrad 0:cdf462088d13 290 # instead of private inheritance when no explicit protection keyword is present.
markrad 0:cdf462088d13 291
markrad 0:cdf462088d13 292 SIP_SUPPORT = NO
markrad 0:cdf462088d13 293
markrad 0:cdf462088d13 294 # For Microsoft's IDL there are propget and propput attributes to indicate
markrad 0:cdf462088d13 295 # getter and setter methods for a property. Setting this option to YES (the
markrad 0:cdf462088d13 296 # default) will make doxygen replace the get and set methods by a property in
markrad 0:cdf462088d13 297 # the documentation. This will only work if the methods are indeed getting or
markrad 0:cdf462088d13 298 # setting a simple type. If this is not the case, or you want to show the
markrad 0:cdf462088d13 299 # methods anyway, you should set this option to NO.
markrad 0:cdf462088d13 300
markrad 0:cdf462088d13 301 IDL_PROPERTY_SUPPORT = YES
markrad 0:cdf462088d13 302
markrad 0:cdf462088d13 303 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
markrad 0:cdf462088d13 304 # tag is set to YES, then doxygen will reuse the documentation of the first
markrad 0:cdf462088d13 305 # member in the group (if any) for the other members of the group. By default
markrad 0:cdf462088d13 306 # all members of a group must be documented explicitly.
markrad 0:cdf462088d13 307
markrad 0:cdf462088d13 308 DISTRIBUTE_GROUP_DOC = NO
markrad 0:cdf462088d13 309
markrad 0:cdf462088d13 310 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
markrad 0:cdf462088d13 311 # the same type (for instance a group of public functions) to be put as a
markrad 0:cdf462088d13 312 # subgroup of that type (e.g. under the Public Functions section). Set it to
markrad 0:cdf462088d13 313 # NO to prevent subgrouping. Alternatively, this can be done per class using
markrad 0:cdf462088d13 314 # the \nosubgrouping command.
markrad 0:cdf462088d13 315
markrad 0:cdf462088d13 316 SUBGROUPING = YES
markrad 0:cdf462088d13 317
markrad 0:cdf462088d13 318 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
markrad 0:cdf462088d13 319 # unions are shown inside the group in which they are included (e.g. using
markrad 0:cdf462088d13 320 # @ingroup) instead of on a separate page (for HTML and Man pages) or
markrad 0:cdf462088d13 321 # section (for LaTeX and RTF).
markrad 0:cdf462088d13 322
markrad 0:cdf462088d13 323 INLINE_GROUPED_CLASSES = NO
markrad 0:cdf462088d13 324
markrad 0:cdf462088d13 325 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
markrad 0:cdf462088d13 326 # unions with only public data fields or simple typedef fields will be shown
markrad 0:cdf462088d13 327 # inline in the documentation of the scope in which they are defined (i.e. file,
markrad 0:cdf462088d13 328 # namespace, or group documentation), provided this scope is documented. If set
markrad 0:cdf462088d13 329 # to NO (the default), structs, classes, and unions are shown on a separate
markrad 0:cdf462088d13 330 # page (for HTML and Man pages) or section (for LaTeX and RTF).
markrad 0:cdf462088d13 331
markrad 0:cdf462088d13 332 INLINE_SIMPLE_STRUCTS = NO
markrad 0:cdf462088d13 333
markrad 0:cdf462088d13 334 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
markrad 0:cdf462088d13 335 # is documented as struct, union, or enum with the name of the typedef. So
markrad 0:cdf462088d13 336 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
markrad 0:cdf462088d13 337 # with name TypeT. When disabled the typedef will appear as a member of a file,
markrad 0:cdf462088d13 338 # namespace, or class. And the struct will be named TypeS. This can typically
markrad 0:cdf462088d13 339 # be useful for C code in case the coding convention dictates that all compound
markrad 0:cdf462088d13 340 # types are typedef'ed and only the typedef is referenced, never the tag name.
markrad 0:cdf462088d13 341
markrad 0:cdf462088d13 342 TYPEDEF_HIDES_STRUCT = NO
markrad 0:cdf462088d13 343
markrad 0:cdf462088d13 344 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
markrad 0:cdf462088d13 345 # cache is used to resolve symbols given their name and scope. Since this can
markrad 0:cdf462088d13 346 # be an expensive process and often the same symbol appear multiple times in
markrad 0:cdf462088d13 347 # the code, doxygen keeps a cache of pre-resolved symbols. If the cache is too
markrad 0:cdf462088d13 348 # small doxygen will become slower. If the cache is too large, memory is wasted.
markrad 0:cdf462088d13 349 # The cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid
markrad 0:cdf462088d13 350 # range is 0..9, the default is 0, corresponding to a cache size of 2^16 = 65536
markrad 0:cdf462088d13 351 # symbols.
markrad 0:cdf462088d13 352
markrad 0:cdf462088d13 353 LOOKUP_CACHE_SIZE = 0
markrad 0:cdf462088d13 354
markrad 0:cdf462088d13 355 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 356 # Build related configuration options
markrad 0:cdf462088d13 357 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 358
markrad 0:cdf462088d13 359 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
markrad 0:cdf462088d13 360 # documentation are documented, even if no documentation was available.
markrad 0:cdf462088d13 361 # Private class members and static file members will be hidden unless
markrad 0:cdf462088d13 362 # the EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES
markrad 0:cdf462088d13 363
markrad 0:cdf462088d13 364 EXTRACT_ALL = YES
markrad 0:cdf462088d13 365
markrad 0:cdf462088d13 366 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
markrad 0:cdf462088d13 367 # will be included in the documentation.
markrad 0:cdf462088d13 368
markrad 0:cdf462088d13 369 EXTRACT_PRIVATE = YES
markrad 0:cdf462088d13 370
markrad 0:cdf462088d13 371 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
markrad 0:cdf462088d13 372 # scope will be included in the documentation.
markrad 0:cdf462088d13 373
markrad 0:cdf462088d13 374 EXTRACT_PACKAGE = NO
markrad 0:cdf462088d13 375
markrad 0:cdf462088d13 376 # If the EXTRACT_STATIC tag is set to YES all static members of a file
markrad 0:cdf462088d13 377 # will be included in the documentation.
markrad 0:cdf462088d13 378
markrad 0:cdf462088d13 379 EXTRACT_STATIC = YES
markrad 0:cdf462088d13 380
markrad 0:cdf462088d13 381 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
markrad 0:cdf462088d13 382 # defined locally in source files will be included in the documentation.
markrad 0:cdf462088d13 383 # If set to NO only classes defined in header files are included.
markrad 0:cdf462088d13 384
markrad 0:cdf462088d13 385 EXTRACT_LOCAL_CLASSES = YES
markrad 0:cdf462088d13 386
markrad 0:cdf462088d13 387 # This flag is only useful for Objective-C code. When set to YES local
markrad 0:cdf462088d13 388 # methods, which are defined in the implementation section but not in
markrad 0:cdf462088d13 389 # the interface are included in the documentation.
markrad 0:cdf462088d13 390 # If set to NO (the default) only methods in the interface are included.
markrad 0:cdf462088d13 391
markrad 0:cdf462088d13 392 EXTRACT_LOCAL_METHODS = YES
markrad 0:cdf462088d13 393
markrad 0:cdf462088d13 394 # If this flag is set to YES, the members of anonymous namespaces will be
markrad 0:cdf462088d13 395 # extracted and appear in the documentation as a namespace called
markrad 0:cdf462088d13 396 # 'anonymous_namespace{file}', where file will be replaced with the base
markrad 0:cdf462088d13 397 # name of the file that contains the anonymous namespace. By default
markrad 0:cdf462088d13 398 # anonymous namespaces are hidden.
markrad 0:cdf462088d13 399
markrad 0:cdf462088d13 400 EXTRACT_ANON_NSPACES = YES
markrad 0:cdf462088d13 401
markrad 0:cdf462088d13 402 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
markrad 0:cdf462088d13 403 # undocumented members of documented classes, files or namespaces.
markrad 0:cdf462088d13 404 # If set to NO (the default) these members will be included in the
markrad 0:cdf462088d13 405 # various overviews, but no documentation section is generated.
markrad 0:cdf462088d13 406 # This option has no effect if EXTRACT_ALL is enabled.
markrad 0:cdf462088d13 407
markrad 0:cdf462088d13 408 HIDE_UNDOC_MEMBERS = NO
markrad 0:cdf462088d13 409
markrad 0:cdf462088d13 410 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
markrad 0:cdf462088d13 411 # undocumented classes that are normally visible in the class hierarchy.
markrad 0:cdf462088d13 412 # If set to NO (the default) these classes will be included in the various
markrad 0:cdf462088d13 413 # overviews. This option has no effect if EXTRACT_ALL is enabled.
markrad 0:cdf462088d13 414
markrad 0:cdf462088d13 415 HIDE_UNDOC_CLASSES = NO
markrad 0:cdf462088d13 416
markrad 0:cdf462088d13 417 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
markrad 0:cdf462088d13 418 # friend (class|struct|union) declarations.
markrad 0:cdf462088d13 419 # If set to NO (the default) these declarations will be included in the
markrad 0:cdf462088d13 420 # documentation.
markrad 0:cdf462088d13 421
markrad 0:cdf462088d13 422 HIDE_FRIEND_COMPOUNDS = NO
markrad 0:cdf462088d13 423
markrad 0:cdf462088d13 424 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
markrad 0:cdf462088d13 425 # documentation blocks found inside the body of a function.
markrad 0:cdf462088d13 426 # If set to NO (the default) these blocks will be appended to the
markrad 0:cdf462088d13 427 # function's detailed documentation block.
markrad 0:cdf462088d13 428
markrad 0:cdf462088d13 429 HIDE_IN_BODY_DOCS = NO
markrad 0:cdf462088d13 430
markrad 0:cdf462088d13 431 # The INTERNAL_DOCS tag determines if documentation
markrad 0:cdf462088d13 432 # that is typed after a \internal command is included. If the tag is set
markrad 0:cdf462088d13 433 # to NO (the default) then the documentation will be excluded.
markrad 0:cdf462088d13 434 # Set it to YES to include the internal documentation.
markrad 0:cdf462088d13 435
markrad 0:cdf462088d13 436 INTERNAL_DOCS = NO
markrad 0:cdf462088d13 437
markrad 0:cdf462088d13 438 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
markrad 0:cdf462088d13 439 # file names in lower-case letters. If set to YES upper-case letters are also
markrad 0:cdf462088d13 440 # allowed. This is useful if you have classes or files whose names only differ
markrad 0:cdf462088d13 441 # in case and if your file system supports case sensitive file names. Windows
markrad 0:cdf462088d13 442 # and Mac users are advised to set this option to NO.
markrad 0:cdf462088d13 443
markrad 0:cdf462088d13 444 CASE_SENSE_NAMES = NO
markrad 0:cdf462088d13 445
markrad 0:cdf462088d13 446 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
markrad 0:cdf462088d13 447 # will show members with their full class and namespace scopes in the
markrad 0:cdf462088d13 448 # documentation. If set to YES the scope will be hidden.
markrad 0:cdf462088d13 449
markrad 0:cdf462088d13 450 HIDE_SCOPE_NAMES = NO
markrad 0:cdf462088d13 451
markrad 0:cdf462088d13 452 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
markrad 0:cdf462088d13 453 # will put a list of the files that are included by a file in the documentation
markrad 0:cdf462088d13 454 # of that file.
markrad 0:cdf462088d13 455
markrad 0:cdf462088d13 456 SHOW_INCLUDE_FILES = YES
markrad 0:cdf462088d13 457
markrad 0:cdf462088d13 458 # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
markrad 0:cdf462088d13 459 # will list include files with double quotes in the documentation
markrad 0:cdf462088d13 460 # rather than with sharp brackets.
markrad 0:cdf462088d13 461
markrad 0:cdf462088d13 462 FORCE_LOCAL_INCLUDES = NO
markrad 0:cdf462088d13 463
markrad 0:cdf462088d13 464 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
markrad 0:cdf462088d13 465 # is inserted in the documentation for inline members.
markrad 0:cdf462088d13 466
markrad 0:cdf462088d13 467 INLINE_INFO = YES
markrad 0:cdf462088d13 468
markrad 0:cdf462088d13 469 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
markrad 0:cdf462088d13 470 # will sort the (detailed) documentation of file and class members
markrad 0:cdf462088d13 471 # alphabetically by member name. If set to NO the members will appear in
markrad 0:cdf462088d13 472 # declaration order.
markrad 0:cdf462088d13 473
markrad 0:cdf462088d13 474 SORT_MEMBER_DOCS = YES
markrad 0:cdf462088d13 475
markrad 0:cdf462088d13 476 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
markrad 0:cdf462088d13 477 # brief documentation of file, namespace and class members alphabetically
markrad 0:cdf462088d13 478 # by member name. If set to NO (the default) the members will appear in
markrad 0:cdf462088d13 479 # declaration order.
markrad 0:cdf462088d13 480
markrad 0:cdf462088d13 481 SORT_BRIEF_DOCS = NO
markrad 0:cdf462088d13 482
markrad 0:cdf462088d13 483 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
markrad 0:cdf462088d13 484 # will sort the (brief and detailed) documentation of class members so that
markrad 0:cdf462088d13 485 # constructors and destructors are listed first. If set to NO (the default)
markrad 0:cdf462088d13 486 # the constructors will appear in the respective orders defined by
markrad 0:cdf462088d13 487 # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
markrad 0:cdf462088d13 488 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
markrad 0:cdf462088d13 489 # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
markrad 0:cdf462088d13 490
markrad 0:cdf462088d13 491 SORT_MEMBERS_CTORS_1ST = NO
markrad 0:cdf462088d13 492
markrad 0:cdf462088d13 493 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
markrad 0:cdf462088d13 494 # hierarchy of group names into alphabetical order. If set to NO (the default)
markrad 0:cdf462088d13 495 # the group names will appear in their defined order.
markrad 0:cdf462088d13 496
markrad 0:cdf462088d13 497 SORT_GROUP_NAMES = NO
markrad 0:cdf462088d13 498
markrad 0:cdf462088d13 499 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
markrad 0:cdf462088d13 500 # sorted by fully-qualified names, including namespaces. If set to
markrad 0:cdf462088d13 501 # NO (the default), the class list will be sorted only by class name,
markrad 0:cdf462088d13 502 # not including the namespace part.
markrad 0:cdf462088d13 503 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
markrad 0:cdf462088d13 504 # Note: This option applies only to the class list, not to the
markrad 0:cdf462088d13 505 # alphabetical list.
markrad 0:cdf462088d13 506
markrad 0:cdf462088d13 507 SORT_BY_SCOPE_NAME = NO
markrad 0:cdf462088d13 508
markrad 0:cdf462088d13 509 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
markrad 0:cdf462088d13 510 # do proper type resolution of all parameters of a function it will reject a
markrad 0:cdf462088d13 511 # match between the prototype and the implementation of a member function even
markrad 0:cdf462088d13 512 # if there is only one candidate or it is obvious which candidate to choose
markrad 0:cdf462088d13 513 # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
markrad 0:cdf462088d13 514 # will still accept a match between prototype and implementation in such cases.
markrad 0:cdf462088d13 515
markrad 0:cdf462088d13 516 STRICT_PROTO_MATCHING = NO
markrad 0:cdf462088d13 517
markrad 0:cdf462088d13 518 # The GENERATE_TODOLIST tag can be used to enable (YES) or
markrad 0:cdf462088d13 519 # disable (NO) the todo list. This list is created by putting \todo
markrad 0:cdf462088d13 520 # commands in the documentation.
markrad 0:cdf462088d13 521
markrad 0:cdf462088d13 522 GENERATE_TODOLIST = YES
markrad 0:cdf462088d13 523
markrad 0:cdf462088d13 524 # The GENERATE_TESTLIST tag can be used to enable (YES) or
markrad 0:cdf462088d13 525 # disable (NO) the test list. This list is created by putting \test
markrad 0:cdf462088d13 526 # commands in the documentation.
markrad 0:cdf462088d13 527
markrad 0:cdf462088d13 528 GENERATE_TESTLIST = YES
markrad 0:cdf462088d13 529
markrad 0:cdf462088d13 530 # The GENERATE_BUGLIST tag can be used to enable (YES) or
markrad 0:cdf462088d13 531 # disable (NO) the bug list. This list is created by putting \bug
markrad 0:cdf462088d13 532 # commands in the documentation.
markrad 0:cdf462088d13 533
markrad 0:cdf462088d13 534 GENERATE_BUGLIST = YES
markrad 0:cdf462088d13 535
markrad 0:cdf462088d13 536 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
markrad 0:cdf462088d13 537 # disable (NO) the deprecated list. This list is created by putting
markrad 0:cdf462088d13 538 # \deprecated commands in the documentation.
markrad 0:cdf462088d13 539
markrad 0:cdf462088d13 540 GENERATE_DEPRECATEDLIST= YES
markrad 0:cdf462088d13 541
markrad 0:cdf462088d13 542 # The ENABLED_SECTIONS tag can be used to enable conditional
markrad 0:cdf462088d13 543 # documentation sections, marked by \if section-label ... \endif
markrad 0:cdf462088d13 544 # and \cond section-label ... \endcond blocks.
markrad 0:cdf462088d13 545
markrad 0:cdf462088d13 546 ENABLED_SECTIONS =
markrad 0:cdf462088d13 547
markrad 0:cdf462088d13 548 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
markrad 0:cdf462088d13 549 # the initial value of a variable or macro consists of for it to appear in
markrad 0:cdf462088d13 550 # the documentation. If the initializer consists of more lines than specified
markrad 0:cdf462088d13 551 # here it will be hidden. Use a value of 0 to hide initializers completely.
markrad 0:cdf462088d13 552 # The appearance of the initializer of individual variables and macros in the
markrad 0:cdf462088d13 553 # documentation can be controlled using \showinitializer or \hideinitializer
markrad 0:cdf462088d13 554 # command in the documentation regardless of this setting.
markrad 0:cdf462088d13 555
markrad 0:cdf462088d13 556 MAX_INITIALIZER_LINES = 30
markrad 0:cdf462088d13 557
markrad 0:cdf462088d13 558 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
markrad 0:cdf462088d13 559 # at the bottom of the documentation of classes and structs. If set to YES the
markrad 0:cdf462088d13 560 # list will mention the files that were used to generate the documentation.
markrad 0:cdf462088d13 561
markrad 0:cdf462088d13 562 SHOW_USED_FILES = YES
markrad 0:cdf462088d13 563
markrad 0:cdf462088d13 564 # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
markrad 0:cdf462088d13 565 # This will remove the Files entry from the Quick Index and from the
markrad 0:cdf462088d13 566 # Folder Tree View (if specified). The default is YES.
markrad 0:cdf462088d13 567
markrad 0:cdf462088d13 568 SHOW_FILES = YES
markrad 0:cdf462088d13 569
markrad 0:cdf462088d13 570 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the
markrad 0:cdf462088d13 571 # Namespaces page.
markrad 0:cdf462088d13 572 # This will remove the Namespaces entry from the Quick Index
markrad 0:cdf462088d13 573 # and from the Folder Tree View (if specified). The default is YES.
markrad 0:cdf462088d13 574
markrad 0:cdf462088d13 575 SHOW_NAMESPACES = YES
markrad 0:cdf462088d13 576
markrad 0:cdf462088d13 577 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
markrad 0:cdf462088d13 578 # doxygen should invoke to get the current version for each file (typically from
markrad 0:cdf462088d13 579 # the version control system). Doxygen will invoke the program by executing (via
markrad 0:cdf462088d13 580 # popen()) the command <command> <input-file>, where <command> is the value of
markrad 0:cdf462088d13 581 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
markrad 0:cdf462088d13 582 # provided by doxygen. Whatever the program writes to standard output
markrad 0:cdf462088d13 583 # is used as the file version. See the manual for examples.
markrad 0:cdf462088d13 584
markrad 0:cdf462088d13 585 FILE_VERSION_FILTER =
markrad 0:cdf462088d13 586
markrad 0:cdf462088d13 587 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
markrad 0:cdf462088d13 588 # by doxygen. The layout file controls the global structure of the generated
markrad 0:cdf462088d13 589 # output files in an output format independent way. To create the layout file
markrad 0:cdf462088d13 590 # that represents doxygen's defaults, run doxygen with the -l option.
markrad 0:cdf462088d13 591 # You can optionally specify a file name after the option, if omitted
markrad 0:cdf462088d13 592 # DoxygenLayout.xml will be used as the name of the layout file.
markrad 0:cdf462088d13 593
markrad 0:cdf462088d13 594 LAYOUT_FILE =
markrad 0:cdf462088d13 595
markrad 0:cdf462088d13 596 # The CITE_BIB_FILES tag can be used to specify one or more bib files
markrad 0:cdf462088d13 597 # containing the references data. This must be a list of .bib files. The
markrad 0:cdf462088d13 598 # .bib extension is automatically appended if omitted. Using this command
markrad 0:cdf462088d13 599 # requires the bibtex tool to be installed. See also
markrad 0:cdf462088d13 600 # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
markrad 0:cdf462088d13 601 # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
markrad 0:cdf462088d13 602 # feature you need bibtex and perl available in the search path. Do not use
markrad 0:cdf462088d13 603 # file names with spaces, bibtex cannot handle them.
markrad 0:cdf462088d13 604
markrad 0:cdf462088d13 605 CITE_BIB_FILES =
markrad 0:cdf462088d13 606
markrad 0:cdf462088d13 607 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 608 # configuration options related to warning and progress messages
markrad 0:cdf462088d13 609 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 610
markrad 0:cdf462088d13 611 # The QUIET tag can be used to turn on/off the messages that are generated
markrad 0:cdf462088d13 612 # by doxygen. Possible values are YES and NO. If left blank NO is used.
markrad 0:cdf462088d13 613
markrad 0:cdf462088d13 614 QUIET = NO
markrad 0:cdf462088d13 615
markrad 0:cdf462088d13 616 # The WARNINGS tag can be used to turn on/off the warning messages that are
markrad 0:cdf462088d13 617 # generated by doxygen. Possible values are YES and NO. If left blank
markrad 0:cdf462088d13 618 # NO is used.
markrad 0:cdf462088d13 619
markrad 0:cdf462088d13 620 WARNINGS = YES
markrad 0:cdf462088d13 621
markrad 0:cdf462088d13 622 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
markrad 0:cdf462088d13 623 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
markrad 0:cdf462088d13 624 # automatically be disabled.
markrad 0:cdf462088d13 625
markrad 0:cdf462088d13 626 WARN_IF_UNDOCUMENTED = YES
markrad 0:cdf462088d13 627
markrad 0:cdf462088d13 628 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
markrad 0:cdf462088d13 629 # potential errors in the documentation, such as not documenting some
markrad 0:cdf462088d13 630 # parameters in a documented function, or documenting parameters that
markrad 0:cdf462088d13 631 # don't exist or using markup commands wrongly.
markrad 0:cdf462088d13 632
markrad 0:cdf462088d13 633 WARN_IF_DOC_ERROR = YES
markrad 0:cdf462088d13 634
markrad 0:cdf462088d13 635 # The WARN_NO_PARAMDOC option can be enabled to get warnings for
markrad 0:cdf462088d13 636 # functions that are documented, but have no documentation for their parameters
markrad 0:cdf462088d13 637 # or return value. If set to NO (the default) doxygen will only warn about
markrad 0:cdf462088d13 638 # wrong or incomplete parameter documentation, but not about the absence of
markrad 0:cdf462088d13 639 # documentation.
markrad 0:cdf462088d13 640
markrad 0:cdf462088d13 641 WARN_NO_PARAMDOC = NO
markrad 0:cdf462088d13 642
markrad 0:cdf462088d13 643 # The WARN_FORMAT tag determines the format of the warning messages that
markrad 0:cdf462088d13 644 # doxygen can produce. The string should contain the $file, $line, and $text
markrad 0:cdf462088d13 645 # tags, which will be replaced by the file and line number from which the
markrad 0:cdf462088d13 646 # warning originated and the warning text. Optionally the format may contain
markrad 0:cdf462088d13 647 # $version, which will be replaced by the version of the file (if it could
markrad 0:cdf462088d13 648 # be obtained via FILE_VERSION_FILTER)
markrad 0:cdf462088d13 649
markrad 0:cdf462088d13 650 WARN_FORMAT = "$file:$line: $text"
markrad 0:cdf462088d13 651
markrad 0:cdf462088d13 652 # The WARN_LOGFILE tag can be used to specify a file to which warning
markrad 0:cdf462088d13 653 # and error messages should be written. If left blank the output is written
markrad 0:cdf462088d13 654 # to stderr.
markrad 0:cdf462088d13 655
markrad 0:cdf462088d13 656 WARN_LOGFILE =
markrad 0:cdf462088d13 657
markrad 0:cdf462088d13 658 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 659 # configuration options related to the input files
markrad 0:cdf462088d13 660 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 661
markrad 0:cdf462088d13 662 # The INPUT tag can be used to specify the files and/or directories that contain
markrad 0:cdf462088d13 663 # documented source files. You may enter file names like "myfile.cpp" or
markrad 0:cdf462088d13 664 # directories like "/usr/src/myproject". Separate the files or directories
markrad 0:cdf462088d13 665 # with spaces.
markrad 0:cdf462088d13 666
markrad 0:cdf462088d13 667 INPUT = .
markrad 0:cdf462088d13 668
markrad 0:cdf462088d13 669 # This tag can be used to specify the character encoding of the source files
markrad 0:cdf462088d13 670 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
markrad 0:cdf462088d13 671 # also the default input encoding. Doxygen uses libiconv (or the iconv built
markrad 0:cdf462088d13 672 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
markrad 0:cdf462088d13 673 # the list of possible encodings.
markrad 0:cdf462088d13 674
markrad 0:cdf462088d13 675 INPUT_ENCODING = UTF-8
markrad 0:cdf462088d13 676
markrad 0:cdf462088d13 677 # If the value of the INPUT tag contains directories, you can use the
markrad 0:cdf462088d13 678 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
markrad 0:cdf462088d13 679 # and *.h) to filter out the source-files in the directories. If left
markrad 0:cdf462088d13 680 # blank the following patterns are tested:
markrad 0:cdf462088d13 681 # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
markrad 0:cdf462088d13 682 # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
markrad 0:cdf462088d13 683 # *.f90 *.f *.for *.vhd *.vhdl
markrad 0:cdf462088d13 684
markrad 0:cdf462088d13 685 FILE_PATTERNS = *.h
markrad 0:cdf462088d13 686
markrad 0:cdf462088d13 687 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
markrad 0:cdf462088d13 688 # should be searched for input files as well. Possible values are YES and NO.
markrad 0:cdf462088d13 689 # If left blank NO is used.
markrad 0:cdf462088d13 690
markrad 0:cdf462088d13 691 RECURSIVE = YES
markrad 0:cdf462088d13 692
markrad 0:cdf462088d13 693 # The EXCLUDE tag can be used to specify files and/or directories that should be
markrad 0:cdf462088d13 694 # excluded from the INPUT source files. This way you can easily exclude a
markrad 0:cdf462088d13 695 # subdirectory from a directory tree whose root is specified with the INPUT tag.
markrad 0:cdf462088d13 696 # Note that relative paths are relative to the directory from which doxygen is
markrad 0:cdf462088d13 697 # run.
markrad 0:cdf462088d13 698
markrad 0:cdf462088d13 699 EXCLUDE = configs yotta/module
markrad 0:cdf462088d13 700
markrad 0:cdf462088d13 701 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
markrad 0:cdf462088d13 702 # directories that are symbolic links (a Unix file system feature) are excluded
markrad 0:cdf462088d13 703 # from the input.
markrad 0:cdf462088d13 704
markrad 0:cdf462088d13 705 EXCLUDE_SYMLINKS = NO
markrad 0:cdf462088d13 706
markrad 0:cdf462088d13 707 # If the value of the INPUT tag contains directories, you can use the
markrad 0:cdf462088d13 708 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
markrad 0:cdf462088d13 709 # certain files from those directories. Note that the wildcards are matched
markrad 0:cdf462088d13 710 # against the file with absolute path, so to exclude all test directories
markrad 0:cdf462088d13 711 # for example use the pattern */test/*
markrad 0:cdf462088d13 712
markrad 0:cdf462088d13 713 EXCLUDE_PATTERNS = *_internal.h *_wrap.h
markrad 0:cdf462088d13 714
markrad 0:cdf462088d13 715 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
markrad 0:cdf462088d13 716 # (namespaces, classes, functions, etc.) that should be excluded from the
markrad 0:cdf462088d13 717 # output. The symbol name can be a fully qualified name, a word, or if the
markrad 0:cdf462088d13 718 # wildcard * is used, a substring. Examples: ANamespace, AClass,
markrad 0:cdf462088d13 719 # AClass::ANamespace, ANamespace::*Test
markrad 0:cdf462088d13 720
markrad 0:cdf462088d13 721 EXCLUDE_SYMBOLS =
markrad 0:cdf462088d13 722
markrad 0:cdf462088d13 723 # The EXAMPLE_PATH tag can be used to specify one or more files or
markrad 0:cdf462088d13 724 # directories that contain example code fragments that are included (see
markrad 0:cdf462088d13 725 # the \include command).
markrad 0:cdf462088d13 726
markrad 0:cdf462088d13 727 EXAMPLE_PATH =
markrad 0:cdf462088d13 728
markrad 0:cdf462088d13 729 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
markrad 0:cdf462088d13 730 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
markrad 0:cdf462088d13 731 # and *.h) to filter out the source-files in the directories. If left
markrad 0:cdf462088d13 732 # blank all files are included.
markrad 0:cdf462088d13 733
markrad 0:cdf462088d13 734 EXAMPLE_PATTERNS = *
markrad 0:cdf462088d13 735
markrad 0:cdf462088d13 736 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
markrad 0:cdf462088d13 737 # searched for input files to be used with the \include or \dontinclude
markrad 0:cdf462088d13 738 # commands irrespective of the value of the RECURSIVE tag.
markrad 0:cdf462088d13 739 # Possible values are YES and NO. If left blank NO is used.
markrad 0:cdf462088d13 740
markrad 0:cdf462088d13 741 EXAMPLE_RECURSIVE = NO
markrad 0:cdf462088d13 742
markrad 0:cdf462088d13 743 # The IMAGE_PATH tag can be used to specify one or more files or
markrad 0:cdf462088d13 744 # directories that contain image that are included in the documentation (see
markrad 0:cdf462088d13 745 # the \image command).
markrad 0:cdf462088d13 746
markrad 0:cdf462088d13 747 IMAGE_PATH =
markrad 0:cdf462088d13 748
markrad 0:cdf462088d13 749 # The INPUT_FILTER tag can be used to specify a program that doxygen should
markrad 0:cdf462088d13 750 # invoke to filter for each input file. Doxygen will invoke the filter program
markrad 0:cdf462088d13 751 # by executing (via popen()) the command <filter> <input-file>, where <filter>
markrad 0:cdf462088d13 752 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
markrad 0:cdf462088d13 753 # input file. Doxygen will then use the output that the filter program writes
markrad 0:cdf462088d13 754 # to standard output.
markrad 0:cdf462088d13 755 # If FILTER_PATTERNS is specified, this tag will be ignored.
markrad 0:cdf462088d13 756 # Note that the filter must not add or remove lines; it is applied before the
markrad 0:cdf462088d13 757 # code is scanned, but not when the output code is generated. If lines are added
markrad 0:cdf462088d13 758 # or removed, the anchors will not be placed correctly.
markrad 0:cdf462088d13 759
markrad 0:cdf462088d13 760 INPUT_FILTER =
markrad 0:cdf462088d13 761
markrad 0:cdf462088d13 762 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
markrad 0:cdf462088d13 763 # basis.
markrad 0:cdf462088d13 764 # Doxygen will compare the file name with each pattern and apply the
markrad 0:cdf462088d13 765 # filter if there is a match.
markrad 0:cdf462088d13 766 # The filters are a list of the form:
markrad 0:cdf462088d13 767 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
markrad 0:cdf462088d13 768 # info on how filters are used. If FILTER_PATTERNS is empty or if
markrad 0:cdf462088d13 769 # non of the patterns match the file name, INPUT_FILTER is applied.
markrad 0:cdf462088d13 770
markrad 0:cdf462088d13 771 FILTER_PATTERNS =
markrad 0:cdf462088d13 772
markrad 0:cdf462088d13 773 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
markrad 0:cdf462088d13 774 # INPUT_FILTER) will be used to filter the input files when producing source
markrad 0:cdf462088d13 775 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
markrad 0:cdf462088d13 776
markrad 0:cdf462088d13 777 FILTER_SOURCE_FILES = NO
markrad 0:cdf462088d13 778
markrad 0:cdf462088d13 779 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
markrad 0:cdf462088d13 780 # pattern. A pattern will override the setting for FILTER_PATTERN (if any)
markrad 0:cdf462088d13 781 # and it is also possible to disable source filtering for a specific pattern
markrad 0:cdf462088d13 782 # using *.ext= (so without naming a filter). This option only has effect when
markrad 0:cdf462088d13 783 # FILTER_SOURCE_FILES is enabled.
markrad 0:cdf462088d13 784
markrad 0:cdf462088d13 785 FILTER_SOURCE_PATTERNS =
markrad 0:cdf462088d13 786
markrad 0:cdf462088d13 787 # If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that
markrad 0:cdf462088d13 788 # is part of the input, its contents will be placed on the main page
markrad 0:cdf462088d13 789 # (index.html). This can be useful if you have a project on for instance GitHub
markrad 0:cdf462088d13 790 # and want reuse the introduction page also for the doxygen output.
markrad 0:cdf462088d13 791
markrad 0:cdf462088d13 792 USE_MDFILE_AS_MAINPAGE =
markrad 0:cdf462088d13 793
markrad 0:cdf462088d13 794 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 795 # configuration options related to source browsing
markrad 0:cdf462088d13 796 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 797
markrad 0:cdf462088d13 798 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
markrad 0:cdf462088d13 799 # be generated. Documented entities will be cross-referenced with these sources.
markrad 0:cdf462088d13 800 # Note: To get rid of all source code in the generated output, make sure also
markrad 0:cdf462088d13 801 # VERBATIM_HEADERS is set to NO.
markrad 0:cdf462088d13 802
markrad 0:cdf462088d13 803 SOURCE_BROWSER = YES
markrad 0:cdf462088d13 804
markrad 0:cdf462088d13 805 # Setting the INLINE_SOURCES tag to YES will include the body
markrad 0:cdf462088d13 806 # of functions and classes directly in the documentation.
markrad 0:cdf462088d13 807
markrad 0:cdf462088d13 808 INLINE_SOURCES = NO
markrad 0:cdf462088d13 809
markrad 0:cdf462088d13 810 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
markrad 0:cdf462088d13 811 # doxygen to hide any special comment blocks from generated source code
markrad 0:cdf462088d13 812 # fragments. Normal C, C++ and Fortran comments will always remain visible.
markrad 0:cdf462088d13 813
markrad 0:cdf462088d13 814 STRIP_CODE_COMMENTS = YES
markrad 0:cdf462088d13 815
markrad 0:cdf462088d13 816 # If the REFERENCED_BY_RELATION tag is set to YES
markrad 0:cdf462088d13 817 # then for each documented function all documented
markrad 0:cdf462088d13 818 # functions referencing it will be listed.
markrad 0:cdf462088d13 819
markrad 0:cdf462088d13 820 REFERENCED_BY_RELATION = YES
markrad 0:cdf462088d13 821
markrad 0:cdf462088d13 822 # If the REFERENCES_RELATION tag is set to YES
markrad 0:cdf462088d13 823 # then for each documented function all documented entities
markrad 0:cdf462088d13 824 # called/used by that function will be listed.
markrad 0:cdf462088d13 825
markrad 0:cdf462088d13 826 REFERENCES_RELATION = YES
markrad 0:cdf462088d13 827
markrad 0:cdf462088d13 828 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
markrad 0:cdf462088d13 829 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
markrad 0:cdf462088d13 830 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
markrad 0:cdf462088d13 831 # link to the source code.
markrad 0:cdf462088d13 832 # Otherwise they will link to the documentation.
markrad 0:cdf462088d13 833
markrad 0:cdf462088d13 834 REFERENCES_LINK_SOURCE = YES
markrad 0:cdf462088d13 835
markrad 0:cdf462088d13 836 # If the USE_HTAGS tag is set to YES then the references to source code
markrad 0:cdf462088d13 837 # will point to the HTML generated by the htags(1) tool instead of doxygen
markrad 0:cdf462088d13 838 # built-in source browser. The htags tool is part of GNU's global source
markrad 0:cdf462088d13 839 # tagging system (see http://www.gnu.org/software/global/global.html). You
markrad 0:cdf462088d13 840 # will need version 4.8.6 or higher.
markrad 0:cdf462088d13 841
markrad 0:cdf462088d13 842 USE_HTAGS = NO
markrad 0:cdf462088d13 843
markrad 0:cdf462088d13 844 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
markrad 0:cdf462088d13 845 # will generate a verbatim copy of the header file for each class for
markrad 0:cdf462088d13 846 # which an include is specified. Set to NO to disable this.
markrad 0:cdf462088d13 847
markrad 0:cdf462088d13 848 VERBATIM_HEADERS = YES
markrad 0:cdf462088d13 849
markrad 0:cdf462088d13 850 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 851 # configuration options related to the alphabetical class index
markrad 0:cdf462088d13 852 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 853
markrad 0:cdf462088d13 854 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
markrad 0:cdf462088d13 855 # of all compounds will be generated. Enable this if the project
markrad 0:cdf462088d13 856 # contains a lot of classes, structs, unions or interfaces.
markrad 0:cdf462088d13 857
markrad 0:cdf462088d13 858 ALPHABETICAL_INDEX = NO
markrad 0:cdf462088d13 859
markrad 0:cdf462088d13 860 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
markrad 0:cdf462088d13 861 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
markrad 0:cdf462088d13 862 # in which this list will be split (can be a number in the range [1..20])
markrad 0:cdf462088d13 863
markrad 0:cdf462088d13 864 COLS_IN_ALPHA_INDEX = 5
markrad 0:cdf462088d13 865
markrad 0:cdf462088d13 866 # In case all classes in a project start with a common prefix, all
markrad 0:cdf462088d13 867 # classes will be put under the same header in the alphabetical index.
markrad 0:cdf462088d13 868 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
markrad 0:cdf462088d13 869 # should be ignored while generating the index headers.
markrad 0:cdf462088d13 870
markrad 0:cdf462088d13 871 IGNORE_PREFIX =
markrad 0:cdf462088d13 872
markrad 0:cdf462088d13 873 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 874 # configuration options related to the HTML output
markrad 0:cdf462088d13 875 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 876
markrad 0:cdf462088d13 877 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 878 # generate HTML output.
markrad 0:cdf462088d13 879
markrad 0:cdf462088d13 880 GENERATE_HTML = YES
markrad 0:cdf462088d13 881
markrad 0:cdf462088d13 882 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
markrad 0:cdf462088d13 883 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
markrad 0:cdf462088d13 884 # put in front of it. If left blank `html' will be used as the default path.
markrad 0:cdf462088d13 885
markrad 0:cdf462088d13 886 HTML_OUTPUT = .
markrad 0:cdf462088d13 887
markrad 0:cdf462088d13 888 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
markrad 0:cdf462088d13 889 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
markrad 0:cdf462088d13 890 # doxygen will generate files with .html extension.
markrad 0:cdf462088d13 891
markrad 0:cdf462088d13 892 HTML_FILE_EXTENSION = .html
markrad 0:cdf462088d13 893
markrad 0:cdf462088d13 894 # The HTML_HEADER tag can be used to specify a personal HTML header for
markrad 0:cdf462088d13 895 # each generated HTML page. If it is left blank doxygen will generate a
markrad 0:cdf462088d13 896 # standard header. Note that when using a custom header you are responsible
markrad 0:cdf462088d13 897 # for the proper inclusion of any scripts and style sheets that doxygen
markrad 0:cdf462088d13 898 # needs, which is dependent on the configuration options used.
markrad 0:cdf462088d13 899 # It is advised to generate a default header using "doxygen -w html
markrad 0:cdf462088d13 900 # header.html footer.html stylesheet.css YourConfigFile" and then modify
markrad 0:cdf462088d13 901 # that header. Note that the header is subject to change so you typically
markrad 0:cdf462088d13 902 # have to redo this when upgrading to a newer version of doxygen or when
markrad 0:cdf462088d13 903 # changing the value of configuration settings such as GENERATE_TREEVIEW!
markrad 0:cdf462088d13 904
markrad 0:cdf462088d13 905 HTML_HEADER =
markrad 0:cdf462088d13 906
markrad 0:cdf462088d13 907 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
markrad 0:cdf462088d13 908 # each generated HTML page. If it is left blank doxygen will generate a
markrad 0:cdf462088d13 909 # standard footer.
markrad 0:cdf462088d13 910
markrad 0:cdf462088d13 911 HTML_FOOTER =
markrad 0:cdf462088d13 912
markrad 0:cdf462088d13 913 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
markrad 0:cdf462088d13 914 # style sheet that is used by each HTML page. It can be used to
markrad 0:cdf462088d13 915 # fine-tune the look of the HTML output. If left blank doxygen will
markrad 0:cdf462088d13 916 # generate a default style sheet. Note that it is recommended to use
markrad 0:cdf462088d13 917 # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this
markrad 0:cdf462088d13 918 # tag will in the future become obsolete.
markrad 0:cdf462088d13 919
markrad 0:cdf462088d13 920 HTML_STYLESHEET =
markrad 0:cdf462088d13 921
markrad 0:cdf462088d13 922 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional
markrad 0:cdf462088d13 923 # user-defined cascading style sheet that is included after the standard
markrad 0:cdf462088d13 924 # style sheets created by doxygen. Using this option one can overrule
markrad 0:cdf462088d13 925 # certain style aspects. This is preferred over using HTML_STYLESHEET
markrad 0:cdf462088d13 926 # since it does not replace the standard style sheet and is therefor more
markrad 0:cdf462088d13 927 # robust against future updates. Doxygen will copy the style sheet file to
markrad 0:cdf462088d13 928 # the output directory.
markrad 0:cdf462088d13 929
markrad 0:cdf462088d13 930 HTML_EXTRA_STYLESHEET =
markrad 0:cdf462088d13 931
markrad 0:cdf462088d13 932 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
markrad 0:cdf462088d13 933 # other source files which should be copied to the HTML output directory. Note
markrad 0:cdf462088d13 934 # that these files will be copied to the base HTML output directory. Use the
markrad 0:cdf462088d13 935 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
markrad 0:cdf462088d13 936 # files. In the HTML_STYLESHEET file, use the file name only. Also note that
markrad 0:cdf462088d13 937 # the files will be copied as-is; there are no commands or markers available.
markrad 0:cdf462088d13 938
markrad 0:cdf462088d13 939 HTML_EXTRA_FILES =
markrad 0:cdf462088d13 940
markrad 0:cdf462088d13 941 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
markrad 0:cdf462088d13 942 # Doxygen will adjust the colors in the style sheet and background images
markrad 0:cdf462088d13 943 # according to this color. Hue is specified as an angle on a colorwheel,
markrad 0:cdf462088d13 944 # see http://en.wikipedia.org/wiki/Hue for more information.
markrad 0:cdf462088d13 945 # For instance the value 0 represents red, 60 is yellow, 120 is green,
markrad 0:cdf462088d13 946 # 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
markrad 0:cdf462088d13 947 # The allowed range is 0 to 359.
markrad 0:cdf462088d13 948
markrad 0:cdf462088d13 949 HTML_COLORSTYLE_HUE = 220
markrad 0:cdf462088d13 950
markrad 0:cdf462088d13 951 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
markrad 0:cdf462088d13 952 # the colors in the HTML output. For a value of 0 the output will use
markrad 0:cdf462088d13 953 # grayscales only. A value of 255 will produce the most vivid colors.
markrad 0:cdf462088d13 954
markrad 0:cdf462088d13 955 HTML_COLORSTYLE_SAT = 100
markrad 0:cdf462088d13 956
markrad 0:cdf462088d13 957 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
markrad 0:cdf462088d13 958 # the luminance component of the colors in the HTML output. Values below
markrad 0:cdf462088d13 959 # 100 gradually make the output lighter, whereas values above 100 make
markrad 0:cdf462088d13 960 # the output darker. The value divided by 100 is the actual gamma applied,
markrad 0:cdf462088d13 961 # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
markrad 0:cdf462088d13 962 # and 100 does not change the gamma.
markrad 0:cdf462088d13 963
markrad 0:cdf462088d13 964 HTML_COLORSTYLE_GAMMA = 80
markrad 0:cdf462088d13 965
markrad 0:cdf462088d13 966 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
markrad 0:cdf462088d13 967 # page will contain the date and time when the page was generated. Setting
markrad 0:cdf462088d13 968 # this to NO can help when comparing the output of multiple runs.
markrad 0:cdf462088d13 969
markrad 0:cdf462088d13 970 HTML_TIMESTAMP = YES
markrad 0:cdf462088d13 971
markrad 0:cdf462088d13 972 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
markrad 0:cdf462088d13 973 # documentation will contain sections that can be hidden and shown after the
markrad 0:cdf462088d13 974 # page has loaded.
markrad 0:cdf462088d13 975
markrad 0:cdf462088d13 976 HTML_DYNAMIC_SECTIONS = NO
markrad 0:cdf462088d13 977
markrad 0:cdf462088d13 978 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of
markrad 0:cdf462088d13 979 # entries shown in the various tree structured indices initially; the user
markrad 0:cdf462088d13 980 # can expand and collapse entries dynamically later on. Doxygen will expand
markrad 0:cdf462088d13 981 # the tree to such a level that at most the specified number of entries are
markrad 0:cdf462088d13 982 # visible (unless a fully collapsed tree already exceeds this amount).
markrad 0:cdf462088d13 983 # So setting the number of entries 1 will produce a full collapsed tree by
markrad 0:cdf462088d13 984 # default. 0 is a special value representing an infinite number of entries
markrad 0:cdf462088d13 985 # and will result in a full expanded tree by default.
markrad 0:cdf462088d13 986
markrad 0:cdf462088d13 987 HTML_INDEX_NUM_ENTRIES = 100
markrad 0:cdf462088d13 988
markrad 0:cdf462088d13 989 # If the GENERATE_DOCSET tag is set to YES, additional index files
markrad 0:cdf462088d13 990 # will be generated that can be used as input for Apple's Xcode 3
markrad 0:cdf462088d13 991 # integrated development environment, introduced with OSX 10.5 (Leopard).
markrad 0:cdf462088d13 992 # To create a documentation set, doxygen will generate a Makefile in the
markrad 0:cdf462088d13 993 # HTML output directory. Running make will produce the docset in that
markrad 0:cdf462088d13 994 # directory and running "make install" will install the docset in
markrad 0:cdf462088d13 995 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
markrad 0:cdf462088d13 996 # it at startup.
markrad 0:cdf462088d13 997 # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
markrad 0:cdf462088d13 998 # for more information.
markrad 0:cdf462088d13 999
markrad 0:cdf462088d13 1000 GENERATE_DOCSET = NO
markrad 0:cdf462088d13 1001
markrad 0:cdf462088d13 1002 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
markrad 0:cdf462088d13 1003 # feed. A documentation feed provides an umbrella under which multiple
markrad 0:cdf462088d13 1004 # documentation sets from a single provider (such as a company or product suite)
markrad 0:cdf462088d13 1005 # can be grouped.
markrad 0:cdf462088d13 1006
markrad 0:cdf462088d13 1007 DOCSET_FEEDNAME = "Doxygen generated docs"
markrad 0:cdf462088d13 1008
markrad 0:cdf462088d13 1009 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
markrad 0:cdf462088d13 1010 # should uniquely identify the documentation set bundle. This should be a
markrad 0:cdf462088d13 1011 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
markrad 0:cdf462088d13 1012 # will append .docset to the name.
markrad 0:cdf462088d13 1013
markrad 0:cdf462088d13 1014 DOCSET_BUNDLE_ID = org.doxygen.Project
markrad 0:cdf462088d13 1015
markrad 0:cdf462088d13 1016 # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely
markrad 0:cdf462088d13 1017 # identify the documentation publisher. This should be a reverse domain-name
markrad 0:cdf462088d13 1018 # style string, e.g. com.mycompany.MyDocSet.documentation.
markrad 0:cdf462088d13 1019
markrad 0:cdf462088d13 1020 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
markrad 0:cdf462088d13 1021
markrad 0:cdf462088d13 1022 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
markrad 0:cdf462088d13 1023
markrad 0:cdf462088d13 1024 DOCSET_PUBLISHER_NAME = Publisher
markrad 0:cdf462088d13 1025
markrad 0:cdf462088d13 1026 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
markrad 0:cdf462088d13 1027 # will be generated that can be used as input for tools like the
markrad 0:cdf462088d13 1028 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
markrad 0:cdf462088d13 1029 # of the generated HTML documentation.
markrad 0:cdf462088d13 1030
markrad 0:cdf462088d13 1031 GENERATE_HTMLHELP = NO
markrad 0:cdf462088d13 1032
markrad 0:cdf462088d13 1033 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
markrad 0:cdf462088d13 1034 # be used to specify the file name of the resulting .chm file. You
markrad 0:cdf462088d13 1035 # can add a path in front of the file if the result should not be
markrad 0:cdf462088d13 1036 # written to the html output directory.
markrad 0:cdf462088d13 1037
markrad 0:cdf462088d13 1038 CHM_FILE =
markrad 0:cdf462088d13 1039
markrad 0:cdf462088d13 1040 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
markrad 0:cdf462088d13 1041 # be used to specify the location (absolute path including file name) of
markrad 0:cdf462088d13 1042 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
markrad 0:cdf462088d13 1043 # the HTML help compiler on the generated index.hhp.
markrad 0:cdf462088d13 1044
markrad 0:cdf462088d13 1045 HHC_LOCATION =
markrad 0:cdf462088d13 1046
markrad 0:cdf462088d13 1047 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
markrad 0:cdf462088d13 1048 # controls if a separate .chi index file is generated (YES) or that
markrad 0:cdf462088d13 1049 # it should be included in the master .chm file (NO).
markrad 0:cdf462088d13 1050
markrad 0:cdf462088d13 1051 GENERATE_CHI = NO
markrad 0:cdf462088d13 1052
markrad 0:cdf462088d13 1053 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
markrad 0:cdf462088d13 1054 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
markrad 0:cdf462088d13 1055 # content.
markrad 0:cdf462088d13 1056
markrad 0:cdf462088d13 1057 CHM_INDEX_ENCODING =
markrad 0:cdf462088d13 1058
markrad 0:cdf462088d13 1059 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
markrad 0:cdf462088d13 1060 # controls whether a binary table of contents is generated (YES) or a
markrad 0:cdf462088d13 1061 # normal table of contents (NO) in the .chm file.
markrad 0:cdf462088d13 1062
markrad 0:cdf462088d13 1063 BINARY_TOC = NO
markrad 0:cdf462088d13 1064
markrad 0:cdf462088d13 1065 # The TOC_EXPAND flag can be set to YES to add extra items for group members
markrad 0:cdf462088d13 1066 # to the contents of the HTML help documentation and to the tree view.
markrad 0:cdf462088d13 1067
markrad 0:cdf462088d13 1068 TOC_EXPAND = NO
markrad 0:cdf462088d13 1069
markrad 0:cdf462088d13 1070 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
markrad 0:cdf462088d13 1071 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
markrad 0:cdf462088d13 1072 # that can be used as input for Qt's qhelpgenerator to generate a
markrad 0:cdf462088d13 1073 # Qt Compressed Help (.qch) of the generated HTML documentation.
markrad 0:cdf462088d13 1074
markrad 0:cdf462088d13 1075 GENERATE_QHP = NO
markrad 0:cdf462088d13 1076
markrad 0:cdf462088d13 1077 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can
markrad 0:cdf462088d13 1078 # be used to specify the file name of the resulting .qch file.
markrad 0:cdf462088d13 1079 # The path specified is relative to the HTML output folder.
markrad 0:cdf462088d13 1080
markrad 0:cdf462088d13 1081 QCH_FILE =
markrad 0:cdf462088d13 1082
markrad 0:cdf462088d13 1083 # The QHP_NAMESPACE tag specifies the namespace to use when generating
markrad 0:cdf462088d13 1084 # Qt Help Project output. For more information please see
markrad 0:cdf462088d13 1085 # http://doc.trolltech.com/qthelpproject.html#namespace
markrad 0:cdf462088d13 1086
markrad 0:cdf462088d13 1087 QHP_NAMESPACE = org.doxygen.Project
markrad 0:cdf462088d13 1088
markrad 0:cdf462088d13 1089 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
markrad 0:cdf462088d13 1090 # Qt Help Project output. For more information please see
markrad 0:cdf462088d13 1091 # http://doc.trolltech.com/qthelpproject.html#virtual-folders
markrad 0:cdf462088d13 1092
markrad 0:cdf462088d13 1093 QHP_VIRTUAL_FOLDER = doc
markrad 0:cdf462088d13 1094
markrad 0:cdf462088d13 1095 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
markrad 0:cdf462088d13 1096 # add. For more information please see
markrad 0:cdf462088d13 1097 # http://doc.trolltech.com/qthelpproject.html#custom-filters
markrad 0:cdf462088d13 1098
markrad 0:cdf462088d13 1099 QHP_CUST_FILTER_NAME =
markrad 0:cdf462088d13 1100
markrad 0:cdf462088d13 1101 # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
markrad 0:cdf462088d13 1102 # custom filter to add. For more information please see
markrad 0:cdf462088d13 1103 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
markrad 0:cdf462088d13 1104 # Qt Help Project / Custom Filters</a>.
markrad 0:cdf462088d13 1105
markrad 0:cdf462088d13 1106 QHP_CUST_FILTER_ATTRS =
markrad 0:cdf462088d13 1107
markrad 0:cdf462088d13 1108 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
markrad 0:cdf462088d13 1109 # project's
markrad 0:cdf462088d13 1110 # filter section matches.
markrad 0:cdf462088d13 1111 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
markrad 0:cdf462088d13 1112 # Qt Help Project / Filter Attributes</a>.
markrad 0:cdf462088d13 1113
markrad 0:cdf462088d13 1114 QHP_SECT_FILTER_ATTRS =
markrad 0:cdf462088d13 1115
markrad 0:cdf462088d13 1116 # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
markrad 0:cdf462088d13 1117 # be used to specify the location of Qt's qhelpgenerator.
markrad 0:cdf462088d13 1118 # If non-empty doxygen will try to run qhelpgenerator on the generated
markrad 0:cdf462088d13 1119 # .qhp file.
markrad 0:cdf462088d13 1120
markrad 0:cdf462088d13 1121 QHG_LOCATION =
markrad 0:cdf462088d13 1122
markrad 0:cdf462088d13 1123 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
markrad 0:cdf462088d13 1124 # will be generated, which together with the HTML files, form an Eclipse help
markrad 0:cdf462088d13 1125 # plugin. To install this plugin and make it available under the help contents
markrad 0:cdf462088d13 1126 # menu in Eclipse, the contents of the directory containing the HTML and XML
markrad 0:cdf462088d13 1127 # files needs to be copied into the plugins directory of eclipse. The name of
markrad 0:cdf462088d13 1128 # the directory within the plugins directory should be the same as
markrad 0:cdf462088d13 1129 # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
markrad 0:cdf462088d13 1130 # the help appears.
markrad 0:cdf462088d13 1131
markrad 0:cdf462088d13 1132 GENERATE_ECLIPSEHELP = NO
markrad 0:cdf462088d13 1133
markrad 0:cdf462088d13 1134 # A unique identifier for the eclipse help plugin. When installing the plugin
markrad 0:cdf462088d13 1135 # the directory name containing the HTML and XML files should also have
markrad 0:cdf462088d13 1136 # this name.
markrad 0:cdf462088d13 1137
markrad 0:cdf462088d13 1138 ECLIPSE_DOC_ID = org.doxygen.Project
markrad 0:cdf462088d13 1139
markrad 0:cdf462088d13 1140 # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)
markrad 0:cdf462088d13 1141 # at top of each HTML page. The value NO (the default) enables the index and
markrad 0:cdf462088d13 1142 # the value YES disables it. Since the tabs have the same information as the
markrad 0:cdf462088d13 1143 # navigation tree you can set this option to NO if you already set
markrad 0:cdf462088d13 1144 # GENERATE_TREEVIEW to YES.
markrad 0:cdf462088d13 1145
markrad 0:cdf462088d13 1146 DISABLE_INDEX = NO
markrad 0:cdf462088d13 1147
markrad 0:cdf462088d13 1148 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
markrad 0:cdf462088d13 1149 # structure should be generated to display hierarchical information.
markrad 0:cdf462088d13 1150 # If the tag value is set to YES, a side panel will be generated
markrad 0:cdf462088d13 1151 # containing a tree-like index structure (just like the one that
markrad 0:cdf462088d13 1152 # is generated for HTML Help). For this to work a browser that supports
markrad 0:cdf462088d13 1153 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
markrad 0:cdf462088d13 1154 # Windows users are probably better off using the HTML help feature.
markrad 0:cdf462088d13 1155 # Since the tree basically has the same information as the tab index you
markrad 0:cdf462088d13 1156 # could consider to set DISABLE_INDEX to NO when enabling this option.
markrad 0:cdf462088d13 1157
markrad 0:cdf462088d13 1158 GENERATE_TREEVIEW = NO
markrad 0:cdf462088d13 1159
markrad 0:cdf462088d13 1160 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
markrad 0:cdf462088d13 1161 # (range [0,1..20]) that doxygen will group on one line in the generated HTML
markrad 0:cdf462088d13 1162 # documentation. Note that a value of 0 will completely suppress the enum
markrad 0:cdf462088d13 1163 # values from appearing in the overview section.
markrad 0:cdf462088d13 1164
markrad 0:cdf462088d13 1165 ENUM_VALUES_PER_LINE = 4
markrad 0:cdf462088d13 1166
markrad 0:cdf462088d13 1167 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
markrad 0:cdf462088d13 1168 # used to set the initial width (in pixels) of the frame in which the tree
markrad 0:cdf462088d13 1169 # is shown.
markrad 0:cdf462088d13 1170
markrad 0:cdf462088d13 1171 TREEVIEW_WIDTH = 250
markrad 0:cdf462088d13 1172
markrad 0:cdf462088d13 1173 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
markrad 0:cdf462088d13 1174 # links to external symbols imported via tag files in a separate window.
markrad 0:cdf462088d13 1175
markrad 0:cdf462088d13 1176 EXT_LINKS_IN_WINDOW = NO
markrad 0:cdf462088d13 1177
markrad 0:cdf462088d13 1178 # Use this tag to change the font size of Latex formulas included
markrad 0:cdf462088d13 1179 # as images in the HTML documentation. The default is 10. Note that
markrad 0:cdf462088d13 1180 # when you change the font size after a successful doxygen run you need
markrad 0:cdf462088d13 1181 # to manually remove any form_*.png images from the HTML output directory
markrad 0:cdf462088d13 1182 # to force them to be regenerated.
markrad 0:cdf462088d13 1183
markrad 0:cdf462088d13 1184 FORMULA_FONTSIZE = 10
markrad 0:cdf462088d13 1185
markrad 0:cdf462088d13 1186 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
markrad 0:cdf462088d13 1187 # generated for formulas are transparent PNGs. Transparent PNGs are
markrad 0:cdf462088d13 1188 # not supported properly for IE 6.0, but are supported on all modern browsers.
markrad 0:cdf462088d13 1189 # Note that when changing this option you need to delete any form_*.png files
markrad 0:cdf462088d13 1190 # in the HTML output before the changes have effect.
markrad 0:cdf462088d13 1191
markrad 0:cdf462088d13 1192 FORMULA_TRANSPARENT = YES
markrad 0:cdf462088d13 1193
markrad 0:cdf462088d13 1194 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
markrad 0:cdf462088d13 1195 # (see http://www.mathjax.org) which uses client side Javascript for the
markrad 0:cdf462088d13 1196 # rendering instead of using prerendered bitmaps. Use this if you do not
markrad 0:cdf462088d13 1197 # have LaTeX installed or if you want to formulas look prettier in the HTML
markrad 0:cdf462088d13 1198 # output. When enabled you may also need to install MathJax separately and
markrad 0:cdf462088d13 1199 # configure the path to it using the MATHJAX_RELPATH option.
markrad 0:cdf462088d13 1200
markrad 0:cdf462088d13 1201 USE_MATHJAX = NO
markrad 0:cdf462088d13 1202
markrad 0:cdf462088d13 1203 # When MathJax is enabled you can set the default output format to be used for
markrad 0:cdf462088d13 1204 # the MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and
markrad 0:cdf462088d13 1205 # SVG. The default value is HTML-CSS, which is slower, but has the best
markrad 0:cdf462088d13 1206 # compatibility.
markrad 0:cdf462088d13 1207
markrad 0:cdf462088d13 1208 MATHJAX_FORMAT = HTML-CSS
markrad 0:cdf462088d13 1209
markrad 0:cdf462088d13 1210 # When MathJax is enabled you need to specify the location relative to the
markrad 0:cdf462088d13 1211 # HTML output directory using the MATHJAX_RELPATH option. The destination
markrad 0:cdf462088d13 1212 # directory should contain the MathJax.js script. For instance, if the mathjax
markrad 0:cdf462088d13 1213 # directory is located at the same level as the HTML output directory, then
markrad 0:cdf462088d13 1214 # MATHJAX_RELPATH should be ../mathjax. The default value points to
markrad 0:cdf462088d13 1215 # the MathJax Content Delivery Network so you can quickly see the result without
markrad 0:cdf462088d13 1216 # installing MathJax.
markrad 0:cdf462088d13 1217 # However, it is strongly recommended to install a local
markrad 0:cdf462088d13 1218 # copy of MathJax from http://www.mathjax.org before deployment.
markrad 0:cdf462088d13 1219
markrad 0:cdf462088d13 1220 MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
markrad 0:cdf462088d13 1221
markrad 0:cdf462088d13 1222 # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
markrad 0:cdf462088d13 1223 # names that should be enabled during MathJax rendering.
markrad 0:cdf462088d13 1224
markrad 0:cdf462088d13 1225 MATHJAX_EXTENSIONS =
markrad 0:cdf462088d13 1226
markrad 0:cdf462088d13 1227 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript
markrad 0:cdf462088d13 1228 # pieces of code that will be used on startup of the MathJax code.
markrad 0:cdf462088d13 1229
markrad 0:cdf462088d13 1230 MATHJAX_CODEFILE =
markrad 0:cdf462088d13 1231
markrad 0:cdf462088d13 1232 # When the SEARCHENGINE tag is enabled doxygen will generate a search box
markrad 0:cdf462088d13 1233 # for the HTML output. The underlying search engine uses javascript
markrad 0:cdf462088d13 1234 # and DHTML and should work on any modern browser. Note that when using
markrad 0:cdf462088d13 1235 # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
markrad 0:cdf462088d13 1236 # (GENERATE_DOCSET) there is already a search function so this one should
markrad 0:cdf462088d13 1237 # typically be disabled. For large projects the javascript based search engine
markrad 0:cdf462088d13 1238 # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
markrad 0:cdf462088d13 1239
markrad 0:cdf462088d13 1240 SEARCHENGINE = NO
markrad 0:cdf462088d13 1241
markrad 0:cdf462088d13 1242 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
markrad 0:cdf462088d13 1243 # implemented using a web server instead of a web client using Javascript.
markrad 0:cdf462088d13 1244 # There are two flavours of web server based search depending on the
markrad 0:cdf462088d13 1245 # EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
markrad 0:cdf462088d13 1246 # searching and an index file used by the script. When EXTERNAL_SEARCH is
markrad 0:cdf462088d13 1247 # enabled the indexing and searching needs to be provided by external tools.
markrad 0:cdf462088d13 1248 # See the manual for details.
markrad 0:cdf462088d13 1249
markrad 0:cdf462088d13 1250 SERVER_BASED_SEARCH = NO
markrad 0:cdf462088d13 1251
markrad 0:cdf462088d13 1252 # When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP
markrad 0:cdf462088d13 1253 # script for searching. Instead the search results are written to an XML file
markrad 0:cdf462088d13 1254 # which needs to be processed by an external indexer. Doxygen will invoke an
markrad 0:cdf462088d13 1255 # external search engine pointed to by the SEARCHENGINE_URL option to obtain
markrad 0:cdf462088d13 1256 # the search results. Doxygen ships with an example indexer (doxyindexer) and
markrad 0:cdf462088d13 1257 # search engine (doxysearch.cgi) which are based on the open source search
markrad 0:cdf462088d13 1258 # engine library Xapian. See the manual for configuration details.
markrad 0:cdf462088d13 1259
markrad 0:cdf462088d13 1260 EXTERNAL_SEARCH = NO
markrad 0:cdf462088d13 1261
markrad 0:cdf462088d13 1262 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
markrad 0:cdf462088d13 1263 # which will returned the search results when EXTERNAL_SEARCH is enabled.
markrad 0:cdf462088d13 1264 # Doxygen ships with an example search engine (doxysearch) which is based on
markrad 0:cdf462088d13 1265 # the open source search engine library Xapian. See the manual for configuration
markrad 0:cdf462088d13 1266 # details.
markrad 0:cdf462088d13 1267
markrad 0:cdf462088d13 1268 SEARCHENGINE_URL =
markrad 0:cdf462088d13 1269
markrad 0:cdf462088d13 1270 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
markrad 0:cdf462088d13 1271 # search data is written to a file for indexing by an external tool. With the
markrad 0:cdf462088d13 1272 # SEARCHDATA_FILE tag the name of this file can be specified.
markrad 0:cdf462088d13 1273
markrad 0:cdf462088d13 1274 SEARCHDATA_FILE = searchdata.xml
markrad 0:cdf462088d13 1275
markrad 0:cdf462088d13 1276 # When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the
markrad 0:cdf462088d13 1277 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
markrad 0:cdf462088d13 1278 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
markrad 0:cdf462088d13 1279 # projects and redirect the results back to the right project.
markrad 0:cdf462088d13 1280
markrad 0:cdf462088d13 1281 EXTERNAL_SEARCH_ID =
markrad 0:cdf462088d13 1282
markrad 0:cdf462088d13 1283 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
markrad 0:cdf462088d13 1284 # projects other than the one defined by this configuration file, but that are
markrad 0:cdf462088d13 1285 # all added to the same external search index. Each project needs to have a
markrad 0:cdf462088d13 1286 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id
markrad 0:cdf462088d13 1287 # of to a relative location where the documentation can be found.
markrad 0:cdf462088d13 1288 # The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ...
markrad 0:cdf462088d13 1289
markrad 0:cdf462088d13 1290 EXTRA_SEARCH_MAPPINGS =
markrad 0:cdf462088d13 1291
markrad 0:cdf462088d13 1292 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1293 # configuration options related to the LaTeX output
markrad 0:cdf462088d13 1294 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1295
markrad 0:cdf462088d13 1296 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1297 # generate Latex output.
markrad 0:cdf462088d13 1298
markrad 0:cdf462088d13 1299 GENERATE_LATEX = NO
markrad 0:cdf462088d13 1300
markrad 0:cdf462088d13 1301 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
markrad 0:cdf462088d13 1302 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
markrad 0:cdf462088d13 1303 # put in front of it. If left blank `latex' will be used as the default path.
markrad 0:cdf462088d13 1304
markrad 0:cdf462088d13 1305 LATEX_OUTPUT = latex
markrad 0:cdf462088d13 1306
markrad 0:cdf462088d13 1307 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
markrad 0:cdf462088d13 1308 # invoked. If left blank `latex' will be used as the default command name.
markrad 0:cdf462088d13 1309 # Note that when enabling USE_PDFLATEX this option is only used for
markrad 0:cdf462088d13 1310 # generating bitmaps for formulas in the HTML output, but not in the
markrad 0:cdf462088d13 1311 # Makefile that is written to the output directory.
markrad 0:cdf462088d13 1312
markrad 0:cdf462088d13 1313 LATEX_CMD_NAME = latex
markrad 0:cdf462088d13 1314
markrad 0:cdf462088d13 1315 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
markrad 0:cdf462088d13 1316 # generate index for LaTeX. If left blank `makeindex' will be used as the
markrad 0:cdf462088d13 1317 # default command name.
markrad 0:cdf462088d13 1318
markrad 0:cdf462088d13 1319 MAKEINDEX_CMD_NAME = makeindex
markrad 0:cdf462088d13 1320
markrad 0:cdf462088d13 1321 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
markrad 0:cdf462088d13 1322 # LaTeX documents. This may be useful for small projects and may help to
markrad 0:cdf462088d13 1323 # save some trees in general.
markrad 0:cdf462088d13 1324
markrad 0:cdf462088d13 1325 COMPACT_LATEX = YES
markrad 0:cdf462088d13 1326
markrad 0:cdf462088d13 1327 # The PAPER_TYPE tag can be used to set the paper type that is used
markrad 0:cdf462088d13 1328 # by the printer. Possible values are: a4, letter, legal and
markrad 0:cdf462088d13 1329 # executive. If left blank a4 will be used.
markrad 0:cdf462088d13 1330
markrad 0:cdf462088d13 1331 PAPER_TYPE = a4wide
markrad 0:cdf462088d13 1332
markrad 0:cdf462088d13 1333 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
markrad 0:cdf462088d13 1334 # packages that should be included in the LaTeX output.
markrad 0:cdf462088d13 1335
markrad 0:cdf462088d13 1336 EXTRA_PACKAGES =
markrad 0:cdf462088d13 1337
markrad 0:cdf462088d13 1338 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
markrad 0:cdf462088d13 1339 # the generated latex document. The header should contain everything until
markrad 0:cdf462088d13 1340 # the first chapter. If it is left blank doxygen will generate a
markrad 0:cdf462088d13 1341 # standard header. Notice: only use this tag if you know what you are doing!
markrad 0:cdf462088d13 1342
markrad 0:cdf462088d13 1343 LATEX_HEADER =
markrad 0:cdf462088d13 1344
markrad 0:cdf462088d13 1345 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
markrad 0:cdf462088d13 1346 # the generated latex document. The footer should contain everything after
markrad 0:cdf462088d13 1347 # the last chapter. If it is left blank doxygen will generate a
markrad 0:cdf462088d13 1348 # standard footer. Notice: only use this tag if you know what you are doing!
markrad 0:cdf462088d13 1349
markrad 0:cdf462088d13 1350 LATEX_FOOTER =
markrad 0:cdf462088d13 1351
markrad 0:cdf462088d13 1352 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images
markrad 0:cdf462088d13 1353 # or other source files which should be copied to the LaTeX output directory.
markrad 0:cdf462088d13 1354 # Note that the files will be copied as-is; there are no commands or markers
markrad 0:cdf462088d13 1355 # available.
markrad 0:cdf462088d13 1356
markrad 0:cdf462088d13 1357 LATEX_EXTRA_FILES =
markrad 0:cdf462088d13 1358
markrad 0:cdf462088d13 1359 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
markrad 0:cdf462088d13 1360 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
markrad 0:cdf462088d13 1361 # contain links (just like the HTML output) instead of page references
markrad 0:cdf462088d13 1362 # This makes the output suitable for online browsing using a pdf viewer.
markrad 0:cdf462088d13 1363
markrad 0:cdf462088d13 1364 PDF_HYPERLINKS = YES
markrad 0:cdf462088d13 1365
markrad 0:cdf462088d13 1366 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
markrad 0:cdf462088d13 1367 # plain latex in the generated Makefile. Set this option to YES to get a
markrad 0:cdf462088d13 1368 # higher quality PDF documentation.
markrad 0:cdf462088d13 1369
markrad 0:cdf462088d13 1370 USE_PDFLATEX = YES
markrad 0:cdf462088d13 1371
markrad 0:cdf462088d13 1372 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
markrad 0:cdf462088d13 1373 # command to the generated LaTeX files. This will instruct LaTeX to keep
markrad 0:cdf462088d13 1374 # running if errors occur, instead of asking the user for help.
markrad 0:cdf462088d13 1375 # This option is also used when generating formulas in HTML.
markrad 0:cdf462088d13 1376
markrad 0:cdf462088d13 1377 LATEX_BATCHMODE = NO
markrad 0:cdf462088d13 1378
markrad 0:cdf462088d13 1379 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
markrad 0:cdf462088d13 1380 # include the index chapters (such as File Index, Compound Index, etc.)
markrad 0:cdf462088d13 1381 # in the output.
markrad 0:cdf462088d13 1382
markrad 0:cdf462088d13 1383 LATEX_HIDE_INDICES = NO
markrad 0:cdf462088d13 1384
markrad 0:cdf462088d13 1385 # If LATEX_SOURCE_CODE is set to YES then doxygen will include
markrad 0:cdf462088d13 1386 # source code with syntax highlighting in the LaTeX output.
markrad 0:cdf462088d13 1387 # Note that which sources are shown also depends on other settings
markrad 0:cdf462088d13 1388 # such as SOURCE_BROWSER.
markrad 0:cdf462088d13 1389
markrad 0:cdf462088d13 1390 LATEX_SOURCE_CODE = NO
markrad 0:cdf462088d13 1391
markrad 0:cdf462088d13 1392 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
markrad 0:cdf462088d13 1393 # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
markrad 0:cdf462088d13 1394 # http://en.wikipedia.org/wiki/BibTeX for more info.
markrad 0:cdf462088d13 1395
markrad 0:cdf462088d13 1396 LATEX_BIB_STYLE = plain
markrad 0:cdf462088d13 1397
markrad 0:cdf462088d13 1398 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1399 # configuration options related to the RTF output
markrad 0:cdf462088d13 1400 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1401
markrad 0:cdf462088d13 1402 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
markrad 0:cdf462088d13 1403 # The RTF output is optimized for Word 97 and may not look very pretty with
markrad 0:cdf462088d13 1404 # other RTF readers or editors.
markrad 0:cdf462088d13 1405
markrad 0:cdf462088d13 1406 GENERATE_RTF = NO
markrad 0:cdf462088d13 1407
markrad 0:cdf462088d13 1408 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
markrad 0:cdf462088d13 1409 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
markrad 0:cdf462088d13 1410 # put in front of it. If left blank `rtf' will be used as the default path.
markrad 0:cdf462088d13 1411
markrad 0:cdf462088d13 1412 RTF_OUTPUT = rtf
markrad 0:cdf462088d13 1413
markrad 0:cdf462088d13 1414 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
markrad 0:cdf462088d13 1415 # RTF documents. This may be useful for small projects and may help to
markrad 0:cdf462088d13 1416 # save some trees in general.
markrad 0:cdf462088d13 1417
markrad 0:cdf462088d13 1418 COMPACT_RTF = NO
markrad 0:cdf462088d13 1419
markrad 0:cdf462088d13 1420 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
markrad 0:cdf462088d13 1421 # will contain hyperlink fields. The RTF file will
markrad 0:cdf462088d13 1422 # contain links (just like the HTML output) instead of page references.
markrad 0:cdf462088d13 1423 # This makes the output suitable for online browsing using WORD or other
markrad 0:cdf462088d13 1424 # programs which support those fields.
markrad 0:cdf462088d13 1425 # Note: wordpad (write) and others do not support links.
markrad 0:cdf462088d13 1426
markrad 0:cdf462088d13 1427 RTF_HYPERLINKS = NO
markrad 0:cdf462088d13 1428
markrad 0:cdf462088d13 1429 # Load style sheet definitions from file. Syntax is similar to doxygen's
markrad 0:cdf462088d13 1430 # config file, i.e. a series of assignments. You only have to provide
markrad 0:cdf462088d13 1431 # replacements, missing definitions are set to their default value.
markrad 0:cdf462088d13 1432
markrad 0:cdf462088d13 1433 RTF_STYLESHEET_FILE =
markrad 0:cdf462088d13 1434
markrad 0:cdf462088d13 1435 # Set optional variables used in the generation of an rtf document.
markrad 0:cdf462088d13 1436 # Syntax is similar to doxygen's config file.
markrad 0:cdf462088d13 1437
markrad 0:cdf462088d13 1438 RTF_EXTENSIONS_FILE =
markrad 0:cdf462088d13 1439
markrad 0:cdf462088d13 1440 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1441 # configuration options related to the man page output
markrad 0:cdf462088d13 1442 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1443
markrad 0:cdf462088d13 1444 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1445 # generate man pages
markrad 0:cdf462088d13 1446
markrad 0:cdf462088d13 1447 GENERATE_MAN = NO
markrad 0:cdf462088d13 1448
markrad 0:cdf462088d13 1449 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
markrad 0:cdf462088d13 1450 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
markrad 0:cdf462088d13 1451 # put in front of it. If left blank `man' will be used as the default path.
markrad 0:cdf462088d13 1452
markrad 0:cdf462088d13 1453 MAN_OUTPUT = man
markrad 0:cdf462088d13 1454
markrad 0:cdf462088d13 1455 # The MAN_EXTENSION tag determines the extension that is added to
markrad 0:cdf462088d13 1456 # the generated man pages (default is the subroutine's section .3)
markrad 0:cdf462088d13 1457
markrad 0:cdf462088d13 1458 MAN_EXTENSION = .3
markrad 0:cdf462088d13 1459
markrad 0:cdf462088d13 1460 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
markrad 0:cdf462088d13 1461 # then it will generate one additional man file for each entity
markrad 0:cdf462088d13 1462 # documented in the real man page(s). These additional files
markrad 0:cdf462088d13 1463 # only source the real man page, but without them the man command
markrad 0:cdf462088d13 1464 # would be unable to find the correct page. The default is NO.
markrad 0:cdf462088d13 1465
markrad 0:cdf462088d13 1466 MAN_LINKS = NO
markrad 0:cdf462088d13 1467
markrad 0:cdf462088d13 1468 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1469 # configuration options related to the XML output
markrad 0:cdf462088d13 1470 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1471
markrad 0:cdf462088d13 1472 # If the GENERATE_XML tag is set to YES Doxygen will
markrad 0:cdf462088d13 1473 # generate an XML file that captures the structure of
markrad 0:cdf462088d13 1474 # the code including all documentation.
markrad 0:cdf462088d13 1475
markrad 0:cdf462088d13 1476 GENERATE_XML = NO
markrad 0:cdf462088d13 1477
markrad 0:cdf462088d13 1478 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
markrad 0:cdf462088d13 1479 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
markrad 0:cdf462088d13 1480 # put in front of it. If left blank `xml' will be used as the default path.
markrad 0:cdf462088d13 1481
markrad 0:cdf462088d13 1482 XML_OUTPUT = xml
markrad 0:cdf462088d13 1483
markrad 0:cdf462088d13 1484 # The XML_SCHEMA tag can be used to specify an XML schema,
markrad 0:cdf462088d13 1485 # which can be used by a validating XML parser to check the
markrad 0:cdf462088d13 1486 # syntax of the XML files.
markrad 0:cdf462088d13 1487
markrad 0:cdf462088d13 1488 #XML_SCHEMA =
markrad 0:cdf462088d13 1489
markrad 0:cdf462088d13 1490 # The XML_DTD tag can be used to specify an XML DTD,
markrad 0:cdf462088d13 1491 # which can be used by a validating XML parser to check the
markrad 0:cdf462088d13 1492 # syntax of the XML files.
markrad 0:cdf462088d13 1493
markrad 0:cdf462088d13 1494 #XML_DTD =
markrad 0:cdf462088d13 1495
markrad 0:cdf462088d13 1496 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
markrad 0:cdf462088d13 1497 # dump the program listings (including syntax highlighting
markrad 0:cdf462088d13 1498 # and cross-referencing information) to the XML output. Note that
markrad 0:cdf462088d13 1499 # enabling this will significantly increase the size of the XML output.
markrad 0:cdf462088d13 1500
markrad 0:cdf462088d13 1501 XML_PROGRAMLISTING = YES
markrad 0:cdf462088d13 1502
markrad 0:cdf462088d13 1503 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1504 # configuration options related to the DOCBOOK output
markrad 0:cdf462088d13 1505 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1506
markrad 0:cdf462088d13 1507 # If the GENERATE_DOCBOOK tag is set to YES Doxygen will generate DOCBOOK files
markrad 0:cdf462088d13 1508 # that can be used to generate PDF.
markrad 0:cdf462088d13 1509
markrad 0:cdf462088d13 1510 GENERATE_DOCBOOK = NO
markrad 0:cdf462088d13 1511
markrad 0:cdf462088d13 1512 # The DOCBOOK_OUTPUT tag is used to specify where the DOCBOOK pages will be put.
markrad 0:cdf462088d13 1513 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
markrad 0:cdf462088d13 1514 # front of it. If left blank docbook will be used as the default path.
markrad 0:cdf462088d13 1515
markrad 0:cdf462088d13 1516 DOCBOOK_OUTPUT = docbook
markrad 0:cdf462088d13 1517
markrad 0:cdf462088d13 1518 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1519 # configuration options for the AutoGen Definitions output
markrad 0:cdf462088d13 1520 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1521
markrad 0:cdf462088d13 1522 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
markrad 0:cdf462088d13 1523 # generate an AutoGen Definitions (see autogen.sf.net) file
markrad 0:cdf462088d13 1524 # that captures the structure of the code including all
markrad 0:cdf462088d13 1525 # documentation. Note that this feature is still experimental
markrad 0:cdf462088d13 1526 # and incomplete at the moment.
markrad 0:cdf462088d13 1527
markrad 0:cdf462088d13 1528 GENERATE_AUTOGEN_DEF = NO
markrad 0:cdf462088d13 1529
markrad 0:cdf462088d13 1530 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1531 # configuration options related to the Perl module output
markrad 0:cdf462088d13 1532 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1533
markrad 0:cdf462088d13 1534 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
markrad 0:cdf462088d13 1535 # generate a Perl module file that captures the structure of
markrad 0:cdf462088d13 1536 # the code including all documentation. Note that this
markrad 0:cdf462088d13 1537 # feature is still experimental and incomplete at the
markrad 0:cdf462088d13 1538 # moment.
markrad 0:cdf462088d13 1539
markrad 0:cdf462088d13 1540 GENERATE_PERLMOD = NO
markrad 0:cdf462088d13 1541
markrad 0:cdf462088d13 1542 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
markrad 0:cdf462088d13 1543 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
markrad 0:cdf462088d13 1544 # to generate PDF and DVI output from the Perl module output.
markrad 0:cdf462088d13 1545
markrad 0:cdf462088d13 1546 PERLMOD_LATEX = NO
markrad 0:cdf462088d13 1547
markrad 0:cdf462088d13 1548 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
markrad 0:cdf462088d13 1549 # nicely formatted so it can be parsed by a human reader.
markrad 0:cdf462088d13 1550 # This is useful
markrad 0:cdf462088d13 1551 # if you want to understand what is going on.
markrad 0:cdf462088d13 1552 # On the other hand, if this
markrad 0:cdf462088d13 1553 # tag is set to NO the size of the Perl module output will be much smaller
markrad 0:cdf462088d13 1554 # and Perl will parse it just the same.
markrad 0:cdf462088d13 1555
markrad 0:cdf462088d13 1556 PERLMOD_PRETTY = YES
markrad 0:cdf462088d13 1557
markrad 0:cdf462088d13 1558 # The names of the make variables in the generated doxyrules.make file
markrad 0:cdf462088d13 1559 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
markrad 0:cdf462088d13 1560 # This is useful so different doxyrules.make files included by the same
markrad 0:cdf462088d13 1561 # Makefile don't overwrite each other's variables.
markrad 0:cdf462088d13 1562
markrad 0:cdf462088d13 1563 PERLMOD_MAKEVAR_PREFIX =
markrad 0:cdf462088d13 1564
markrad 0:cdf462088d13 1565 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1566 # Configuration options related to the preprocessor
markrad 0:cdf462088d13 1567 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1568
markrad 0:cdf462088d13 1569 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1570 # evaluate all C-preprocessor directives found in the sources and include
markrad 0:cdf462088d13 1571 # files.
markrad 0:cdf462088d13 1572
markrad 0:cdf462088d13 1573 ENABLE_PREPROCESSING = YES
markrad 0:cdf462088d13 1574
markrad 0:cdf462088d13 1575 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
markrad 0:cdf462088d13 1576 # names in the source code. If set to NO (the default) only conditional
markrad 0:cdf462088d13 1577 # compilation will be performed. Macro expansion can be done in a controlled
markrad 0:cdf462088d13 1578 # way by setting EXPAND_ONLY_PREDEF to YES.
markrad 0:cdf462088d13 1579
markrad 0:cdf462088d13 1580 MACRO_EXPANSION = NO
markrad 0:cdf462088d13 1581
markrad 0:cdf462088d13 1582 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
markrad 0:cdf462088d13 1583 # then the macro expansion is limited to the macros specified with the
markrad 0:cdf462088d13 1584 # PREDEFINED and EXPAND_AS_DEFINED tags.
markrad 0:cdf462088d13 1585
markrad 0:cdf462088d13 1586 EXPAND_ONLY_PREDEF = NO
markrad 0:cdf462088d13 1587
markrad 0:cdf462088d13 1588 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
markrad 0:cdf462088d13 1589 # pointed to by INCLUDE_PATH will be searched when a #include is found.
markrad 0:cdf462088d13 1590
markrad 0:cdf462088d13 1591 SEARCH_INCLUDES = YES
markrad 0:cdf462088d13 1592
markrad 0:cdf462088d13 1593 # The INCLUDE_PATH tag can be used to specify one or more directories that
markrad 0:cdf462088d13 1594 # contain include files that are not input files but should be processed by
markrad 0:cdf462088d13 1595 # the preprocessor.
markrad 0:cdf462088d13 1596
markrad 0:cdf462088d13 1597 INCLUDE_PATH =
markrad 0:cdf462088d13 1598
markrad 0:cdf462088d13 1599 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
markrad 0:cdf462088d13 1600 # patterns (like *.h and *.hpp) to filter out the header-files in the
markrad 0:cdf462088d13 1601 # directories. If left blank, the patterns specified with FILE_PATTERNS will
markrad 0:cdf462088d13 1602 # be used.
markrad 0:cdf462088d13 1603
markrad 0:cdf462088d13 1604 INCLUDE_FILE_PATTERNS =
markrad 0:cdf462088d13 1605
markrad 0:cdf462088d13 1606 # The PREDEFINED tag can be used to specify one or more macro names that
markrad 0:cdf462088d13 1607 # are defined before the preprocessor is started (similar to the -D option of
markrad 0:cdf462088d13 1608 # gcc). The argument of the tag is a list of macros of the form: name
markrad 0:cdf462088d13 1609 # or name=definition (no spaces). If the definition and the = are
markrad 0:cdf462088d13 1610 # omitted =1 is assumed. To prevent a macro definition from being
markrad 0:cdf462088d13 1611 # undefined via #undef or recursively expanded use the := operator
markrad 0:cdf462088d13 1612 # instead of the = operator.
markrad 0:cdf462088d13 1613
markrad 0:cdf462088d13 1614 PREDEFINED = WIN32 \
markrad 0:cdf462088d13 1615 NTLM \
markrad 0:cdf462088d13 1616 USE_LZO \
markrad 0:cdf462088d13 1617 ENABLE_FRAGMENT \
markrad 0:cdf462088d13 1618 P2MP \
markrad 0:cdf462088d13 1619 P2MP_SERVER \
markrad 0:cdf462088d13 1620 USE_CRYPTO \
markrad 0:cdf462088d13 1621 USE_SSL \
markrad 0:cdf462088d13 1622 ENABLE_PLUGIN \
markrad 0:cdf462088d13 1623 ENABLE_MANAGEMENT \
markrad 0:cdf462088d13 1624 ENABLE_OCC \
markrad 0:cdf462088d13 1625 HAVE_GETTIMEOFDAY
markrad 0:cdf462088d13 1626
markrad 0:cdf462088d13 1627 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
markrad 0:cdf462088d13 1628 # this tag can be used to specify a list of macro names that should be expanded.
markrad 0:cdf462088d13 1629 # The macro definition that is found in the sources will be used.
markrad 0:cdf462088d13 1630 # Use the PREDEFINED tag if you want to use a different macro definition that
markrad 0:cdf462088d13 1631 # overrules the definition found in the source code.
markrad 0:cdf462088d13 1632
markrad 0:cdf462088d13 1633 EXPAND_AS_DEFINED =
markrad 0:cdf462088d13 1634
markrad 0:cdf462088d13 1635 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
markrad 0:cdf462088d13 1636 # doxygen's preprocessor will remove all references to function-like macros
markrad 0:cdf462088d13 1637 # that are alone on a line, have an all uppercase name, and do not end with a
markrad 0:cdf462088d13 1638 # semicolon, because these will confuse the parser if not removed.
markrad 0:cdf462088d13 1639
markrad 0:cdf462088d13 1640 SKIP_FUNCTION_MACROS = YES
markrad 0:cdf462088d13 1641
markrad 0:cdf462088d13 1642 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1643 # Configuration::additions related to external references
markrad 0:cdf462088d13 1644 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1645
markrad 0:cdf462088d13 1646 # The TAGFILES option can be used to specify one or more tagfiles. For each
markrad 0:cdf462088d13 1647 # tag file the location of the external documentation should be added. The
markrad 0:cdf462088d13 1648 # format of a tag file without this location is as follows:
markrad 0:cdf462088d13 1649 #
markrad 0:cdf462088d13 1650 # TAGFILES = file1 file2 ...
markrad 0:cdf462088d13 1651 # Adding location for the tag files is done as follows:
markrad 0:cdf462088d13 1652 #
markrad 0:cdf462088d13 1653 # TAGFILES = file1=loc1 "file2 = loc2" ...
markrad 0:cdf462088d13 1654 # where "loc1" and "loc2" can be relative or absolute paths
markrad 0:cdf462088d13 1655 # or URLs. Note that each tag file must have a unique name (where the name does
markrad 0:cdf462088d13 1656 # NOT include the path). If a tag file is not located in the directory in which
markrad 0:cdf462088d13 1657 # doxygen is run, you must also specify the path to the tagfile here.
markrad 0:cdf462088d13 1658
markrad 0:cdf462088d13 1659 TAGFILES =
markrad 0:cdf462088d13 1660
markrad 0:cdf462088d13 1661 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
markrad 0:cdf462088d13 1662 # a tag file that is based on the input files it reads.
markrad 0:cdf462088d13 1663
markrad 0:cdf462088d13 1664 GENERATE_TAGFILE =
markrad 0:cdf462088d13 1665
markrad 0:cdf462088d13 1666 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
markrad 0:cdf462088d13 1667 # in the class index. If set to NO only the inherited external classes
markrad 0:cdf462088d13 1668 # will be listed.
markrad 0:cdf462088d13 1669
markrad 0:cdf462088d13 1670 ALLEXTERNALS = NO
markrad 0:cdf462088d13 1671
markrad 0:cdf462088d13 1672 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
markrad 0:cdf462088d13 1673 # in the modules index. If set to NO, only the current project's groups will
markrad 0:cdf462088d13 1674 # be listed.
markrad 0:cdf462088d13 1675
markrad 0:cdf462088d13 1676 EXTERNAL_GROUPS = YES
markrad 0:cdf462088d13 1677
markrad 0:cdf462088d13 1678 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed
markrad 0:cdf462088d13 1679 # in the related pages index. If set to NO, only the current project's
markrad 0:cdf462088d13 1680 # pages will be listed.
markrad 0:cdf462088d13 1681
markrad 0:cdf462088d13 1682 EXTERNAL_PAGES = YES
markrad 0:cdf462088d13 1683
markrad 0:cdf462088d13 1684 # The PERL_PATH should be the absolute path and name of the perl script
markrad 0:cdf462088d13 1685 # interpreter (i.e. the result of `which perl').
markrad 0:cdf462088d13 1686
markrad 0:cdf462088d13 1687 PERL_PATH = /usr/bin/perl
markrad 0:cdf462088d13 1688
markrad 0:cdf462088d13 1689 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1690 # Configuration options related to the dot tool
markrad 0:cdf462088d13 1691 #---------------------------------------------------------------------------
markrad 0:cdf462088d13 1692
markrad 0:cdf462088d13 1693 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1694 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
markrad 0:cdf462088d13 1695 # or super classes. Setting the tag to NO turns the diagrams off. Note that
markrad 0:cdf462088d13 1696 # this option also works with HAVE_DOT disabled, but it is recommended to
markrad 0:cdf462088d13 1697 # install and use dot, since it yields more powerful graphs.
markrad 0:cdf462088d13 1698
markrad 0:cdf462088d13 1699 CLASS_DIAGRAMS = NO
markrad 0:cdf462088d13 1700
markrad 0:cdf462088d13 1701 # You can define message sequence charts within doxygen comments using the \msc
markrad 0:cdf462088d13 1702 # command. Doxygen will then run the mscgen tool (see
markrad 0:cdf462088d13 1703 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
markrad 0:cdf462088d13 1704 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
markrad 0:cdf462088d13 1705 # the mscgen tool resides. If left empty the tool is assumed to be found in the
markrad 0:cdf462088d13 1706 # default search path.
markrad 0:cdf462088d13 1707
markrad 0:cdf462088d13 1708 MSCGEN_PATH =
markrad 0:cdf462088d13 1709
markrad 0:cdf462088d13 1710 # If set to YES, the inheritance and collaboration graphs will hide
markrad 0:cdf462088d13 1711 # inheritance and usage relations if the target is undocumented
markrad 0:cdf462088d13 1712 # or is not a class.
markrad 0:cdf462088d13 1713
markrad 0:cdf462088d13 1714 HIDE_UNDOC_RELATIONS = YES
markrad 0:cdf462088d13 1715
markrad 0:cdf462088d13 1716 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
markrad 0:cdf462088d13 1717 # available from the path. This tool is part of Graphviz, a graph visualization
markrad 0:cdf462088d13 1718 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
markrad 0:cdf462088d13 1719 # have no effect if this option is set to NO (the default)
markrad 0:cdf462088d13 1720
markrad 0:cdf462088d13 1721 HAVE_DOT = YES
markrad 0:cdf462088d13 1722
markrad 0:cdf462088d13 1723 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
markrad 0:cdf462088d13 1724 # allowed to run in parallel. When set to 0 (the default) doxygen will
markrad 0:cdf462088d13 1725 # base this on the number of processors available in the system. You can set it
markrad 0:cdf462088d13 1726 # explicitly to a value larger than 0 to get control over the balance
markrad 0:cdf462088d13 1727 # between CPU load and processing speed.
markrad 0:cdf462088d13 1728
markrad 0:cdf462088d13 1729 DOT_NUM_THREADS = 0
markrad 0:cdf462088d13 1730
markrad 0:cdf462088d13 1731 # By default doxygen will use the Helvetica font for all dot files that
markrad 0:cdf462088d13 1732 # doxygen generates. When you want a differently looking font you can specify
markrad 0:cdf462088d13 1733 # the font name using DOT_FONTNAME. You need to make sure dot is able to find
markrad 0:cdf462088d13 1734 # the font, which can be done by putting it in a standard location or by setting
markrad 0:cdf462088d13 1735 # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
markrad 0:cdf462088d13 1736 # directory containing the font.
markrad 0:cdf462088d13 1737
markrad 0:cdf462088d13 1738 DOT_FONTNAME = Helvetica
markrad 0:cdf462088d13 1739
markrad 0:cdf462088d13 1740 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
markrad 0:cdf462088d13 1741 # The default size is 10pt.
markrad 0:cdf462088d13 1742
markrad 0:cdf462088d13 1743 DOT_FONTSIZE = 10
markrad 0:cdf462088d13 1744
markrad 0:cdf462088d13 1745 # By default doxygen will tell dot to use the Helvetica font.
markrad 0:cdf462088d13 1746 # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
markrad 0:cdf462088d13 1747 # set the path where dot can find it.
markrad 0:cdf462088d13 1748
markrad 0:cdf462088d13 1749 DOT_FONTPATH =
markrad 0:cdf462088d13 1750
markrad 0:cdf462088d13 1751 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
markrad 0:cdf462088d13 1752 # will generate a graph for each documented class showing the direct and
markrad 0:cdf462088d13 1753 # indirect inheritance relations. Setting this tag to YES will force the
markrad 0:cdf462088d13 1754 # CLASS_DIAGRAMS tag to NO.
markrad 0:cdf462088d13 1755
markrad 0:cdf462088d13 1756 CLASS_GRAPH = YES
markrad 0:cdf462088d13 1757
markrad 0:cdf462088d13 1758 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
markrad 0:cdf462088d13 1759 # will generate a graph for each documented class showing the direct and
markrad 0:cdf462088d13 1760 # indirect implementation dependencies (inheritance, containment, and
markrad 0:cdf462088d13 1761 # class references variables) of the class with other documented classes.
markrad 0:cdf462088d13 1762
markrad 0:cdf462088d13 1763 COLLABORATION_GRAPH = YES
markrad 0:cdf462088d13 1764
markrad 0:cdf462088d13 1765 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
markrad 0:cdf462088d13 1766 # will generate a graph for groups, showing the direct groups dependencies
markrad 0:cdf462088d13 1767
markrad 0:cdf462088d13 1768 GROUP_GRAPHS = YES
markrad 0:cdf462088d13 1769
markrad 0:cdf462088d13 1770 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
markrad 0:cdf462088d13 1771 # collaboration diagrams in a style similar to the OMG's Unified Modeling
markrad 0:cdf462088d13 1772 # Language.
markrad 0:cdf462088d13 1773
markrad 0:cdf462088d13 1774 UML_LOOK = NO
markrad 0:cdf462088d13 1775
markrad 0:cdf462088d13 1776 # If the UML_LOOK tag is enabled, the fields and methods are shown inside
markrad 0:cdf462088d13 1777 # the class node. If there are many fields or methods and many nodes the
markrad 0:cdf462088d13 1778 # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS
markrad 0:cdf462088d13 1779 # threshold limits the number of items for each type to make the size more
markrad 0:cdf462088d13 1780 # manageable. Set this to 0 for no limit. Note that the threshold may be
markrad 0:cdf462088d13 1781 # exceeded by 50% before the limit is enforced.
markrad 0:cdf462088d13 1782
markrad 0:cdf462088d13 1783 UML_LIMIT_NUM_FIELDS = 10
markrad 0:cdf462088d13 1784
markrad 0:cdf462088d13 1785 # If set to YES, the inheritance and collaboration graphs will show the
markrad 0:cdf462088d13 1786 # relations between templates and their instances.
markrad 0:cdf462088d13 1787
markrad 0:cdf462088d13 1788 TEMPLATE_RELATIONS = NO
markrad 0:cdf462088d13 1789
markrad 0:cdf462088d13 1790 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
markrad 0:cdf462088d13 1791 # tags are set to YES then doxygen will generate a graph for each documented
markrad 0:cdf462088d13 1792 # file showing the direct and indirect include dependencies of the file with
markrad 0:cdf462088d13 1793 # other documented files.
markrad 0:cdf462088d13 1794
markrad 0:cdf462088d13 1795 INCLUDE_GRAPH = YES
markrad 0:cdf462088d13 1796
markrad 0:cdf462088d13 1797 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
markrad 0:cdf462088d13 1798 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
markrad 0:cdf462088d13 1799 # documented header file showing the documented files that directly or
markrad 0:cdf462088d13 1800 # indirectly include this file.
markrad 0:cdf462088d13 1801
markrad 0:cdf462088d13 1802 INCLUDED_BY_GRAPH = YES
markrad 0:cdf462088d13 1803
markrad 0:cdf462088d13 1804 # If the CALL_GRAPH and HAVE_DOT options are set to YES then
markrad 0:cdf462088d13 1805 # doxygen will generate a call dependency graph for every global function
markrad 0:cdf462088d13 1806 # or class method. Note that enabling this option will significantly increase
markrad 0:cdf462088d13 1807 # the time of a run. So in most cases it will be better to enable call graphs
markrad 0:cdf462088d13 1808 # for selected functions only using the \callgraph command.
markrad 0:cdf462088d13 1809
markrad 0:cdf462088d13 1810 CALL_GRAPH = NO
markrad 0:cdf462088d13 1811
markrad 0:cdf462088d13 1812 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
markrad 0:cdf462088d13 1813 # doxygen will generate a caller dependency graph for every global function
markrad 0:cdf462088d13 1814 # or class method. Note that enabling this option will significantly increase
markrad 0:cdf462088d13 1815 # the time of a run. So in most cases it will be better to enable caller
markrad 0:cdf462088d13 1816 # graphs for selected functions only using the \callergraph command.
markrad 0:cdf462088d13 1817
markrad 0:cdf462088d13 1818 CALLER_GRAPH = NO
markrad 0:cdf462088d13 1819
markrad 0:cdf462088d13 1820 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
markrad 0:cdf462088d13 1821 # will generate a graphical hierarchy of all classes instead of a textual one.
markrad 0:cdf462088d13 1822
markrad 0:cdf462088d13 1823 GRAPHICAL_HIERARCHY = YES
markrad 0:cdf462088d13 1824
markrad 0:cdf462088d13 1825 # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES
markrad 0:cdf462088d13 1826 # then doxygen will show the dependencies a directory has on other directories
markrad 0:cdf462088d13 1827 # in a graphical way. The dependency relations are determined by the #include
markrad 0:cdf462088d13 1828 # relations between the files in the directories.
markrad 0:cdf462088d13 1829
markrad 0:cdf462088d13 1830 DIRECTORY_GRAPH = YES
markrad 0:cdf462088d13 1831
markrad 0:cdf462088d13 1832 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
markrad 0:cdf462088d13 1833 # generated by dot. Possible values are svg, png, jpg, or gif.
markrad 0:cdf462088d13 1834 # If left blank png will be used. If you choose svg you need to set
markrad 0:cdf462088d13 1835 # HTML_FILE_EXTENSION to xhtml in order to make the SVG files
markrad 0:cdf462088d13 1836 # visible in IE 9+ (other browsers do not have this requirement).
markrad 0:cdf462088d13 1837
markrad 0:cdf462088d13 1838 DOT_IMAGE_FORMAT = png
markrad 0:cdf462088d13 1839
markrad 0:cdf462088d13 1840 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
markrad 0:cdf462088d13 1841 # enable generation of interactive SVG images that allow zooming and panning.
markrad 0:cdf462088d13 1842 # Note that this requires a modern browser other than Internet Explorer.
markrad 0:cdf462088d13 1843 # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
markrad 0:cdf462088d13 1844 # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
markrad 0:cdf462088d13 1845 # visible. Older versions of IE do not have SVG support.
markrad 0:cdf462088d13 1846
markrad 0:cdf462088d13 1847 INTERACTIVE_SVG = NO
markrad 0:cdf462088d13 1848
markrad 0:cdf462088d13 1849 # The tag DOT_PATH can be used to specify the path where the dot tool can be
markrad 0:cdf462088d13 1850 # found. If left blank, it is assumed the dot tool can be found in the path.
markrad 0:cdf462088d13 1851
markrad 0:cdf462088d13 1852 DOT_PATH =
markrad 0:cdf462088d13 1853
markrad 0:cdf462088d13 1854 # The DOTFILE_DIRS tag can be used to specify one or more directories that
markrad 0:cdf462088d13 1855 # contain dot files that are included in the documentation (see the
markrad 0:cdf462088d13 1856 # \dotfile command).
markrad 0:cdf462088d13 1857
markrad 0:cdf462088d13 1858 DOTFILE_DIRS =
markrad 0:cdf462088d13 1859
markrad 0:cdf462088d13 1860 # The MSCFILE_DIRS tag can be used to specify one or more directories that
markrad 0:cdf462088d13 1861 # contain msc files that are included in the documentation (see the
markrad 0:cdf462088d13 1862 # \mscfile command).
markrad 0:cdf462088d13 1863
markrad 0:cdf462088d13 1864 MSCFILE_DIRS =
markrad 0:cdf462088d13 1865
markrad 0:cdf462088d13 1866 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
markrad 0:cdf462088d13 1867 # nodes that will be shown in the graph. If the number of nodes in a graph
markrad 0:cdf462088d13 1868 # becomes larger than this value, doxygen will truncate the graph, which is
markrad 0:cdf462088d13 1869 # visualized by representing a node as a red box. Note that doxygen if the
markrad 0:cdf462088d13 1870 # number of direct children of the root node in a graph is already larger than
markrad 0:cdf462088d13 1871 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
markrad 0:cdf462088d13 1872 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
markrad 0:cdf462088d13 1873
markrad 0:cdf462088d13 1874 DOT_GRAPH_MAX_NODES = 200
markrad 0:cdf462088d13 1875
markrad 0:cdf462088d13 1876 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
markrad 0:cdf462088d13 1877 # graphs generated by dot. A depth value of 3 means that only nodes reachable
markrad 0:cdf462088d13 1878 # from the root by following a path via at most 3 edges will be shown. Nodes
markrad 0:cdf462088d13 1879 # that lay further from the root node will be omitted. Note that setting this
markrad 0:cdf462088d13 1880 # option to 1 or 2 may greatly reduce the computation time needed for large
markrad 0:cdf462088d13 1881 # code bases. Also note that the size of a graph can be further restricted by
markrad 0:cdf462088d13 1882 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
markrad 0:cdf462088d13 1883
markrad 0:cdf462088d13 1884 MAX_DOT_GRAPH_DEPTH = 1000
markrad 0:cdf462088d13 1885
markrad 0:cdf462088d13 1886 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
markrad 0:cdf462088d13 1887 # background. This is disabled by default, because dot on Windows does not
markrad 0:cdf462088d13 1888 # seem to support this out of the box. Warning: Depending on the platform used,
markrad 0:cdf462088d13 1889 # enabling this option may lead to badly anti-aliased labels on the edges of
markrad 0:cdf462088d13 1890 # a graph (i.e. they become hard to read).
markrad 0:cdf462088d13 1891
markrad 0:cdf462088d13 1892 DOT_TRANSPARENT = YES
markrad 0:cdf462088d13 1893
markrad 0:cdf462088d13 1894 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
markrad 0:cdf462088d13 1895 # files in one run (i.e. multiple -o and -T options on the command line). This
markrad 0:cdf462088d13 1896 # makes dot run faster, but since only newer versions of dot (>1.8.10)
markrad 0:cdf462088d13 1897 # support this, this feature is disabled by default.
markrad 0:cdf462088d13 1898
markrad 0:cdf462088d13 1899 DOT_MULTI_TARGETS = NO
markrad 0:cdf462088d13 1900
markrad 0:cdf462088d13 1901 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1902 # generate a legend page explaining the meaning of the various boxes and
markrad 0:cdf462088d13 1903 # arrows in the dot generated graphs.
markrad 0:cdf462088d13 1904
markrad 0:cdf462088d13 1905 GENERATE_LEGEND = YES
markrad 0:cdf462088d13 1906
markrad 0:cdf462088d13 1907 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
markrad 0:cdf462088d13 1908 # remove the intermediate dot files that are used to generate
markrad 0:cdf462088d13 1909 # the various graphs.
markrad 0:cdf462088d13 1910
markrad 0:cdf462088d13 1911 DOT_CLEANUP = YES