Subversion Repositories gelsvn

# EXCLUDE                = "../TextureVolume/TrackBall.h"

# EXCLUDE = "../TextureVolume/Neighbours.h"

# EXCLUDE = "../TextureVolume/MarchingCubes.h"

#---------------------------------------------------------------------------

# configuration options related to the HTML output

#---------------------------------------------------------------------------

# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 

# generate HTML output. 

GENERATE_HTML          = YES

# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 

# If a relative path is entered the value of OUTPUT_DIRECTORY will be 

# put in front of it. If left blank `html' will be used as the default path. 

HTML_OUTPUT            = html

# The HTML_HEADER tag can be used to specify a personal HTML header for 

# each generated HTML page. If it is left blank doxygen will generate a 

# standard header.

HTML_HEADER            = 

# The HTML_FOOTER tag can be used to specify a personal HTML footer for 

# each generated HTML page. If it is left blank doxygen will generate a 

# standard footer.

HTML_FOOTER            = 

# The HTML_STYLESHEET tag can be used to specify a user defined cascading 

# style sheet that is used by each HTML page. It can be used to 

# fine-tune the look of the HTML output. If the tag is left blank doxygen 

# will generate a default style sheet 

HTML_STYLESHEET        = 

# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 

# files or namespaces will be aligned in HTML using tables. If set to 

# NO a bullet list will be used. 

HTML_ALIGN_MEMBERS     = YES

# If the GENERATE_HTMLHELP tag is set to YES, additional index files 

# will be generated that can be used as input for tools like the 

# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 

# of the generated HTML documentation. 

GENERATE_HTMLHELP      = NO

# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 

# controls if a separate .chi index file is generated (YES) or that 

# it should be included in the master .chm file (NO).

GENERATE_CHI           = NO

# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 

# controls whether a binary table of contents is generated (YES) or a 

# normal table of contents (NO) in the .chm file.

BINARY_TOC             = NO

# The TOC_EXPAND flag can be set YES to add extra items for group members 

# to the contents of the Html help documentation and to the tree view. 

TOC_EXPAND             = NO

# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 

# top of each HTML page. The value NO (the default) enables the index and 

# the value YES disables it. 

DISABLE_INDEX          = YES

# This tag can be used to set the number of enum values (range [1..20]) 

# that doxygen will group on one line in the generated HTML documentation. 

ENUM_VALUES_PER_LINE   = 4

# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be

# generated containing a tree-like index structure (just like the one that 

# is generated for HTML Help). For this to work a browser that supports 

# JavaScript and frames is required (for instance Netscape 4.0+ 

# or Internet explorer 4.0+). 

GENERATE_TREEVIEW      = NO

# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 

# used to set the initial width (in pixels) of the frame in which the tree 

# is shown. 

TREEVIEW_WIDTH         = 250

#---------------------------------------------------------------------------

# configuration options related to the LaTeX output

#---------------------------------------------------------------------------

# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 

# The RTF output is optimised for Word 97 and may not look very pretty with 

# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 

# If a relative path is entered the value of OUTPUT_DIRECTORY will be 

# put in front of it. If left blank `rtf' will be used as the default path. 

RTF_OUTPUT             = rtf

# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 

# RTF documents. This may be useful for small projects and may help to 

# save some trees in general. 

COMPACT_RTF            = NO

# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 

# will contain hyperlink fields. The RTF file will 

# contain links (just like the HTML output) instead of page references. 

# This makes the output suitable for online browsing using a WORD or other. 

# programs which support those fields. 

# Note: wordpad (write) and others do not support links. 

RTF_HYPERLINKS         = NO

# Load stylesheet definitions from file. Syntax is similar to doxygen's 

# config file, i.e. a series of assigments. You only have to provide 

# replacements, missing definitions are set to their default value. 

RTF_STYLESHEET_FILE    = 

#---------------------------------------------------------------------------

# configuration options related to the man page output

#---------------------------------------------------------------------------

# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 

# generate man pages 

# The MAN_OUTPUT tag is used to specify where the man pages will be put. 

# If a relative path is entered the value of OUTPUT_DIRECTORY will be 

# put in front of it. If left blank `man' will be used as the default path. 

MAN_OUTPUT             = man

# The MAN_EXTENSION tag determines the extension that is added to 

# the generated man pages (default is the subroutine's section .3) 

MAN_EXTENSION          = .3

#---------------------------------------------------------------------------

# Configuration options related to the preprocessor   

#---------------------------------------------------------------------------

# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 

# evaluate all C-preprocessor directives found in the sources and include 

# files. 

ENABLE_PREPROCESSING   = YES

# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 

# names in the source code. If set to NO (the default) only conditional 

# compilation will be performed. Macro expansion can be done in a controlled 

# way by setting EXPAND_ONLY_PREDEF to YES. 

MACRO_EXPANSION        = NO

# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 

# then the macro expansion is limited to the macros specified with the 

# PREDEFINED and EXPAND_AS_PREDEFINED tags. 

EXPAND_ONLY_PREDEF     = NO

# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 

# in the INCLUDE_PATH (see below) will be search if a #include is found. 

SEARCH_INCLUDES        = YES

# The INCLUDE_PATH tag can be used to specify one or more directories that 

# contain include files that are not input files but should be processed by 

# the preprocessor. 

