1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/os/security/cryptoservices/certificateandkeymgmt/tcertcommon/doxygen.conf Fri Jun 15 03:10:57 2012 +0200
1.3 @@ -0,0 +1,808 @@
1.4 +# Doxyfile 1.2.8.1
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 = TCertCommon
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.00
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 = .
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, Chinese, Croatian, Czech, Danish, Dutch, Finnish, French,
1.43 +# German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish,
1.44 +# Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish.
1.45 +
1.46 +OUTPUT_LANGUAGE = English
1.47 +
1.48 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
1.49 +# documentation are documented, even if no documentation was available.
1.50 +# Private class members and static file members will be hidden unless
1.51 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
1.52 +
1.53 +EXTRACT_ALL = NO
1.54 +
1.55 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
1.56 +# will be included in the documentation.
1.57 +
1.58 +EXTRACT_PRIVATE = YES
1.59 +
1.60 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
1.61 +# will be included in the documentation.
1.62 +
1.63 +EXTRACT_STATIC = YES
1.64 +
1.65 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
1.66 +# undocumented members of documented classes, files or namespaces.
1.67 +# If set to NO (the default) these members will be included in the
1.68 +# various overviews, but no documentation section is generated.
1.69 +# This option has no effect if EXTRACT_ALL is enabled.
1.70 +
1.71 +HIDE_UNDOC_MEMBERS = NO
1.72 +
1.73 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
1.74 +# undocumented classes that are normally visible in the class hierarchy.
1.75 +# If set to NO (the default) these class will be included in the various
1.76 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
1.77 +
1.78 +HIDE_UNDOC_CLASSES = NO
1.79 +
1.80 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
1.81 +# include brief member descriptions after the members that are listed in
1.82 +# the file and class documentation (similar to JavaDoc).
1.83 +# Set to NO to disable this.
1.84 +
1.85 +BRIEF_MEMBER_DESC = YES
1.86 +
1.87 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
1.88 +# the brief description of a member or function before the detailed description.
1.89 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
1.90 +# brief descriptions will be completely suppressed.
1.91 +
1.92 +REPEAT_BRIEF = YES
1.93 +
1.94 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
1.95 +# Doxygen will generate a detailed section even if there is only a brief
1.96 +# description.
1.97 +
1.98 +ALWAYS_DETAILED_SEC = NO
1.99 +
1.100 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
1.101 +# path before files name in the file list and in the header files. If set
1.102 +# to NO the shortest path that makes the file name unique will be used.
1.103 +
1.104 +FULL_PATH_NAMES = NO
1.105 +
1.106 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
1.107 +# can be used to strip a user defined part of the path. Stripping is
1.108 +# only done if one of the specified strings matches the left-hand part of
1.109 +# the path. It is allowed to use relative paths in the argument list.
1.110 +
1.111 +STRIP_FROM_PATH =
1.112 +
1.113 +# The INTERNAL_DOCS tag determines if documentation
1.114 +# that is typed after a \internal command is included. If the tag is set
1.115 +# to NO (the default) then the documentation will be excluded.
1.116 +# Set it to YES to include the internal documentation.
1.117 +
1.118 +INTERNAL_DOCS = NO
1.119 +
1.120 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1.121 +# generate a class diagram (in Html and LaTeX) for classes with base or
1.122 +# super classes. Setting the tag to NO turns the diagrams off.
1.123 +
1.124 +CLASS_DIAGRAMS = YES
1.125 +
1.126 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
1.127 +# be generated. Documented entities will be cross-referenced with these sources.
1.128 +
1.129 +SOURCE_BROWSER = NO
1.130 +
1.131 +# Setting the INLINE_SOURCES tag to YES will include the body
1.132 +# of functions and classes directly in the documentation.
1.133 +
1.134 +INLINE_SOURCES = NO
1.135 +
1.136 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
1.137 +# doxygen to hide any special comment blocks from generated source code
1.138 +# fragments. Normal C and C++ comments will always remain visible.
1.139 +
1.140 +STRIP_CODE_COMMENTS = YES
1.141 +
1.142 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
1.143 +# file names in lower case letters. If set to YES upper case letters are also
1.144 +# allowed. This is useful if you have classes or files whose names only differ
1.145 +# in case and if your file system supports case sensitive file names. Windows
1.146 +# users are adviced to set this option to NO.
1.147 +
1.148 +CASE_SENSE_NAMES = YES
1.149 +
1.150 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
1.151 +# (but less readable) file names. This can be useful is your file systems
1.152 +# doesn't support long names like on DOS, Mac, or CD-ROM.
1.153 +
1.154 +SHORT_NAMES = NO
1.155 +
1.156 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
1.157 +# will show members with their full class and namespace scopes in the
1.158 +# documentation. If set to YES the scope will be hidden.
1.159 +
1.160 +HIDE_SCOPE_NAMES = NO
1.161 +
1.162 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
1.163 +# will generate a verbatim copy of the header file for each class for
1.164 +# which an include is specified. Set to NO to disable this.
1.165 +
1.166 +VERBATIM_HEADERS = YES
1.167 +
1.168 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
1.169 +# will put list of the files that are included by a file in the documentation
1.170 +# of that file.
1.171 +
1.172 +SHOW_INCLUDE_FILES = YES
1.173 +
1.174 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
1.175 +# will interpret the first line (until the first dot) of a JavaDoc-style
1.176 +# comment as the brief description. If set to NO, the JavaDoc
1.177 +# comments will behave just like the Qt-style comments (thus requiring an
1.178 +# explict @brief command for a brief description.
1.179 +
1.180 +JAVADOC_AUTOBRIEF = NO
1.181 +
1.182 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
1.183 +# member inherits the documentation from any documented member that it
1.184 +# reimplements.
1.185 +
1.186 +INHERIT_DOCS = YES
1.187 +
1.188 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
1.189 +# is inserted in the documentation for inline members.
1.190 +
1.191 +INLINE_INFO = YES
1.192 +
1.193 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
1.194 +# will sort the (detailed) documentation of file and class members
1.195 +# alphabetically by member name. If set to NO the members will appear in
1.196 +# declaration order.
1.197 +
1.198 +SORT_MEMBER_DOCS = YES
1.199 +
1.200 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
1.201 +# tag is set to YES, then doxygen will reuse the documentation of the first
1.202 +# member in the group (if any) for the other members of the group. By default
1.203 +# all members of a group must be documented explicitly.
1.204 +
1.205 +DISTRIBUTE_GROUP_DOC = NO
1.206 +
1.207 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
1.208 +# Doxygen uses this value to replace tabs by spaces in code fragments.
1.209 +
1.210 +TAB_SIZE = 8
1.211 +
1.212 +# The ENABLED_SECTIONS tag can be used to enable conditional
1.213 +# documentation sections, marked by \if sectionname ... \endif.
1.214 +
1.215 +ENABLED_SECTIONS =
1.216 +
1.217 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
1.218 +# disable (NO) the list. This list is created by putting keyword
1.219 +# commands in the documentation.
1.220 +
1.221 +GENERATE_TODOLIST = YES
1.222 +
1.223 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
1.224 +# disable (NO) the test list. This list is created by putting \test
1.225 +# commands in the documentation.
1.226 +
1.227 +GENERATE_TESTLIST = YES
1.228 +
1.229 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
1.230 +# disable (NO) the list. This list is created by putting keyword
1.231 +# commands in the documentation.
1.232 +
1.233 +GENERATE_BUGLIST = YES
1.234 +
1.235 +# This tag can be used to specify a number of aliases that acts
1.236 +# as commands in the documentation. An alias has the form "name=value".
1.237 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
1.238 +# put the command \sideeffect (or @sideeffect) in the documentation, which
1.239 +# will result in a user defined paragraph with heading "Side Effects:".
1.240 +# You can put \n's in the value part of an alias to insert newlines.
1.241 +
1.242 +ALIASES =
1.243 +
1.244 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
1.245 +# the initial value of a variable or define consist of for it to appear in
1.246 +# the documentation. If the initializer consists of more lines than specified
1.247 +# here it will be hidden. Use a value of 0 to hide initializers completely.
1.248 +# The appearance of the initializer of individual variables and defines in the
1.249 +# documentation can be controlled using \showinitializer or \hideinitializer
1.250 +# command in the documentation regardless of this setting.
1.251 +
1.252 +MAX_INITIALIZER_LINES = 30
1.253 +
1.254 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
1.255 +# only. Doxygen will then generate output that is more tailored for C.
1.256 +# For instance some of the names that are used will be different. The list
1.257 +# of all members will be omitted, etc.
1.258 +
1.259 +OPTIMIZE_OUTPUT_FOR_C = NO
1.260 +
1.261 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
1.262 +# at the bottom of the documentation of classes and structs. If set to YES the
1.263 +# list will mention the files that were used to generate the documentation.
1.264 +
1.265 +SHOW_USED_FILES = YES
1.266 +
1.267 +#---------------------------------------------------------------------------
1.268 +# configuration options related to warning and progress messages
1.269 +#---------------------------------------------------------------------------
1.270 +
1.271 +# The QUIET tag can be used to turn on/off the messages that are generated
1.272 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
1.273 +
1.274 +QUIET = NO
1.275 +
1.276 +# The WARNINGS tag can be used to turn on/off the warning messages that are
1.277 +# generated by doxygen. Possible values are YES and NO. If left blank
1.278 +# NO is used.
1.279 +
1.280 +WARNINGS = YES
1.281 +
1.282 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
1.283 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
1.284 +# automatically be disabled.
1.285 +
1.286 +WARN_IF_UNDOCUMENTED = YES
1.287 +
1.288 +# The WARN_FORMAT tag determines the format of the warning messages that
1.289 +# doxygen can produce. The string should contain the $file, $line, and $text
1.290 +# tags, which will be replaced by the file and line number from which the
1.291 +# warning originated and the warning text.
1.292 +
1.293 +WARN_FORMAT =
1.294 +
1.295 +# The WARN_LOGFILE tag can be used to specify a file to which warning
1.296 +# and error messages should be written. If left blank the output is written
1.297 +# to stderr.
1.298 +
1.299 +WARN_LOGFILE =
1.300 +
1.301 +#---------------------------------------------------------------------------
1.302 +# configuration options related to the input files
1.303 +#---------------------------------------------------------------------------
1.304 +
1.305 +# The INPUT tag can be used to specify the files and/or directories that contain
1.306 +# documented source files. You may enter file names like "myfile.cpp" or
1.307 +# directories like "/usr/src/myproject". Separate the files or directories
1.308 +# with spaces.
1.309 +
1.310 +INPUT = \security\certman\tcertcommon
1.311 +
1.312 +# If the value of the INPUT tag contains directories, you can use the
1.313 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.314 +# and *.h) to filter out the source-files in the directories. If left
1.315 +# blank all files are included.
1.316 +
1.317 +FILE_PATTERNS =
1.318 +
1.319 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
1.320 +# should be searched for input files as well. Possible values are YES and NO.
1.321 +# If left blank NO is used.
1.322 +
1.323 +RECURSIVE = NO
1.324 +
1.325 +# The EXCLUDE tag can be used to specify files and/or directories that should
1.326 +# excluded from the INPUT source files. This way you can easily exclude a
1.327 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
1.328 +
1.329 +EXCLUDE =
1.330 +
1.331 +# If the value of the INPUT tag contains directories, you can use the
1.332 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1.333 +# certain files from those directories.
1.334 +
1.335 +EXCLUDE_PATTERNS =
1.336 +
1.337 +# The EXAMPLE_PATH tag can be used to specify one or more files or
1.338 +# directories that contain example code fragments that are included (see
1.339 +# the \include command).
1.340 +
1.341 +EXAMPLE_PATH =
1.342 +
1.343 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
1.344 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.345 +# and *.h) to filter out the source-files in the directories. If left
1.346 +# blank all files are included.
1.347 +
1.348 +EXAMPLE_PATTERNS =
1.349 +
1.350 +# The IMAGE_PATH tag can be used to specify one or more files or
1.351 +# directories that contain image that are included in the documentation (see
1.352 +# the \image command).
1.353 +
1.354 +IMAGE_PATH =
1.355 +
1.356 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
1.357 +# invoke to filter for each input file. Doxygen will invoke the filter program
1.358 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
1.359 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
1.360 +# input file. Doxygen will then use the output that the filter program writes
1.361 +# to standard output.
1.362 +
1.363 +INPUT_FILTER =
1.364 +
1.365 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1.366 +# INPUT_FILTER) will be used to filter the input files when producing source
1.367 +# files to browse.
1.368 +
1.369 +FILTER_SOURCE_FILES = NO
1.370 +
1.371 +#---------------------------------------------------------------------------
1.372 +# configuration options related to the alphabetical class index
1.373 +#---------------------------------------------------------------------------
1.374 +
1.375 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
1.376 +# of all compounds will be generated. Enable this if the project
1.377 +# contains a lot of classes, structs, unions or interfaces.
1.378 +
1.379 +ALPHABETICAL_INDEX = NO
1.380 +
1.381 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
1.382 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
1.383 +# in which this list will be split (can be a number in the range [1..20])
1.384 +
1.385 +COLS_IN_ALPHA_INDEX = 5
1.386 +
1.387 +# In case all classes in a project start with a common prefix, all
1.388 +# classes will be put under the same header in the alphabetical index.
1.389 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
1.390 +# should be ignored while generating the index headers.
1.391 +
1.392 +IGNORE_PREFIX =
1.393 +
1.394 +#---------------------------------------------------------------------------
1.395 +# configuration options related to the HTML output
1.396 +#---------------------------------------------------------------------------
1.397 +
1.398 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
1.399 +# generate HTML output.
1.400 +
1.401 +GENERATE_HTML = YES
1.402 +
1.403 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
1.404 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.405 +# put in front of it. If left blank `html' will be used as the default path.
1.406 +
1.407 +HTML_OUTPUT =
1.408 +
1.409 +# The HTML_HEADER tag can be used to specify a personal HTML header for
1.410 +# each generated HTML page. If it is left blank doxygen will generate a
1.411 +# standard header.
1.412 +
1.413 +HTML_HEADER =
1.414 +
1.415 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
1.416 +# each generated HTML page. If it is left blank doxygen will generate a
1.417 +# standard footer.
1.418 +
1.419 +HTML_FOOTER =
1.420 +
1.421 +# The HTML_STYLESHEET tag can be used to specify a user defined cascading
1.422 +# style sheet that is used by each HTML page. It can be used to
1.423 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
1.424 +# will generate a default style sheet
1.425 +
1.426 +HTML_STYLESHEET =
1.427 +
1.428 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
1.429 +# files or namespaces will be aligned in HTML using tables. If set to
1.430 +# NO a bullet list will be used.
1.431 +
1.432 +HTML_ALIGN_MEMBERS = YES
1.433 +
1.434 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
1.435 +# will be generated that can be used as input for tools like the
1.436 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
1.437 +# of the generated HTML documentation.
1.438 +
1.439 +GENERATE_HTMLHELP = NO
1.440 +
1.441 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
1.442 +# controls if a separate .chi index file is generated (YES) or that
1.443 +# it should be included in the master .chm file (NO).
1.444 +
1.445 +GENERATE_CHI = NO
1.446 +
1.447 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
1.448 +# controls whether a binary table of contents is generated (YES) or a
1.449 +# normal table of contents (NO) in the .chm file.
1.450 +
1.451 +BINARY_TOC = NO
1.452 +
1.453 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
1.454 +# to the contents of the Html help documentation and to the tree view.
1.455 +
1.456 +TOC_EXPAND = NO
1.457 +
1.458 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1.459 +# top of each HTML page. The value NO (the default) enables the index and
1.460 +# the value YES disables it.
1.461 +
1.462 +DISABLE_INDEX = NO
1.463 +
1.464 +# This tag can be used to set the number of enum values (range [1..20])
1.465 +# that doxygen will group on one line in the generated HTML documentation.
1.466 +
1.467 +ENUM_VALUES_PER_LINE = 4
1.468 +
1.469 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
1.470 +# generated containing a tree-like index structure (just like the one that
1.471 +# is generated for HTML Help). For this to work a browser that supports
1.472 +# JavaScript and frames is required (for instance Netscape 4.0+
1.473 +# or Internet explorer 4.0+).
1.474 +
1.475 +GENERATE_TREEVIEW = NO
1.476 +
1.477 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1.478 +# used to set the initial width (in pixels) of the frame in which the tree
1.479 +# is shown.
1.480 +
1.481 +TREEVIEW_WIDTH = 250
1.482 +
1.483 +#---------------------------------------------------------------------------
1.484 +# configuration options related to the LaTeX output
1.485 +#---------------------------------------------------------------------------
1.486 +
1.487 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1.488 +# generate Latex output.
1.489 +
1.490 +GENERATE_LATEX = YES
1.491 +
1.492 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1.493 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.494 +# put in front of it. If left blank `latex' will be used as the default path.
1.495 +
1.496 +LATEX_OUTPUT =
1.497 +
1.498 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1.499 +# LaTeX documents. This may be useful for small projects and may help to
1.500 +# save some trees in general.
1.501 +
1.502 +COMPACT_LATEX = NO
1.503 +
1.504 +# The PAPER_TYPE tag can be used to set the paper type that is used
1.505 +# by the printer. Possible values are: a4, a4wide, letter, legal and
1.506 +# executive. If left blank a4wide will be used.
1.507 +
1.508 +PAPER_TYPE = a4wide
1.509 +
1.510 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1.511 +# packages that should be included in the LaTeX output.
1.512 +
1.513 +EXTRA_PACKAGES =
1.514 +
1.515 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1.516 +# the generated latex document. The header should contain everything until
1.517 +# the first chapter. If it is left blank doxygen will generate a
1.518 +# standard header. Notice: only use this tag if you know what you are doing!
1.519 +
1.520 +LATEX_HEADER =
1.521 +
1.522 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1.523 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1.524 +# contain links (just like the HTML output) instead of page references
1.525 +# This makes the output suitable for online browsing using a pdf viewer.
1.526 +
1.527 +PDF_HYPERLINKS = NO
1.528 +
1.529 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1.530 +# plain latex in the generated Makefile. Set this option to YES to get a
1.531 +# higher quality PDF documentation.
1.532 +
1.533 +USE_PDFLATEX = NO
1.534 +
1.535 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1.536 +# command to the generated LaTeX files. This will instruct LaTeX to keep
1.537 +# running if errors occur, instead of asking the user for help.
1.538 +# This option is also used when generating formulas in HTML.
1.539 +
1.540 +LATEX_BATCHMODE = NO
1.541 +
1.542 +#---------------------------------------------------------------------------
1.543 +# configuration options related to the RTF output
1.544 +#---------------------------------------------------------------------------
1.545 +
1.546 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1.547 +# The RTF output is optimised for Word 97 and may not look very pretty with
1.548 +# other RTF readers or editors.
1.549 +
1.550 +GENERATE_RTF = NO
1.551 +
1.552 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1.553 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.554 +# put in front of it. If left blank `rtf' will be used as the default path.
1.555 +
1.556 +RTF_OUTPUT =
1.557 +
1.558 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1.559 +# RTF documents. This may be useful for small projects and may help to
1.560 +# save some trees in general.
1.561 +
1.562 +COMPACT_RTF = NO
1.563 +
1.564 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1.565 +# will contain hyperlink fields. The RTF file will
1.566 +# contain links (just like the HTML output) instead of page references.
1.567 +# This makes the output suitable for online browsing using WORD or other
1.568 +# programs which support those fields.
1.569 +# Note: wordpad (write) and others do not support links.
1.570 +
1.571 +RTF_HYPERLINKS = NO
1.572 +
1.573 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
1.574 +# config file, i.e. a series of assigments. You only have to provide
1.575 +# replacements, missing definitions are set to their default value.
1.576 +
1.577 +RTF_STYLESHEET_FILE =
1.578 +
1.579 +# Set optional variables used in the generation of an rtf document.
1.580 +# Syntax is similar to doxygen's config file.
1.581 +
1.582 +RTF_EXTENSIONS_FILE =
1.583 +
1.584 +#---------------------------------------------------------------------------
1.585 +# configuration options related to the man page output
1.586 +#---------------------------------------------------------------------------
1.587 +
1.588 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1.589 +# generate man pages
1.590 +
1.591 +GENERATE_MAN = NO
1.592 +
1.593 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1.594 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.595 +# put in front of it. If left blank `man' will be used as the default path.
1.596 +
1.597 +MAN_OUTPUT =
1.598 +
1.599 +# The MAN_EXTENSION tag determines the extension that is added to
1.600 +# the generated man pages (default is the subroutine's section .3)
1.601 +
1.602 +MAN_EXTENSION =
1.603 +
1.604 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1.605 +# then it will generate one additional man file for each entity
1.606 +# documented in the real man page(s). These additional files
1.607 +# only source the real man page, but without them the man command
1.608 +# would be unable to find the correct page. The default is NO.
1.609 +
1.610 +MAN_LINKS = NO
1.611 +
1.612 +#---------------------------------------------------------------------------
1.613 +# Configuration options related to the preprocessor
1.614 +#---------------------------------------------------------------------------
1.615 +
1.616 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1.617 +# evaluate all C-preprocessor directives found in the sources and include
1.618 +# files.
1.619 +
1.620 +ENABLE_PREPROCESSING = YES
1.621 +
1.622 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1.623 +# names in the source code. If set to NO (the default) only conditional
1.624 +# compilation will be performed. Macro expansion can be done in a controlled
1.625 +# way by setting EXPAND_ONLY_PREDEF to YES.
1.626 +
1.627 +MACRO_EXPANSION = NO
1.628 +
1.629 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1.630 +# then the macro expansion is limited to the macros specified with the
1.631 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
1.632 +
1.633 +EXPAND_ONLY_PREDEF = NO
1.634 +
1.635 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1.636 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
1.637 +
1.638 +SEARCH_INCLUDES = YES
1.639 +
1.640 +# The INCLUDE_PATH tag can be used to specify one or more directories that
1.641 +# contain include files that are not input files but should be processed by
1.642 +# the preprocessor.
1.643 +
1.644 +INCLUDE_PATH =
1.645 +
1.646 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1.647 +# patterns (like *.h and *.hpp) to filter out the header-files in the
1.648 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
1.649 +# be used.
1.650 +
1.651 +INCLUDE_FILE_PATTERNS =
1.652 +
1.653 +# The PREDEFINED tag can be used to specify one or more macro names that
1.654 +# are defined before the preprocessor is started (similar to the -D option of
1.655 +# gcc). The argument of the tag is a list of macros of the form: name
1.656 +# or name=definition (no spaces). If the definition and the = are
1.657 +# omitted =1 is assumed.
1.658 +
1.659 +PREDEFINED =
1.660 +
1.661 +# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
1.662 +# this tag can be used to specify a list of macro names that should be expanded.
1.663 +# The macro definition that is found in the sources will be used.
1.664 +# Use the PREDEFINED tag if you want to use a different macro definition.
1.665 +
1.666 +EXPAND_AS_DEFINED =
1.667 +
1.668 +#---------------------------------------------------------------------------
1.669 +# Configuration::addtions related to external references
1.670 +#---------------------------------------------------------------------------
1.671 +
1.672 +# The TAGFILES tag can be used to specify one or more tagfiles.
1.673 +
1.674 +TAGFILES =
1.675 +
1.676 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1.677 +# a tag file that is based on the input files it reads.
1.678 +
1.679 +GENERATE_TAGFILE =
1.680 +
1.681 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1.682 +# in the class index. If set to NO only the inherited external classes
1.683 +# will be listed.
1.684 +
1.685 +ALLEXTERNALS = NO
1.686 +
1.687 +# The PERL_PATH should be the absolute path and name of the perl script
1.688 +# interpreter (i.e. the result of `which perl').
1.689 +
1.690 +PERL_PATH =
1.691 +
1.692 +#---------------------------------------------------------------------------
1.693 +# Configuration options related to the dot tool
1.694 +#---------------------------------------------------------------------------
1.695 +
1.696 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1.697 +# available from the path. This tool is part of Graphviz, a graph visualization
1.698 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1.699 +# have no effect if this option is set to NO (the default)
1.700 +
1.701 +HAVE_DOT = NO
1.702 +
1.703 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.704 +# will generate a graph for each documented class showing the direct and
1.705 +# indirect inheritance relations. Setting this tag to YES will force the
1.706 +# the CLASS_DIAGRAMS tag to NO.
1.707 +
1.708 +CLASS_GRAPH = YES
1.709 +
1.710 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.711 +# will generate a graph for each documented class showing the direct and
1.712 +# indirect implementation dependencies (inheritance, containment, and
1.713 +# class references variables) of the class with other documented classes.
1.714 +
1.715 +COLLABORATION_GRAPH = YES
1.716 +
1.717 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1.718 +# tags are set to YES then doxygen will generate a graph for each documented
1.719 +# file showing the direct and indirect include dependencies of the file with
1.720 +# other documented files.
1.721 +
1.722 +INCLUDE_GRAPH = YES
1.723 +
1.724 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1.725 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1.726 +# documented header file showing the documented files that directly or
1.727 +# indirectly include this file.
1.728 +
1.729 +INCLUDED_BY_GRAPH = YES
1.730 +
1.731 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1.732 +# will graphical hierarchy of all classes instead of a textual one.
1.733 +
1.734 +GRAPHICAL_HIERARCHY = YES
1.735 +
1.736 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
1.737 +# found. If left blank, it is assumed the dot tool can be found on the path.
1.738 +
1.739 +DOT_PATH =
1.740 +
1.741 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1.742 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.743 +# this value, doxygen will try to truncate the graph, so that it fits within
1.744 +# the specified constraint. Beware that most browsers cannot cope with very
1.745 +# large images.
1.746 +
1.747 +MAX_DOT_GRAPH_WIDTH = 1024
1.748 +
1.749 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1.750 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.751 +# this value, doxygen will try to truncate the graph, so that it fits within
1.752 +# the specified constraint. Beware that most browsers cannot cope with very
1.753 +# large images.
1.754 +
1.755 +MAX_DOT_GRAPH_HEIGHT = 1024
1.756 +
1.757 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1.758 +# generate a legend page explaining the meaning of the various boxes and
1.759 +# arrows in the dot generated graphs.
1.760 +
1.761 +GENERATE_LEGEND = YES
1.762 +
1.763 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1.764 +# remove the intermedate dot files that are used to generate
1.765 +# the various graphs.
1.766 +
1.767 +DOT_CLEANUP = YES
1.768 +
1.769 +#---------------------------------------------------------------------------
1.770 +# Configuration::addtions related to the search engine
1.771 +#---------------------------------------------------------------------------
1.772 +
1.773 +# The SEARCHENGINE tag specifies whether or not a search engine should be
1.774 +# used. If set to NO the values of all tags below this one will be ignored.
1.775 +
1.776 +SEARCHENGINE = NO
1.777 +
1.778 +# The CGI_NAME tag should be the name of the CGI script that
1.779 +# starts the search engine (doxysearch) with the correct parameters.
1.780 +# A script with this name will be generated by doxygen.
1.781 +
1.782 +CGI_NAME =
1.783 +
1.784 +# The CGI_URL tag should be the absolute URL to the directory where the
1.785 +# cgi binaries are located. See the documentation of your http daemon for
1.786 +# details.
1.787 +
1.788 +CGI_URL =
1.789 +
1.790 +# The DOC_URL tag should be the absolute URL to the directory where the
1.791 +# documentation is located. If left blank the absolute path to the
1.792 +# documentation, with file:// prepended to it, will be used.
1.793 +
1.794 +DOC_URL =
1.795 +
1.796 +# The DOC_ABSPATH tag should be the absolute path to the directory where the
1.797 +# documentation is located. If left blank the directory on the local machine
1.798 +# will be used.
1.799 +
1.800 +DOC_ABSPATH =
1.801 +
1.802 +# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
1.803 +# is installed.
1.804 +
1.805 +BIN_ABSPATH =
1.806 +
1.807 +# The EXT_DOC_PATHS tag can be used to specify one or more paths to
1.808 +# documentation generated for other projects. This allows doxysearch to search
1.809 +# the documentation for these projects as well.
1.810 +
1.811 +EXT_DOC_PATHS =