1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/Makefile.am Tue Dec 18 10:56:09 2007 +0100
1.3 @@ -0,0 +1,66 @@
1.4 +ACLOCAL_AMFLAGS = -I m4
1.5 +
1.6 +AM_CPPFLAGS = -I$(top_srcdir)
1.7 +LDADD = $(top_builddir)/lemon/libemon.la
1.8 +
1.9 +EXTRA_DIST = \
1.10 + m4/lx_check_cplex.m4 \
1.11 + m4/lx_check_glpk.m4 \
1.12 + m4/lx_check_soplex.m4
1.13 +
1.14 +pkgconfigdir = $(libdir)/pkgconfig
1.15 +lemondir = $(pkgincludedir)
1.16 +bitsdir = $(lemondir)/bits
1.17 +conceptdir = $(lemondir)/concepts
1.18 +pkgconfig_DATA =
1.19 +lib_LTLIBRARIES =
1.20 +lemon_HEADERS =
1.21 +bits_HEADERS =
1.22 +concept_HEADERS =
1.23 +noinst_HEADERS =
1.24 +noinst_PROGRAMS =
1.25 +bin_PROGRAMS =
1.26 +check_PROGRAMS =
1.27 +TESTS =
1.28 +XFAIL_TESTS =
1.29 +
1.30 +include lemon/Makefile.am
1.31 +include test/Makefile.am
1.32 +include doc/Makefile.am
1.33 +include demo/Makefile.am
1.34 +include benchmark/Makefile.am
1.35 +include tools/Makefile.am
1.36 +
1.37 +MRPROPERFILES = \
1.38 + aclocal.m4 \
1.39 + config.h.in \
1.40 + config.h.in~ \
1.41 + configure \
1.42 + Makefile.in \
1.43 + build-aux/config.guess \
1.44 + build-aux/config.sub \
1.45 + build-aux/depcomp \
1.46 + build-aux/install-sh \
1.47 + build-aux/ltmain.sh \
1.48 + build-aux/missing \
1.49 + doc/Makefile.in \
1.50 + doc/doxygen.log \
1.51 + Makefile.in \
1.52 + lemon/Makefile.in \
1.53 + test/Makefile.in \
1.54 + benchmark/Makefile.in \
1.55 + demo/Makefile.in
1.56 +
1.57 +mrproper:
1.58 + $(MAKE) $(AM_MAKEFLAGS) maintainer-clean
1.59 + -rm -f $(MRPROPERFILES)
1.60 +
1.61 +dist-bz2: dist
1.62 + zcat $(PACKAGE)-$(VERSION).tar.gz | \
1.63 + bzip2 --best -c > $(PACKAGE)-$(VERSION).tar.bz2
1.64 +
1.65 +distcheck-bz2: distcheck
1.66 + zcat $(PACKAGE)-$(VERSION).tar.gz | \
1.67 + bzip2 --best -c > $(PACKAGE)-$(VERSION).tar.bz2
1.68 +
1.69 +.PHONY: mrproper dist-bz2 distcheck-bz2
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/benchmark/Makefile Tue Dec 18 10:56:09 2007 +0100
2.3 @@ -0,0 +1,2 @@
2.4 +all:
2.5 + $(MAKE) -C ..
3.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
3.2 +++ b/benchmark/Makefile.am Tue Dec 18 10:56:09 2007 +0100
3.3 @@ -0,0 +1,10 @@
3.4 +EXTRA_DIST += \
3.5 + benchmark/Makefile
3.6 +
3.7 +if WANT_BENCHMARK
3.8 +
3.9 +noinst_HEADERS +=
3.10 +
3.11 +noinst_PROGRAMS +=
3.12 +
3.13 +endif WANT_BENCHMARK
4.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
4.2 +++ b/configure.ac Tue Dec 18 10:56:09 2007 +0100
4.3 @@ -0,0 +1,156 @@
4.4 +dnl Process this file with autoconf to produce a configure script.
4.5 +
4.6 +dnl Version information.
4.7 +m4_define([lemon_version_major], [0])
4.8 +m4_define([lemon_version_minor], [6])
4.9 +m4_define([lemon_version_micro], [90])
4.10 +m4_define([lemon_version_nano], [])
4.11 +m4_define([lemon_version_tag], [hg])
4.12 +m4_define([lemon_hg_revision], [m4_normalize(esyscmd([hg tip |grep ^changeset |cut -d ':' -f 3]))])
4.13 +m4_define([lemon_version], [lemon_version_major().lemon_version_minor()ifelse(lemon_version_micro(), [], [], [.lemon_version_micro()])ifelse(lemon_version_nano(), [], [], [.lemon_version_nano()])ifelse(lemon_version_tag(), [], [], lemon_version_tag(), [hg], [[_]lemon_version_tag()[]lemon_hg_revision()], [[_]lemon_version_tag()])])
4.14 +
4.15 +AC_PREREQ([2.59])
4.16 +AC_INIT([LEMON], [lemon_version()], [etik-ol@cs.elte.hu], [lemon])
4.17 +AC_CONFIG_AUX_DIR([build-aux])
4.18 +AC_CONFIG_MACRO_DIR([m4])
4.19 +AM_INIT_AUTOMAKE([-Wall -Werror foreign subdir-objects])
4.20 +AC_CONFIG_SRCDIR([lemon/list_graph.h])
4.21 +AC_CONFIG_HEADERS([config.h lemon/config.h])
4.22 +
4.23 +lx_cmdline_cxxflags_set=${CXXFLAGS+set}
4.24 +
4.25 +dnl Checks for programs.
4.26 +AC_PROG_CXX
4.27 +AC_PROG_CXXCPP
4.28 +AC_PROG_INSTALL
4.29 +AC_DISABLE_SHARED
4.30 +AC_PROG_LIBTOOL
4.31 +
4.32 +if test x"$lx_cmdline_cxxflags_set" != x"set" -a "$GXX" = yes; then
4.33 + CXXFLAGS="$CXXFLAGS -Wall -W -Wall -W -Wunused -Wformat=2 -Wctor-dtor-privacy -Wnon-virtual-dtor -Wno-char-subscripts -Wwrite-strings -Wno-char-subscripts -Wreturn-type -Wcast-qual -Wcast-align -Wsign-promo -Woverloaded-virtual -Woverloaded-virtual -ansi -fno-strict-aliasing -Wold-style-cast -Wno-unknown-pragmas"
4.34 +fi
4.35 +
4.36 +AC_CHECK_PROG([doxygen_found],[doxygen],[yes],[no])
4.37 +
4.38 +dnl Checks for libraries.
4.39 +LX_CHECK_GLPK
4.40 +LX_CHECK_CPLEX
4.41 +LX_CHECK_SOPLEX
4.42 +
4.43 +dnl Enable/disable installing the documentation
4.44 +AC_ARG_ENABLE([doc],
4.45 +AS_HELP_STRING([--enable-doc@<:@=yes|no|full@:>@], [build the documentation (full enables internal documentation too) @<:@default=yes@:>@])
4.46 +AS_HELP_STRING([--disable-doc], [do not build the documentation]),
4.47 + [], [enable_doc=yes])
4.48 +
4.49 +AC_MSG_CHECKING([whether to build the documention])
4.50 +case "$enable_doc" in
4.51 + yes)
4.52 + DOXYGEN_INTERNAL_DOCS=NO
4.53 + AC_MSG_RESULT([yes])
4.54 + ;;
4.55 + full)
4.56 + DOXYGEN_INTERNAL_DOCS=YES
4.57 + AC_MSG_RESULT([full])
4.58 + ;;
4.59 + no)
4.60 + DOXYGEN_INTERNAL_DOCS=NO
4.61 + AC_MSG_RESULT([no])
4.62 + ;;
4.63 + *)
4.64 + AC_MSG_ERROR([bad value $enable_doc for option --enable-doc])
4.65 + ;;
4.66 +esac
4.67 +AC_SUBST(DOXYGEN_INTERNAL_DOCS)
4.68 +AM_CONDITIONAL([WANT_DOC], [test x"$enable_doc" != x"no"])
4.69 +
4.70 +dnl Disable/enable building the demo programs
4.71 +AC_ARG_ENABLE([demo],
4.72 +AS_HELP_STRING([--enable-demo], [build the demo programs])
4.73 +AS_HELP_STRING([--disable-demo], [do not build the demo programs @<:@default@:>@]),
4.74 + [], [enable_demo=no])
4.75 +AC_MSG_CHECKING([whether to build the demo programs])
4.76 +if test x"$enable_demo" != x"no"; then
4.77 + AC_MSG_RESULT([yes])
4.78 +else
4.79 + AC_MSG_RESULT([no])
4.80 +fi
4.81 +AM_CONDITIONAL([WANT_DEMO], [test x"$enable_demo" != x"no"])
4.82 +
4.83 +dnl Disable/enable building the binary tools
4.84 +AC_ARG_ENABLE([tools],
4.85 +AS_HELP_STRING([--enable-tools], [build additional tools @<:@default@:>@])
4.86 +AS_HELP_STRING([--disable-tools], [do not build additional tools]),
4.87 + [], [enable_tools=yes])
4.88 +AC_MSG_CHECKING([whether to build the additional tools])
4.89 +if test x"$enable_tools" != x"no"; then
4.90 + AC_MSG_RESULT([yes])
4.91 +else
4.92 + AC_MSG_RESULT([no])
4.93 +fi
4.94 +AM_CONDITIONAL([WANT_TOOLS], [test x"$enable_tools" != x"no"])
4.95 +
4.96 +dnl Disable/enable building the benchmarks
4.97 +AC_ARG_ENABLE([benchmark],
4.98 +AS_HELP_STRING([--enable-benchmark], [build the benchmarks])
4.99 +AS_HELP_STRING([--disable-benchmark], [do not build the benchmarks @<:@default@:>@]),
4.100 + [], [enable_benchmark=no])
4.101 +AC_MSG_CHECKING([whether to build the benchmarks])
4.102 +if test x"$enable_benchmark" != x"no"; then
4.103 + AC_MSG_RESULT([yes])
4.104 +else
4.105 + AC_MSG_RESULT([no])
4.106 +fi
4.107 +AM_CONDITIONAL([WANT_BENCHMARK], [test x"$enable_benchmark" != x"no"])
4.108 +
4.109 +dnl Checks for header files.
4.110 +AC_CHECK_HEADERS(limits.h sys/time.h sys/times.h unistd.h)
4.111 +
4.112 +dnl Checks for typedefs, structures, and compiler characteristics.
4.113 +AC_C_CONST
4.114 +AC_C_INLINE
4.115 +AC_TYPE_SIZE_T
4.116 +AC_HEADER_TIME
4.117 +AC_STRUCT_TM
4.118 +
4.119 +dnl Checks for library functions.
4.120 +AC_HEADER_STDC
4.121 +AC_CHECK_FUNCS(gettimeofday times ctime_r)
4.122 +
4.123 +AC_CONFIG_FILES([
4.124 +Makefile
4.125 +doc/Doxyfile
4.126 +lemon/lemon.pc
4.127 +])
4.128 +
4.129 +AC_OUTPUT
4.130 +
4.131 +echo
4.132 +echo '****************************** SUMMARY ******************************'
4.133 +echo
4.134 +echo Package version............... : $PACKAGE-$VERSION
4.135 +echo
4.136 +echo C++ compiler.................. : $CXX
4.137 +echo C++ compiles flags............ : $CXXFLAGS
4.138 +echo
4.139 +echo GLPK support.................. : $lx_glpk_found
4.140 +echo CPLEX support................. : $lx_cplex_found
4.141 +echo SOPLEX support................ : $lx_soplex_found
4.142 +echo
4.143 +echo build benchmarks.............. : $enable_benchmark
4.144 +echo build demo programs........... : $enable_demo
4.145 +echo build additional tools........ : $enable_tools
4.146 +echo
4.147 +echo The packace will be installed in
4.148 +echo -n ' '
4.149 +echo $prefix.
4.150 +echo
4.151 +echo The documentation will be installed in
4.152 +echo -n ' '
4.153 +eval echo ${datadir}/doc/$PACKAGE.
4.154 +echo
4.155 +echo '*********************************************************************'
4.156 +
4.157 +echo
4.158 +echo configure complete, now type \'make\' and then \'make install\'.
4.159 +echo
5.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
5.2 +++ b/demo/Makefile Tue Dec 18 10:56:09 2007 +0100
5.3 @@ -0,0 +1,2 @@
5.4 +all:
5.5 + $(MAKE) -C ..
6.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
6.2 +++ b/demo/Makefile.am Tue Dec 18 10:56:09 2007 +0100
6.3 @@ -0,0 +1,8 @@
6.4 +EXTRA_DIST += \
6.5 + demo/Makefile
6.6 +
6.7 +if WANT_DEMO
6.8 +
6.9 +noinst_PROGRAMS +=
6.10 +
6.11 +endif WANT_DEMO
7.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
7.2 +++ b/doc/Doxyfile.in Tue Dec 18 10:56:09 2007 +0100
7.3 @@ -0,0 +1,1227 @@
7.4 +# Doxyfile 1.4.2
7.5 +
7.6 +# This file describes the settings to be used by the documentation system
7.7 +# doxygen (www.doxygen.org) for a project
7.8 +#
7.9 +# All text after a hash (#) is considered a comment and will be ignored
7.10 +# The format is:
7.11 +# TAG = value [value, ...]
7.12 +# For lists items can also be appended using:
7.13 +# TAG += value [value, ...]
7.14 +# Values that contain spaces should be placed between quotes (" ")
7.15 +
7.16 +#---------------------------------------------------------------------------
7.17 +# Project related configuration options
7.18 +#---------------------------------------------------------------------------
7.19 +
7.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
7.21 +# by quotes) that should identify the project.
7.22 +
7.23 +PROJECT_NAME = @PACKAGE_NAME@
7.24 +
7.25 +# The PROJECT_NUMBER tag can be used to enter a project or revision number.
7.26 +# This could be handy for archiving the generated documentation or
7.27 +# if some version control system is used.
7.28 +
7.29 +PROJECT_NUMBER = @PACKAGE_VERSION@
7.30 +
7.31 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
7.32 +# base path where the generated documentation will be put.
7.33 +# If a relative path is entered, it will be relative to the location
7.34 +# where doxygen was started. If left blank the current directory will be used.
7.35 +
7.36 +OUTPUT_DIRECTORY =
7.37 +
7.38 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
7.39 +# 4096 sub-directories (in 2 levels) under the output directory of each output
7.40 +# format and will distribute the generated files over these directories.
7.41 +# Enabling this option can be useful when feeding doxygen a huge amount of
7.42 +# source files, where putting all generated files in the same directory would
7.43 +# otherwise cause performance problems for the file system.
7.44 +
7.45 +CREATE_SUBDIRS = NO
7.46 +
7.47 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all
7.48 +# documentation generated by doxygen is written. Doxygen will use this
7.49 +# information to generate all constant output in the proper language.
7.50 +# The default language is English, other supported languages are:
7.51 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
7.52 +# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
7.53 +# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
7.54 +# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
7.55 +# Swedish, and Ukrainian.
7.56 +
7.57 +OUTPUT_LANGUAGE = English
7.58 +
7.59 +# This tag can be used to specify the encoding used in the generated output.
7.60 +# The encoding is not always determined by the language that is chosen,
7.61 +# but also whether or not the output is meant for Windows or non-Windows users.
7.62 +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
7.63 +# forces the Windows encoding (this is the default for the Windows binary),
7.64 +# whereas setting the tag to NO uses a Unix-style encoding (the default for
7.65 +# all platforms other than Windows).
7.66 +
7.67 +USE_WINDOWS_ENCODING = NO
7.68 +
7.69 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
7.70 +# include brief member descriptions after the members that are listed in
7.71 +# the file and class documentation (similar to JavaDoc).
7.72 +# Set to NO to disable this.
7.73 +
7.74 +BRIEF_MEMBER_DESC = YES
7.75 +
7.76 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
7.77 +# the brief description of a member or function before the detailed description.
7.78 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
7.79 +# brief descriptions will be completely suppressed.
7.80 +
7.81 +REPEAT_BRIEF = NO
7.82 +
7.83 +# This tag implements a quasi-intelligent brief description abbreviator
7.84 +# that is used to form the text in various listings. Each string
7.85 +# in this list, if found as the leading text of the brief description, will be
7.86 +# stripped from the text and the result after processing the whole list, is
7.87 +# used as the annotated text. Otherwise, the brief description is used as-is.
7.88 +# If left blank, the following values are used ("$name" is automatically
7.89 +# replaced with the name of the entity): "The $name class" "The $name widget"
7.90 +# "The $name file" "is" "provides" "specifies" "contains"
7.91 +# "represents" "a" "an" "the"
7.92 +
7.93 +ABBREVIATE_BRIEF =
7.94 +
7.95 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
7.96 +# Doxygen will generate a detailed section even if there is only a brief
7.97 +# description.
7.98 +
7.99 +ALWAYS_DETAILED_SEC = NO
7.100 +
7.101 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
7.102 +# inherited members of a class in the documentation of that class as if those
7.103 +# members were ordinary class members. Constructors, destructors and assignment
7.104 +# operators of the base classes will not be shown.
7.105 +
7.106 +INLINE_INHERITED_MEMB = NO
7.107 +
7.108 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
7.109 +# path before files name in the file list and in the header files. If set
7.110 +# to NO the shortest path that makes the file name unique will be used.
7.111 +
7.112 +FULL_PATH_NAMES = YES
7.113 +
7.114 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
7.115 +# can be used to strip a user-defined part of the path. Stripping is
7.116 +# only done if one of the specified strings matches the left-hand part of
7.117 +# the path. The tag can be used to show relative paths in the file list.
7.118 +# If left blank the directory from which doxygen is run is used as the
7.119 +# path to strip.
7.120 +
7.121 +STRIP_FROM_PATH = @abs_top_srcdir@
7.122 +
7.123 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
7.124 +# the path mentioned in the documentation of a class, which tells
7.125 +# the reader which header file to include in order to use a class.
7.126 +# If left blank only the name of the header file containing the class
7.127 +# definition is used. Otherwise one should specify the include paths that
7.128 +# are normally passed to the compiler using the -I flag.
7.129 +
7.130 +STRIP_FROM_INC_PATH = @abs_top_srcdir@
7.131 +
7.132 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
7.133 +# (but less readable) file names. This can be useful is your file systems
7.134 +# doesn't support long names like on DOS, Mac, or CD-ROM.
7.135 +
7.136 +SHORT_NAMES = YES
7.137 +
7.138 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
7.139 +# will interpret the first line (until the first dot) of a JavaDoc-style
7.140 +# comment as the brief description. If set to NO, the JavaDoc
7.141 +# comments will behave just like the Qt-style comments (thus requiring an
7.142 +# explicit @brief command for a brief description.
7.143 +
7.144 +JAVADOC_AUTOBRIEF = NO
7.145 +
7.146 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
7.147 +# treat a multi-line C++ special comment block (i.e. a block of //! or ///
7.148 +# comments) as a brief description. This used to be the default behaviour.
7.149 +# The new default is to treat a multi-line C++ comment block as a detailed
7.150 +# description. Set this tag to YES if you prefer the old behaviour instead.
7.151 +
7.152 +MULTILINE_CPP_IS_BRIEF = NO
7.153 +
7.154 +# If the DETAILS_AT_TOP tag is set to YES then Doxygen
7.155 +# will output the detailed description near the top, like JavaDoc.
7.156 +# If set to NO, the detailed description appears after the member
7.157 +# documentation.
7.158 +
7.159 +DETAILS_AT_TOP = YES
7.160 +
7.161 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
7.162 +# member inherits the documentation from any documented member that it
7.163 +# re-implements.
7.164 +
7.165 +INHERIT_DOCS = NO
7.166 +
7.167 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
7.168 +# tag is set to YES, then doxygen will reuse the documentation of the first
7.169 +# member in the group (if any) for the other members of the group. By default
7.170 +# all members of a group must be documented explicitly.
7.171 +
7.172 +DISTRIBUTE_GROUP_DOC = NO
7.173 +
7.174 +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
7.175 +# a new page for each member. If set to NO, the documentation of a member will
7.176 +# be part of the file/class/namespace that contains it.
7.177 +
7.178 +SEPARATE_MEMBER_PAGES = NO
7.179 +
7.180 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
7.181 +# Doxygen uses this value to replace tabs by spaces in code fragments.
7.182 +
7.183 +TAB_SIZE = 8
7.184 +
7.185 +# This tag can be used to specify a number of aliases that acts
7.186 +# as commands in the documentation. An alias has the form "name=value".
7.187 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
7.188 +# put the command \sideeffect (or @sideeffect) in the documentation, which
7.189 +# will result in a user-defined paragraph with heading "Side Effects:".
7.190 +# You can put \n's in the value part of an alias to insert newlines.
7.191 +
7.192 +ALIASES =
7.193 +
7.194 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
7.195 +# sources only. Doxygen will then generate output that is more tailored for C.
7.196 +# For instance, some of the names that are used will be different. The list
7.197 +# of all members will be omitted, etc.
7.198 +
7.199 +OPTIMIZE_OUTPUT_FOR_C = NO
7.200 +
7.201 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
7.202 +# only. Doxygen will then generate output that is more tailored for Java.
7.203 +# For instance, namespaces will be presented as packages, qualified scopes
7.204 +# will look different, etc.
7.205 +
7.206 +OPTIMIZE_OUTPUT_JAVA = NO
7.207 +
7.208 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
7.209 +# the same type (for instance a group of public functions) to be put as a
7.210 +# subgroup of that type (e.g. under the Public Functions section). Set it to
7.211 +# NO to prevent subgrouping. Alternatively, this can be done per class using
7.212 +# the \nosubgrouping command.
7.213 +
7.214 +SUBGROUPING = YES
7.215 +
7.216 +#---------------------------------------------------------------------------
7.217 +# Build related configuration options
7.218 +#---------------------------------------------------------------------------
7.219 +
7.220 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
7.221 +# documentation are documented, even if no documentation was available.
7.222 +# Private class members and static file members will be hidden unless
7.223 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
7.224 +
7.225 +EXTRACT_ALL = NO
7.226 +
7.227 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
7.228 +# will be included in the documentation.
7.229 +
7.230 +EXTRACT_PRIVATE = YES
7.231 +
7.232 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
7.233 +# will be included in the documentation.
7.234 +
7.235 +EXTRACT_STATIC = YES
7.236 +
7.237 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
7.238 +# defined locally in source files will be included in the documentation.
7.239 +# If set to NO only classes defined in header files are included.
7.240 +
7.241 +EXTRACT_LOCAL_CLASSES = NO
7.242 +
7.243 +# This flag is only useful for Objective-C code. When set to YES local
7.244 +# methods, which are defined in the implementation section but not in
7.245 +# the interface are included in the documentation.
7.246 +# If set to NO (the default) only methods in the interface are included.
7.247 +
7.248 +EXTRACT_LOCAL_METHODS = NO
7.249 +
7.250 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
7.251 +# undocumented members of documented classes, files or namespaces.
7.252 +# If set to NO (the default) these members will be included in the
7.253 +# various overviews, but no documentation section is generated.
7.254 +# This option has no effect if EXTRACT_ALL is enabled.
7.255 +
7.256 +HIDE_UNDOC_MEMBERS = YES
7.257 +
7.258 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
7.259 +# undocumented classes that are normally visible in the class hierarchy.
7.260 +# If set to NO (the default) these classes will be included in the various
7.261 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
7.262 +
7.263 +HIDE_UNDOC_CLASSES = YES
7.264 +
7.265 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
7.266 +# friend (class|struct|union) declarations.
7.267 +# If set to NO (the default) these declarations will be included in the
7.268 +# documentation.
7.269 +
7.270 +HIDE_FRIEND_COMPOUNDS = NO
7.271 +
7.272 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
7.273 +# documentation blocks found inside the body of a function.
7.274 +# If set to NO (the default) these blocks will be appended to the
7.275 +# function's detailed documentation block.
7.276 +
7.277 +HIDE_IN_BODY_DOCS = NO
7.278 +
7.279 +# The INTERNAL_DOCS tag determines if documentation
7.280 +# that is typed after a \internal command is included. If the tag is set
7.281 +# to NO (the default) then the documentation will be excluded.
7.282 +# Set it to YES to include the internal documentation.
7.283 +
7.284 +INTERNAL_DOCS = @DOXYGEN_INTERNAL_DOCS@
7.285 +
7.286 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
7.287 +# file names in lower-case letters. If set to YES upper-case letters are also
7.288 +# allowed. This is useful if you have classes or files whose names only differ
7.289 +# in case and if your file system supports case sensitive file names. Windows
7.290 +# and Mac users are advised to set this option to NO.
7.291 +
7.292 +CASE_SENSE_NAMES = YES
7.293 +
7.294 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
7.295 +# will show members with their full class and namespace scopes in the
7.296 +# documentation. If set to YES the scope will be hidden.
7.297 +
7.298 +HIDE_SCOPE_NAMES = YES
7.299 +
7.300 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
7.301 +# will put a list of the files that are included by a file in the documentation
7.302 +# of that file.
7.303 +
7.304 +SHOW_INCLUDE_FILES = YES
7.305 +
7.306 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
7.307 +# is inserted in the documentation for inline members.
7.308 +
7.309 +INLINE_INFO = YES
7.310 +
7.311 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
7.312 +# will sort the (detailed) documentation of file and class members
7.313 +# alphabetically by member name. If set to NO the members will appear in
7.314 +# declaration order.
7.315 +
7.316 +SORT_MEMBER_DOCS = NO
7.317 +
7.318 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
7.319 +# brief documentation of file, namespace and class members alphabetically
7.320 +# by member name. If set to NO (the default) the members will appear in
7.321 +# declaration order.
7.322 +
7.323 +SORT_BRIEF_DOCS = NO
7.324 +
7.325 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
7.326 +# sorted by fully-qualified names, including namespaces. If set to
7.327 +# NO (the default), the class list will be sorted only by class name,
7.328 +# not including the namespace part.
7.329 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
7.330 +# Note: This option applies only to the class list, not to the
7.331 +# alphabetical list.
7.332 +
7.333 +SORT_BY_SCOPE_NAME = NO
7.334 +
7.335 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
7.336 +# disable (NO) the todo list. This list is created by putting \todo
7.337 +# commands in the documentation.
7.338 +
7.339 +GENERATE_TODOLIST = YES
7.340 +
7.341 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
7.342 +# disable (NO) the test list. This list is created by putting \test
7.343 +# commands in the documentation.
7.344 +
7.345 +GENERATE_TESTLIST = YES
7.346 +
7.347 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
7.348 +# disable (NO) the bug list. This list is created by putting \bug
7.349 +# commands in the documentation.
7.350 +
7.351 +GENERATE_BUGLIST = YES
7.352 +
7.353 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
7.354 +# disable (NO) the deprecated list. This list is created by putting
7.355 +# \deprecated commands in the documentation.
7.356 +
7.357 +GENERATE_DEPRECATEDLIST= YES
7.358 +
7.359 +# The ENABLED_SECTIONS tag can be used to enable conditional
7.360 +# documentation sections, marked by \if sectionname ... \endif.
7.361 +
7.362 +ENABLED_SECTIONS =
7.363 +
7.364 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
7.365 +# the initial value of a variable or define consists of for it to appear in
7.366 +# the documentation. If the initializer consists of more lines than specified
7.367 +# here it will be hidden. Use a value of 0 to hide initializers completely.
7.368 +# The appearance of the initializer of individual variables and defines in the
7.369 +# documentation can be controlled using \showinitializer or \hideinitializer
7.370 +# command in the documentation regardless of this setting.
7.371 +
7.372 +MAX_INITIALIZER_LINES = 5
7.373 +
7.374 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
7.375 +# at the bottom of the documentation of classes and structs. If set to YES the
7.376 +# list will mention the files that were used to generate the documentation.
7.377 +
7.378 +SHOW_USED_FILES = YES
7.379 +
7.380 +# If the sources in your project are distributed over multiple directories
7.381 +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
7.382 +# in the documentation.
7.383 +
7.384 +SHOW_DIRECTORIES = YES
7.385 +
7.386 +# The FILE_VERSION_FILTER tag can be used to specify a program or script that
7.387 +# doxygen should invoke to get the current version for each file (typically from the
7.388 +# version control system). Doxygen will invoke the program by executing (via
7.389 +# popen()) the command <command> <input-file>, where <command> is the value of
7.390 +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
7.391 +# provided by doxygen. Whatever the progam writes to standard output
7.392 +# is used as the file version. See the manual for examples.
7.393 +
7.394 +FILE_VERSION_FILTER =
7.395 +
7.396 +#---------------------------------------------------------------------------
7.397 +# configuration options related to warning and progress messages
7.398 +#---------------------------------------------------------------------------
7.399 +
7.400 +# The QUIET tag can be used to turn on/off the messages that are generated
7.401 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
7.402 +
7.403 +QUIET = NO
7.404 +
7.405 +# The WARNINGS tag can be used to turn on/off the warning messages that are
7.406 +# generated by doxygen. Possible values are YES and NO. If left blank
7.407 +# NO is used.
7.408 +
7.409 +WARNINGS = YES
7.410 +
7.411 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
7.412 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
7.413 +# automatically be disabled.
7.414 +
7.415 +WARN_IF_UNDOCUMENTED = YES
7.416 +
7.417 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
7.418 +# potential errors in the documentation, such as not documenting some
7.419 +# parameters in a documented function, or documenting parameters that
7.420 +# don't exist or using markup commands wrongly.
7.421 +
7.422 +WARN_IF_DOC_ERROR = YES
7.423 +
7.424 +# This WARN_NO_PARAMDOC option can be abled to get warnings for
7.425 +# functions that are documented, but have no documentation for their parameters
7.426 +# or return value. If set to NO (the default) doxygen will only warn about
7.427 +# wrong or incomplete parameter documentation, but not about the absence of
7.428 +# documentation.
7.429 +
7.430 +WARN_NO_PARAMDOC = NO
7.431 +
7.432 +# The WARN_FORMAT tag determines the format of the warning messages that
7.433 +# doxygen can produce. The string should contain the $file, $line, and $text
7.434 +# tags, which will be replaced by the file and line number from which the
7.435 +# warning originated and the warning text. Optionally the format may contain
7.436 +# $version, which will be replaced by the version of the file (if it could
7.437 +# be obtained via FILE_VERSION_FILTER)
7.438 +
7.439 +WARN_FORMAT = "$file:$line: $text"
7.440 +
7.441 +# The WARN_LOGFILE tag can be used to specify a file to which warning
7.442 +# and error messages should be written. If left blank the output is written
7.443 +# to stderr.
7.444 +
7.445 +WARN_LOGFILE = doxygen.log
7.446 +
7.447 +#---------------------------------------------------------------------------
7.448 +# configuration options related to the input files
7.449 +#---------------------------------------------------------------------------
7.450 +
7.451 +# The INPUT tag can be used to specify the files and/or directories that contain
7.452 +# documented source files. You may enter file names like "myfile.cpp" or
7.453 +# directories like "/usr/src/myproject". Separate the files or directories
7.454 +# with spaces.
7.455 +
7.456 +INPUT = @abs_top_srcdir@/doc \
7.457 + @abs_top_srcdir@/lemon \
7.458 + @abs_top_srcdir@/lemon/bits \
7.459 + @abs_top_srcdir@/lemon/concepts \
7.460 + @abs_top_srcdir@/demo \
7.461 + @abs_top_srcdir@/tools \
7.462 + @abs_top_srcdir@/test/test_tools.h
7.463 +
7.464 +# If the value of the INPUT tag contains directories, you can use the
7.465 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
7.466 +# and *.h) to filter out the source-files in the directories. If left
7.467 +# blank the following patterns are tested:
7.468 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
7.469 +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
7.470 +
7.471 +FILE_PATTERNS = *.h *.cc *.dox
7.472 +
7.473 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
7.474 +# should be searched for input files as well. Possible values are YES and NO.
7.475 +# If left blank NO is used.
7.476 +
7.477 +RECURSIVE = NO
7.478 +
7.479 +# The EXCLUDE tag can be used to specify files and/or directories that should
7.480 +# excluded from the INPUT source files. This way you can easily exclude a
7.481 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
7.482 +
7.483 +EXCLUDE =
7.484 +
7.485 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
7.486 +# directories that are symbolic links (a Unix filesystem feature) are excluded
7.487 +# from the input.
7.488 +
7.489 +EXCLUDE_SYMLINKS = NO
7.490 +
7.491 +# If the value of the INPUT tag contains directories, you can use the
7.492 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
7.493 +# certain files from those directories.
7.494 +
7.495 +EXCLUDE_PATTERNS =
7.496 +
7.497 +# The EXAMPLE_PATH tag can be used to specify one or more files or
7.498 +# directories that contain example code fragments that are included (see
7.499 +# the \include command).
7.500 +
7.501 +EXAMPLE_PATH = @abs_top_srcdir@/demo \
7.502 + @abs_top_srcdir@/LICENSE \
7.503 + @abs_top_srcdir@/doc
7.504 +
7.505 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
7.506 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
7.507 +# and *.h) to filter out the source-files in the directories. If left
7.508 +# blank all files are included.
7.509 +
7.510 +EXAMPLE_PATTERNS =
7.511 +
7.512 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
7.513 +# searched for input files to be used with the \include or \dontinclude
7.514 +# commands irrespective of the value of the RECURSIVE tag.
7.515 +# Possible values are YES and NO. If left blank NO is used.
7.516 +
7.517 +EXAMPLE_RECURSIVE = NO
7.518 +
7.519 +# The IMAGE_PATH tag can be used to specify one or more files or
7.520 +# directories that contain image that are included in the documentation (see
7.521 +# the \image command).
7.522 +
7.523 +IMAGE_PATH = @abs_top_srcdir@/doc/images
7.524 +
7.525 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
7.526 +# invoke to filter for each input file. Doxygen will invoke the filter program
7.527 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
7.528 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
7.529 +# input file. Doxygen will then use the output that the filter program writes
7.530 +# to standard output. If FILTER_PATTERNS is specified, this tag will be
7.531 +# ignored.
7.532 +
7.533 +INPUT_FILTER =
7.534 +
7.535 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
7.536 +# basis. Doxygen will compare the file name with each pattern and apply the
7.537 +# filter if there is a match. The filters are a list of the form:
7.538 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
7.539 +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
7.540 +# is applied to all files.
7.541 +
7.542 +FILTER_PATTERNS =
7.543 +
7.544 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
7.545 +# INPUT_FILTER) will be used to filter the input files when producing source
7.546 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
7.547 +
7.548 +FILTER_SOURCE_FILES = NO
7.549 +
7.550 +#---------------------------------------------------------------------------
7.551 +# configuration options related to source browsing
7.552 +#---------------------------------------------------------------------------
7.553 +
7.554 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
7.555 +# be generated. Documented entities will be cross-referenced with these sources.
7.556 +# Note: To get rid of all source code in the generated output, make sure also
7.557 +# VERBATIM_HEADERS is set to NO.
7.558 +
7.559 +SOURCE_BROWSER = NO
7.560 +
7.561 +# Setting the INLINE_SOURCES tag to YES will include the body
7.562 +# of functions and classes directly in the documentation.
7.563 +
7.564 +INLINE_SOURCES = NO
7.565 +
7.566 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
7.567 +# doxygen to hide any special comment blocks from generated source code
7.568 +# fragments. Normal C and C++ comments will always remain visible.
7.569 +
7.570 +STRIP_CODE_COMMENTS = YES
7.571 +
7.572 +# If the REFERENCED_BY_RELATION tag is set to YES (the default)
7.573 +# then for each documented function all documented
7.574 +# functions referencing it will be listed.
7.575 +
7.576 +REFERENCED_BY_RELATION = NO
7.577 +
7.578 +# If the REFERENCES_RELATION tag is set to YES (the default)
7.579 +# then for each documented function all documented entities
7.580 +# called/used by that function will be listed.
7.581 +
7.582 +REFERENCES_RELATION = NO
7.583 +
7.584 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
7.585 +# will generate a verbatim copy of the header file for each class for
7.586 +# which an include is specified. Set to NO to disable this.
7.587 +
7.588 +VERBATIM_HEADERS = NO
7.589 +
7.590 +#---------------------------------------------------------------------------
7.591 +# configuration options related to the alphabetical class index
7.592 +#---------------------------------------------------------------------------
7.593 +
7.594 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
7.595 +# of all compounds will be generated. Enable this if the project
7.596 +# contains a lot of classes, structs, unions or interfaces.
7.597 +
7.598 +ALPHABETICAL_INDEX = YES
7.599 +
7.600 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
7.601 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
7.602 +# in which this list will be split (can be a number in the range [1..20])
7.603 +
7.604 +COLS_IN_ALPHA_INDEX = 2
7.605 +
7.606 +# In case all classes in a project start with a common prefix, all
7.607 +# classes will be put under the same header in the alphabetical index.
7.608 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
7.609 +# should be ignored while generating the index headers.
7.610 +
7.611 +IGNORE_PREFIX =
7.612 +
7.613 +#---------------------------------------------------------------------------
7.614 +# configuration options related to the HTML output
7.615 +#---------------------------------------------------------------------------
7.616 +
7.617 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
7.618 +# generate HTML output.
7.619 +
7.620 +GENERATE_HTML = YES
7.621 +
7.622 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
7.623 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
7.624 +# put in front of it. If left blank `html' will be used as the default path.
7.625 +
7.626 +HTML_OUTPUT = html
7.627 +
7.628 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
7.629 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
7.630 +# doxygen will generate files with .html extension.
7.631 +
7.632 +HTML_FILE_EXTENSION = .html
7.633 +
7.634 +# The HTML_HEADER tag can be used to specify a personal HTML header for
7.635 +# each generated HTML page. If it is left blank doxygen will generate a
7.636 +# standard header.
7.637 +
7.638 +HTML_HEADER =
7.639 +
7.640 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
7.641 +# each generated HTML page. If it is left blank doxygen will generate a
7.642 +# standard footer.
7.643 +
7.644 +HTML_FOOTER =
7.645 +
7.646 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
7.647 +# style sheet that is used by each HTML page. It can be used to
7.648 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
7.649 +# will generate a default style sheet. Note that doxygen will try to copy
7.650 +# the style sheet file to the HTML output directory, so don't put your own
7.651 +# stylesheet in the HTML output directory as well, or it will be erased!
7.652 +
7.653 +HTML_STYLESHEET =
7.654 +
7.655 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
7.656 +# files or namespaces will be aligned in HTML using tables. If set to
7.657 +# NO a bullet list will be used.
7.658 +
7.659 +HTML_ALIGN_MEMBERS = YES
7.660 +
7.661 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
7.662 +# will be generated that can be used as input for tools like the
7.663 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
7.664 +# of the generated HTML documentation.
7.665 +
7.666 +GENERATE_HTMLHELP = NO
7.667 +
7.668 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
7.669 +# be used to specify the file name of the resulting .chm file. You
7.670 +# can add a path in front of the file if the result should not be
7.671 +# written to the html output directory.
7.672 +
7.673 +CHM_FILE =
7.674 +
7.675 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
7.676 +# be used to specify the location (absolute path including file name) of
7.677 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
7.678 +# the HTML help compiler on the generated index.hhp.
7.679 +
7.680 +HHC_LOCATION =
7.681 +
7.682 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
7.683 +# controls if a separate .chi index file is generated (YES) or that
7.684 +# it should be included in the master .chm file (NO).
7.685 +
7.686 +GENERATE_CHI = NO
7.687 +
7.688 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
7.689 +# controls whether a binary table of contents is generated (YES) or a
7.690 +# normal table of contents (NO) in the .chm file.
7.691 +
7.692 +BINARY_TOC = NO
7.693 +
7.694 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
7.695 +# to the contents of the HTML help documentation and to the tree view.
7.696 +
7.697 +TOC_EXPAND = NO
7.698 +
7.699 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
7.700 +# top of each HTML page. The value NO (the default) enables the index and
7.701 +# the value YES disables it.
7.702 +
7.703 +DISABLE_INDEX = NO
7.704 +
7.705 +# This tag can be used to set the number of enum values (range [1..20])
7.706 +# that doxygen will group on one line in the generated HTML documentation.
7.707 +
7.708 +ENUM_VALUES_PER_LINE = 4
7.709 +
7.710 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
7.711 +# generated containing a tree-like index structure (just like the one that
7.712 +# is generated for HTML Help). For this to work a browser that supports
7.713 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
7.714 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
7.715 +# probably better off using the HTML help feature.
7.716 +
7.717 +GENERATE_TREEVIEW = YES
7.718 +
7.719 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
7.720 +# used to set the initial width (in pixels) of the frame in which the tree
7.721 +# is shown.
7.722 +
7.723 +TREEVIEW_WIDTH = 250
7.724 +
7.725 +#---------------------------------------------------------------------------
7.726 +# configuration options related to the LaTeX output
7.727 +#---------------------------------------------------------------------------
7.728 +
7.729 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
7.730 +# generate Latex output.
7.731 +
7.732 +GENERATE_LATEX = NO
7.733 +
7.734 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
7.735 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
7.736 +# put in front of it. If left blank `latex' will be used as the default path.
7.737 +
7.738 +LATEX_OUTPUT = latex
7.739 +
7.740 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
7.741 +# invoked. If left blank `latex' will be used as the default command name.
7.742 +
7.743 +LATEX_CMD_NAME = latex
7.744 +
7.745 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
7.746 +# generate index for LaTeX. If left blank `makeindex' will be used as the
7.747 +# default command name.
7.748 +
7.749 +MAKEINDEX_CMD_NAME = makeindex
7.750 +
7.751 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
7.752 +# LaTeX documents. This may be useful for small projects and may help to
7.753 +# save some trees in general.
7.754 +
7.755 +COMPACT_LATEX = YES
7.756 +
7.757 +# The PAPER_TYPE tag can be used to set the paper type that is used
7.758 +# by the printer. Possible values are: a4, a4wide, letter, legal and
7.759 +# executive. If left blank a4wide will be used.
7.760 +
7.761 +PAPER_TYPE = a4wide
7.762 +
7.763 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
7.764 +# packages that should be included in the LaTeX output.
7.765 +
7.766 +EXTRA_PACKAGES = amsmath \
7.767 + amssymb
7.768 +
7.769 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
7.770 +# the generated latex document. The header should contain everything until
7.771 +# the first chapter. If it is left blank doxygen will generate a
7.772 +# standard header. Notice: only use this tag if you know what you are doing!
7.773 +
7.774 +LATEX_HEADER =
7.775 +
7.776 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
7.777 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
7.778 +# contain links (just like the HTML output) instead of page references
7.779 +# This makes the output suitable for online browsing using a pdf viewer.
7.780 +
7.781 +PDF_HYPERLINKS = YES
7.782 +
7.783 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
7.784 +# plain latex in the generated Makefile. Set this option to YES to get a
7.785 +# higher quality PDF documentation.
7.786 +
7.787 +USE_PDFLATEX = YES
7.788 +
7.789 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
7.790 +# command to the generated LaTeX files. This will instruct LaTeX to keep
7.791 +# running if errors occur, instead of asking the user for help.
7.792 +# This option is also used when generating formulas in HTML.
7.793 +
7.794 +LATEX_BATCHMODE = NO
7.795 +
7.796 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
7.797 +# include the index chapters (such as File Index, Compound Index, etc.)
7.798 +# in the output.
7.799 +
7.800 +LATEX_HIDE_INDICES = NO
7.801 +
7.802 +#---------------------------------------------------------------------------
7.803 +# configuration options related to the RTF output
7.804 +#---------------------------------------------------------------------------
7.805 +
7.806 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
7.807 +# The RTF output is optimized for Word 97 and may not look very pretty with
7.808 +# other RTF readers or editors.
7.809 +
7.810 +GENERATE_RTF = NO
7.811 +
7.812 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
7.813 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
7.814 +# put in front of it. If left blank `rtf' will be used as the default path.
7.815 +
7.816 +RTF_OUTPUT = rtf
7.817 +
7.818 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
7.819 +# RTF documents. This may be useful for small projects and may help to
7.820 +# save some trees in general.
7.821 +
7.822 +COMPACT_RTF = NO
7.823 +
7.824 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
7.825 +# will contain hyperlink fields. The RTF file will
7.826 +# contain links (just like the HTML output) instead of page references.
7.827 +# This makes the output suitable for online browsing using WORD or other
7.828 +# programs which support those fields.
7.829 +# Note: wordpad (write) and others do not support links.
7.830 +
7.831 +RTF_HYPERLINKS = NO
7.832 +
7.833 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
7.834 +# config file, i.e. a series of assignments. You only have to provide
7.835 +# replacements, missing definitions are set to their default value.
7.836 +
7.837 +RTF_STYLESHEET_FILE =
7.838 +
7.839 +# Set optional variables used in the generation of an rtf document.
7.840 +# Syntax is similar to doxygen's config file.
7.841 +
7.842 +RTF_EXTENSIONS_FILE =
7.843 +
7.844 +#---------------------------------------------------------------------------
7.845 +# configuration options related to the man page output
7.846 +#---------------------------------------------------------------------------
7.847 +
7.848 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
7.849 +# generate man pages
7.850 +
7.851 +GENERATE_MAN = NO
7.852 +
7.853 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
7.854 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
7.855 +# put in front of it. If left blank `man' will be used as the default path.
7.856 +
7.857 +MAN_OUTPUT = man
7.858 +
7.859 +# The MAN_EXTENSION tag determines the extension that is added to
7.860 +# the generated man pages (default is the subroutine's section .3)
7.861 +
7.862 +MAN_EXTENSION = .3
7.863 +
7.864 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
7.865 +# then it will generate one additional man file for each entity
7.866 +# documented in the real man page(s). These additional files
7.867 +# only source the real man page, but without them the man command
7.868 +# would be unable to find the correct page. The default is NO.
7.869 +
7.870 +MAN_LINKS = NO
7.871 +
7.872 +#---------------------------------------------------------------------------
7.873 +# configuration options related to the XML output
7.874 +#---------------------------------------------------------------------------
7.875 +
7.876 +# If the GENERATE_XML tag is set to YES Doxygen will
7.877 +# generate an XML file that captures the structure of
7.878 +# the code including all documentation.
7.879 +
7.880 +GENERATE_XML = NO
7.881 +
7.882 +# The XML_OUTPUT tag is used to specify where the XML pages will be put.
7.883 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
7.884 +# put in front of it. If left blank `xml' will be used as the default path.
7.885 +
7.886 +XML_OUTPUT = xml
7.887 +
7.888 +# The XML_SCHEMA tag can be used to specify an XML schema,
7.889 +# which can be used by a validating XML parser to check the
7.890 +# syntax of the XML files.
7.891 +
7.892 +XML_SCHEMA =
7.893 +
7.894 +# The XML_DTD tag can be used to specify an XML DTD,
7.895 +# which can be used by a validating XML parser to check the
7.896 +# syntax of the XML files.
7.897 +
7.898 +XML_DTD =
7.899 +
7.900 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
7.901 +# dump the program listings (including syntax highlighting
7.902 +# and cross-referencing information) to the XML output. Note that
7.903 +# enabling this will significantly increase the size of the XML output.
7.904 +
7.905 +XML_PROGRAMLISTING = YES
7.906 +
7.907 +#---------------------------------------------------------------------------
7.908 +# configuration options for the AutoGen Definitions output
7.909 +#---------------------------------------------------------------------------
7.910 +
7.911 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
7.912 +# generate an AutoGen Definitions (see autogen.sf.net) file
7.913 +# that captures the structure of the code including all
7.914 +# documentation. Note that this feature is still experimental
7.915 +# and incomplete at the moment.
7.916 +
7.917 +GENERATE_AUTOGEN_DEF = NO
7.918 +
7.919 +#---------------------------------------------------------------------------
7.920 +# configuration options related to the Perl module output
7.921 +#---------------------------------------------------------------------------
7.922 +
7.923 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will
7.924 +# generate a Perl module file that captures the structure of
7.925 +# the code including all documentation. Note that this
7.926 +# feature is still experimental and incomplete at the
7.927 +# moment.
7.928 +
7.929 +GENERATE_PERLMOD = NO
7.930 +
7.931 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
7.932 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able
7.933 +# to generate PDF and DVI output from the Perl module output.
7.934 +
7.935 +PERLMOD_LATEX = NO
7.936 +
7.937 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
7.938 +# nicely formatted so it can be parsed by a human reader. This is useful
7.939 +# if you want to understand what is going on. On the other hand, if this
7.940 +# tag is set to NO the size of the Perl module output will be much smaller
7.941 +# and Perl will parse it just the same.
7.942 +
7.943 +PERLMOD_PRETTY = YES
7.944 +
7.945 +# The names of the make variables in the generated doxyrules.make file
7.946 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
7.947 +# This is useful so different doxyrules.make files included by the same
7.948 +# Makefile don't overwrite each other's variables.
7.949 +
7.950 +PERLMOD_MAKEVAR_PREFIX =
7.951 +
7.952 +#---------------------------------------------------------------------------
7.953 +# Configuration options related to the preprocessor
7.954 +#---------------------------------------------------------------------------
7.955 +
7.956 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
7.957 +# evaluate all C-preprocessor directives found in the sources and include
7.958 +# files.
7.959 +
7.960 +ENABLE_PREPROCESSING = YES
7.961 +
7.962 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
7.963 +# names in the source code. If set to NO (the default) only conditional
7.964 +# compilation will be performed. Macro expansion can be done in a controlled
7.965 +# way by setting EXPAND_ONLY_PREDEF to YES.
7.966 +
7.967 +MACRO_EXPANSION = NO
7.968 +
7.969 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
7.970 +# then the macro expansion is limited to the macros specified with the
7.971 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
7.972 +
7.973 +EXPAND_ONLY_PREDEF = NO
7.974 +
7.975 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
7.976 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
7.977 +
7.978 +SEARCH_INCLUDES = YES
7.979 +
7.980 +# The INCLUDE_PATH tag can be used to specify one or more directories that
7.981 +# contain include files that are not input files but should be processed by
7.982 +# the preprocessor.
7.983 +
7.984 +INCLUDE_PATH =
7.985 +
7.986 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
7.987 +# patterns (like *.h and *.hpp) to filter out the header-files in the
7.988 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
7.989 +# be used.
7.990 +
7.991 +INCLUDE_FILE_PATTERNS =
7.992 +
7.993 +# The PREDEFINED tag can be used to specify one or more macro names that
7.994 +# are defined before the preprocessor is started (similar to the -D option of
7.995 +# gcc). The argument of the tag is a list of macros of the form: name
7.996 +# or name=definition (no spaces). If the definition and the = are
7.997 +# omitted =1 is assumed. To prevent a macro definition from being
7.998 +# undefined via #undef or recursively expanded use the := operator
7.999 +# instead of the = operator.
7.1000 +
7.1001 +PREDEFINED = DOXYGEN
7.1002 +
7.1003 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
7.1004 +# this tag can be used to specify a list of macro names that should be expanded.
7.1005 +# The macro definition that is found in the sources will be used.
7.1006 +# Use the PREDEFINED tag if you want to use a different macro definition.
7.1007 +
7.1008 +EXPAND_AS_DEFINED =
7.1009 +
7.1010 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
7.1011 +# doxygen's preprocessor will remove all function-like macros that are alone
7.1012 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
7.1013 +# function macros are typically used for boiler-plate code, and will confuse
7.1014 +# the parser if not removed.
7.1015 +
7.1016 +SKIP_FUNCTION_MACROS = YES
7.1017 +
7.1018 +#---------------------------------------------------------------------------
7.1019 +# Configuration::additions related to external references
7.1020 +#---------------------------------------------------------------------------
7.1021 +
7.1022 +# The TAGFILES option can be used to specify one or more tagfiles.
7.1023 +# Optionally an initial location of the external documentation
7.1024 +# can be added for each tagfile. The format of a tag file without
7.1025 +# this location is as follows:
7.1026 +# TAGFILES = file1 file2 ...
7.1027 +# Adding location for the tag files is done as follows:
7.1028 +# TAGFILES = file1=loc1 "file2 = loc2" ...
7.1029 +# where "loc1" and "loc2" can be relative or absolute paths or
7.1030 +# URLs. If a location is present for each tag, the installdox tool
7.1031 +# does not have to be run to correct the links.
7.1032 +# Note that each tag file must have a unique name
7.1033 +# (where the name does NOT include the path)
7.1034 +# If a tag file is not located in the directory in which doxygen
7.1035 +# is run, you must also specify the path to the tagfile here.
7.1036 +
7.1037 +TAGFILES = "@abs_top_srcdir@/doc/libstdc++.tag = http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/"
7.1038 +
7.1039 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
7.1040 +# a tag file that is based on the input files it reads.
7.1041 +
7.1042 +GENERATE_TAGFILE = html/lemon.tag
7.1043 +
7.1044 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
7.1045 +# in the class index. If set to NO only the inherited external classes
7.1046 +# will be listed.
7.1047 +
7.1048 +ALLEXTERNALS = NO
7.1049 +
7.1050 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
7.1051 +# in the modules index. If set to NO, only the current project's groups will
7.1052 +# be listed.
7.1053 +
7.1054 +EXTERNAL_GROUPS = NO
7.1055 +
7.1056 +# The PERL_PATH should be the absolute path and name of the perl script
7.1057 +# interpreter (i.e. the result of `which perl').
7.1058 +
7.1059 +PERL_PATH = /usr/bin/perl
7.1060 +
7.1061 +#---------------------------------------------------------------------------
7.1062 +# Configuration options related to the dot tool
7.1063 +#---------------------------------------------------------------------------
7.1064 +
7.1065 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
7.1066 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
7.1067 +# or super classes. Setting the tag to NO turns the diagrams off. Note that
7.1068 +# this option is superseded by the HAVE_DOT option below. This is only a
7.1069 +# fallback. It is recommended to install and use dot, since it yields more
7.1070 +# powerful graphs.
7.1071 +
7.1072 +CLASS_DIAGRAMS = NO
7.1073 +
7.1074 +# If set to YES, the inheritance and collaboration graphs will hide
7.1075 +# inheritance and usage relations if the target is undocumented
7.1076 +# or is not a class.
7.1077 +
7.1078 +HIDE_UNDOC_RELATIONS = YES
7.1079 +
7.1080 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
7.1081 +# available from the path. This tool is part of Graphviz, a graph visualization
7.1082 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
7.1083 +# have no effect if this option is set to NO (the default)
7.1084 +
7.1085 +HAVE_DOT = YES
7.1086 +
7.1087 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
7.1088 +# will generate a graph for each documented class showing the direct and
7.1089 +# indirect inheritance relations. Setting this tag to YES will force the
7.1090 +# the CLASS_DIAGRAMS tag to NO.
7.1091 +
7.1092 +CLASS_GRAPH = YES
7.1093 +
7.1094 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
7.1095 +# will generate a graph for each documented class showing the direct and
7.1096 +# indirect implementation dependencies (inheritance, containment, and
7.1097 +# class references variables) of the class with other documented classes.
7.1098 +
7.1099 +COLLABORATION_GRAPH = NO
7.1100 +
7.1101 +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
7.1102 +# will generate a graph for groups, showing the direct groups dependencies
7.1103 +
7.1104 +GROUP_GRAPHS = NO
7.1105 +
7.1106 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
7.1107 +# collaboration diagrams in a style similar to the OMG's Unified Modeling
7.1108 +# Language.
7.1109 +
7.1110 +UML_LOOK = NO
7.1111 +
7.1112 +# If set to YES, the inheritance and collaboration graphs will show the
7.1113 +# relations between templates and their instances.
7.1114 +
7.1115 +TEMPLATE_RELATIONS = NO
7.1116 +
7.1117 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
7.1118 +# tags are set to YES then doxygen will generate a graph for each documented
7.1119 +# file showing the direct and indirect include dependencies of the file with
7.1120 +# other documented files.
7.1121 +
7.1122 +INCLUDE_GRAPH = NO
7.1123 +
7.1124 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
7.1125 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
7.1126 +# documented header file showing the documented files that directly or
7.1127 +# indirectly include this file.
7.1128 +
7.1129 +INCLUDED_BY_GRAPH = NO
7.1130 +
7.1131 +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
7.1132 +# generate a call dependency graph for every global function or class method.
7.1133 +# Note that enabling this option will significantly increase the time of a run.
7.1134 +# So in most cases it will be better to enable call graphs for selected
7.1135 +# functions only using the \callgraph command.
7.1136 +
7.1137 +CALL_GRAPH = NO
7.1138 +
7.1139 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
7.1140 +# will graphical hierarchy of all classes instead of a textual one.
7.1141 +
7.1142 +GRAPHICAL_HIERARCHY = NO
7.1143 +
7.1144 +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
7.1145 +# then doxygen will show the dependencies a directory has on other directories
7.1146 +# in a graphical way. The dependency relations are determined by the #include
7.1147 +# relations between the files in the directories.
7.1148 +
7.1149 +DIRECTORY_GRAPH = NO
7.1150 +
7.1151 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
7.1152 +# generated by dot. Possible values are png, jpg, or gif
7.1153 +# If left blank png will be used.
7.1154 +
7.1155 +DOT_IMAGE_FORMAT = png
7.1156 +
7.1157 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
7.1158 +# found. If left blank, it is assumed the dot tool can be found in the path.
7.1159 +
7.1160 +DOT_PATH =
7.1161 +
7.1162 +# The DOTFILE_DIRS tag can be used to specify one or more directories that
7.1163 +# contain dot files that are included in the documentation (see the
7.1164 +# \dotfile command).
7.1165 +
7.1166 +DOTFILE_DIRS =
7.1167 +
7.1168 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
7.1169 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
7.1170 +# this value, doxygen will try to truncate the graph, so that it fits within
7.1171 +# the specified constraint. Beware that most browsers cannot cope with very
7.1172 +# large images.
7.1173 +
7.1174 +MAX_DOT_GRAPH_WIDTH = 1024
7.1175 +
7.1176 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
7.1177 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
7.1178 +# this value, doxygen will try to truncate the graph, so that it fits within
7.1179 +# the specified constraint. Beware that most browsers cannot cope with very
7.1180 +# large images.
7.1181 +
7.1182 +MAX_DOT_GRAPH_HEIGHT = 1024
7.1183 +
7.1184 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
7.1185 +# graphs generated by dot. A depth value of 3 means that only nodes reachable
7.1186 +# from the root by following a path via at most 3 edges will be shown. Nodes
7.1187 +# that lay further from the root node will be omitted. Note that setting this
7.1188 +# option to 1 or 2 may greatly reduce the computation time needed for large
7.1189 +# code bases. Also note that a graph may be further truncated if the graph's
7.1190 +# image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
7.1191 +# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
7.1192 +# the graph is not depth-constrained.
7.1193 +
7.1194 +MAX_DOT_GRAPH_DEPTH = 0
7.1195 +
7.1196 +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
7.1197 +# background. This is disabled by default, which results in a white background.
7.1198 +# Warning: Depending on the platform used, enabling this option may lead to
7.1199 +# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
7.1200 +# read).
7.1201 +
7.1202 +DOT_TRANSPARENT = NO
7.1203 +
7.1204 +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
7.1205 +# files in one run (i.e. multiple -o and -T options on the command line). This
7.1206 +# makes dot run faster, but since only newer versions of dot (>1.8.10)
7.1207 +# support this, this feature is disabled by default.
7.1208 +
7.1209 +DOT_MULTI_TARGETS = NO
7.1210 +
7.1211 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
7.1212 +# generate a legend page explaining the meaning of the various boxes and
7.1213 +# arrows in the dot generated graphs.
7.1214 +
7.1215 +GENERATE_LEGEND = YES
7.1216 +
7.1217 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
7.1218 +# remove the intermediate dot files that are used to generate
7.1219 +# the various graphs.
7.1220 +
7.1221 +DOT_CLEANUP = YES
7.1222 +
7.1223 +#---------------------------------------------------------------------------
7.1224 +# Configuration::additions related to the search engine
7.1225 +#---------------------------------------------------------------------------
7.1226 +
7.1227 +# The SEARCHENGINE tag specifies whether or not a search engine should be
7.1228 +# used. If set to NO the values of all tags below this one will be ignored.
7.1229 +
7.1230 +SEARCHENGINE = NO
8.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
8.2 +++ b/doc/Makefile Tue Dec 18 10:56:09 2007 +0100
8.3 @@ -0,0 +1,2 @@
8.4 +all:
8.5 + $(MAKE) -C ..
9.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
9.2 +++ b/doc/Makefile.am Tue Dec 18 10:56:09 2007 +0100
9.3 @@ -0,0 +1,53 @@
9.4 +htmldir = $(datadir)/doc/$(PACKAGE)/html
9.5 +
9.6 +EXTRA_DIST += \
9.7 + doc/Makefile \
9.8 + doc/Doxyfile.in
9.9 +
9.10 +doc:
9.11 + if test ${doxygen_found} = yes; then \
9.12 + cd doc; \
9.13 + doxygen Doxyfile; \
9.14 + cd ..; \
9.15 + cp $(srcdir)/doc/icons/geom/ftv2* doc/html; \
9.16 + fi
9.17 +
9.18 +doc-clean:
9.19 + if test ${doxygen_found} = yes; then \
9.20 + rm -rf doc/html; \
9.21 + rm -f doc/doxygen.log; \
9.22 + cd doc; \
9.23 + doxygen Doxyfile; \
9.24 + cd ..; \
9.25 + cp $(srcdir)/doc/icons/geom/ftv2* doc/html; \
9.26 + fi
9.27 +
9.28 +clean-local:
9.29 + -rm -rf doc/html
9.30 + -rm -f doc/doxygen.log
9.31 +
9.32 +doc/html:
9.33 + $(MAKE) $(AM_MAKEFLAGS) doc-clean
9.34 +
9.35 +if WANT_DOC
9.36 +
9.37 +install-data-local: doc/html
9.38 + @$(NORMAL_INSTALL)
9.39 + $(mkinstalldirs) $(DESTDIR)$(htmldir)
9.40 + @dir='doc/html'; shopt -s nullglob; for p in $$dir/*.html $$dir/*.css $$dir/*.png $$dir/*.gif $$dir/*.dot $$dir/*.php $$dir/*.idx $$dir/*.tag ; do \
9.41 + f="`echo $$p | sed -e 's|^.*/||'`"; \
9.42 + echo " $(INSTALL_DATA) $$p $(DESTDIR)$(htmldir)/$$f"; \
9.43 + $(INSTALL_DATA) $$p $(DESTDIR)$(htmldir)/$$f; \
9.44 + done
9.45 +
9.46 +uninstall-local: doc/html
9.47 + @$(NORMAL_UNINSTALL)
9.48 + @dir='doc/html'; shopt -s nullglob; for p in $$dir/*.html $$dir/*.css $$dir/*.png $$dir/*.gif $$dir/*.dot $$dir/*.php $$dir/*.idx $$dir/*.tag ; do \
9.49 + f="`echo $$p | sed -e 's|^.*/||'`"; \
9.50 + echo " rm -f $(DESTDIR)$(htmldir)/$$f"; \
9.51 + rm -f $(DESTDIR)$(htmldir)/$$f; \
9.52 + done
9.53 +
9.54 +endif WANT_DOC
9.55 +
9.56 +.PHONY: doc doc-clean
10.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
10.2 +++ b/lemon/Makefile Tue Dec 18 10:56:09 2007 +0100
10.3 @@ -0,0 +1,2 @@
10.4 +all:
10.5 + $(MAKE) -C ..
11.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
11.2 +++ b/lemon/Makefile.am Tue Dec 18 10:56:09 2007 +0100
11.3 @@ -0,0 +1,18 @@
11.4 +EXTRA_DIST += \
11.5 + lemon/Makefile \
11.6 + lemon/lemon.pc.in
11.7 +
11.8 +pkgconfig_DATA += lemon/lemon.pc
11.9 +
11.10 +lib_LTLIBRARIES += lemon/libemon.la
11.11 +
11.12 +lemon_libemon_la_SOURCES =
11.13 +
11.14 +lemon_libemon_la_CXXFLAGS = $(GLPK_CFLAGS) $(CPLEX_CFLAGS) $(SOPLEX_CXXFLAGS)
11.15 +lemon_libemon_la_LDFLAGS = $(GLPK_LIBS) $(CPLEX_LIBS) $(SOPLEX_LIBS)
11.16 +
11.17 +lemon_HEADERS +=
11.18 +
11.19 +bits_HEADERS +=
11.20 +
11.21 +concept_HEADERS +=
12.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
12.2 +++ b/lemon/config.h.in Tue Dec 18 10:56:09 2007 +0100
12.3 @@ -0,0 +1,5 @@
12.4 +/* Define to 1 if you have CPLEX. */
12.5 +#undef HAVE_CPLEX
12.6 +
12.7 +/* Define to 1 if you have GLPK. */
12.8 +#undef HAVE_GLPK
13.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
13.2 +++ b/lemon/lemon.pc.in Tue Dec 18 10:56:09 2007 +0100
13.3 @@ -0,0 +1,10 @@
13.4 +prefix=@prefix@
13.5 +exec_prefix=@exec_prefix@
13.6 +libdir=@libdir@
13.7 +includedir=@includedir@
13.8 +
13.9 +Name: @PACKAGE_NAME@
13.10 +Description: Library of Efficient Models and Optimization in Networks
13.11 +Version: @PACKAGE_VERSION@
13.12 +Libs: -L${libdir} -lemon @GLPK_LIBS@ @CPLEX_LIBS@
13.13 +Cflags: -I${includedir} @GLPK_CFLAGS@ @CPLEX_CFLAGS@
14.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
14.2 +++ b/m4/lx_check_cplex.m4 Tue Dec 18 10:56:09 2007 +0100
14.3 @@ -0,0 +1,77 @@
14.4 +AC_DEFUN([LX_CHECK_CPLEX],
14.5 +[
14.6 + AC_ARG_WITH([cplex],
14.7 +AS_HELP_STRING([--with-cplex@<:@=PREFIX@:>@], [search for CPLEX under PREFIX or under the default search paths if PREFIX is not given @<:@default@:>@])
14.8 +AS_HELP_STRING([--without-cplex], [disable checking for CPLEX]),
14.9 + [], [with_cplex=yes])
14.10 +
14.11 + AC_ARG_WITH([cplex-includedir],
14.12 +AS_HELP_STRING([--with-cplex-includedir=DIR], [search for CPLEX headers in DIR]),
14.13 + [], [with_cplex_includedir=no])
14.14 +
14.15 + AC_ARG_WITH([cplex-libdir],
14.16 +AS_HELP_STRING([--with-cplex-libdir=DIR], [search for CPLEX libraries in DIR]),
14.17 + [], [with_cplex_libdir=no])
14.18 +
14.19 + lx_cplex_found=no
14.20 + if test x"$with_cplex" != x"no"; then
14.21 + AC_MSG_CHECKING([for CPLEX])
14.22 +
14.23 + if test x"$with_cplex_includedir" != x"no"; then
14.24 + CPLEX_CFLAGS="-I$with_cplex_includedir"
14.25 + elif test x"$with_cplex" != x"yes"; then
14.26 + CPLEX_CFLAGS="-I$with_cplex/include"
14.27 + elif test x"$CPLEX_INCLUDEDIR" != x; then
14.28 + CPLEX_CFLAGS="-I$CPLEX_INCLUDEDIR"
14.29 + fi
14.30 +
14.31 + if test x"$with_cplex_libdir" != x"no"; then
14.32 + CPLEX_LDFLAGS="-L$with_cplex_libdir"
14.33 + elif test x"$with_cplex" != x"yes"; then
14.34 + CPLEX_LDFLAGS="-L$with_cplex/lib"
14.35 + elif test x"$CPLEX_LIBDIR" != x; then
14.36 + CPLEX_LDFLAGS="-L$CPLEX_LIBDIR"
14.37 + fi
14.38 + CPLEX_LIBS="-lcplex -lm -lpthread"
14.39 +
14.40 + lx_save_cxxflags="$CXXFLAGS"
14.41 + lx_save_ldflags="$LDFLAGS"
14.42 + lx_save_libs="$LIBS"
14.43 + CXXFLAGS="$CPLEX_CFLAGS"
14.44 + LDFLAGS="$CPLEX_LDFLAGS"
14.45 + LIBS="$CPLEX_LIBS"
14.46 +
14.47 + lx_cplex_test_prog='
14.48 + extern "C" {
14.49 + #include <ilcplex/cplex.h>
14.50 + }
14.51 +
14.52 + int main(int argc, char* argv[])
14.53 + {
14.54 + CPXENVptr env = NULL;
14.55 + return 0;
14.56 + }'
14.57 +
14.58 + AC_LANG_PUSH(C++)
14.59 + AC_LINK_IFELSE([$lx_cplex_test_prog], [lx_cplex_found=yes], [lx_cplex_found=no])
14.60 + AC_LANG_POP(C++)
14.61 +
14.62 + CXXFLAGS="$lx_save_cxxflags"
14.63 + LDFLAGS="$lx_save_ldflags"
14.64 + LIBS="$lx_save_libs"
14.65 +
14.66 + if test x"$lx_cplex_found" = x"yes"; then
14.67 + AC_DEFINE([HAVE_CPLEX], [1], [Define to 1 if you have CPLEX.])
14.68 + AC_MSG_RESULT([yes])
14.69 + else
14.70 + CPLEX_CFLAGS=""
14.71 + CPLEX_LDFLAGS=""
14.72 + CPLEX_LIBS=""
14.73 + AC_MSG_RESULT([no])
14.74 + fi
14.75 + fi
14.76 + CPLEX_LIBS="$CPLEX_LDFLAGS $CPLEX_LIBS"
14.77 + AC_SUBST(CPLEX_CFLAGS)
14.78 + AC_SUBST(CPLEX_LIBS)
14.79 + AM_CONDITIONAL([HAVE_CPLEX], [test x"$lx_cplex_found" = x"yes"])
14.80 +])
15.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
15.2 +++ b/m4/lx_check_glpk.m4 Tue Dec 18 10:56:09 2007 +0100
15.3 @@ -0,0 +1,75 @@
15.4 +AC_DEFUN([LX_CHECK_GLPK],
15.5 +[
15.6 + AC_ARG_WITH([glpk],
15.7 +AS_HELP_STRING([--with-glpk@<:@=PREFIX@:>@], [search for GLPK under PREFIX or under the default search paths if PREFIX is not given @<:@default@:>@])
15.8 +AS_HELP_STRING([--without-glpk], [disable checking for GLPK]),
15.9 + [], [with_glpk=yes])
15.10 +
15.11 + AC_ARG_WITH([glpk-includedir],
15.12 +AS_HELP_STRING([--with-glpk-includedir=DIR], [search for GLPK headers in DIR]),
15.13 + [], [with_glpk_includedir=no])
15.14 +
15.15 + AC_ARG_WITH([glpk-libdir],
15.16 +AS_HELP_STRING([--with-glpk-libdir=DIR], [search for GLPK libraries in DIR]),
15.17 + [], [with_glpk_libdir=no])
15.18 +
15.19 + lx_glpk_found=no
15.20 + if test x"$with_glpk" != x"no"; then
15.21 + AC_MSG_CHECKING([for GLPK])
15.22 +
15.23 + if test x"$with_glpk_includedir" != x"no"; then
15.24 + GLPK_CFLAGS="-I$with_glpk_includedir"
15.25 + elif test x"$with_glpk" != x"yes"; then
15.26 + GLPK_CFLAGS="-I$with_glpk/include"
15.27 + fi
15.28 +
15.29 + if test x"$with_glpk_libdir" != x"no"; then
15.30 + GLPK_LDFLAGS="-L$with_glpk_libdir"
15.31 + elif test x"$with_glpk" != x"yes"; then
15.32 + GLPK_LDFLAGS="-L$with_glpk/lib"
15.33 + fi
15.34 + GLPK_LIBS="-lglpk"
15.35 +
15.36 + lx_save_cxxflags="$CXXFLAGS"
15.37 + lx_save_ldflags="$LDFLAGS"
15.38 + lx_save_libs="$LIBS"
15.39 + CXXFLAGS="$GLPK_CFLAGS"
15.40 + LDFLAGS="$GLPK_LDFLAGS"
15.41 + LIBS="$GLPK_LIBS"
15.42 +
15.43 + lx_glpk_test_prog='
15.44 + extern "C" {
15.45 + #include <glpk.h>
15.46 + }
15.47 +
15.48 + int main(int argc, char* argv[])
15.49 + {
15.50 + LPX *lp;
15.51 + lp = lpx_create_prob();
15.52 + lpx_delete_prob(lp);
15.53 + return 0;
15.54 + }'
15.55 +
15.56 + AC_LANG_PUSH(C++)
15.57 + AC_LINK_IFELSE([$lx_glpk_test_prog], [lx_glpk_found=yes], [lx_glpk_found=no])
15.58 + AC_LANG_POP(C++)
15.59 +
15.60 + CXXFLAGS="$lx_save_cxxflags"
15.61 + LDFLAGS="$lx_save_ldflags"
15.62 + LIBS="$lx_save_libs"
15.63 +
15.64 + if test x"$lx_glpk_found" = x"yes"; then
15.65 + AC_DEFINE([HAVE_GLPK], [1], [Define to 1 if you have GLPK.])
15.66 + AC_MSG_RESULT([yes])
15.67 + else
15.68 + GLPK_CFLAGS=""
15.69 + GLPK_LDFLAGS=""
15.70 + GLPK_LIBS=""
15.71 + AC_MSG_RESULT([no])
15.72 + fi
15.73 + fi
15.74 + GLPK_LIBS="$GLPK_LDFLAGS $GLPK_LIBS"
15.75 + AC_SUBST(GLPK_CFLAGS)
15.76 + AC_SUBST(GLPK_LIBS)
15.77 + AM_CONDITIONAL([HAVE_GLPK], [test x"$lx_glpk_found" = x"yes"])
15.78 +])
16.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
16.2 +++ b/m4/lx_check_soplex.m4 Tue Dec 18 10:56:09 2007 +0100
16.3 @@ -0,0 +1,71 @@
16.4 +AC_DEFUN([LX_CHECK_SOPLEX],
16.5 +[
16.6 + AC_ARG_WITH([soplex],
16.7 +AS_HELP_STRING([--with-soplex@<:@=PREFIX@:>@], [search for SOPLEX under PREFIX or under the default search paths if PREFIX is not given @<:@default@:>@])
16.8 +AS_HELP_STRING([--without-soplex], [disable checking for SOPLEX]),
16.9 + [], [with_soplex=yes])
16.10 +
16.11 + AC_ARG_WITH([soplex-includedir],
16.12 +AS_HELP_STRING([--with-soplex-includedir=DIR], [search for SOPLEX headers in DIR]),
16.13 + [], [with_soplex_includedir=no])
16.14 +
16.15 + AC_ARG_WITH([soplex-libdir],
16.16 +AS_HELP_STRING([--with-soplex-libdir=DIR], [search for SOPLEX libraries in DIR]),
16.17 + [], [with_soplex_libdir=no])
16.18 +
16.19 + lx_soplex_found=no
16.20 + if test x"$with_soplex" != x"no"; then
16.21 + AC_MSG_CHECKING([for SOPLEX])
16.22 +
16.23 + if test x"$with_soplex_includedir" != x"no"; then
16.24 + SOPLEX_CXXFLAGS="-I$with_soplex_includedir"
16.25 + elif test x"$with_soplex" != x"yes"; then
16.26 + SOPLEX_CXXFLAGS="-I$with_soplex/include"
16.27 + fi
16.28 +
16.29 + if test x"$with_soplex_libdir" != x"no"; then
16.30 + SOPLEX_LDFLAGS="-L$with_soplex_libdir"
16.31 + elif test x"$with_soplex" != x"yes"; then
16.32 + SOPLEX_LDFLAGS="-L$with_soplex/lib"
16.33 + fi
16.34 + SOPLEX_LIBS="-lsoplex -lz"
16.35 +
16.36 + lx_save_cxxflags="$CXXFLAGS"
16.37 + lx_save_ldflags="$LDFLAGS"
16.38 + lx_save_libs="$LIBS"
16.39 + CXXFLAGS="$SOPLEX_CXXFLAGS"
16.40 + LDFLAGS="$SOPLEX_LDFLAGS"
16.41 + LIBS="$SOPLEX_LIBS"
16.42 +
16.43 + lx_soplex_test_prog='
16.44 + #include <soplex/soplex.h>
16.45 +
16.46 + int main(int argc, char* argv[])
16.47 + {
16.48 + soplex::SoPlex soplex;
16.49 + return 0;
16.50 + }'
16.51 +
16.52 + AC_LANG_PUSH(C++)
16.53 + AC_LINK_IFELSE([$lx_soplex_test_prog], [lx_soplex_found=yes], [lx_soplex_found=no])
16.54 + AC_LANG_POP(C++)
16.55 +
16.56 + CXXFLAGS="$lx_save_cxxflags"
16.57 + LDFLAGS="$lx_save_ldflags"
16.58 + LIBS="$lx_save_libs"
16.59 +
16.60 + if test x"$lx_soplex_found" = x"yes"; then
16.61 + AC_DEFINE([HAVE_SOPLEX], [1], [Define to 1 if you have SOPLEX.])
16.62 + AC_MSG_RESULT([yes])
16.63 + else
16.64 + SOPLEX_CXXFLAGS=""
16.65 + SOPLEX_LDFLAGS=""
16.66 + SOPLEX_LIBS=""
16.67 + AC_MSG_RESULT([no])
16.68 + fi
16.69 + fi
16.70 + SOPLEX_LIBS="$SOPLEX_LDFLAGS $SOPLEX_LIBS"
16.71 + AC_SUBST(SOPLEX_CXXFLAGS)
16.72 + AC_SUBST(SOPLEX_LIBS)
16.73 + AM_CONDITIONAL([HAVE_SOPLEX], [test x"$lx_soplex_found" = x"yes"])
16.74 +])
17.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
17.2 +++ b/test/Makefile Tue Dec 18 10:56:09 2007 +0100
17.3 @@ -0,0 +1,2 @@
17.4 +all:
17.5 + $(MAKE) -C ..
18.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
18.2 +++ b/test/Makefile.am Tue Dec 18 10:56:09 2007 +0100
18.3 @@ -0,0 +1,9 @@
18.4 +EXTRA_DIST += \
18.5 + test/Makefile
18.6 +
18.7 +noinst_HEADERS +=
18.8 +
18.9 +check_PROGRAMS +=
18.10 +
18.11 +TESTS += $(check_PROGRAMS)
18.12 +XFAIL_TESTS += test/test_tools_fail$(EXEEXT)
19.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
19.2 +++ b/tools/Makefile Tue Dec 18 10:56:09 2007 +0100
19.3 @@ -0,0 +1,2 @@
19.4 +all:
19.5 + $(MAKE) -C ..
20.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
20.2 +++ b/tools/Makefile.am Tue Dec 18 10:56:09 2007 +0100
20.3 @@ -0,0 +1,8 @@
20.4 +EXTRA_DIST += \
20.5 + tools/Makefile
20.6 +
20.7 +if WANT_TOOLS
20.8 +
20.9 +bin_PROGRAMS +=
20.10 +
20.11 +endif WANT_TOOLS