INCLUDE_PATH           = 

# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 

# patterns (like *.h and *.hpp) to filter out the header-files in the 

# directories. If left blank, the patterns specified with FILE_PATTERNS will 

# be used. 

INCLUDE_FILE_PATTERNS  = 

# The PREDEFINED tag can be used to specify one or more macro names that 

# are defined before the preprocessor is started (similar to the -D option of 

# gcc). The argument of the tag is a list of macros of the form: name 

# or name=definition (no spaces). If the definition and the = are 

# omitted =1 is assumed. 

PREDEFINED             = 

# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then 

# this tag can be used to specify a list of macro names that should be expanded. 

# The macro definition that is found in the sources will be used. 

# Use the PREDEFINED tag if you want to use a different macro definition. 

EXPAND_AS_DEFINED      = 

#---------------------------------------------------------------------------

# Configuration::addtions related to external references   

#---------------------------------------------------------------------------

# The TAGFILES tag can be used to specify one or more tagfiles. 

TAGFILES               = 

# When a file name is specified after GENERATE_TAGFILE, doxygen will create 

# a tag file that is based on the input files it reads. 

GENERATE_TAGFILE       = 

# If the ALLEXTERNALS tag is set to YES all external classes will be listed 

# in the class index. If set to NO only the inherited external classes 

# will be listed. 

ALLEXTERNALS           = NO

# The PERL_PATH should be the absolute path and name of the perl script 

# interpreter (i.e. the result of `which perl'). 

PERL_PATH              = /usr/bin/perl

#---------------------------------------------------------------------------

# Configuration options related to the dot tool   

#---------------------------------------------------------------------------

# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 

# available from the path. This tool is part of Graphviz, a graph visualization 

# toolkit from AT&T and Lucent Bell Labs. The other options in this section 

# have no effect if this option is set to NO (the default) 

# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 

# will generate a graph for each documented class showing the direct and 

# indirect inheritance relations. Setting this tag to YES will force the 

# the CLASS_DIAGRAMS tag to NO.

CLASS_GRAPH            = YES

# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 

# will generate a graph for each documented class showing the direct and 

# indirect implementation dependencies (inheritance, containment, and 

# class references variables) of the class with other documented classes. 

COLLABORATION_GRAPH    = YES

# If the ENABLE_PREPROCESSING, INCLUDE_GRAPH, and HAVE_DOT tags are set to 

# YES then doxygen will generate a graph for each documented file showing 

# the direct and indirect include dependencies of the file with other 

# documented files. 

INCLUDE_GRAPH          = YES

# If the ENABLE_PREPROCESSING, INCLUDED_BY_GRAPH, and HAVE_DOT tags are set to 

# YES then doxygen will generate a graph for each documented header file showing 

# the documented files that directly or indirectly include this file 

INCLUDED_BY_GRAPH      = YES

# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 

# will graphical hierarchy of all classes instead of a textual one. 

GRAPHICAL_HIERARCHY    = YES

# The tag DOT_PATH can be used to specify the path where the dot tool can be 

# found. If left blank, it is assumed the dot tool can be found on the path. 

DOT_PATH               = 

# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 

# (in pixels) of the graphs generated by dot. If a graph becomes larger than 

# this value, doxygen will try to truncate the graph, so that it fits within 

# the specified constraint. Beware that most browsers cannot cope with very 

# large images. 

MAX_DOT_GRAPH_WIDTH    = 1024

# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 

# (in pixels) of the graphs generated by dot. If a graph becomes larger than 

# this value, doxygen will try to truncate the graph, so that it fits within 

# the specified constraint. Beware that most browsers cannot cope with very 

# large images. 

MAX_DOT_GRAPH_HEIGHT   = 1024

# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 

# generate a legend page explaining the meaning of the various boxes and 

# arrows in the dot generated graphs. 

GENERATE_LEGEND        = YES

# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 

# remove the intermedate dot files that are used to generate 

# the various graphs. 

DOT_CLEANUP            = YES

#---------------------------------------------------------------------------

# Configuration::addtions related to the search engine   

#---------------------------------------------------------------------------

# The SEARCHENGINE tag specifies whether or not a search engine should be 

# used. If set to NO the values of all tags below this one will be ignored. 

# The CGI_NAME tag should be the name of the CGI script that 

# starts the search engine (doxysearch) with the correct parameters. 

# A script with this name will be generated by doxygen. 

CGI_NAME               = search.cgi

# The CGI_URL tag should be the absolute URL to the directory where the 

# cgi binaries are located. See the documentation of your http daemon for 

# details. 

CGI_URL                = 

# The DOC_URL tag should be the absolute URL to the directory where the 

# documentation is located. If left blank the absolute path to the 

# documentation, with file:// prepended to it, will be used. 

DOC_URL                = 

# The DOC_ABSPATH tag should be the absolute path to the directory where the 

# documentation is located. If left blank the directory on the local machine 

# will be used. 

DOC_ABSPATH            = 

# The BIN_ABSPATH tag must point to the directory where the doxysearch binary 

# is installed. 

BIN_ABSPATH            = /usr/local/bin/

# The EXT_DOC_PATHS tag can be used to specify one or more paths to 

# documentation generated for other projects. This allows doxysearch to search 

# the documentation for these projects as well. 

EXT_DOC_PATHS          =