1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/os/security/cryptoservices/certificateandkeymgmt/group/doxyfile Fri Jun 15 03:10:57 2012 +0200
1.3 @@ -0,0 +1,1138 @@
1.4 +# Doxyfile 1.3.3
1.5 +
1.6 +# This file describes the settings to be used by the documentation system
1.7 +# doxygen (www.doxygen.org) for a project
1.8 +#
1.9 +# All text after a hash (#) is considered a comment and will be ignored
1.10 +# The format is:
1.11 +# TAG = value [value, ...]
1.12 +# For lists items can also be appended using:
1.13 +# TAG += value [value, ...]
1.14 +# Values that contain spaces should be placed between quotes (" ")
1.15 +
1.16 +#---------------------------------------------------------------------------
1.17 +# General configuration options
1.18 +#---------------------------------------------------------------------------
1.19 +
1.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
1.21 +# by quotes) that should identify the project.
1.22 +
1.23 +PROJECT_NAME = "Certificate Management"
1.24 +
1.25 +# The PROJECT_NUMBER tag can be used to enter a project or revision number.
1.26 +# This could be handy for archiving the generated documentation or
1.27 +# if some version control system is used.
1.28 +
1.29 +PROJECT_NUMBER =
1.30 +
1.31 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
1.32 +# base path where the generated documentation will be put.
1.33 +# If a relative path is entered, it will be relative to the location
1.34 +# where doxygen was started. If left blank the current directory will be used.
1.35 +
1.36 +OUTPUT_DIRECTORY = ../docs/
1.37 +
1.38 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all
1.39 +# documentation generated by doxygen is written. Doxygen will use this
1.40 +# information to generate all constant output in the proper language.
1.41 +# The default language is English, other supported languages are:
1.42 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
1.43 +# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
1.44 +# (Japanese with English messages), Korean, Norwegian, Polish, Portuguese,
1.45 +# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
1.46 +
1.47 +OUTPUT_LANGUAGE = English
1.48 +
1.49 +# This tag can be used to specify the encoding used in the generated output.
1.50 +# The encoding is not always determined by the language that is chosen,
1.51 +# but also whether or not the output is meant for Windows or non-Windows users.
1.52 +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
1.53 +# forces the Windows encoding (this is the default for the Windows binary),
1.54 +# whereas setting the tag to NO uses a Unix-style encoding (the default for
1.55 +# all platforms other than Windows).
1.56 +
1.57 +USE_WINDOWS_ENCODING = YES
1.58 +
1.59 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
1.60 +# documentation are documented, even if no documentation was available.
1.61 +# Private class members and static file members will be hidden unless
1.62 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
1.63 +
1.64 +EXTRACT_ALL = YES
1.65 +
1.66 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
1.67 +# will be included in the documentation.
1.68 +
1.69 +EXTRACT_PRIVATE = NO
1.70 +
1.71 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
1.72 +# will be included in the documentation.
1.73 +
1.74 +EXTRACT_STATIC = YES
1.75 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
1.76 +# defined locally in source files will be included in the documentation.
1.77 +# If set to NO only classes defined in header files are included.
1.78 +
1.79 +EXTRACT_LOCAL_CLASSES = NO
1.80 +
1.81 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
1.82 +# undocumented members of documented classes, files or namespaces.
1.83 +# If set to NO (the default) these members will be included in the
1.84 +# various overviews, but no documentation section is generated.
1.85 +# This option has no effect if EXTRACT_ALL is enabled.
1.86 +
1.87 +HIDE_UNDOC_MEMBERS = NO
1.88 +
1.89 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
1.90 +# undocumented classes that are normally visible in the class hierarchy.
1.91 +# If set to NO (the default) these classes will be included in the various
1.92 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
1.93 +
1.94 +HIDE_UNDOC_CLASSES = NO
1.95 +
1.96 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
1.97 +# friend (class|struct|union) declarations.
1.98 +# If set to NO (the default) these declarations will be included in the
1.99 +# documentation.
1.100 +
1.101 +HIDE_FRIEND_COMPOUNDS = NO
1.102 +
1.103 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
1.104 +# documentation blocks found inside the body of a function.
1.105 +# If set to NO (the default) these blocks will be appended to the
1.106 +# function's detailed documentation block.
1.107 +
1.108 +HIDE_IN_BODY_DOCS = NO
1.109 +
1.110 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
1.111 +# include brief member descriptions after the members that are listed in
1.112 +# the file and class documentation (similar to JavaDoc).
1.113 +# Set to NO to disable this.
1.114 +
1.115 +BRIEF_MEMBER_DESC = YES
1.116 +
1.117 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
1.118 +# the brief description of a member or function before the detailed description.
1.119 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
1.120 +# brief descriptions will be completely suppressed.
1.121 +
1.122 +REPEAT_BRIEF = YES
1.123 +
1.124 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
1.125 +# Doxygen will generate a detailed section even if there is only a brief
1.126 +# description.
1.127 +
1.128 +ALWAYS_DETAILED_SEC = NO
1.129 +
1.130 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
1.131 +# members of a class in the documentation of that class as if those members were
1.132 +# ordinary class members. Constructors, destructors and assignment operators of
1.133 +# the base classes will not be shown.
1.134 +
1.135 +INLINE_INHERITED_MEMB = NO
1.136 +
1.137 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
1.138 +# path before files name in the file list and in the header files. If set
1.139 +# to NO the shortest path that makes the file name unique will be used.
1.140 +
1.141 +FULL_PATH_NAMES = NO
1.142 +
1.143 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
1.144 +# can be used to strip a user defined part of the path. Stripping is
1.145 +# only done if one of the specified strings matches the left-hand part of
1.146 +# the path. It is allowed to use relative paths in the argument list.
1.147 +
1.148 +STRIP_FROM_PATH = ../..
1.149 +
1.150 +# The INTERNAL_DOCS tag determines if documentation
1.151 +# that is typed after a \internal command is included. If the tag is set
1.152 +# to NO (the default) then the documentation will be excluded.
1.153 +# Set it to YES to include the internal documentation.
1.154 +
1.155 +INTERNAL_DOCS = NO
1.156 +
1.157 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
1.158 +# file names in lower case letters. If set to YES upper case letters are also
1.159 +# allowed. This is useful if you have classes or files whose names only differ
1.160 +# in case and if your file system supports case sensitive file names. Windows
1.161 +# users are advised to set this option to NO.
1.162 +
1.163 +CASE_SENSE_NAMES = YES
1.164 +
1.165 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
1.166 +# (but less readable) file names. This can be useful is your file systems
1.167 +# doesn't support long names like on DOS, Mac, or CD-ROM.
1.168 +
1.169 +SHORT_NAMES = NO
1.170 +
1.171 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
1.172 +# will show members with their full class and namespace scopes in the
1.173 +# documentation. If set to YES the scope will be hidden.
1.174 +
1.175 +HIDE_SCOPE_NAMES = NO
1.176 +
1.177 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
1.178 +# will put list of the files that are included by a file in the documentation
1.179 +# of that file.
1.180 +
1.181 +SHOW_INCLUDE_FILES = YES
1.182 +
1.183 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
1.184 +# will interpret the first line (until the first dot) of a JavaDoc-style
1.185 +# comment as the brief description. If set to NO, the JavaDoc
1.186 +# comments will behave just like the Qt-style comments (thus requiring an
1.187 +# explict @brief command for a brief description.
1.188 +
1.189 +JAVADOC_AUTOBRIEF = YES
1.190 +
1.191 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
1.192 +# treat a multi-line C++ special comment block (i.e. a block of //! or ///
1.193 +# comments) as a brief description. This used to be the default behaviour.
1.194 +# The new default is to treat a multi-line C++ comment block as a detailed
1.195 +# description. Set this tag to YES if you prefer the old behaviour instead.
1.196 +
1.197 +MULTILINE_CPP_IS_BRIEF = NO
1.198 +
1.199 +# If the DETAILS_AT_TOP tag is set to YES then Doxygen
1.200 +# will output the detailed description near the top, like JavaDoc.
1.201 +# If set to NO, the detailed description appears after the member
1.202 +# documentation.
1.203 +
1.204 +DETAILS_AT_TOP = YES
1.205 +
1.206 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
1.207 +# member inherits the documentation from any documented member that it
1.208 +# reimplements.
1.209 +
1.210 +INHERIT_DOCS = YES
1.211 +
1.212 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
1.213 +# is inserted in the documentation for inline members.
1.214 +
1.215 +INLINE_INFO = YES
1.216 +
1.217 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
1.218 +# will sort the (detailed) documentation of file and class members
1.219 +# alphabetically by member name. If set to NO the members will appear in
1.220 +# declaration order.
1.221 +
1.222 +SORT_MEMBER_DOCS = NO
1.223 +
1.224 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
1.225 +# tag is set to YES, then doxygen will reuse the documentation of the first
1.226 +# member in the group (if any) for the other members of the group. By default
1.227 +# all members of a group must be documented explicitly.
1.228 +
1.229 +DISTRIBUTE_GROUP_DOC = YES
1.230 +
1.231 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
1.232 +# Doxygen uses this value to replace tabs by spaces in code fragments.
1.233 +
1.234 +TAB_SIZE = 4
1.235 +
1.236 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
1.237 +# disable (NO) the list. This list is created by putting keyword
1.238 +# commands in the documentation.
1.239 +
1.240 +GENERATE_TODOLIST = YES
1.241 +
1.242 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
1.243 +# disable (NO) the test list. This list is created by putting \test
1.244 +# commands in the documentation.
1.245 +
1.246 +GENERATE_TESTLIST = YES
1.247 +
1.248 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
1.249 +# disable (NO) the list. This list is created by putting keyword
1.250 +# commands in the documentation.
1.251 +
1.252 +GENERATE_BUGLIST = YES
1.253 +
1.254 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
1.255 +# disable (NO) the deprecated list. This list is created by putting
1.256 +# \deprecated commands in the documentation.
1.257 +
1.258 +GENERATE_DEPRECATEDLIST= YES
1.259 +
1.260 +# This tag can be used to specify a number of aliases that acts
1.261 +# as commands in the documentation. An alias has the form "name=value".
1.262 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
1.263 +# put the command \sideeffect (or @sideeffect) in the documentation, which
1.264 +# will result in a user defined paragraph with heading "Side Effects:".
1.265 +# You can put \n's in the value part of an alias to insert newlines.
1.266 +
1.267 +ALIASES = \
1.268 + "publishedAll=@par publishedAll\n" \
1.269 + "publishedPartner=@par publishedPartner\n" \
1.270 + "internalAll=@par internalAll\n" \
1.271 + "internalComponent=@par internalComponent\n" \
1.272 + "internalTechnology=@par internalTechnology\n" \
1.273 + "prototype=@par prototype\n" \
1.274 + "interim=@par interim\n" \
1.275 + "released=@par released\n" \
1.276 + "deprecated=@par deprecated\n" \
1.277 + "removed=@par removed\n" \
1.278 + "capability=@par capability\n" \
1.279 + "leave=@par leave\n" \
1.280 + "panic=@par panic\n"
1.281 +
1.282 +# The ENABLED_SECTIONS tag can be used to enable conditional
1.283 +# documentation sections, marked by \if sectionname ... \endif.
1.284 +
1.285 +ENABLED_SECTIONS =
1.286 +
1.287 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
1.288 +# the initial value of a variable or define consists of for it to appear in
1.289 +# the documentation. If the initializer consists of more lines than specified
1.290 +# here it will be hidden. Use a value of 0 to hide initializers completely.
1.291 +# The appearance of the initializer of individual variables and defines in the
1.292 +# documentation can be controlled using \showinitializer or \hideinitializer
1.293 +# command in the documentation regardless of this setting.
1.294 +
1.295 +MAX_INITIALIZER_LINES = 30
1.296 +
1.297 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
1.298 +# only. Doxygen will then generate output that is more tailored for C.
1.299 +# For instance, some of the names that are used will be different. The list
1.300 +# of all members will be omitted, etc.
1.301 +
1.302 +OPTIMIZE_OUTPUT_FOR_C = NO
1.303 +
1.304 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
1.305 +# only. Doxygen will then generate output that is more tailored for Java.
1.306 +# For instance, namespaces will be presented as packages, qualified scopes
1.307 +# will look different, etc.
1.308 +
1.309 +OPTIMIZE_OUTPUT_JAVA = NO
1.310 +
1.311 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
1.312 +# at the bottom of the documentation of classes and structs. If set to YES the
1.313 +# list will mention the files that were used to generate the documentation.
1.314 +
1.315 +SHOW_USED_FILES = YES
1.316 +
1.317 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
1.318 +# the same type (for instance a group of public functions) to be put as a
1.319 +# subgroup of that type (e.g. under the Public Functions section). Set it to
1.320 +# NO to prevent subgrouping. Alternatively, this can be done per class using
1.321 +# the \nosubgrouping command.
1.322 +
1.323 +SUBGROUPING = YES
1.324 +
1.325 +#---------------------------------------------------------------------------
1.326 +# configuration options related to warning and progress messages
1.327 +#---------------------------------------------------------------------------
1.328 +
1.329 +# The QUIET tag can be used to turn on/off the messages that are generated
1.330 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
1.331 +
1.332 +QUIET = YES
1.333 +
1.334 +# The WARNINGS tag can be used to turn on/off the warning messages that are
1.335 +# generated by doxygen. Possible values are YES and NO. If left blank
1.336 +# NO is used.
1.337 +
1.338 +WARNINGS = YES
1.339 +
1.340 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
1.341 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
1.342 +# automatically be disabled.
1.343 +
1.344 +WARN_IF_UNDOCUMENTED = YES
1.345 +
1.346 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
1.347 +# potential errors in the documentation, such as not documenting some
1.348 +# parameters in a documented function, or documenting parameters that
1.349 +# don't exist or using markup commands wrongly.
1.350 +
1.351 +WARN_IF_DOC_ERROR = YES
1.352 +
1.353 +# The WARN_FORMAT tag determines the format of the warning messages that
1.354 +# doxygen can produce. The string should contain the $file, $line, and $text
1.355 +# tags, which will be replaced by the file and line number from which the
1.356 +# warning originated and the warning text.
1.357 +
1.358 +WARN_FORMAT = "$file:$line: $text"
1.359 +
1.360 +# The WARN_LOGFILE tag can be used to specify a file to which warning
1.361 +# and error messages should be written. If left blank the output is written
1.362 +# to stderr.
1.363 +
1.364 +WARN_LOGFILE = "warning.log"
1.365 +
1.366 +#---------------------------------------------------------------------------
1.367 +# configuration options related to the input files
1.368 +#---------------------------------------------------------------------------
1.369 +
1.370 +# The INPUT tag can be used to specify the files and/or directories that contain
1.371 +# documented source files. You may enter file names like "myfile.cpp" or
1.372 +# directories like "/usr/src/myproject". Separate the files or directories
1.373 +# with spaces.
1.374 +
1.375 +INPUT = ../inc
1.376 +
1.377 +# If the value of the INPUT tag contains directories, you can use the
1.378 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.379 +# and *.h) to filter out the source-files in the directories. If left
1.380 +# blank the following patterns are tested:
1.381 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
1.382 +# *.h++ *.idl *.odl *.cs
1.383 +
1.384 +FILE_PATTERNS = *.cpp \
1.385 + *.h \
1.386 + *.inl \
1.387 + *.mmp \
1.388 + *.rss \
1.389 + *.hrh \
1.390 + *.pam \
1.391 + *.dox
1.392 +
1.393 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
1.394 +# should be searched for input files as well. Possible values are YES and NO.
1.395 +# If left blank NO is used.
1.396 +
1.397 +RECURSIVE = NO
1.398 +
1.399 +# The EXCLUDE tag can be used to specify files and/or directories that should
1.400 +# excluded from the INPUT source files. This way you can easily exclude a
1.401 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
1.402 +
1.403 +EXCLUDE =
1.404 +
1.405 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
1.406 +# that are symbolic links (a Unix filesystem feature) are excluded from the input.
1.407 +
1.408 +EXCLUDE_SYMLINKS = NO
1.409 +
1.410 +# If the value of the INPUT tag contains directories, you can use the
1.411 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1.412 +# certain files from those directories.
1.413 +
1.414 +EXCLUDE_PATTERNS =
1.415 +
1.416 +# The EXAMPLE_PATH tag can be used to specify one or more files or
1.417 +# directories that contain example code fragments that are included (see
1.418 +# the \include command).
1.419 +
1.420 +EXAMPLE_PATH =
1.421 +
1.422 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
1.423 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.424 +# and *.h) to filter out the source-files in the directories. If left
1.425 +# blank all files are included.
1.426 +
1.427 +EXAMPLE_PATTERNS =
1.428 +
1.429 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1.430 +# searched for input files to be used with the \include or \dontinclude
1.431 +# commands irrespective of the value of the RECURSIVE tag.
1.432 +# Possible values are YES and NO. If left blank NO is used.
1.433 +
1.434 +EXAMPLE_RECURSIVE = NO
1.435 +
1.436 +# The IMAGE_PATH tag can be used to specify one or more files or
1.437 +# directories that contain image that are included in the documentation (see
1.438 +# the \image command).
1.439 +
1.440 +IMAGE_PATH =
1.441 +
1.442 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
1.443 +# invoke to filter for each input file. Doxygen will invoke the filter program
1.444 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
1.445 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
1.446 +# input file. Doxygen will then use the output that the filter program writes
1.447 +# to standard output.
1.448 +
1.449 +INPUT_FILTER =
1.450 +
1.451 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1.452 +# INPUT_FILTER) will be used to filter the input files when producing source
1.453 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
1.454 +
1.455 +FILTER_SOURCE_FILES = NO
1.456 +
1.457 +#---------------------------------------------------------------------------
1.458 +# configuration options related to source browsing
1.459 +#---------------------------------------------------------------------------
1.460 +
1.461 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
1.462 +# be generated. Documented entities will be cross-referenced with these sources.
1.463 +
1.464 +SOURCE_BROWSER = NO
1.465 +
1.466 +# Setting the INLINE_SOURCES tag to YES will include the body
1.467 +# of functions and classes directly in the documentation.
1.468 +
1.469 +INLINE_SOURCES = NO
1.470 +
1.471 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
1.472 +# doxygen to hide any special comment blocks from generated source code
1.473 +# fragments. Normal C and C++ comments will always remain visible.
1.474 +
1.475 +STRIP_CODE_COMMENTS = YES
1.476 +
1.477 +# If the REFERENCED_BY_RELATION tag is set to YES (the default)
1.478 +# then for each documented function all documented
1.479 +# functions referencing it will be listed.
1.480 +
1.481 +REFERENCED_BY_RELATION = YES
1.482 +
1.483 +# If the REFERENCES_RELATION tag is set to YES (the default)
1.484 +# then for each documented function all documented entities
1.485 +# called/used by that function will be listed.
1.486 +
1.487 +REFERENCES_RELATION = YES
1.488 +
1.489 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
1.490 +# will generate a verbatim copy of the header file for each class for
1.491 +# which an include is specified. Set to NO to disable this.
1.492 +
1.493 +VERBATIM_HEADERS = YES
1.494 +
1.495 +#---------------------------------------------------------------------------
1.496 +# configuration options related to the alphabetical class index
1.497 +#---------------------------------------------------------------------------
1.498 +
1.499 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
1.500 +# of all compounds will be generated. Enable this if the project
1.501 +# contains a lot of classes, structs, unions or interfaces.
1.502 +
1.503 +ALPHABETICAL_INDEX = YES
1.504 +
1.505 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
1.506 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
1.507 +# in which this list will be split (can be a number in the range [1..20])
1.508 +
1.509 +COLS_IN_ALPHA_INDEX = 5
1.510 +
1.511 +# In case all classes in a project start with a common prefix, all
1.512 +# classes will be put under the same header in the alphabetical index.
1.513 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
1.514 +# should be ignored while generating the index headers.
1.515 +
1.516 +IGNORE_PREFIX = C \
1.517 + T \
1.518 + R \
1.519 + M
1.520 +
1.521 +#---------------------------------------------------------------------------
1.522 +# configuration options related to the HTML output
1.523 +#---------------------------------------------------------------------------
1.524 +
1.525 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
1.526 +# generate HTML output.
1.527 +
1.528 +GENERATE_HTML = YES
1.529 +
1.530 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
1.531 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.532 +# put in front of it. If left blank `html' will be used as the default path.
1.533 +
1.534 +HTML_OUTPUT =
1.535 +
1.536 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
1.537 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
1.538 +# doxygen will generate files with .html extension.
1.539 +
1.540 +HTML_FILE_EXTENSION = .html
1.541 +
1.542 +# The HTML_HEADER tag can be used to specify a personal HTML header for
1.543 +# each generated HTML page. If it is left blank doxygen will generate a
1.544 +# standard header.
1.545 +
1.546 +HTML_HEADER = "c:/apps/doxygen/symdox/html_headerfile.txt"
1.547 +
1.548 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
1.549 +# each generated HTML page. If it is left blank doxygen will generate a
1.550 +# standard footer.
1.551 +
1.552 +HTML_FOOTER = "c:/apps/doxygen/symdox/html_footerfile.txt"
1.553 +
1.554 +# The HTML_STYLESHEET tag can be used to specify a user defined cascading
1.555 +# style sheet that is used by each HTML page. It can be used to
1.556 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
1.557 +# will generate a default style sheet
1.558 +
1.559 +HTML_STYLESHEET =
1.560 +
1.561 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
1.562 +# files or namespaces will be aligned in HTML using tables. If set to
1.563 +# NO a bullet list will be used.
1.564 +
1.565 +HTML_ALIGN_MEMBERS = YES
1.566 +
1.567 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
1.568 +# will be generated that can be used as input for tools like the
1.569 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
1.570 +# of the generated HTML documentation.
1.571 +
1.572 +GENERATE_HTMLHELP = NO
1.573 +
1.574 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
1.575 +# be used to specify the file name of the resulting .chm file. You
1.576 +# can add a path in front of the file if the result should not be
1.577 +# written to the html output dir.
1.578 +
1.579 +CHM_FILE = "Security.chm"
1.580 +
1.581 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
1.582 +# be used to specify the location (absolute path including file name) of
1.583 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1.584 +# the HTML help compiler on the generated index.hhp.
1.585 +
1.586 +HHC_LOCATION = "C:\Program Files\HTML Help Workshop\hhc.exe"
1.587 +
1.588 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
1.589 +# controls if a separate .chi index file is generated (YES) or that
1.590 +# it should be included in the master .chm file (NO).
1.591 +
1.592 +GENERATE_CHI = NO
1.593 +
1.594 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
1.595 +# controls whether a binary table of contents is generated (YES) or a
1.596 +# normal table of contents (NO) in the .chm file.
1.597 +
1.598 +BINARY_TOC = NO
1.599 +
1.600 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
1.601 +# to the contents of the HTML help documentation and to the tree view.
1.602 +
1.603 +TOC_EXPAND = NO
1.604 +
1.605 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1.606 +# top of each HTML page. The value NO (the default) enables the index and
1.607 +# the value YES disables it.
1.608 +
1.609 +DISABLE_INDEX = NO
1.610 +
1.611 +# This tag can be used to set the number of enum values (range [1..20])
1.612 +# that doxygen will group on one line in the generated HTML documentation.
1.613 +
1.614 +ENUM_VALUES_PER_LINE = 4
1.615 +
1.616 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
1.617 +# generated containing a tree-like index structure (just like the one that
1.618 +# is generated for HTML Help). For this to work a browser that supports
1.619 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
1.620 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
1.621 +# probably better off using the HTML help feature.
1.622 +
1.623 +GENERATE_TREEVIEW = NO
1.624 +
1.625 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1.626 +# used to set the initial width (in pixels) of the frame in which the tree
1.627 +# is shown.
1.628 +
1.629 +TREEVIEW_WIDTH = 250
1.630 +
1.631 +#---------------------------------------------------------------------------
1.632 +# configuration options related to the LaTeX output
1.633 +#---------------------------------------------------------------------------
1.634 +
1.635 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1.636 +# generate Latex output.
1.637 +
1.638 +GENERATE_LATEX = NO
1.639 +
1.640 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1.641 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.642 +# put in front of it. If left blank `latex' will be used as the default path.
1.643 +
1.644 +LATEX_OUTPUT = latex
1.645 +
1.646 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1.647 +# invoked. If left blank `latex' will be used as the default command name.
1.648 +
1.649 +LATEX_CMD_NAME = latex
1.650 +
1.651 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1.652 +# generate index for LaTeX. If left blank `makeindex' will be used as the
1.653 +# default command name.
1.654 +
1.655 +MAKEINDEX_CMD_NAME = makeindex
1.656 +
1.657 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1.658 +# LaTeX documents. This may be useful for small projects and may help to
1.659 +# save some trees in general.
1.660 +
1.661 +COMPACT_LATEX = NO
1.662 +
1.663 +# The PAPER_TYPE tag can be used to set the paper type that is used
1.664 +# by the printer. Possible values are: a4, a4wide, letter, legal and
1.665 +# executive. If left blank a4wide will be used.
1.666 +
1.667 +PAPER_TYPE = a4wide
1.668 +
1.669 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1.670 +# packages that should be included in the LaTeX output.
1.671 +
1.672 +EXTRA_PACKAGES =
1.673 +
1.674 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1.675 +# the generated latex document. The header should contain everything until
1.676 +# the first chapter. If it is left blank doxygen will generate a
1.677 +# standard header. Notice: only use this tag if you know what you are doing!
1.678 +
1.679 +LATEX_HEADER =
1.680 +
1.681 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1.682 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1.683 +# contain links (just like the HTML output) instead of page references
1.684 +# This makes the output suitable for online browsing using a pdf viewer.
1.685 +
1.686 +PDF_HYPERLINKS = NO
1.687 +
1.688 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1.689 +# plain latex in the generated Makefile. Set this option to YES to get a
1.690 +# higher quality PDF documentation.
1.691 +
1.692 +USE_PDFLATEX = NO
1.693 +
1.694 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1.695 +# command to the generated LaTeX files. This will instruct LaTeX to keep
1.696 +# running if errors occur, instead of asking the user for help.
1.697 +# This option is also used when generating formulas in HTML.
1.698 +
1.699 +LATEX_BATCHMODE = NO
1.700 +
1.701 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1.702 +# include the index chapters (such as File Index, Compound Index, etc.)
1.703 +# in the output.
1.704 +
1.705 +LATEX_HIDE_INDICES = NO
1.706 +
1.707 +#---------------------------------------------------------------------------
1.708 +# configuration options related to the RTF output
1.709 +#---------------------------------------------------------------------------
1.710 +
1.711 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1.712 +# The RTF output is optimised for Word 97 and may not look very pretty with
1.713 +# other RTF readers or editors.
1.714 +
1.715 +GENERATE_RTF = NO
1.716 +
1.717 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1.718 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.719 +# put in front of it. If left blank `rtf' will be used as the default path.
1.720 +
1.721 +RTF_OUTPUT = rtf
1.722 +
1.723 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1.724 +# RTF documents. This may be useful for small projects and may help to
1.725 +# save some trees in general.
1.726 +
1.727 +COMPACT_RTF = NO
1.728 +
1.729 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1.730 +# will contain hyperlink fields. The RTF file will
1.731 +# contain links (just like the HTML output) instead of page references.
1.732 +# This makes the output suitable for online browsing using WORD or other
1.733 +# programs which support those fields.
1.734 +# Note: wordpad (write) and others do not support links.
1.735 +
1.736 +RTF_HYPERLINKS = NO
1.737 +
1.738 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
1.739 +# config file, i.e. a series of assigments. You only have to provide
1.740 +# replacements, missing definitions are set to their default value.
1.741 +
1.742 +RTF_STYLESHEET_FILE =
1.743 +
1.744 +# Set optional variables used in the generation of an rtf document.
1.745 +# Syntax is similar to doxygen's config file.
1.746 +
1.747 +RTF_EXTENSIONS_FILE =
1.748 +
1.749 +#---------------------------------------------------------------------------
1.750 +# configuration options related to the man page output
1.751 +#---------------------------------------------------------------------------
1.752 +
1.753 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1.754 +# generate man pages
1.755 +
1.756 +GENERATE_MAN = NO
1.757 +
1.758 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1.759 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.760 +# put in front of it. If left blank `man' will be used as the default path.
1.761 +
1.762 +MAN_OUTPUT = man
1.763 +
1.764 +# The MAN_EXTENSION tag determines the extension that is added to
1.765 +# the generated man pages (default is the subroutine's section .3)
1.766 +
1.767 +MAN_EXTENSION = .3
1.768 +
1.769 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1.770 +# then it will generate one additional man file for each entity
1.771 +# documented in the real man page(s). These additional files
1.772 +# only source the real man page, but without them the man command
1.773 +# would be unable to find the correct page. The default is NO.
1.774 +
1.775 +MAN_LINKS = NO
1.776 +
1.777 +#---------------------------------------------------------------------------
1.778 +# configuration options related to the XML output
1.779 +#---------------------------------------------------------------------------
1.780 +
1.781 +# If the GENERATE_XML tag is set to YES Doxygen will
1.782 +# generate an XML file that captures the structure of
1.783 +# the code including all documentation. Note that this
1.784 +# feature is still experimental and not complete at the
1.785 +# moment.
1.786 +
1.787 +GENERATE_XML = NO
1.788 +
1.789 +# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1.790 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.791 +# put in front of it. If left blank `xml' will be used as the default path.
1.792 +
1.793 +XML_OUTPUT = xml
1.794 +
1.795 +# The XML_SCHEMA tag can be used to specify an XML schema,
1.796 +# which can be used by a validating XML parser to check the
1.797 +# syntax of the XML files.
1.798 +
1.799 +XML_SCHEMA =
1.800 +
1.801 +# The XML_DTD tag can be used to specify an XML DTD,
1.802 +# which can be used by a validating XML parser to check the
1.803 +# syntax of the XML files.
1.804 +
1.805 +XML_DTD =
1.806 +
1.807 +#---------------------------------------------------------------------------
1.808 +# configuration options for the AutoGen Definitions output
1.809 +#---------------------------------------------------------------------------
1.810 +
1.811 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1.812 +# generate an AutoGen Definitions (see autogen.sf.net) file
1.813 +# that captures the structure of the code including all
1.814 +# documentation. Note that this feature is still experimental
1.815 +# and not complete at the moment.
1.816 +
1.817 +GENERATE_AUTOGEN_DEF = NO
1.818 +
1.819 +#---------------------------------------------------------------------------
1.820 +# configuration options related to the Perl module output
1.821 +#---------------------------------------------------------------------------
1.822 +
1.823 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1.824 +# generate a Perl module file that captures the structure of
1.825 +# the code including all documentation. Note that this
1.826 +# feature is still experimental and not complete at the
1.827 +# moment.
1.828 +
1.829 +GENERATE_PERLMOD = NO
1.830 +
1.831 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1.832 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1.833 +# to generate PDF and DVI output from the Perl module output.
1.834 +
1.835 +PERLMOD_LATEX = NO
1.836 +
1.837 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1.838 +# nicely formatted so it can be parsed by a human reader. This is useful
1.839 +# if you want to understand what is going on. On the other hand, if this
1.840 +# tag is set to NO the size of the Perl module output will be much smaller
1.841 +# and Perl will parse it just the same.
1.842 +
1.843 +PERLMOD_PRETTY = YES
1.844 +
1.845 +# The names of the make variables in the generated doxyrules.make file
1.846 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1.847 +# This is useful so different doxyrules.make files included by the same
1.848 +# Makefile don't overwrite each other's variables.
1.849 +
1.850 +PERLMOD_MAKEVAR_PREFIX =
1.851 +
1.852 +#---------------------------------------------------------------------------
1.853 +# Configuration options related to the preprocessor
1.854 +#---------------------------------------------------------------------------
1.855 +
1.856 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1.857 +# evaluate all C-preprocessor directives found in the sources and include
1.858 +# files.
1.859 +
1.860 +ENABLE_PREPROCESSING = YES
1.861 +
1.862 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1.863 +# names in the source code. If set to NO (the default) only conditional
1.864 +# compilation will be performed. Macro expansion can be done in a controlled
1.865 +# way by setting EXPAND_ONLY_PREDEF to YES.
1.866 +
1.867 +MACRO_EXPANSION = NO
1.868 +
1.869 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1.870 +# then the macro expansion is limited to the macros specified with the
1.871 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
1.872 +
1.873 +EXPAND_ONLY_PREDEF = NO
1.874 +
1.875 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1.876 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
1.877 +
1.878 +SEARCH_INCLUDES = YES
1.879 +
1.880 +# The INCLUDE_PATH tag can be used to specify one or more directories that
1.881 +# contain include files that are not input files but should be processed by
1.882 +# the preprocessor.
1.883 +
1.884 +INCLUDE_PATH =
1.885 +
1.886 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1.887 +# patterns (like *.h and *.hpp) to filter out the header-files in the
1.888 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
1.889 +# be used.
1.890 +
1.891 +INCLUDE_FILE_PATTERNS =
1.892 +
1.893 +# The PREDEFINED tag can be used to specify one or more macro names that
1.894 +# are defined before the preprocessor is started (similar to the -D option of
1.895 +# gcc). The argument of the tag is a list of macros of the form: name
1.896 +# or name=definition (no spaces). If the definition and the = are
1.897 +# omitted =1 is assumed.
1.898 +
1.899 +PREDEFINED = NDEBUG \
1.900 + _UNICODE \
1.901 + __SYMBIAN32__ \
1.902 + __GCC32__ \
1.903 + __EPOC32__ \
1.904 + __MARM__ \
1.905 + __MARM_ARMI__ \
1.906 + __DLL__
1.907 +
1.908 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1.909 +# this tag can be used to specify a list of macro names that should be expanded.
1.910 +# The macro definition that is found in the sources will be used.
1.911 +# Use the PREDEFINED tag if you want to use a different macro definition.
1.912 +
1.913 +EXPAND_AS_DEFINED =
1.914 +
1.915 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1.916 +# doxygen's preprocessor will remove all function-like macros that are alone
1.917 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
1.918 +# function macros are typically used for boiler-plate code, and will confuse the
1.919 +# parser if not removed.
1.920 +
1.921 +SKIP_FUNCTION_MACROS = YES
1.922 +
1.923 +#---------------------------------------------------------------------------
1.924 +# Configuration::addtions related to external references
1.925 +#---------------------------------------------------------------------------
1.926 +
1.927 +# The TAGFILES option can be used to specify one or more tagfiles.
1.928 +# Optionally an initial location of the external documentation
1.929 +# can be added for each tagfile. The format of a tag file without
1.930 +# this location is as follows:
1.931 +# TAGFILES = file1 file2 ...
1.932 +# Adding location for the tag files is done as follows:
1.933 +# TAGFILES = file1=loc1 "file2 = loc2" ...
1.934 +# where "loc1" and "loc2" can be relative or absolute paths or
1.935 +# URLs. If a location is present for each tag, the installdox tool
1.936 +# does not have to be run to correct the links.
1.937 +# Note that each tag file must have a unique name
1.938 +# (where the name does NOT include the path)
1.939 +# If a tag file is not located in the directory in which doxygen
1.940 +# is run, you must also specify the path to the tagfile here.
1.941 +
1.942 +TAGFILES =
1.943 +
1.944 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1.945 +# a tag file that is based on the input files it reads.
1.946 +
1.947 +GENERATE_TAGFILE =
1.948 +
1.949 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1.950 +# in the class index. If set to NO only the inherited external classes
1.951 +# will be listed.
1.952 +
1.953 +ALLEXTERNALS = NO
1.954 +
1.955 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1.956 +# in the modules index. If set to NO, only the current project's groups will
1.957 +# be listed.
1.958 +
1.959 +EXTERNAL_GROUPS = YES
1.960 +
1.961 +# The PERL_PATH should be the absolute path and name of the perl script
1.962 +# interpreter (i.e. the result of `which perl').
1.963 +
1.964 +PERL_PATH = C:\perl\bin\perl
1.965 +
1.966 +#---------------------------------------------------------------------------
1.967 +# Configuration options related to the dot tool
1.968 +#---------------------------------------------------------------------------
1.969 +
1.970 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1.971 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
1.972 +# super classes. Setting the tag to NO turns the diagrams off. Note that this
1.973 +# option is superceded by the HAVE_DOT option below. This is only a fallback. It is
1.974 +# recommended to install and use dot, since it yields more powerful graphs.
1.975 +
1.976 +CLASS_DIAGRAMS = YES
1.977 +
1.978 +# If set to YES, the inheritance and collaboration graphs will hide
1.979 +# inheritance and usage relations if the target is undocumented
1.980 +# or is not a class.
1.981 +
1.982 +HIDE_UNDOC_RELATIONS = YES
1.983 +
1.984 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1.985 +# available from the path. This tool is part of Graphviz, a graph visualization
1.986 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1.987 +# have no effect if this option is set to NO (the default)
1.988 +
1.989 +HAVE_DOT = YES
1.990 +
1.991 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.992 +# will generate a graph for each documented class showing the direct and
1.993 +# indirect inheritance relations. Setting this tag to YES will force the
1.994 +# the CLASS_DIAGRAMS tag to NO.
1.995 +
1.996 +CLASS_GRAPH = YES
1.997 +
1.998 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.999 +# will generate a graph for each documented class showing the direct and
1.1000 +# indirect implementation dependencies (inheritance, containment, and
1.1001 +# class references variables) of the class with other documented classes.
1.1002 +
1.1003 +COLLABORATION_GRAPH = YES
1.1004 +
1.1005 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1.1006 +# collaboration diagrams in a style similiar to the OMG's Unified Modeling
1.1007 +# Language.
1.1008 +
1.1009 +UML_LOOK = NO
1.1010 +
1.1011 +# If set to YES, the inheritance and collaboration graphs will show the
1.1012 +# relations between templates and their instances.
1.1013 +
1.1014 +TEMPLATE_RELATIONS = YES
1.1015 +
1.1016 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1.1017 +# tags are set to YES then doxygen will generate a graph for each documented
1.1018 +# file showing the direct and indirect include dependencies of the file with
1.1019 +# other documented files.
1.1020 +
1.1021 +INCLUDE_GRAPH = YES
1.1022 +
1.1023 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1.1024 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1.1025 +# documented header file showing the documented files that directly or
1.1026 +# indirectly include this file.
1.1027 +
1.1028 +INCLUDED_BY_GRAPH = YES
1.1029 +
1.1030 +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1.1031 +# generate a call dependency graph for every global function or class method.
1.1032 +# Note that enabling this option will significantly increase the time of a run.
1.1033 +# So in most cases it will be better to enable call graphs for selected
1.1034 +# functions only using the \callgraph command.
1.1035 +
1.1036 +CALL_GRAPH = NO
1.1037 +
1.1038 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1.1039 +# will graphical hierarchy of all classes instead of a textual one.
1.1040 +
1.1041 +GRAPHICAL_HIERARCHY = YES
1.1042 +
1.1043 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1.1044 +# generated by dot. Possible values are png, jpg, or gif
1.1045 +# If left blank png will be used.
1.1046 +
1.1047 +DOT_IMAGE_FORMAT = png
1.1048 +
1.1049 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
1.1050 +# found. If left blank, it is assumed the dot tool can be found on the path.
1.1051 +
1.1052 +DOT_PATH = "C:\apps\doxygen\graphviz\bin"
1.1053 +
1.1054 +# The DOTFILE_DIRS tag can be used to specify one or more directories that
1.1055 +# contain dot files that are included in the documentation (see the
1.1056 +# \dotfile command).
1.1057 +
1.1058 +DOTFILE_DIRS =
1.1059 +
1.1060 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1.1061 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.1062 +# this value, doxygen will try to truncate the graph, so that it fits within
1.1063 +# the specified constraint. Beware that most browsers cannot cope with very
1.1064 +# large images.
1.1065 +
1.1066 +MAX_DOT_GRAPH_WIDTH = 1024
1.1067 +
1.1068 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1.1069 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.1070 +# this value, doxygen will try to truncate the graph, so that it fits within
1.1071 +# the specified constraint. Beware that most browsers cannot cope with very
1.1072 +# large images.
1.1073 +
1.1074 +MAX_DOT_GRAPH_HEIGHT = 1024
1.1075 +
1.1076 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1.1077 +# graphs generated by dot. A depth value of 3 means that only nodes reachable
1.1078 +# from the root by following a path via at most 3 edges will be shown. Nodes that
1.1079 +# lay further from the root node will be omitted. Note that setting this option to
1.1080 +# 1 or 2 may greatly reduce the computation time needed for large code bases. Also
1.1081 +# note that a graph may be further truncated if the graph's image dimensions are
1.1082 +# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
1.1083 +# If 0 is used for the depth value (the default), the graph is not depth-constrained.
1.1084 +
1.1085 +MAX_DOT_GRAPH_DEPTH = 0
1.1086 +
1.1087 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1.1088 +# generate a legend page explaining the meaning of the various boxes and
1.1089 +# arrows in the dot generated graphs.
1.1090 +
1.1091 +GENERATE_LEGEND = YES
1.1092 +
1.1093 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1.1094 +# remove the intermediate dot files that are used to generate
1.1095 +# the various graphs.
1.1096 +
1.1097 +DOT_CLEANUP = YES
1.1098 +
1.1099 +#---------------------------------------------------------------------------
1.1100 +# Configuration::addtions related to the search engine
1.1101 +#---------------------------------------------------------------------------
1.1102 +
1.1103 +# The SEARCHENGINE tag specifies whether or not a search engine should be
1.1104 +# used. If set to NO the values of all tags below this one will be ignored.
1.1105 +
1.1106 +SEARCHENGINE = NO
1.1107 +
1.1108 +# The CGI_NAME tag should be the name of the CGI script that
1.1109 +# starts the search engine (doxysearch) with the correct parameters.
1.1110 +# A script with this name will be generated by doxygen.
1.1111 +
1.1112 +# CGI_NAME = search.cgi
1.1113 +
1.1114 +# The CGI_URL tag should be the absolute URL to the directory where the
1.1115 +# cgi binaries are located. See the documentation of your http daemon for
1.1116 +# details.
1.1117 +
1.1118 +# CGI_URL =
1.1119 +
1.1120 +# The DOC_URL tag should be the absolute URL to the directory where the
1.1121 +# documentation is located. If left blank the absolute path to the
1.1122 +# documentation, with file:// prepended to it, will be used.
1.1123 +
1.1124 +# DOC_URL =
1.1125 +
1.1126 +# The DOC_ABSPATH tag should be the absolute path to the directory where the
1.1127 +# documentation is located. If left blank the directory on the local machine
1.1128 +# will be used.
1.1129 +
1.1130 +# DOC_ABSPATH =
1.1131 +
1.1132 +# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
1.1133 +# is installed.
1.1134 +
1.1135 +# BIN_ABSPATH = /usr/local/bin/
1.1136 +
1.1137 +# The EXT_DOC_PATHS tag can be used to specify one or more paths to
1.1138 +# documentation generated for other projects. This allows doxysearch to search
1.1139 +# the documentation for these projects as well.
1.1140 +
1.1141 +# EXT_DOC_PATHS =