1.1 --- a/bootstrap Tue Apr 05 06:41:21 2005 +0000
1.2 +++ b/bootstrap Tue Apr 05 08:43:51 2005 +0000
1.3 @@ -1,4 +1,71 @@
1.4 -#! /bin/sh
1.5 -aclocal-1.7 \
1.6 -&& automake-1.7 --gnu --add-missing \
1.7 -&& autoconf
1.8 +#!/bin/bash
1.9 +
1.10 +prev=
1.11 +for option
1.12 +do
1.13 + if test -n "$prev"
1.14 + then
1.15 + eval "$prev=\$option"
1.16 + prev=
1.17 + continue
1.18 + fi
1.19 +
1.20 + optarg=`expr "x$option" : 'x[^=]*=\(.*\)'`
1.21 +
1.22 + case $option in
1.23 +
1.24 + -amver | --amver)
1.25 + prev=amver ;;
1.26 + -amver=* | --amver=*)
1.27 + amver=$optarg ;;
1.28 +
1.29 + -acver | --acver)
1.30 + prev=acver ;;
1.31 + -acver=* | --acver=*)
1.32 + acver=$optarg ;;
1.33 +
1.34 + --help | -h)
1.35 + cat << EOF
1.36 +Usage: $0 [OPTION]
1.37 +
1.38 +Options:
1.39 + -h, --help display this help and exit
1.40 + --amver=VERSION use VERSION version of automake
1.41 + --acver=VERSION use VERSION version of autoconf
1.42 +
1.43 +Expamle:
1.44 + $0 --amver=1.8 --acver=2.59
1.45 +EOF
1.46 + exit 0
1.47 + ;;
1.48 +
1.49 + *)
1.50 + cat << EOF >&2
1.51 +$0: unrecognized option: $option
1.52 +Try \`$0 --help' for more information.
1.53 +EOF
1.54 + exit 1
1.55 + ;;
1.56 +
1.57 + esac
1.58 +done
1.59 +
1.60 +automake=automake
1.61 +aclocal=aclocal
1.62 +autoconf=autoconf
1.63 +
1.64 +if test -n "$amver"
1.65 +then
1.66 + automake=automake-$amver
1.67 + aclocal=aclocal-$amver
1.68 +fi
1.69 +
1.70 +if test -n "$acver"
1.71 +then
1.72 + autoconf=autoconf-$acver
1.73 +fi
1.74 +
1.75 +$aclocal \
1.76 +&& libtoolize --force --copy \
1.77 +&& $automake --add-missing --copy --gnu \
1.78 +&& $autoconf
2.1 --- a/configure.ac Tue Apr 05 06:41:21 2005 +0000
2.2 +++ b/configure.ac Tue Apr 05 08:43:51 2005 +0000
2.3 @@ -6,8 +6,9 @@
2.4 AC_PREREQ(2.57)
2.5
2.6 dnl Checks for programs.
2.7 -AC_PROG_CC
2.8 AC_PROG_CXX
2.9 +AC_PROG_INSTALL
2.10 +AC_PROG_LIBTOOL
2.11
2.12 CXXFLAGS="$CXXFLAGS -Wall"
2.13
2.14 @@ -27,5 +28,16 @@
2.15 AC_HEADER_STDC
2.16 AC_CHECK_FUNCS(gettimeofday times ctime_r)
2.17
2.18 -AC_CONFIG_FILES([Makefile doc/Makefile src/Makefile src/lemon/Makefile src/test/Makefile src/benchmark/Makefile src/demo/Makefile autopackage/default.apspec])
2.19 +AC_CONFIG_FILES([
2.20 +Makefile
2.21 +autopackage/default.apspec
2.22 +doc/Makefile
2.23 +doc/Doxyfile
2.24 +src/Makefile
2.25 +src/lemon/Makefile
2.26 +src/lemon/lemon.pc
2.27 +src/benchmark/Makefile
2.28 +src/demo/Makefile
2.29 +src/test/Makefile
2.30 +])
2.31 AC_OUTPUT
3.1 --- a/doc/Doxyfile Tue Apr 05 06:41:21 2005 +0000
3.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
3.3 @@ -1,1234 +0,0 @@
3.4 -# Doxyfile 1.4.0
3.5 -
3.6 -# This file describes the settings to be used by the documentation system
3.7 -# doxygen (www.doxygen.org) for a project
3.8 -#
3.9 -# All text after a hash (#) is considered a comment and will be ignored
3.10 -# The format is:
3.11 -# TAG = value [value, ...]
3.12 -# For lists items can also be appended using:
3.13 -# TAG += value [value, ...]
3.14 -# Values that contain spaces should be placed between quotes (" ")
3.15 -
3.16 -#---------------------------------------------------------------------------
3.17 -# Project related configuration options
3.18 -#---------------------------------------------------------------------------
3.19 -
3.20 -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
3.21 -# by quotes) that should identify the project.
3.22 -
3.23 -PROJECT_NAME = LEMON
3.24 -
3.25 -# The PROJECT_NUMBER tag can be used to enter a project or revision number.
3.26 -# This could be handy for archiving the generated documentation or
3.27 -# if some version control system is used.
3.28 -
3.29 -PROJECT_NUMBER = 0.4
3.30 -
3.31 -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
3.32 -# base path where the generated documentation will be put.
3.33 -# If a relative path is entered, it will be relative to the location
3.34 -# where doxygen was started. If left blank the current directory will be used.
3.35 -
3.36 -OUTPUT_DIRECTORY =
3.37 -
3.38 -# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
3.39 -# 4096 sub-directories (in 2 levels) under the output directory of each output
3.40 -# format and will distribute the generated files over these directories.
3.41 -# Enabling this option can be useful when feeding doxygen a huge amount of
3.42 -# source files, where putting all generated files in the same directory would
3.43 -# otherwise cause performance problems for the file system.
3.44 -
3.45 -CREATE_SUBDIRS = NO
3.46 -
3.47 -# The OUTPUT_LANGUAGE tag is used to specify the language in which all
3.48 -# documentation generated by doxygen is written. Doxygen will use this
3.49 -# information to generate all constant output in the proper language.
3.50 -# The default language is English, other supported languages are:
3.51 -# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
3.52 -# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
3.53 -# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
3.54 -# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
3.55 -# Swedish, and Ukrainian.
3.56 -
3.57 -OUTPUT_LANGUAGE = English
3.58 -
3.59 -# This tag can be used to specify the encoding used in the generated output.
3.60 -# The encoding is not always determined by the language that is chosen,
3.61 -# but also whether or not the output is meant for Windows or non-Windows users.
3.62 -# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
3.63 -# forces the Windows encoding (this is the default for the Windows binary),
3.64 -# whereas setting the tag to NO uses a Unix-style encoding (the default for
3.65 -# all platforms other than Windows).
3.66 -
3.67 -USE_WINDOWS_ENCODING = NO
3.68 -
3.69 -# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
3.70 -# include brief member descriptions after the members that are listed in
3.71 -# the file and class documentation (similar to JavaDoc).
3.72 -# Set to NO to disable this.
3.73 -
3.74 -BRIEF_MEMBER_DESC = YES
3.75 -
3.76 -# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
3.77 -# the brief description of a member or function before the detailed description.
3.78 -# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
3.79 -# brief descriptions will be completely suppressed.
3.80 -
3.81 -REPEAT_BRIEF = NO
3.82 -
3.83 -# This tag implements a quasi-intelligent brief description abbreviator
3.84 -# that is used to form the text in various listings. Each string
3.85 -# in this list, if found as the leading text of the brief description, will be
3.86 -# stripped from the text and the result after processing the whole list, is
3.87 -# used as the annotated text. Otherwise, the brief description is used as-is.
3.88 -# If left blank, the following values are used ("$name" is automatically
3.89 -# replaced with the name of the entity): "The $name class" "The $name widget"
3.90 -# "The $name file" "is" "provides" "specifies" "contains"
3.91 -# "represents" "a" "an" "the"
3.92 -
3.93 -ABBREVIATE_BRIEF =
3.94 -
3.95 -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
3.96 -# Doxygen will generate a detailed section even if there is only a brief
3.97 -# description.
3.98 -
3.99 -ALWAYS_DETAILED_SEC = NO
3.100 -
3.101 -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
3.102 -# inherited members of a class in the documentation of that class as if those
3.103 -# members were ordinary class members. Constructors, destructors and assignment
3.104 -# operators of the base classes will not be shown.
3.105 -
3.106 -INLINE_INHERITED_MEMB = NO
3.107 -
3.108 -# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
3.109 -# path before files name in the file list and in the header files. If set
3.110 -# to NO the shortest path that makes the file name unique will be used.
3.111 -
3.112 -FULL_PATH_NAMES = YES
3.113 -
3.114 -# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
3.115 -# can be used to strip a user-defined part of the path. Stripping is
3.116 -# only done if one of the specified strings matches the left-hand part of
3.117 -# the path. The tag can be used to show relative paths in the file list.
3.118 -# If left blank the directory from which doxygen is run is used as the
3.119 -# path to strip.
3.120 -
3.121 -STRIP_FROM_PATH = ../src
3.122 -
3.123 -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
3.124 -# the path mentioned in the documentation of a class, which tells
3.125 -# the reader which header file to include in order to use a class.
3.126 -# If left blank only the name of the header file containing the class
3.127 -# definition is used. Otherwise one should specify the include paths that
3.128 -# are normally passed to the compiler using the -I flag.
3.129 -
3.130 -STRIP_FROM_INC_PATH = ../src
3.131 -
3.132 -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
3.133 -# (but less readable) file names. This can be useful is your file systems
3.134 -# doesn't support long names like on DOS, Mac, or CD-ROM.
3.135 -
3.136 -SHORT_NAMES = NO
3.137 -
3.138 -# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
3.139 -# will interpret the first line (until the first dot) of a JavaDoc-style
3.140 -# comment as the brief description. If set to NO, the JavaDoc
3.141 -# comments will behave just like the Qt-style comments (thus requiring an
3.142 -# explicit @brief command for a brief description.
3.143 -
3.144 -JAVADOC_AUTOBRIEF = NO
3.145 -
3.146 -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
3.147 -# treat a multi-line C++ special comment block (i.e. a block of //! or ///
3.148 -# comments) as a brief description. This used to be the default behaviour.
3.149 -# The new default is to treat a multi-line C++ comment block as a detailed
3.150 -# description. Set this tag to YES if you prefer the old behaviour instead.
3.151 -
3.152 -MULTILINE_CPP_IS_BRIEF = NO
3.153 -
3.154 -# If the DETAILS_AT_TOP tag is set to YES then Doxygen
3.155 -# will output the detailed description near the top, like JavaDoc.
3.156 -# If set to NO, the detailed description appears after the member
3.157 -# documentation.
3.158 -
3.159 -DETAILS_AT_TOP = YES
3.160 -
3.161 -# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
3.162 -# member inherits the documentation from any documented member that it
3.163 -# re-implements.
3.164 -
3.165 -INHERIT_DOCS = NO
3.166 -
3.167 -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
3.168 -# tag is set to YES, then doxygen will reuse the documentation of the first
3.169 -# member in the group (if any) for the other members of the group. By default
3.170 -# all members of a group must be documented explicitly.
3.171 -
3.172 -DISTRIBUTE_GROUP_DOC = NO
3.173 -
3.174 -# The TAB_SIZE tag can be used to set the number of spaces in a tab.
3.175 -# Doxygen uses this value to replace tabs by spaces in code fragments.
3.176 -
3.177 -TAB_SIZE = 8
3.178 -
3.179 -# This tag can be used to specify a number of aliases that acts
3.180 -# as commands in the documentation. An alias has the form "name=value".
3.181 -# For example adding "sideeffect=\par Side Effects:\n" will allow you to
3.182 -# put the command \sideeffect (or @sideeffect) in the documentation, which
3.183 -# will result in a user-defined paragraph with heading "Side Effects:".
3.184 -# You can put \n's in the value part of an alias to insert newlines.
3.185 -
3.186 -ALIASES =
3.187 -
3.188 -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
3.189 -# sources only. Doxygen will then generate output that is more tailored for C.
3.190 -# For instance, some of the names that are used will be different. The list
3.191 -# of all members will be omitted, etc.
3.192 -
3.193 -OPTIMIZE_OUTPUT_FOR_C = NO
3.194 -
3.195 -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
3.196 -# only. Doxygen will then generate output that is more tailored for Java.
3.197 -# For instance, namespaces will be presented as packages, qualified scopes
3.198 -# will look different, etc.
3.199 -
3.200 -OPTIMIZE_OUTPUT_JAVA = NO
3.201 -
3.202 -# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
3.203 -# the same type (for instance a group of public functions) to be put as a
3.204 -# subgroup of that type (e.g. under the Public Functions section). Set it to
3.205 -# NO to prevent subgrouping. Alternatively, this can be done per class using
3.206 -# the \nosubgrouping command.
3.207 -
3.208 -SUBGROUPING = YES
3.209 -
3.210 -#---------------------------------------------------------------------------
3.211 -# Build related configuration options
3.212 -#---------------------------------------------------------------------------
3.213 -
3.214 -# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
3.215 -# documentation are documented, even if no documentation was available.
3.216 -# Private class members and static file members will be hidden unless
3.217 -# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
3.218 -
3.219 -EXTRACT_ALL = NO
3.220 -
3.221 -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
3.222 -# will be included in the documentation.
3.223 -
3.224 -EXTRACT_PRIVATE = NO
3.225 -
3.226 -# If the EXTRACT_STATIC tag is set to YES all static members of a file
3.227 -# will be included in the documentation.
3.228 -
3.229 -EXTRACT_STATIC = NO
3.230 -
3.231 -# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
3.232 -# defined locally in source files will be included in the documentation.
3.233 -# If set to NO only classes defined in header files are included.
3.234 -
3.235 -EXTRACT_LOCAL_CLASSES = YES
3.236 -
3.237 -# This flag is only useful for Objective-C code. When set to YES local
3.238 -# methods, which are defined in the implementation section but not in
3.239 -# the interface are included in the documentation.
3.240 -# If set to NO (the default) only methods in the interface are included.
3.241 -
3.242 -EXTRACT_LOCAL_METHODS = NO
3.243 -
3.244 -# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
3.245 -# undocumented members of documented classes, files or namespaces.
3.246 -# If set to NO (the default) these members will be included in the
3.247 -# various overviews, but no documentation section is generated.
3.248 -# This option has no effect if EXTRACT_ALL is enabled.
3.249 -
3.250 -HIDE_UNDOC_MEMBERS = YES
3.251 -
3.252 -# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
3.253 -# undocumented classes that are normally visible in the class hierarchy.
3.254 -# If set to NO (the default) these classes will be included in the various
3.255 -# overviews. This option has no effect if EXTRACT_ALL is enabled.
3.256 -
3.257 -HIDE_UNDOC_CLASSES = YES
3.258 -
3.259 -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
3.260 -# friend (class|struct|union) declarations.
3.261 -# If set to NO (the default) these declarations will be included in the
3.262 -# documentation.
3.263 -
3.264 -HIDE_FRIEND_COMPOUNDS = NO
3.265 -
3.266 -# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
3.267 -# documentation blocks found inside the body of a function.
3.268 -# If set to NO (the default) these blocks will be appended to the
3.269 -# function's detailed documentation block.
3.270 -
3.271 -HIDE_IN_BODY_DOCS = NO
3.272 -
3.273 -# The INTERNAL_DOCS tag determines if documentation
3.274 -# that is typed after a \internal command is included. If the tag is set
3.275 -# to NO (the default) then the documentation will be excluded.
3.276 -# Set it to YES to include the internal documentation.
3.277 -
3.278 -INTERNAL_DOCS = NO
3.279 -
3.280 -# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
3.281 -# file names in lower-case letters. If set to YES upper-case letters are also
3.282 -# allowed. This is useful if you have classes or files whose names only differ
3.283 -# in case and if your file system supports case sensitive file names. Windows
3.284 -# and Mac users are advised to set this option to NO.
3.285 -
3.286 -CASE_SENSE_NAMES = YES
3.287 -
3.288 -# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
3.289 -# will show members with their full class and namespace scopes in the
3.290 -# documentation. If set to YES the scope will be hidden.
3.291 -
3.292 -HIDE_SCOPE_NAMES = YES
3.293 -
3.294 -# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
3.295 -# will put a list of the files that are included by a file in the documentation
3.296 -# of that file.
3.297 -
3.298 -SHOW_INCLUDE_FILES = YES
3.299 -
3.300 -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
3.301 -# is inserted in the documentation for inline members.
3.302 -
3.303 -INLINE_INFO = YES
3.304 -
3.305 -# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
3.306 -# will sort the (detailed) documentation of file and class members
3.307 -# alphabetically by member name. If set to NO the members will appear in
3.308 -# declaration order.
3.309 -
3.310 -SORT_MEMBER_DOCS = NO
3.311 -
3.312 -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
3.313 -# brief documentation of file, namespace and class members alphabetically
3.314 -# by member name. If set to NO (the default) the members will appear in
3.315 -# declaration order.
3.316 -
3.317 -SORT_BRIEF_DOCS = NO
3.318 -
3.319 -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
3.320 -# sorted by fully-qualified names, including namespaces. If set to
3.321 -# NO (the default), the class list will be sorted only by class name,
3.322 -# not including the namespace part.
3.323 -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
3.324 -# Note: This option applies only to the class list, not to the
3.325 -# alphabetical list.
3.326 -
3.327 -SORT_BY_SCOPE_NAME = NO
3.328 -
3.329 -# The GENERATE_TODOLIST tag can be used to enable (YES) or
3.330 -# disable (NO) the todo list. This list is created by putting \todo
3.331 -# commands in the documentation.
3.332 -
3.333 -GENERATE_TODOLIST = YES
3.334 -
3.335 -# The GENERATE_TESTLIST tag can be used to enable (YES) or
3.336 -# disable (NO) the test list. This list is created by putting \test
3.337 -# commands in the documentation.
3.338 -
3.339 -GENERATE_TESTLIST = YES
3.340 -
3.341 -# The GENERATE_BUGLIST tag can be used to enable (YES) or
3.342 -# disable (NO) the bug list. This list is created by putting \bug
3.343 -# commands in the documentation.
3.344 -
3.345 -GENERATE_BUGLIST = YES
3.346 -
3.347 -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
3.348 -# disable (NO) the deprecated list. This list is created by putting
3.349 -# \deprecated commands in the documentation.
3.350 -
3.351 -GENERATE_DEPRECATEDLIST= YES
3.352 -
3.353 -# The ENABLED_SECTIONS tag can be used to enable conditional
3.354 -# documentation sections, marked by \if sectionname ... \endif.
3.355 -
3.356 -ENABLED_SECTIONS =
3.357 -
3.358 -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
3.359 -# the initial value of a variable or define consists of for it to appear in
3.360 -# the documentation. If the initializer consists of more lines than specified
3.361 -# here it will be hidden. Use a value of 0 to hide initializers completely.
3.362 -# The appearance of the initializer of individual variables and defines in the
3.363 -# documentation can be controlled using \showinitializer or \hideinitializer
3.364 -# command in the documentation regardless of this setting.
3.365 -
3.366 -MAX_INITIALIZER_LINES = 5
3.367 -
3.368 -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
3.369 -# at the bottom of the documentation of classes and structs. If set to YES the
3.370 -# list will mention the files that were used to generate the documentation.
3.371 -
3.372 -SHOW_USED_FILES = YES
3.373 -
3.374 -# If the sources in your project are distributed over multiple directories
3.375 -# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
3.376 -# in the documentation.
3.377 -
3.378 -SHOW_DIRECTORIES = YES
3.379 -
3.380 -# The FILE_VERSION_FILTER tag can be used to specify a program or script that
3.381 -# doxygen should invoke to get the current version for each file (typically from the
3.382 -# version control system). Doxygen will invoke the program by executing (via
3.383 -# popen()) the command <command> <input-file>, where <command> is the value of
3.384 -# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
3.385 -# provided by doxygen. Whatever the progam writes to standard output
3.386 -# is used as the file version. See the manual for examples.
3.387 -
3.388 -FILE_VERSION_FILTER =
3.389 -
3.390 -#---------------------------------------------------------------------------
3.391 -# configuration options related to warning and progress messages
3.392 -#---------------------------------------------------------------------------
3.393 -
3.394 -# The QUIET tag can be used to turn on/off the messages that are generated
3.395 -# by doxygen. Possible values are YES and NO. If left blank NO is used.
3.396 -
3.397 -QUIET = NO
3.398 -
3.399 -# The WARNINGS tag can be used to turn on/off the warning messages that are
3.400 -# generated by doxygen. Possible values are YES and NO. If left blank
3.401 -# NO is used.
3.402 -
3.403 -WARNINGS = YES
3.404 -
3.405 -# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
3.406 -# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
3.407 -# automatically be disabled.
3.408 -
3.409 -WARN_IF_UNDOCUMENTED = YES
3.410 -
3.411 -# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
3.412 -# potential errors in the documentation, such as not documenting some
3.413 -# parameters in a documented function, or documenting parameters that
3.414 -# don't exist or using markup commands wrongly.
3.415 -
3.416 -WARN_IF_DOC_ERROR = YES
3.417 -
3.418 -# This WARN_NO_PARAMDOC option can be abled to get warnings for
3.419 -# functions that are documented, but have no documentation for their parameters
3.420 -# or return value. If set to NO (the default) doxygen will only warn about
3.421 -# wrong or incomplete parameter documentation, but not about the absence of
3.422 -# documentation.
3.423 -
3.424 -WARN_NO_PARAMDOC = NO
3.425 -
3.426 -# The WARN_FORMAT tag determines the format of the warning messages that
3.427 -# doxygen can produce. The string should contain the $file, $line, and $text
3.428 -# tags, which will be replaced by the file and line number from which the
3.429 -# warning originated and the warning text. Optionally the format may contain
3.430 -# $version, which will be replaced by the version of the file (if it could
3.431 -# be obtained via FILE_VERSION_FILTER)
3.432 -
3.433 -WARN_FORMAT = "$file:$line: $text"
3.434 -
3.435 -# The WARN_LOGFILE tag can be used to specify a file to which warning
3.436 -# and error messages should be written. If left blank the output is written
3.437 -# to stderr.
3.438 -
3.439 -WARN_LOGFILE = doxygen.log
3.440 -
3.441 -#---------------------------------------------------------------------------
3.442 -# configuration options related to the input files
3.443 -#---------------------------------------------------------------------------
3.444 -
3.445 -# The INPUT tag can be used to specify the files and/or directories that contain
3.446 -# documented source files. You may enter file names like "myfile.cpp" or
3.447 -# directories like "/usr/src/myproject". Separate the files or directories
3.448 -# with spaces.
3.449 -
3.450 -INPUT = mainpage.dox \
3.451 - getstart.dox \
3.452 - quicktour.dox \
3.453 - demoprograms.dox \
3.454 - graphs.dox \
3.455 - undir_graphs.dox \
3.456 - named-param.dox \
3.457 - maps.dox \
3.458 - coding_style.dox \
3.459 - groups.dox \
3.460 - namespaces.dox \
3.461 - license.dox \
3.462 - developers_interface.dox \
3.463 - graph_io.dox \
3.464 - dirs.dox \
3.465 - gwrappers.dox \
3.466 - ../src/lemon \
3.467 - ../src/lemon/concept \
3.468 - ../src/demo \
3.469 - ../src/test/test_tools.h
3.470 -
3.471 -# If the value of the INPUT tag contains directories, you can use the
3.472 -# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
3.473 -# and *.h) to filter out the source-files in the directories. If left
3.474 -# blank the following patterns are tested:
3.475 -# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
3.476 -# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
3.477 -
3.478 -FILE_PATTERNS =
3.479 -
3.480 -# The RECURSIVE tag can be used to turn specify whether or not subdirectories
3.481 -# should be searched for input files as well. Possible values are YES and NO.
3.482 -# If left blank NO is used.
3.483 -
3.484 -RECURSIVE = NO
3.485 -
3.486 -# The EXCLUDE tag can be used to specify files and/or directories that should
3.487 -# excluded from the INPUT source files. This way you can easily exclude a
3.488 -# subdirectory from a directory tree whose root is specified with the INPUT tag.
3.489 -
3.490 -EXCLUDE =
3.491 -
3.492 -# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
3.493 -# directories that are symbolic links (a Unix filesystem feature) are excluded
3.494 -# from the input.
3.495 -
3.496 -EXCLUDE_SYMLINKS = NO
3.497 -
3.498 -# If the value of the INPUT tag contains directories, you can use the
3.499 -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
3.500 -# certain files from those directories.
3.501 -
3.502 -EXCLUDE_PATTERNS =
3.503 -
3.504 -# The EXAMPLE_PATH tag can be used to specify one or more files or
3.505 -# directories that contain example code fragments that are included (see
3.506 -# the \include command).
3.507 -
3.508 -EXAMPLE_PATH = ../src/demo \
3.509 - ../LICENSE \
3.510 - .
3.511 -
3.512 -# If the value of the EXAMPLE_PATH tag contains directories, you can use the
3.513 -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
3.514 -# and *.h) to filter out the source-files in the directories. If left
3.515 -# blank all files are included.
3.516 -
3.517 -EXAMPLE_PATTERNS =
3.518 -
3.519 -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
3.520 -# searched for input files to be used with the \include or \dontinclude
3.521 -# commands irrespective of the value of the RECURSIVE tag.
3.522 -# Possible values are YES and NO. If left blank NO is used.
3.523 -
3.524 -EXAMPLE_RECURSIVE = NO
3.525 -
3.526 -# The IMAGE_PATH tag can be used to specify one or more files or
3.527 -# directories that contain image that are included in the documentation (see
3.528 -# the \image command).
3.529 -
3.530 -IMAGE_PATH = images
3.531 -
3.532 -# The INPUT_FILTER tag can be used to specify a program that doxygen should
3.533 -# invoke to filter for each input file. Doxygen will invoke the filter program
3.534 -# by executing (via popen()) the command <filter> <input-file>, where <filter>
3.535 -# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
3.536 -# input file. Doxygen will then use the output that the filter program writes
3.537 -# to standard output. If FILTER_PATTERNS is specified, this tag will be
3.538 -# ignored.
3.539 -
3.540 -INPUT_FILTER =
3.541 -
3.542 -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
3.543 -# basis. Doxygen will compare the file name with each pattern and apply the
3.544 -# filter if there is a match. The filters are a list of the form:
3.545 -# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
3.546 -# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
3.547 -# is applied to all files.
3.548 -
3.549 -FILTER_PATTERNS =
3.550 -
3.551 -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
3.552 -# INPUT_FILTER) will be used to filter the input files when producing source
3.553 -# files to browse (i.e. when SOURCE_BROWSER is set to YES).
3.554 -
3.555 -FILTER_SOURCE_FILES = NO
3.556 -
3.557 -#---------------------------------------------------------------------------
3.558 -# configuration options related to source browsing
3.559 -#---------------------------------------------------------------------------
3.560 -
3.561 -# If the SOURCE_BROWSER tag is set to YES then a list of source files will
3.562 -# be generated. Documented entities will be cross-referenced with these sources.
3.563 -# Note: To get rid of all source code in the generated output, make sure also
3.564 -# VERBATIM_HEADERS is set to NO.
3.565 -
3.566 -SOURCE_BROWSER = YES
3.567 -
3.568 -# Setting the INLINE_SOURCES tag to YES will include the body
3.569 -# of functions and classes directly in the documentation.
3.570 -
3.571 -INLINE_SOURCES = NO
3.572 -
3.573 -# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
3.574 -# doxygen to hide any special comment blocks from generated source code
3.575 -# fragments. Normal C and C++ comments will always remain visible.
3.576 -
3.577 -STRIP_CODE_COMMENTS = YES
3.578 -
3.579 -# If the REFERENCED_BY_RELATION tag is set to YES (the default)
3.580 -# then for each documented function all documented
3.581 -# functions referencing it will be listed.
3.582 -
3.583 -REFERENCED_BY_RELATION = NO
3.584 -
3.585 -# If the REFERENCES_RELATION tag is set to YES (the default)
3.586 -# then for each documented function all documented entities
3.587 -# called/used by that function will be listed.
3.588 -
3.589 -REFERENCES_RELATION = NO
3.590 -
3.591 -# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
3.592 -# will generate a verbatim copy of the header file for each class for
3.593 -# which an include is specified. Set to NO to disable this.
3.594 -
3.595 -VERBATIM_HEADERS = YES
3.596 -
3.597 -#---------------------------------------------------------------------------
3.598 -# configuration options related to the alphabetical class index
3.599 -#---------------------------------------------------------------------------
3.600 -
3.601 -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
3.602 -# of all compounds will be generated. Enable this if the project
3.603 -# contains a lot of classes, structs, unions or interfaces.
3.604 -
3.605 -ALPHABETICAL_INDEX = YES
3.606 -
3.607 -# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
3.608 -# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
3.609 -# in which this list will be split (can be a number in the range [1..20])
3.610 -
3.611 -COLS_IN_ALPHA_INDEX = 2
3.612 -
3.613 -# In case all classes in a project start with a common prefix, all
3.614 -# classes will be put under the same header in the alphabetical index.
3.615 -# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
3.616 -# should be ignored while generating the index headers.
3.617 -
3.618 -IGNORE_PREFIX =
3.619 -
3.620 -#---------------------------------------------------------------------------
3.621 -# configuration options related to the HTML output
3.622 -#---------------------------------------------------------------------------
3.623 -
3.624 -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
3.625 -# generate HTML output.
3.626 -
3.627 -GENERATE_HTML = YES
3.628 -
3.629 -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
3.630 -# If a relative path is entered the value of OUTPUT_DIRECTORY will be
3.631 -# put in front of it. If left blank `html' will be used as the default path.
3.632 -
3.633 -HTML_OUTPUT = html
3.634 -
3.635 -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
3.636 -# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
3.637 -# doxygen will generate files with .html extension.
3.638 -
3.639 -HTML_FILE_EXTENSION = .html
3.640 -
3.641 -# The HTML_HEADER tag can be used to specify a personal HTML header for
3.642 -# each generated HTML page. If it is left blank doxygen will generate a
3.643 -# standard header.
3.644 -
3.645 -HTML_HEADER =
3.646 -
3.647 -# The HTML_FOOTER tag can be used to specify a personal HTML footer for
3.648 -# each generated HTML page. If it is left blank doxygen will generate a
3.649 -# standard footer.
3.650 -
3.651 -HTML_FOOTER =
3.652 -
3.653 -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
3.654 -# style sheet that is used by each HTML page. It can be used to
3.655 -# fine-tune the look of the HTML output. If the tag is left blank doxygen
3.656 -# will generate a default style sheet. Note that doxygen will try to copy
3.657 -# the style sheet file to the HTML output directory, so don't put your own
3.658 -# stylesheet in the HTML output directory as well, or it will be erased!
3.659 -
3.660 -HTML_STYLESHEET =
3.661 -
3.662 -# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
3.663 -# files or namespaces will be aligned in HTML using tables. If set to
3.664 -# NO a bullet list will be used.
3.665 -
3.666 -HTML_ALIGN_MEMBERS = YES
3.667 -
3.668 -# If the GENERATE_HTMLHELP tag is set to YES, additional index files
3.669 -# will be generated that can be used as input for tools like the
3.670 -# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
3.671 -# of the generated HTML documentation.
3.672 -
3.673 -GENERATE_HTMLHELP = NO
3.674 -
3.675 -# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
3.676 -# be used to specify the file name of the resulting .chm file. You
3.677 -# can add a path in front of the file if the result should not be
3.678 -# written to the html output directory.
3.679 -
3.680 -CHM_FILE =
3.681 -
3.682 -# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
3.683 -# be used to specify the location (absolute path including file name) of
3.684 -# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
3.685 -# the HTML help compiler on the generated index.hhp.
3.686 -
3.687 -HHC_LOCATION =
3.688 -
3.689 -# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
3.690 -# controls if a separate .chi index file is generated (YES) or that
3.691 -# it should be included in the master .chm file (NO).
3.692 -
3.693 -GENERATE_CHI = NO
3.694 -
3.695 -# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
3.696 -# controls whether a binary table of contents is generated (YES) or a
3.697 -# normal table of contents (NO) in the .chm file.
3.698 -
3.699 -BINARY_TOC = NO
3.700 -
3.701 -# The TOC_EXPAND flag can be set to YES to add extra items for group members
3.702 -# to the contents of the HTML help documentation and to the tree view.
3.703 -
3.704 -TOC_EXPAND = NO
3.705 -
3.706 -# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
3.707 -# top of each HTML page. The value NO (the default) enables the index and
3.708 -# the value YES disables it.
3.709 -
3.710 -DISABLE_INDEX = NO
3.711 -
3.712 -# This tag can be used to set the number of enum values (range [1..20])
3.713 -# that doxygen will group on one line in the generated HTML documentation.
3.714 -
3.715 -ENUM_VALUES_PER_LINE = 4
3.716 -
3.717 -# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
3.718 -# generated containing a tree-like index structure (just like the one that
3.719 -# is generated for HTML Help). For this to work a browser that supports
3.720 -# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
3.721 -# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
3.722 -# probably better off using the HTML help feature.
3.723 -
3.724 -GENERATE_TREEVIEW = YES
3.725 -
3.726 -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
3.727 -# used to set the initial width (in pixels) of the frame in which the tree
3.728 -# is shown.
3.729 -
3.730 -TREEVIEW_WIDTH = 250
3.731 -
3.732 -#---------------------------------------------------------------------------
3.733 -# configuration options related to the LaTeX output
3.734 -#---------------------------------------------------------------------------
3.735 -
3.736 -# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
3.737 -# generate Latex output.
3.738 -
3.739 -GENERATE_LATEX = NO
3.740 -
3.741 -# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
3.742 -# If a relative path is entered the value of OUTPUT_DIRECTORY will be
3.743 -# put in front of it. If left blank `latex' will be used as the default path.
3.744 -
3.745 -LATEX_OUTPUT = latex
3.746 -
3.747 -# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
3.748 -# invoked. If left blank `latex' will be used as the default command name.
3.749 -
3.750 -LATEX_CMD_NAME = latex
3.751 -
3.752 -# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
3.753 -# generate index for LaTeX. If left blank `makeindex' will be used as the
3.754 -# default command name.
3.755 -
3.756 -MAKEINDEX_CMD_NAME = makeindex
3.757 -
3.758 -# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
3.759 -# LaTeX documents. This may be useful for small projects and may help to
3.760 -# save some trees in general.
3.761 -
3.762 -COMPACT_LATEX = YES
3.763 -
3.764 -# The PAPER_TYPE tag can be used to set the paper type that is used
3.765 -# by the printer. Possible values are: a4, a4wide, letter, legal and
3.766 -# executive. If left blank a4wide will be used.
3.767 -
3.768 -PAPER_TYPE = a4wide
3.769 -
3.770 -# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
3.771 -# packages that should be included in the LaTeX output.
3.772 -
3.773 -EXTRA_PACKAGES = amsmath \
3.774 - amssymb
3.775 -
3.776 -# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
3.777 -# the generated latex document. The header should contain everything until
3.778 -# the first chapter. If it is left blank doxygen will generate a
3.779 -# standard header. Notice: only use this tag if you know what you are doing!
3.780 -
3.781 -LATEX_HEADER =
3.782 -
3.783 -# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
3.784 -# is prepared for conversion to pdf (using ps2pdf). The pdf file will
3.785 -# contain links (just like the HTML output) instead of page references
3.786 -# This makes the output suitable for online browsing using a pdf viewer.
3.787 -
3.788 -PDF_HYPERLINKS = YES
3.789 -
3.790 -# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
3.791 -# plain latex in the generated Makefile. Set this option to YES to get a
3.792 -# higher quality PDF documentation.
3.793 -
3.794 -USE_PDFLATEX = YES
3.795 -
3.796 -# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
3.797 -# command to the generated LaTeX files. This will instruct LaTeX to keep
3.798 -# running if errors occur, instead of asking the user for help.
3.799 -# This option is also used when generating formulas in HTML.
3.800 -
3.801 -LATEX_BATCHMODE = NO
3.802 -
3.803 -# If LATEX_HIDE_INDICES is set to YES then doxygen will not
3.804 -# include the index chapters (such as File Index, Compound Index, etc.)
3.805 -# in the output.
3.806 -
3.807 -LATEX_HIDE_INDICES = NO
3.808 -
3.809 -#---------------------------------------------------------------------------
3.810 -# configuration options related to the RTF output
3.811 -#---------------------------------------------------------------------------
3.812 -
3.813 -# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
3.814 -# The RTF output is optimized for Word 97 and may not look very pretty with
3.815 -# other RTF readers or editors.
3.816 -
3.817 -GENERATE_RTF = NO
3.818 -
3.819 -# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
3.820 -# If a relative path is entered the value of OUTPUT_DIRECTORY will be
3.821 -# put in front of it. If left blank `rtf' will be used as the default path.
3.822 -
3.823 -RTF_OUTPUT = rtf
3.824 -
3.825 -# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
3.826 -# RTF documents. This may be useful for small projects and may help to
3.827 -# save some trees in general.
3.828 -
3.829 -COMPACT_RTF = NO
3.830 -
3.831 -# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
3.832 -# will contain hyperlink fields. The RTF file will
3.833 -# contain links (just like the HTML output) instead of page references.
3.834 -# This makes the output suitable for online browsing using WORD or other
3.835 -# programs which support those fields.
3.836 -# Note: wordpad (write) and others do not support links.
3.837 -
3.838 -RTF_HYPERLINKS = NO
3.839 -
3.840 -# Load stylesheet definitions from file. Syntax is similar to doxygen's
3.841 -# config file, i.e. a series of assignments. You only have to provide
3.842 -# replacements, missing definitions are set to their default value.
3.843 -
3.844 -RTF_STYLESHEET_FILE =
3.845 -
3.846 -# Set optional variables used in the generation of an rtf document.
3.847 -# Syntax is similar to doxygen's config file.
3.848 -
3.849 -RTF_EXTENSIONS_FILE =
3.850 -
3.851 -#---------------------------------------------------------------------------
3.852 -# configuration options related to the man page output
3.853 -#---------------------------------------------------------------------------
3.854 -
3.855 -# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
3.856 -# generate man pages
3.857 -
3.858 -GENERATE_MAN = NO
3.859 -
3.860 -# The MAN_OUTPUT tag is used to specify where the man pages will be put.
3.861 -# If a relative path is entered the value of OUTPUT_DIRECTORY will be
3.862 -# put in front of it. If left blank `man' will be used as the default path.
3.863 -
3.864 -MAN_OUTPUT = man
3.865 -
3.866 -# The MAN_EXTENSION tag determines the extension that is added to
3.867 -# the generated man pages (default is the subroutine's section .3)
3.868 -
3.869 -MAN_EXTENSION = .3
3.870 -
3.871 -# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
3.872 -# then it will generate one additional man file for each entity
3.873 -# documented in the real man page(s). These additional files
3.874 -# only source the real man page, but without them the man command
3.875 -# would be unable to find the correct page. The default is NO.
3.876 -
3.877 -MAN_LINKS = NO
3.878 -
3.879 -#---------------------------------------------------------------------------
3.880 -# configuration options related to the XML output
3.881 -#---------------------------------------------------------------------------
3.882 -
3.883 -# If the GENERATE_XML tag is set to YES Doxygen will
3.884 -# generate an XML file that captures the structure of
3.885 -# the code including all documentation.
3.886 -
3.887 -GENERATE_XML = NO
3.888 -
3.889 -# The XML_OUTPUT tag is used to specify where the XML pages will be put.
3.890 -# If a relative path is entered the value of OUTPUT_DIRECTORY will be
3.891 -# put in front of it. If left blank `xml' will be used as the default path.
3.892 -
3.893 -XML_OUTPUT = xml
3.894 -
3.895 -# The XML_SCHEMA tag can be used to specify an XML schema,
3.896 -# which can be used by a validating XML parser to check the
3.897 -# syntax of the XML files.
3.898 -
3.899 -XML_SCHEMA =
3.900 -
3.901 -# The XML_DTD tag can be used to specify an XML DTD,
3.902 -# which can be used by a validating XML parser to check the
3.903 -# syntax of the XML files.
3.904 -
3.905 -XML_DTD =
3.906 -
3.907 -# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
3.908 -# dump the program listings (including syntax highlighting
3.909 -# and cross-referencing information) to the XML output. Note that
3.910 -# enabling this will significantly increase the size of the XML output.
3.911 -
3.912 -XML_PROGRAMLISTING = YES
3.913 -
3.914 -#---------------------------------------------------------------------------
3.915 -# configuration options for the AutoGen Definitions output
3.916 -#---------------------------------------------------------------------------
3.917 -
3.918 -# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
3.919 -# generate an AutoGen Definitions (see autogen.sf.net) file
3.920 -# that captures the structure of the code including all
3.921 -# documentation. Note that this feature is still experimental
3.922 -# and incomplete at the moment.
3.923 -
3.924 -GENERATE_AUTOGEN_DEF = NO
3.925 -
3.926 -#---------------------------------------------------------------------------
3.927 -# configuration options related to the Perl module output
3.928 -#---------------------------------------------------------------------------
3.929 -
3.930 -# If the GENERATE_PERLMOD tag is set to YES Doxygen will
3.931 -# generate a Perl module file that captures the structure of
3.932 -# the code including all documentation. Note that this
3.933 -# feature is still experimental and incomplete at the
3.934 -# moment.
3.935 -
3.936 -GENERATE_PERLMOD = NO
3.937 -
3.938 -# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
3.939 -# the necessary Makefile rules, Perl scripts and LaTeX code to be able
3.940 -# to generate PDF and DVI output from the Perl module output.
3.941 -
3.942 -PERLMOD_LATEX = NO
3.943 -
3.944 -# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
3.945 -# nicely formatted so it can be parsed by a human reader. This is useful
3.946 -# if you want to understand what is going on. On the other hand, if this
3.947 -# tag is set to NO the size of the Perl module output will be much smaller
3.948 -# and Perl will parse it just the same.
3.949 -
3.950 -PERLMOD_PRETTY = YES
3.951 -
3.952 -# The names of the make variables in the generated doxyrules.make file
3.953 -# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
3.954 -# This is useful so different doxyrules.make files included by the same
3.955 -# Makefile don't overwrite each other's variables.
3.956 -
3.957 -PERLMOD_MAKEVAR_PREFIX =
3.958 -
3.959 -#---------------------------------------------------------------------------
3.960 -# Configuration options related to the preprocessor
3.961 -#---------------------------------------------------------------------------
3.962 -
3.963 -# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
3.964 -# evaluate all C-preprocessor directives found in the sources and include
3.965 -# files.
3.966 -
3.967 -ENABLE_PREPROCESSING = YES
3.968 -
3.969 -# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
3.970 -# names in the source code. If set to NO (the default) only conditional
3.971 -# compilation will be performed. Macro expansion can be done in a controlled
3.972 -# way by setting EXPAND_ONLY_PREDEF to YES.
3.973 -
3.974 -MACRO_EXPANSION = NO
3.975 -
3.976 -# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
3.977 -# then the macro expansion is limited to the macros specified with the
3.978 -# PREDEFINED and EXPAND_AS_PREDEFINED tags.
3.979 -
3.980 -EXPAND_ONLY_PREDEF = NO
3.981 -
3.982 -# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
3.983 -# in the INCLUDE_PATH (see below) will be search if a #include is found.
3.984 -
3.985 -SEARCH_INCLUDES = YES
3.986 -
3.987 -# The INCLUDE_PATH tag can be used to specify one or more directories that
3.988 -# contain include files that are not input files but should be processed by
3.989 -# the preprocessor.
3.990 -
3.991 -INCLUDE_PATH =
3.992 -
3.993 -# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
3.994 -# patterns (like *.h and *.hpp) to filter out the header-files in the
3.995 -# directories. If left blank, the patterns specified with FILE_PATTERNS will
3.996 -# be used.
3.997 -
3.998 -INCLUDE_FILE_PATTERNS =
3.999 -
3.1000 -# The PREDEFINED tag can be used to specify one or more macro names that
3.1001 -# are defined before the preprocessor is started (similar to the -D option of
3.1002 -# gcc). The argument of the tag is a list of macros of the form: name
3.1003 -# or name=definition (no spaces). If the definition and the = are
3.1004 -# omitted =1 is assumed. To prevent a macro definition from being
3.1005 -# undefined via #undef or recursively expanded use the := operator
3.1006 -# instead of the = operator.
3.1007 -
3.1008 -PREDEFINED = DOXYGEN
3.1009 -
3.1010 -# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
3.1011 -# this tag can be used to specify a list of macro names that should be expanded.
3.1012 -# The macro definition that is found in the sources will be used.
3.1013 -# Use the PREDEFINED tag if you want to use a different macro definition.
3.1014 -
3.1015 -EXPAND_AS_DEFINED =
3.1016 -
3.1017 -# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
3.1018 -# doxygen's preprocessor will remove all function-like macros that are alone
3.1019 -# on a line, have an all uppercase name, and do not end with a semicolon. Such
3.1020 -# function macros are typically used for boiler-plate code, and will confuse
3.1021 -# the parser if not removed.
3.1022 -
3.1023 -SKIP_FUNCTION_MACROS = YES
3.1024 -
3.1025 -#---------------------------------------------------------------------------
3.1026 -# Configuration::additions related to external references
3.1027 -#---------------------------------------------------------------------------
3.1028 -
3.1029 -# The TAGFILES option can be used to specify one or more tagfiles.
3.1030 -# Optionally an initial location of the external documentation
3.1031 -# can be added for each tagfile. The format of a tag file without
3.1032 -# this location is as follows:
3.1033 -# TAGFILES = file1 file2 ...
3.1034 -# Adding location for the tag files is done as follows:
3.1035 -# TAGFILES = file1=loc1 "file2 = loc2" ...
3.1036 -# where "loc1" and "loc2" can be relative or absolute paths or
3.1037 -# URLs. If a location is present for each tag, the installdox tool
3.1038 -# does not have to be run to correct the links.
3.1039 -# Note that each tag file must have a unique name
3.1040 -# (where the name does NOT include the path)
3.1041 -# If a tag file is not located in the directory in which doxygen
3.1042 -# is run, you must also specify the path to the tagfile here.
3.1043 -
3.1044 -TAGFILES =
3.1045 -
3.1046 -# When a file name is specified after GENERATE_TAGFILE, doxygen will create
3.1047 -# a tag file that is based on the input files it reads.
3.1048 -
3.1049 -GENERATE_TAGFILE =
3.1050 -
3.1051 -# If the ALLEXTERNALS tag is set to YES all external classes will be listed
3.1052 -# in the class index. If set to NO only the inherited external classes
3.1053 -# will be listed.
3.1054 -
3.1055 -ALLEXTERNALS = NO
3.1056 -
3.1057 -# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
3.1058 -# in the modules index. If set to NO, only the current project's groups will
3.1059 -# be listed.
3.1060 -
3.1061 -EXTERNAL_GROUPS = YES
3.1062 -
3.1063 -# The PERL_PATH should be the absolute path and name of the perl script
3.1064 -# interpreter (i.e. the result of `which perl').
3.1065 -
3.1066 -PERL_PATH = /usr/bin/perl
3.1067 -
3.1068 -#---------------------------------------------------------------------------
3.1069 -# Configuration options related to the dot tool
3.1070 -#---------------------------------------------------------------------------
3.1071 -
3.1072 -# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
3.1073 -# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
3.1074 -# or super classes. Setting the tag to NO turns the diagrams off. Note that
3.1075 -# this option is superseded by the HAVE_DOT option below. This is only a
3.1076 -# fallback. It is recommended to install and use dot, since it yields more
3.1077 -# powerful graphs.
3.1078 -
3.1079 -CLASS_DIAGRAMS = YES
3.1080 -
3.1081 -# If set to YES, the inheritance and collaboration graphs will hide
3.1082 -# inheritance and usage relations if the target is undocumented
3.1083 -# or is not a class.
3.1084 -
3.1085 -HIDE_UNDOC_RELATIONS = NO
3.1086 -
3.1087 -# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
3.1088 -# available from the path. This tool is part of Graphviz, a graph visualization
3.1089 -# toolkit from AT&T and Lucent Bell Labs. The other options in this section
3.1090 -# have no effect if this option is set to NO (the default)
3.1091 -
3.1092 -HAVE_DOT = YES
3.1093 -
3.1094 -# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
3.1095 -# will generate a graph for each documented class showing the direct and
3.1096 -# indirect inheritance relations. Setting this tag to YES will force the
3.1097 -# the CLASS_DIAGRAMS tag to NO.
3.1098 -
3.1099 -CLASS_GRAPH = YES
3.1100 -
3.1101 -# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
3.1102 -# will generate a graph for each documented class showing the direct and
3.1103 -# indirect implementation dependencies (inheritance, containment, and
3.1104 -# class references variables) of the class with other documented classes.
3.1105 -
3.1106 -COLLABORATION_GRAPH = YES
3.1107 -
3.1108 -# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
3.1109 -# will generate a graph for groups, showing the direct groups dependencies
3.1110 -
3.1111 -GROUP_GRAPHS = YES
3.1112 -
3.1113 -# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
3.1114 -# collaboration diagrams in a style similar to the OMG's Unified Modeling
3.1115 -# Language.
3.1116 -
3.1117 -UML_LOOK = NO
3.1118 -
3.1119 -# If set to YES, the inheritance and collaboration graphs will show the
3.1120 -# relations between templates and their instances.
3.1121 -
3.1122 -TEMPLATE_RELATIONS = YES
3.1123 -
3.1124 -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
3.1125 -# tags are set to YES then doxygen will generate a graph for each documented
3.1126 -# file showing the direct and indirect include dependencies of the file with
3.1127 -# other documented files.
3.1128 -
3.1129 -INCLUDE_GRAPH = YES
3.1130 -
3.1131 -# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
3.1132 -# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
3.1133 -# documented header file showing the documented files that directly or
3.1134 -# indirectly include this file.
3.1135 -
3.1136 -INCLUDED_BY_GRAPH = YES
3.1137 -
3.1138 -# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
3.1139 -# generate a call dependency graph for every global function or class method.
3.1140 -# Note that enabling this option will significantly increase the time of a run.
3.1141 -# So in most cases it will be better to enable call graphs for selected
3.1142 -# functions only using the \callgraph command.
3.1143 -
3.1144 -CALL_GRAPH = YES
3.1145 -
3.1146 -# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
3.1147 -# will graphical hierarchy of all classes instead of a textual one.
3.1148 -
3.1149 -GRAPHICAL_HIERARCHY = YES
3.1150 -
3.1151 -# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
3.1152 -# then doxygen will show the dependencies a directory has on other directories
3.1153 -# in a graphical way. The dependency relations are determined by the #include
3.1154 -# relations between the files in the directories.
3.1155 -
3.1156 -DIRECTORY_GRAPH = YES
3.1157 -
3.1158 -# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
3.1159 -# generated by dot. Possible values are png, jpg, or gif
3.1160 -# If left blank png will be used.
3.1161 -
3.1162 -DOT_IMAGE_FORMAT = png
3.1163 -
3.1164 -# The tag DOT_PATH can be used to specify the path where the dot tool can be
3.1165 -# found. If left blank, it is assumed the dot tool can be found on the path.
3.1166 -
3.1167 -DOT_PATH =
3.1168 -
3.1169 -# The DOTFILE_DIRS tag can be used to specify one or more directories that
3.1170 -# contain dot files that are included in the documentation (see the
3.1171 -# \dotfile command).
3.1172 -
3.1173 -DOTFILE_DIRS =
3.1174 -
3.1175 -# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
3.1176 -# (in pixels) of the graphs generated by dot. If a graph becomes larger than
3.1177 -# this value, doxygen will try to truncate the graph, so that it fits within
3.1178 -# the specified constraint. Beware that most browsers cannot cope with very
3.1179 -# large images.
3.1180 -
3.1181 -MAX_DOT_GRAPH_WIDTH = 1024
3.1182 -
3.1183 -# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
3.1184 -# (in pixels) of the graphs generated by dot. If a graph becomes larger than
3.1185 -# this value, doxygen will try to truncate the graph, so that it fits within
3.1186 -# the specified constraint. Beware that most browsers cannot cope with very
3.1187 -# large images.
3.1188 -
3.1189 -MAX_DOT_GRAPH_HEIGHT = 1024
3.1190 -
3.1191 -# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
3.1192 -# graphs generated by dot. A depth value of 3 means that only nodes reachable
3.1193 -# from the root by following a path via at most 3 edges will be shown. Nodes
3.1194 -# that lay further from the root node will be omitted. Note that setting this
3.1195 -# option to 1 or 2 may greatly reduce the computation time needed for large
3.1196 -# code bases. Also note that a graph may be further truncated if the graph's
3.1197 -# image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
3.1198 -# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
3.1199 -# the graph is not depth-constrained.
3.1200 -
3.1201 -MAX_DOT_GRAPH_DEPTH = 0
3.1202 -
3.1203 -# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
3.1204 -# background. This is disabled by default, which results in a white background.
3.1205 -# Warning: Depending on the platform used, enabling this option may lead to
3.1206 -# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
3.1207 -# read).
3.1208 -
3.1209 -DOT_TRANSPARENT = NO
3.1210 -
3.1211 -# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
3.1212 -# files in one run (i.e. multiple -o and -T options on the command line). This
3.1213 -# makes dot run faster, but since only newer versions of dot (>1.8.10)
3.1214 -# support this, this feature is disabled by default.
3.1215 -
3.1216 -DOT_MULTI_TARGETS = NO
3.1217 -
3.1218 -# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
3.1219 -# generate a legend page explaining the meaning of the various boxes and
3.1220 -# arrows in the dot generated graphs.
3.1221 -
3.1222 -GENERATE_LEGEND = YES
3.1223 -
3.1224 -# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
3.1225 -# remove the intermediate dot files that are used to generate
3.1226 -# the various graphs.
3.1227 -
3.1228 -DOT_CLEANUP = YES
3.1229 -
3.1230 -#---------------------------------------------------------------------------
3.1231 -# Configuration::additions related to the search engine
3.1232 -#---------------------------------------------------------------------------
3.1233 -
3.1234 -# The SEARCHENGINE tag specifies whether or not a search engine should be
3.1235 -# used. If set to NO the values of all tags below this one will be ignored.
3.1236 -
3.1237 -SEARCHENGINE = NO
4.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
4.2 +++ b/doc/Doxyfile.in Tue Apr 05 08:43:51 2005 +0000
4.3 @@ -0,0 +1,1238 @@
4.4 +# Doxyfile 1.4.2
4.5 +
4.6 +# This file describes the settings to be used by the documentation system
4.7 +# doxygen (www.doxygen.org) for a project
4.8 +#
4.9 +# All text after a hash (#) is considered a comment and will be ignored
4.10 +# The format is:
4.11 +# TAG = value [value, ...]
4.12 +# For lists items can also be appended using:
4.13 +# TAG += value [value, ...]
4.14 +# Values that contain spaces should be placed between quotes (" ")
4.15 +
4.16 +#---------------------------------------------------------------------------
4.17 +# Project related configuration options
4.18 +#---------------------------------------------------------------------------
4.19 +
4.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
4.21 +# by quotes) that should identify the project.
4.22 +
4.23 +PROJECT_NAME = @PACKAGE_NAME@
4.24 +
4.25 +# The PROJECT_NUMBER tag can be used to enter a project or revision number.
4.26 +# This could be handy for archiving the generated documentation or
4.27 +# if some version control system is used.
4.28 +
4.29 +PROJECT_NUMBER = @PACKAGE_VERSION@
4.30 +
4.31 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
4.32 +# base path where the generated documentation will be put.
4.33 +# If a relative path is entered, it will be relative to the location
4.34 +# where doxygen was started. If left blank the current directory will be used.
4.35 +
4.36 +OUTPUT_DIRECTORY =
4.37 +
4.38 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
4.39 +# 4096 sub-directories (in 2 levels) under the output directory of each output
4.40 +# format and will distribute the generated files over these directories.
4.41 +# Enabling this option can be useful when feeding doxygen a huge amount of
4.42 +# source files, where putting all generated files in the same directory would
4.43 +# otherwise cause performance problems for the file system.
4.44 +
4.45 +CREATE_SUBDIRS = NO
4.46 +
4.47 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all
4.48 +# documentation generated by doxygen is written. Doxygen will use this
4.49 +# information to generate all constant output in the proper language.
4.50 +# The default language is English, other supported languages are:
4.51 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
4.52 +# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
4.53 +# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
4.54 +# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
4.55 +# Swedish, and Ukrainian.
4.56 +
4.57 +OUTPUT_LANGUAGE = English
4.58 +
4.59 +# This tag can be used to specify the encoding used in the generated output.
4.60 +# The encoding is not always determined by the language that is chosen,
4.61 +# but also whether or not the output is meant for Windows or non-Windows users.
4.62 +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
4.63 +# forces the Windows encoding (this is the default for the Windows binary),
4.64 +# whereas setting the tag to NO uses a Unix-style encoding (the default for
4.65 +# all platforms other than Windows).
4.66 +
4.67 +USE_WINDOWS_ENCODING = NO
4.68 +
4.69 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
4.70 +# include brief member descriptions after the members that are listed in
4.71 +# the file and class documentation (similar to JavaDoc).
4.72 +# Set to NO to disable this.
4.73 +
4.74 +BRIEF_MEMBER_DESC = YES
4.75 +
4.76 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
4.77 +# the brief description of a member or function before the detailed description.
4.78 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
4.79 +# brief descriptions will be completely suppressed.
4.80 +
4.81 +REPEAT_BRIEF = NO
4.82 +
4.83 +# This tag implements a quasi-intelligent brief description abbreviator
4.84 +# that is used to form the text in various listings. Each string
4.85 +# in this list, if found as the leading text of the brief description, will be
4.86 +# stripped from the text and the result after processing the whole list, is
4.87 +# used as the annotated text. Otherwise, the brief description is used as-is.
4.88 +# If left blank, the following values are used ("$name" is automatically
4.89 +# replaced with the name of the entity): "The $name class" "The $name widget"
4.90 +# "The $name file" "is" "provides" "specifies" "contains"
4.91 +# "represents" "a" "an" "the"
4.92 +
4.93 +ABBREVIATE_BRIEF =
4.94 +
4.95 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
4.96 +# Doxygen will generate a detailed section even if there is only a brief
4.97 +# description.
4.98 +
4.99 +ALWAYS_DETAILED_SEC = NO
4.100 +
4.101 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
4.102 +# inherited members of a class in the documentation of that class as if those
4.103 +# members were ordinary class members. Constructors, destructors and assignment
4.104 +# operators of the base classes will not be shown.
4.105 +
4.106 +INLINE_INHERITED_MEMB = NO
4.107 +
4.108 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
4.109 +# path before files name in the file list and in the header files. If set
4.110 +# to NO the shortest path that makes the file name unique will be used.
4.111 +
4.112 +FULL_PATH_NAMES = YES
4.113 +
4.114 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
4.115 +# can be used to strip a user-defined part of the path. Stripping is
4.116 +# only done if one of the specified strings matches the left-hand part of
4.117 +# the path. The tag can be used to show relative paths in the file list.
4.118 +# If left blank the directory from which doxygen is run is used as the
4.119 +# path to strip.
4.120 +
4.121 +STRIP_FROM_PATH = ../src
4.122 +
4.123 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
4.124 +# the path mentioned in the documentation of a class, which tells
4.125 +# the reader which header file to include in order to use a class.
4.126 +# If left blank only the name of the header file containing the class
4.127 +# definition is used. Otherwise one should specify the include paths that
4.128 +# are normally passed to the compiler using the -I flag.
4.129 +
4.130 +STRIP_FROM_INC_PATH = ../src
4.131 +
4.132 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
4.133 +# (but less readable) file names. This can be useful is your file systems
4.134 +# doesn't support long names like on DOS, Mac, or CD-ROM.
4.135 +
4.136 +SHORT_NAMES = NO
4.137 +
4.138 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
4.139 +# will interpret the first line (until the first dot) of a JavaDoc-style
4.140 +# comment as the brief description. If set to NO, the JavaDoc
4.141 +# comments will behave just like the Qt-style comments (thus requiring an
4.142 +# explicit @brief command for a brief description.
4.143 +
4.144 +JAVADOC_AUTOBRIEF = NO
4.145 +
4.146 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
4.147 +# treat a multi-line C++ special comment block (i.e. a block of //! or ///
4.148 +# comments) as a brief description. This used to be the default behaviour.
4.149 +# The new default is to treat a multi-line C++ comment block as a detailed
4.150 +# description. Set this tag to YES if you prefer the old behaviour instead.
4.151 +
4.152 +MULTILINE_CPP_IS_BRIEF = NO
4.153 +
4.154 +# If the DETAILS_AT_TOP tag is set to YES then Doxygen
4.155 +# will output the detailed description near the top, like JavaDoc.
4.156 +# If set to NO, the detailed description appears after the member
4.157 +# documentation.
4.158 +
4.159 +DETAILS_AT_TOP = YES
4.160 +
4.161 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
4.162 +# member inherits the documentation from any documented member that it
4.163 +# re-implements.
4.164 +
4.165 +INHERIT_DOCS = NO
4.166 +
4.167 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
4.168 +# tag is set to YES, then doxygen will reuse the documentation of the first
4.169 +# member in the group (if any) for the other members of the group. By default
4.170 +# all members of a group must be documented explicitly.
4.171 +
4.172 +DISTRIBUTE_GROUP_DOC = NO
4.173 +
4.174 +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
4.175 +# a new page for each member. If set to NO, the documentation of a member will
4.176 +# be part of the file/class/namespace that contains it.
4.177 +
4.178 +SEPARATE_MEMBER_PAGES = NO
4.179 +
4.180 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
4.181 +# Doxygen uses this value to replace tabs by spaces in code fragments.
4.182 +
4.183 +TAB_SIZE = 8
4.184 +
4.185 +# This tag can be used to specify a number of aliases that acts
4.186 +# as commands in the documentation. An alias has the form "name=value".
4.187 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
4.188 +# put the command \sideeffect (or @sideeffect) in the documentation, which
4.189 +# will result in a user-defined paragraph with heading "Side Effects:".
4.190 +# You can put \n's in the value part of an alias to insert newlines.
4.191 +
4.192 +ALIASES =
4.193 +
4.194 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
4.195 +# sources only. Doxygen will then generate output that is more tailored for C.
4.196 +# For instance, some of the names that are used will be different. The list
4.197 +# of all members will be omitted, etc.
4.198 +
4.199 +OPTIMIZE_OUTPUT_FOR_C = NO
4.200 +
4.201 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
4.202 +# only. Doxygen will then generate output that is more tailored for Java.
4.203 +# For instance, namespaces will be presented as packages, qualified scopes
4.204 +# will look different, etc.
4.205 +
4.206 +OPTIMIZE_OUTPUT_JAVA = NO
4.207 +
4.208 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
4.209 +# the same type (for instance a group of public functions) to be put as a
4.210 +# subgroup of that type (e.g. under the Public Functions section). Set it to
4.211 +# NO to prevent subgrouping. Alternatively, this can be done per class using
4.212 +# the \nosubgrouping command.
4.213 +
4.214 +SUBGROUPING = YES
4.215 +
4.216 +#---------------------------------------------------------------------------
4.217 +# Build related configuration options
4.218 +#---------------------------------------------------------------------------
4.219 +
4.220 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
4.221 +# documentation are documented, even if no documentation was available.
4.222 +# Private class members and static file members will be hidden unless
4.223 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
4.224 +
4.225 +EXTRACT_ALL = NO
4.226 +
4.227 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
4.228 +# will be included in the documentation.
4.229 +
4.230 +EXTRACT_PRIVATE = NO
4.231 +
4.232 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
4.233 +# will be included in the documentation.
4.234 +
4.235 +EXTRACT_STATIC = NO
4.236 +
4.237 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
4.238 +# defined locally in source files will be included in the documentation.
4.239 +# If set to NO only classes defined in header files are included.
4.240 +
4.241 +EXTRACT_LOCAL_CLASSES = YES
4.242 +
4.243 +# This flag is only useful for Objective-C code. When set to YES local
4.244 +# methods, which are defined in the implementation section but not in
4.245 +# the interface are included in the documentation.
4.246 +# If set to NO (the default) only methods in the interface are included.
4.247 +
4.248 +EXTRACT_LOCAL_METHODS = NO
4.249 +
4.250 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
4.251 +# undocumented members of documented classes, files or namespaces.
4.252 +# If set to NO (the default) these members will be included in the
4.253 +# various overviews, but no documentation section is generated.
4.254 +# This option has no effect if EXTRACT_ALL is enabled.
4.255 +
4.256 +HIDE_UNDOC_MEMBERS = YES
4.257 +
4.258 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
4.259 +# undocumented classes that are normally visible in the class hierarchy.
4.260 +# If set to NO (the default) these classes will be included in the various
4.261 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
4.262 +
4.263 +HIDE_UNDOC_CLASSES = YES
4.264 +
4.265 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
4.266 +# friend (class|struct|union) declarations.
4.267 +# If set to NO (the default) these declarations will be included in the
4.268 +# documentation.
4.269 +
4.270 +HIDE_FRIEND_COMPOUNDS = NO
4.271 +
4.272 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
4.273 +# documentation blocks found inside the body of a function.
4.274 +# If set to NO (the default) these blocks will be appended to the
4.275 +# function's detailed documentation block.
4.276 +
4.277 +HIDE_IN_BODY_DOCS = NO
4.278 +
4.279 +# The INTERNAL_DOCS tag determines if documentation
4.280 +# that is typed after a \internal command is included. If the tag is set
4.281 +# to NO (the default) then the documentation will be excluded.
4.282 +# Set it to YES to include the internal documentation.
4.283 +
4.284 +INTERNAL_DOCS = NO
4.285 +
4.286 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
4.287 +# file names in lower-case letters. If set to YES upper-case letters are also
4.288 +# allowed. This is useful if you have classes or files whose names only differ
4.289 +# in case and if your file system supports case sensitive file names. Windows
4.290 +# and Mac users are advised to set this option to NO.
4.291 +
4.292 +CASE_SENSE_NAMES = YES
4.293 +
4.294 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
4.295 +# will show members with their full class and namespace scopes in the
4.296 +# documentation. If set to YES the scope will be hidden.
4.297 +
4.298 +HIDE_SCOPE_NAMES = YES
4.299 +
4.300 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
4.301 +# will put a list of the files that are included by a file in the documentation
4.302 +# of that file.
4.303 +
4.304 +SHOW_INCLUDE_FILES = YES
4.305 +
4.306 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
4.307 +# is inserted in the documentation for inline members.
4.308 +
4.309 +INLINE_INFO = YES
4.310 +
4.311 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
4.312 +# will sort the (detailed) documentation of file and class members
4.313 +# alphabetically by member name. If set to NO the members will appear in
4.314 +# declaration order.
4.315 +
4.316 +SORT_MEMBER_DOCS = NO
4.317 +
4.318 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
4.319 +# brief documentation of file, namespace and class members alphabetically
4.320 +# by member name. If set to NO (the default) the members will appear in
4.321 +# declaration order.
4.322 +
4.323 +SORT_BRIEF_DOCS = NO
4.324 +
4.325 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
4.326 +# sorted by fully-qualified names, including namespaces. If set to
4.327 +# NO (the default), the class list will be sorted only by class name,
4.328 +# not including the namespace part.
4.329 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
4.330 +# Note: This option applies only to the class list, not to the
4.331 +# alphabetical list.
4.332 +
4.333 +SORT_BY_SCOPE_NAME = NO
4.334 +
4.335 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
4.336 +# disable (NO) the todo list. This list is created by putting \todo
4.337 +# commands in the documentation.
4.338 +
4.339 +GENERATE_TODOLIST = YES
4.340 +
4.341 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
4.342 +# disable (NO) the test list. This list is created by putting \test
4.343 +# commands in the documentation.
4.344 +
4.345 +GENERATE_TESTLIST = YES
4.346 +
4.347 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
4.348 +# disable (NO) the bug list. This list is created by putting \bug
4.349 +# commands in the documentation.
4.350 +
4.351 +GENERATE_BUGLIST = YES
4.352 +
4.353 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
4.354 +# disable (NO) the deprecated list. This list is created by putting
4.355 +# \deprecated commands in the documentation.
4.356 +
4.357 +GENERATE_DEPRECATEDLIST= YES
4.358 +
4.359 +# The ENABLED_SECTIONS tag can be used to enable conditional
4.360 +# documentation sections, marked by \if sectionname ... \endif.
4.361 +
4.362 +ENABLED_SECTIONS =
4.363 +
4.364 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
4.365 +# the initial value of a variable or define consists of for it to appear in
4.366 +# the documentation. If the initializer consists of more lines than specified
4.367 +# here it will be hidden. Use a value of 0 to hide initializers completely.
4.368 +# The appearance of the initializer of individual variables and defines in the
4.369 +# documentation can be controlled using \showinitializer or \hideinitializer
4.370 +# command in the documentation regardless of this setting.
4.371 +
4.372 +MAX_INITIALIZER_LINES = 5
4.373 +
4.374 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
4.375 +# at the bottom of the documentation of classes and structs. If set to YES the
4.376 +# list will mention the files that were used to generate the documentation.
4.377 +
4.378 +SHOW_USED_FILES = YES
4.379 +
4.380 +# If the sources in your project are distributed over multiple directories
4.381 +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
4.382 +# in the documentation.
4.383 +
4.384 +SHOW_DIRECTORIES = YES
4.385 +
4.386 +# The FILE_VERSION_FILTER tag can be used to specify a program or script that
4.387 +# doxygen should invoke to get the current version for each file (typically from the
4.388 +# version control system). Doxygen will invoke the program by executing (via
4.389 +# popen()) the command <command> <input-file>, where <command> is the value of
4.390 +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
4.391 +# provided by doxygen. Whatever the progam writes to standard output
4.392 +# is used as the file version. See the manual for examples.
4.393 +
4.394 +FILE_VERSION_FILTER =
4.395 +
4.396 +#---------------------------------------------------------------------------
4.397 +# configuration options related to warning and progress messages
4.398 +#---------------------------------------------------------------------------
4.399 +
4.400 +# The QUIET tag can be used to turn on/off the messages that are generated
4.401 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
4.402 +
4.403 +QUIET = NO
4.404 +
4.405 +# The WARNINGS tag can be used to turn on/off the warning messages that are
4.406 +# generated by doxygen. Possible values are YES and NO. If left blank
4.407 +# NO is used.
4.408 +
4.409 +WARNINGS = YES
4.410 +
4.411 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
4.412 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
4.413 +# automatically be disabled.
4.414 +
4.415 +WARN_IF_UNDOCUMENTED = YES
4.416 +
4.417 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
4.418 +# potential errors in the documentation, such as not documenting some
4.419 +# parameters in a documented function, or documenting parameters that
4.420 +# don't exist or using markup commands wrongly.
4.421 +
4.422 +WARN_IF_DOC_ERROR = YES
4.423 +
4.424 +# This WARN_NO_PARAMDOC option can be abled to get warnings for
4.425 +# functions that are documented, but have no documentation for their parameters
4.426 +# or return value. If set to NO (the default) doxygen will only warn about
4.427 +# wrong or incomplete parameter documentation, but not about the absence of
4.428 +# documentation.
4.429 +
4.430 +WARN_NO_PARAMDOC = NO
4.431 +
4.432 +# The WARN_FORMAT tag determines the format of the warning messages that
4.433 +# doxygen can produce. The string should contain the $file, $line, and $text
4.434 +# tags, which will be replaced by the file and line number from which the
4.435 +# warning originated and the warning text. Optionally the format may contain
4.436 +# $version, which will be replaced by the version of the file (if it could
4.437 +# be obtained via FILE_VERSION_FILTER)
4.438 +
4.439 +WARN_FORMAT = "$file:$line: $text"
4.440 +
4.441 +# The WARN_LOGFILE tag can be used to specify a file to which warning
4.442 +# and error messages should be written. If left blank the output is written
4.443 +# to stderr.
4.444 +
4.445 +WARN_LOGFILE = doxygen.log
4.446 +
4.447 +#---------------------------------------------------------------------------
4.448 +# configuration options related to the input files
4.449 +#---------------------------------------------------------------------------
4.450 +
4.451 +# The INPUT tag can be used to specify the files and/or directories that contain
4.452 +# documented source files. You may enter file names like "myfile.cpp" or
4.453 +# directories like "/usr/src/myproject". Separate the files or directories
4.454 +# with spaces.
4.455 +
4.456 +INPUT = mainpage.dox \
4.457 + getstart.dox \
4.458 + quicktour.dox \
4.459 + demoprograms.dox \
4.460 + graphs.dox \
4.461 + undir_graphs.dox \
4.462 + named-param.dox \
4.463 + maps.dox \
4.464 + coding_style.dox \
4.465 + groups.dox \
4.466 + namespaces.dox \
4.467 + license.dox \
4.468 + developers_interface.dox \
4.469 + graph_io.dox \
4.470 + dirs.dox \
4.471 + gwrappers.dox \
4.472 + ../src/lemon \
4.473 + ../src/lemon/concept \
4.474 + ../src/test/test_tools.h
4.475 +
4.476 +# If the value of the INPUT tag contains directories, you can use the
4.477 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
4.478 +# and *.h) to filter out the source-files in the directories. If left
4.479 +# blank the following patterns are tested:
4.480 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
4.481 +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
4.482 +
4.483 +FILE_PATTERNS =
4.484 +
4.485 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
4.486 +# should be searched for input files as well. Possible values are YES and NO.
4.487 +# If left blank NO is used.
4.488 +
4.489 +RECURSIVE = NO
4.490 +
4.491 +# The EXCLUDE tag can be used to specify files and/or directories that should
4.492 +# excluded from the INPUT source files. This way you can easily exclude a
4.493 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
4.494 +
4.495 +EXCLUDE =
4.496 +
4.497 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
4.498 +# directories that are symbolic links (a Unix filesystem feature) are excluded
4.499 +# from the input.
4.500 +
4.501 +EXCLUDE_SYMLINKS = NO
4.502 +
4.503 +# If the value of the INPUT tag contains directories, you can use the
4.504 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
4.505 +# certain files from those directories.
4.506 +
4.507 +EXCLUDE_PATTERNS =
4.508 +
4.509 +# The EXAMPLE_PATH tag can be used to specify one or more files or
4.510 +# directories that contain example code fragments that are included (see
4.511 +# the \include command).
4.512 +
4.513 +EXAMPLE_PATH = ../src/demo \
4.514 + ../LICENSE \
4.515 + .
4.516 +
4.517 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
4.518 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
4.519 +# and *.h) to filter out the source-files in the directories. If left
4.520 +# blank all files are included.
4.521 +
4.522 +EXAMPLE_PATTERNS =
4.523 +
4.524 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
4.525 +# searched for input files to be used with the \include or \dontinclude
4.526 +# commands irrespective of the value of the RECURSIVE tag.
4.527 +# Possible values are YES and NO. If left blank NO is used.
4.528 +
4.529 +EXAMPLE_RECURSIVE = NO
4.530 +
4.531 +# The IMAGE_PATH tag can be used to specify one or more files or
4.532 +# directories that contain image that are included in the documentation (see
4.533 +# the \image command).
4.534 +
4.535 +IMAGE_PATH = images
4.536 +
4.537 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
4.538 +# invoke to filter for each input file. Doxygen will invoke the filter program
4.539 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
4.540 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
4.541 +# input file. Doxygen will then use the output that the filter program writes
4.542 +# to standard output. If FILTER_PATTERNS is specified, this tag will be
4.543 +# ignored.
4.544 +
4.545 +INPUT_FILTER =
4.546 +
4.547 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
4.548 +# basis. Doxygen will compare the file name with each pattern and apply the
4.549 +# filter if there is a match. The filters are a list of the form:
4.550 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
4.551 +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
4.552 +# is applied to all files.
4.553 +
4.554 +FILTER_PATTERNS =
4.555 +
4.556 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
4.557 +# INPUT_FILTER) will be used to filter the input files when producing source
4.558 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
4.559 +
4.560 +FILTER_SOURCE_FILES = NO
4.561 +
4.562 +#---------------------------------------------------------------------------
4.563 +# configuration options related to source browsing
4.564 +#---------------------------------------------------------------------------
4.565 +
4.566 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
4.567 +# be generated. Documented entities will be cross-referenced with these sources.
4.568 +# Note: To get rid of all source code in the generated output, make sure also
4.569 +# VERBATIM_HEADERS is set to NO.
4.570 +
4.571 +SOURCE_BROWSER = YES
4.572 +
4.573 +# Setting the INLINE_SOURCES tag to YES will include the body
4.574 +# of functions and classes directly in the documentation.
4.575 +
4.576 +INLINE_SOURCES = NO
4.577 +
4.578 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
4.579 +# doxygen to hide any special comment blocks from generated source code
4.580 +# fragments. Normal C and C++ comments will always remain visible.
4.581 +
4.582 +STRIP_CODE_COMMENTS = YES
4.583 +
4.584 +# If the REFERENCED_BY_RELATION tag is set to YES (the default)
4.585 +# then for each documented function all documented
4.586 +# functions referencing it will be listed.
4.587 +
4.588 +REFERENCED_BY_RELATION = NO
4.589 +
4.590 +# If the REFERENCES_RELATION tag is set to YES (the default)
4.591 +# then for each documented function all documented entities
4.592 +# called/used by that function will be listed.
4.593 +
4.594 +REFERENCES_RELATION = NO
4.595 +
4.596 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
4.597 +# will generate a verbatim copy of the header file for each class for
4.598 +# which an include is specified. Set to NO to disable this.
4.599 +
4.600 +VERBATIM_HEADERS = YES
4.601 +
4.602 +#---------------------------------------------------------------------------
4.603 +# configuration options related to the alphabetical class index
4.604 +#---------------------------------------------------------------------------
4.605 +
4.606 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
4.607 +# of all compounds will be generated. Enable this if the project
4.608 +# contains a lot of classes, structs, unions or interfaces.
4.609 +
4.610 +ALPHABETICAL_INDEX = YES
4.611 +
4.612 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
4.613 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
4.614 +# in which this list will be split (can be a number in the range [1..20])
4.615 +
4.616 +COLS_IN_ALPHA_INDEX = 2
4.617 +
4.618 +# In case all classes in a project start with a common prefix, all
4.619 +# classes will be put under the same header in the alphabetical index.
4.620 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
4.621 +# should be ignored while generating the index headers.
4.622 +
4.623 +IGNORE_PREFIX =
4.624 +
4.625 +#---------------------------------------------------------------------------
4.626 +# configuration options related to the HTML output
4.627 +#---------------------------------------------------------------------------
4.628 +
4.629 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
4.630 +# generate HTML output.
4.631 +
4.632 +GENERATE_HTML = YES
4.633 +
4.634 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
4.635 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
4.636 +# put in front of it. If left blank `html' will be used as the default path.
4.637 +
4.638 +HTML_OUTPUT = html
4.639 +
4.640 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
4.641 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
4.642 +# doxygen will generate files with .html extension.
4.643 +
4.644 +HTML_FILE_EXTENSION = .html
4.645 +
4.646 +# The HTML_HEADER tag can be used to specify a personal HTML header for
4.647 +# each generated HTML page. If it is left blank doxygen will generate a
4.648 +# standard header.
4.649 +
4.650 +HTML_HEADER =
4.651 +
4.652 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
4.653 +# each generated HTML page. If it is left blank doxygen will generate a
4.654 +# standard footer.
4.655 +
4.656 +HTML_FOOTER =
4.657 +
4.658 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
4.659 +# style sheet that is used by each HTML page. It can be used to
4.660 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
4.661 +# will generate a default style sheet. Note that doxygen will try to copy
4.662 +# the style sheet file to the HTML output directory, so don't put your own
4.663 +# stylesheet in the HTML output directory as well, or it will be erased!
4.664 +
4.665 +HTML_STYLESHEET =
4.666 +
4.667 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
4.668 +# files or namespaces will be aligned in HTML using tables. If set to
4.669 +# NO a bullet list will be used.
4.670 +
4.671 +HTML_ALIGN_MEMBERS = YES
4.672 +
4.673 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
4.674 +# will be generated that can be used as input for tools like the
4.675 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
4.676 +# of the generated HTML documentation.
4.677 +
4.678 +GENERATE_HTMLHELP = NO
4.679 +
4.680 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
4.681 +# be used to specify the file name of the resulting .chm file. You
4.682 +# can add a path in front of the file if the result should not be
4.683 +# written to the html output directory.
4.684 +
4.685 +CHM_FILE =
4.686 +
4.687 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
4.688 +# be used to specify the location (absolute path including file name) of
4.689 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
4.690 +# the HTML help compiler on the generated index.hhp.
4.691 +
4.692 +HHC_LOCATION =
4.693 +
4.694 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
4.695 +# controls if a separate .chi index file is generated (YES) or that
4.696 +# it should be included in the master .chm file (NO).
4.697 +
4.698 +GENERATE_CHI = NO
4.699 +
4.700 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
4.701 +# controls whether a binary table of contents is generated (YES) or a
4.702 +# normal table of contents (NO) in the .chm file.
4.703 +
4.704 +BINARY_TOC = NO
4.705 +
4.706 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
4.707 +# to the contents of the HTML help documentation and to the tree view.
4.708 +
4.709 +TOC_EXPAND = NO
4.710 +
4.711 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
4.712 +# top of each HTML page. The value NO (the default) enables the index and
4.713 +# the value YES disables it.
4.714 +
4.715 +DISABLE_INDEX = NO
4.716 +
4.717 +# This tag can be used to set the number of enum values (range [1..20])
4.718 +# that doxygen will group on one line in the generated HTML documentation.
4.719 +
4.720 +ENUM_VALUES_PER_LINE = 4
4.721 +
4.722 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
4.723 +# generated containing a tree-like index structure (just like the one that
4.724 +# is generated for HTML Help). For this to work a browser that supports
4.725 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
4.726 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
4.727 +# probably better off using the HTML help feature.
4.728 +
4.729 +GENERATE_TREEVIEW = YES
4.730 +
4.731 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
4.732 +# used to set the initial width (in pixels) of the frame in which the tree
4.733 +# is shown.
4.734 +
4.735 +TREEVIEW_WIDTH = 250
4.736 +
4.737 +#---------------------------------------------------------------------------
4.738 +# configuration options related to the LaTeX output
4.739 +#---------------------------------------------------------------------------
4.740 +
4.741 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
4.742 +# generate Latex output.
4.743 +
4.744 +GENERATE_LATEX = NO
4.745 +
4.746 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
4.747 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
4.748 +# put in front of it. If left blank `latex' will be used as the default path.
4.749 +
4.750 +LATEX_OUTPUT = latex
4.751 +
4.752 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
4.753 +# invoked. If left blank `latex' will be used as the default command name.
4.754 +
4.755 +LATEX_CMD_NAME = latex
4.756 +
4.757 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
4.758 +# generate index for LaTeX. If left blank `makeindex' will be used as the
4.759 +# default command name.
4.760 +
4.761 +MAKEINDEX_CMD_NAME = makeindex
4.762 +
4.763 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
4.764 +# LaTeX documents. This may be useful for small projects and may help to
4.765 +# save some trees in general.
4.766 +
4.767 +COMPACT_LATEX = YES
4.768 +
4.769 +# The PAPER_TYPE tag can be used to set the paper type that is used
4.770 +# by the printer. Possible values are: a4, a4wide, letter, legal and
4.771 +# executive. If left blank a4wide will be used.
4.772 +
4.773 +PAPER_TYPE = a4wide
4.774 +
4.775 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
4.776 +# packages that should be included in the LaTeX output.
4.777 +
4.778 +EXTRA_PACKAGES =
4.779 +
4.780 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
4.781 +# the generated latex document. The header should contain everything until
4.782 +# the first chapter. If it is left blank doxygen will generate a
4.783 +# standard header. Notice: only use this tag if you know what you are doing!
4.784 +
4.785 +LATEX_HEADER =
4.786 +
4.787 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
4.788 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
4.789 +# contain links (just like the HTML output) instead of page references
4.790 +# This makes the output suitable for online browsing using a pdf viewer.
4.791 +
4.792 +PDF_HYPERLINKS = YES
4.793 +
4.794 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
4.795 +# plain latex in the generated Makefile. Set this option to YES to get a
4.796 +# higher quality PDF documentation.
4.797 +
4.798 +USE_PDFLATEX = YES
4.799 +
4.800 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
4.801 +# command to the generated LaTeX files. This will instruct LaTeX to keep
4.802 +# running if errors occur, instead of asking the user for help.
4.803 +# This option is also used when generating formulas in HTML.
4.804 +
4.805 +LATEX_BATCHMODE = NO
4.806 +
4.807 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
4.808 +# include the index chapters (such as File Index, Compound Index, etc.)
4.809 +# in the output.
4.810 +
4.811 +LATEX_HIDE_INDICES = NO
4.812 +
4.813 +#---------------------------------------------------------------------------
4.814 +# configuration options related to the RTF output
4.815 +#---------------------------------------------------------------------------
4.816 +
4.817 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
4.818 +# The RTF output is optimized for Word 97 and may not look very pretty with
4.819 +# other RTF readers or editors.
4.820 +
4.821 +GENERATE_RTF = NO
4.822 +
4.823 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
4.824 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
4.825 +# put in front of it. If left blank `rtf' will be used as the default path.
4.826 +
4.827 +RTF_OUTPUT = rtf
4.828 +
4.829 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
4.830 +# RTF documents. This may be useful for small projects and may help to
4.831 +# save some trees in general.
4.832 +
4.833 +COMPACT_RTF = NO
4.834 +
4.835 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
4.836 +# will contain hyperlink fields. The RTF file will
4.837 +# contain links (just like the HTML output) instead of page references.
4.838 +# This makes the output suitable for online browsing using WORD or other
4.839 +# programs which support those fields.
4.840 +# Note: wordpad (write) and others do not support links.
4.841 +
4.842 +RTF_HYPERLINKS = NO
4.843 +
4.844 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
4.845 +# config file, i.e. a series of assignments. You only have to provide
4.846 +# replacements, missing definitions are set to their default value.
4.847 +
4.848 +RTF_STYLESHEET_FILE =
4.849 +
4.850 +# Set optional variables used in the generation of an rtf document.
4.851 +# Syntax is similar to doxygen's config file.
4.852 +
4.853 +RTF_EXTENSIONS_FILE =
4.854 +
4.855 +#---------------------------------------------------------------------------
4.856 +# configuration options related to the man page output
4.857 +#---------------------------------------------------------------------------
4.858 +
4.859 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
4.860 +# generate man pages
4.861 +
4.862 +GENERATE_MAN = NO
4.863 +
4.864 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
4.865 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
4.866 +# put in front of it. If left blank `man' will be used as the default path.
4.867 +
4.868 +MAN_OUTPUT = man
4.869 +
4.870 +# The MAN_EXTENSION tag determines the extension that is added to
4.871 +# the generated man pages (default is the subroutine's section .3)
4.872 +
4.873 +MAN_EXTENSION = .3
4.874 +
4.875 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
4.876 +# then it will generate one additional man file for each entity
4.877 +# documented in the real man page(s). These additional files
4.878 +# only source the real man page, but without them the man command
4.879 +# would be unable to find the correct page. The default is NO.
4.880 +
4.881 +MAN_LINKS = NO
4.882 +
4.883 +#---------------------------------------------------------------------------
4.884 +# configuration options related to the XML output
4.885 +#---------------------------------------------------------------------------
4.886 +
4.887 +# If the GENERATE_XML tag is set to YES Doxygen will
4.888 +# generate an XML file that captures the structure of
4.889 +# the code including all documentation.
4.890 +
4.891 +GENERATE_XML = NO
4.892 +
4.893 +# The XML_OUTPUT tag is used to specify where the XML pages will be put.
4.894 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
4.895 +# put in front of it. If left blank `xml' will be used as the default path.
4.896 +
4.897 +XML_OUTPUT = xml
4.898 +
4.899 +# The XML_SCHEMA tag can be used to specify an XML schema,
4.900 +# which can be used by a validating XML parser to check the
4.901 +# syntax of the XML files.
4.902 +
4.903 +XML_SCHEMA =
4.904 +
4.905 +# The XML_DTD tag can be used to specify an XML DTD,
4.906 +# which can be used by a validating XML parser to check the
4.907 +# syntax of the XML files.
4.908 +
4.909 +XML_DTD =
4.910 +
4.911 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
4.912 +# dump the program listings (including syntax highlighting
4.913 +# and cross-referencing information) to the XML output. Note that
4.914 +# enabling this will significantly increase the size of the XML output.
4.915 +
4.916 +XML_PROGRAMLISTING = YES
4.917 +
4.918 +#---------------------------------------------------------------------------
4.919 +# configuration options for the AutoGen Definitions output
4.920 +#---------------------------------------------------------------------------
4.921 +
4.922 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
4.923 +# generate an AutoGen Definitions (see autogen.sf.net) file
4.924 +# that captures the structure of the code including all
4.925 +# documentation. Note that this feature is still experimental
4.926 +# and incomplete at the moment.
4.927 +
4.928 +GENERATE_AUTOGEN_DEF = NO
4.929 +
4.930 +#---------------------------------------------------------------------------
4.931 +# configuration options related to the Perl module output
4.932 +#---------------------------------------------------------------------------
4.933 +
4.934 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will
4.935 +# generate a Perl module file that captures the structure of
4.936 +# the code including all documentation. Note that this
4.937 +# feature is still experimental and incomplete at the
4.938 +# moment.
4.939 +
4.940 +GENERATE_PERLMOD = NO
4.941 +
4.942 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
4.943 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able
4.944 +# to generate PDF and DVI output from the Perl module output.
4.945 +
4.946 +PERLMOD_LATEX = NO
4.947 +
4.948 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
4.949 +# nicely formatted so it can be parsed by a human reader. This is useful
4.950 +# if you want to understand what is going on. On the other hand, if this
4.951 +# tag is set to NO the size of the Perl module output will be much smaller
4.952 +# and Perl will parse it just the same.
4.953 +
4.954 +PERLMOD_PRETTY = YES
4.955 +
4.956 +# The names of the make variables in the generated doxyrules.make file
4.957 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
4.958 +# This is useful so different doxyrules.make files included by the same
4.959 +# Makefile don't overwrite each other's variables.
4.960 +
4.961 +PERLMOD_MAKEVAR_PREFIX =
4.962 +
4.963 +#---------------------------------------------------------------------------
4.964 +# Configuration options related to the preprocessor
4.965 +#---------------------------------------------------------------------------
4.966 +
4.967 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
4.968 +# evaluate all C-preprocessor directives found in the sources and include
4.969 +# files.
4.970 +
4.971 +ENABLE_PREPROCESSING = YES
4.972 +
4.973 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
4.974 +# names in the source code. If set to NO (the default) only conditional
4.975 +# compilation will be performed. Macro expansion can be done in a controlled
4.976 +# way by setting EXPAND_ONLY_PREDEF to YES.
4.977 +
4.978 +MACRO_EXPANSION = NO
4.979 +
4.980 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
4.981 +# then the macro expansion is limited to the macros specified with the
4.982 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
4.983 +
4.984 +EXPAND_ONLY_PREDEF = NO
4.985 +
4.986 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
4.987 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
4.988 +
4.989 +SEARCH_INCLUDES = YES
4.990 +
4.991 +# The INCLUDE_PATH tag can be used to specify one or more directories that
4.992 +# contain include files that are not input files but should be processed by
4.993 +# the preprocessor.
4.994 +
4.995 +INCLUDE_PATH =
4.996 +
4.997 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
4.998 +# patterns (like *.h and *.hpp) to filter out the header-files in the
4.999 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
4.1000 +# be used.
4.1001 +
4.1002 +INCLUDE_FILE_PATTERNS =
4.1003 +
4.1004 +# The PREDEFINED tag can be used to specify one or more macro names that
4.1005 +# are defined before the preprocessor is started (similar to the -D option of
4.1006 +# gcc). The argument of the tag is a list of macros of the form: name
4.1007 +# or name=definition (no spaces). If the definition and the = are
4.1008 +# omitted =1 is assumed. To prevent a macro definition from being
4.1009 +# undefined via #undef or recursively expanded use the := operator
4.1010 +# instead of the = operator.
4.1011 +
4.1012 +PREDEFINED = DOXYGEN
4.1013 +
4.1014 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
4.1015 +# this tag can be used to specify a list of macro names that should be expanded.
4.1016 +# The macro definition that is found in the sources will be used.
4.1017 +# Use the PREDEFINED tag if you want to use a different macro definition.
4.1018 +
4.1019 +EXPAND_AS_DEFINED =
4.1020 +
4.1021 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
4.1022 +# doxygen's preprocessor will remove all function-like macros that are alone
4.1023 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
4.1024 +# function macros are typically used for boiler-plate code, and will confuse
4.1025 +# the parser if not removed.
4.1026 +
4.1027 +SKIP_FUNCTION_MACROS = YES
4.1028 +
4.1029 +#---------------------------------------------------------------------------
4.1030 +# Configuration::additions related to external references
4.1031 +#---------------------------------------------------------------------------
4.1032 +
4.1033 +# The TAGFILES option can be used to specify one or more tagfiles.
4.1034 +# Optionally an initial location of the external documentation
4.1035 +# can be added for each tagfile. The format of a tag file without
4.1036 +# this location is as follows:
4.1037 +# TAGFILES = file1 file2 ...
4.1038 +# Adding location for the tag files is done as follows:
4.1039 +# TAGFILES = file1=loc1 "file2 = loc2" ...
4.1040 +# where "loc1" and "loc2" can be relative or absolute paths or
4.1041 +# URLs. If a location is present for each tag, the installdox tool
4.1042 +# does not have to be run to correct the links.
4.1043 +# Note that each tag file must have a unique name
4.1044 +# (where the name does NOT include the path)
4.1045 +# If a tag file is not located in the directory in which doxygen
4.1046 +# is run, you must also specify the path to the tagfile here.
4.1047 +
4.1048 +TAGFILES =
4.1049 +
4.1050 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
4.1051 +# a tag file that is based on the input files it reads.
4.1052 +
4.1053 +GENERATE_TAGFILE =
4.1054 +
4.1055 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
4.1056 +# in the class index. If set to NO only the inherited external classes
4.1057 +# will be listed.
4.1058 +
4.1059 +ALLEXTERNALS = NO
4.1060 +
4.1061 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
4.1062 +# in the modules index. If set to NO, only the current project's groups will
4.1063 +# be listed.
4.1064 +
4.1065 +EXTERNAL_GROUPS = YES
4.1066 +
4.1067 +# The PERL_PATH should be the absolute path and name of the perl script
4.1068 +# interpreter (i.e. the result of `which perl').
4.1069 +
4.1070 +PERL_PATH = /usr/bin/perl
4.1071 +
4.1072 +#---------------------------------------------------------------------------
4.1073 +# Configuration options related to the dot tool
4.1074 +#---------------------------------------------------------------------------
4.1075 +
4.1076 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
4.1077 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
4.1078 +# or super classes. Setting the tag to NO turns the diagrams off. Note that
4.1079 +# this option is superseded by the HAVE_DOT option below. This is only a
4.1080 +# fallback. It is recommended to install and use dot, since it yields more
4.1081 +# powerful graphs.
4.1082 +
4.1083 +CLASS_DIAGRAMS = YES
4.1084 +
4.1085 +# If set to YES, the inheritance and collaboration graphs will hide
4.1086 +# inheritance and usage relations if the target is undocumented
4.1087 +# or is not a class.
4.1088 +
4.1089 +HIDE_UNDOC_RELATIONS = NO
4.1090 +
4.1091 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
4.1092 +# available from the path. This tool is part of Graphviz, a graph visualization
4.1093 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
4.1094 +# have no effect if this option is set to NO (the default)
4.1095 +
4.1096 +HAVE_DOT = YES
4.1097 +
4.1098 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
4.1099 +# will generate a graph for each documented class showing the direct and
4.1100 +# indirect inheritance relations. Setting this tag to YES will force the
4.1101 +# the CLASS_DIAGRAMS tag to NO.
4.1102 +
4.1103 +CLASS_GRAPH = YES
4.1104 +
4.1105 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
4.1106 +# will generate a graph for each documented class showing the direct and
4.1107 +# indirect implementation dependencies (inheritance, containment, and
4.1108 +# class references variables) of the class with other documented classes.
4.1109 +
4.1110 +COLLABORATION_GRAPH = YES
4.1111 +
4.1112 +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
4.1113 +# will generate a graph for groups, showing the direct groups dependencies
4.1114 +
4.1115 +GROUP_GRAPHS = YES
4.1116 +
4.1117 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
4.1118 +# collaboration diagrams in a style similar to the OMG's Unified Modeling
4.1119 +# Language.
4.1120 +
4.1121 +UML_LOOK = NO
4.1122 +
4.1123 +# If set to YES, the inheritance and collaboration graphs will show the
4.1124 +# relations between templates and their instances.
4.1125 +
4.1126 +TEMPLATE_RELATIONS = YES
4.1127 +
4.1128 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
4.1129 +# tags are set to YES then doxygen will generate a graph for each documented
4.1130 +# file showing the direct and indirect include dependencies of the file with
4.1131 +# other documented files.
4.1132 +
4.1133 +INCLUDE_GRAPH = YES
4.1134 +
4.1135 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
4.1136 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
4.1137 +# documented header file showing the documented files that directly or
4.1138 +# indirectly include this file.
4.1139 +
4.1140 +INCLUDED_BY_GRAPH = YES
4.1141 +
4.1142 +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
4.1143 +# generate a call dependency graph for every global function or class method.
4.1144 +# Note that enabling this option will significantly increase the time of a run.
4.1145 +# So in most cases it will be better to enable call graphs for selected
4.1146 +# functions only using the \callgraph command.
4.1147 +
4.1148 +CALL_GRAPH = YES
4.1149 +
4.1150 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
4.1151 +# will graphical hierarchy of all classes instead of a textual one.
4.1152 +
4.1153 +GRAPHICAL_HIERARCHY = YES
4.1154 +
4.1155 +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
4.1156 +# then doxygen will show the dependencies a directory has on other directories
4.1157 +# in a graphical way. The dependency relations are determined by the #include
4.1158 +# relations between the files in the directories.
4.1159 +
4.1160 +DIRECTORY_GRAPH = YES
4.1161 +
4.1162 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
4.1163 +# generated by dot. Possible values are png, jpg, or gif
4.1164 +# If left blank png will be used.
4.1165 +
4.1166 +DOT_IMAGE_FORMAT = png
4.1167 +
4.1168 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
4.1169 +# found. If left blank, it is assumed the dot tool can be found in the path.
4.1170 +
4.1171 +DOT_PATH =
4.1172 +
4.1173 +# The DOTFILE_DIRS tag can be used to specify one or more directories that
4.1174 +# contain dot files that are included in the documentation (see the
4.1175 +# \dotfile command).
4.1176 +
4.1177 +DOTFILE_DIRS =
4.1178 +
4.1179 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
4.1180 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
4.1181 +# this value, doxygen will try to truncate the graph, so that it fits within
4.1182 +# the specified constraint. Beware that most browsers cannot cope with very
4.1183 +# large images.
4.1184 +
4.1185 +MAX_DOT_GRAPH_WIDTH = 1024
4.1186 +
4.1187 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
4.1188 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
4.1189 +# this value, doxygen will try to truncate the graph, so that it fits within
4.1190 +# the specified constraint. Beware that most browsers cannot cope with very
4.1191 +# large images.
4.1192 +
4.1193 +MAX_DOT_GRAPH_HEIGHT = 1024
4.1194 +
4.1195 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
4.1196 +# graphs generated by dot. A depth value of 3 means that only nodes reachable
4.1197 +# from the root by following a path via at most 3 edges will be shown. Nodes
4.1198 +# that lay further from the root node will be omitted. Note that setting this
4.1199 +# option to 1 or 2 may greatly reduce the computation time needed for large
4.1200 +# code bases. Also note that a graph may be further truncated if the graph's
4.1201 +# image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
4.1202 +# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
4.1203 +# the graph is not depth-constrained.
4.1204 +
4.1205 +MAX_DOT_GRAPH_DEPTH = 0
4.1206 +
4.1207 +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
4.1208 +# background. This is disabled by default, which results in a white background.
4.1209 +# Warning: Depending on the platform used, enabling this option may lead to
4.1210 +# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
4.1211 +# read).
4.1212 +
4.1213 +DOT_TRANSPARENT = NO
4.1214 +
4.1215 +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
4.1216 +# files in one run (i.e. multiple -o and -T options on the command line). This
4.1217 +# makes dot run faster, but since only newer versions of dot (>1.8.10)
4.1218 +# support this, this feature is disabled by default.
4.1219 +
4.1220 +DOT_MULTI_TARGETS = NO
4.1221 +
4.1222 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
4.1223 +# generate a legend page explaining the meaning of the various boxes and
4.1224 +# arrows in the dot generated graphs.
4.1225 +
4.1226 +GENERATE_LEGEND = YES
4.1227 +
4.1228 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
4.1229 +# remove the intermediate dot files that are used to generate
4.1230 +# the various graphs.
4.1231 +
4.1232 +DOT_CLEANUP = YES
4.1233 +
4.1234 +#---------------------------------------------------------------------------
4.1235 +# Configuration::additions related to the search engine
4.1236 +#---------------------------------------------------------------------------
4.1237 +
4.1238 +# The SEARCHENGINE tag specifies whether or not a search engine should be
4.1239 +# used. If set to NO the values of all tags below this one will be ignored.
4.1240 +
4.1241 +SEARCHENGINE = NO
5.1 --- a/src/lemon/Makefile.am Tue Apr 05 06:41:21 2005 +0000
5.2 +++ b/src/lemon/Makefile.am Tue Apr 05 08:43:51 2005 +0000
5.3 @@ -1,3 +1,11 @@
5.4 +AM_CPPFLAGS = -I$(top_srcdir)/src
5.5 +
5.6 +pkgconfigdir = $(libdir)/pkgconfig
5.7 +pkgconfig_DATA = lemon.pc
5.8 +
5.9 +lib_LTLIBRARIES = libemon.la
5.10 +libemon_la_SOURCES =
5.11 +
5.12 pkginclude_HEADERS = \
5.13 array_map.h \
5.14 bezier.h \
6.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
6.2 +++ b/src/lemon/lemon.pc.in Tue Apr 05 08:43:51 2005 +0000
6.3 @@ -0,0 +1,10 @@
6.4 +prefix=@prefix@
6.5 +exec_prefix=@exec_prefix@
6.6 +libdir=@libdir@
6.7 +includedir=@includedir@
6.8 +
6.9 +Name: @PACKAGE_NAME@
6.10 +Description: a Library of Efficient Models and Optimization in Networks
6.11 +Version: @PACKAGE_VERSION@
6.12 +Libs: -L${libdir} -lemon
6.13 +Cflags: -I${includedir}