Chris@719: # Doxyfile 1.4.4
Chris@719: 
Chris@719: # This file describes the settings to be used by the documentation system
Chris@719: # doxygen (www.doxygen.org) for a project
Chris@719: #
Chris@719: # All text after a hash (#) is considered a comment and will be ignored
Chris@719: # The format is:
Chris@719: #       TAG = value [value, ...]
Chris@719: # For lists items can also be appended using:
Chris@719: #       TAG += value [value, ...]
Chris@719: # Values that contain spaces should be placed between quotes (" ")
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Project related configuration options
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
Chris@719: # by quotes) that should identify the project.
Chris@719: 
Chris@719: PROJECT_NAME           = svcore
Chris@719: 
Chris@719: # The PROJECT_NUMBER tag can be used to enter a project or revision number.
Chris@719: # This could be handy for archiving the generated documentation or
Chris@719: # if some version control system is used.
Chris@719: 
Chris@719: PROJECT_NUMBER         = 1.9
Chris@719: 
Chris@719: # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
Chris@719: # base path where the generated documentation will be put.
Chris@719: # If a relative path is entered, it will be relative to the location
Chris@719: # where doxygen was started. If left blank the current directory will be used.
Chris@719: 
Chris@719: OUTPUT_DIRECTORY       = doc
Chris@719: 
Chris@719: # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
Chris@719: # 4096 sub-directories (in 2 levels) under the output directory of each output
Chris@719: # format and will distribute the generated files over these directories.
Chris@719: # Enabling this option can be useful when feeding doxygen a huge amount of
Chris@719: # source files, where putting all generated files in the same directory would
Chris@719: # otherwise cause performance problems for the file system.
Chris@719: 
Chris@719: CREATE_SUBDIRS         = NO
Chris@719: 
Chris@719: # The OUTPUT_LANGUAGE tag is used to specify the language in which all
Chris@719: # documentation generated by doxygen is written. Doxygen will use this
Chris@719: # information to generate all constant output in the proper language.
Chris@719: # The default language is English, other supported languages are:
Chris@719: # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
Chris@719: # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
Chris@719: # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
Chris@719: # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
Chris@719: # Swedish, and Ukrainian.
Chris@719: 
Chris@719: OUTPUT_LANGUAGE        = English
Chris@719: 
Chris@719: # This tag can be used to specify the encoding used in the generated output.
Chris@719: # The encoding is not always determined by the language that is chosen,
Chris@719: # but also whether or not the output is meant for Windows or non-Windows users.
Chris@719: # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
Chris@719: # forces the Windows encoding (this is the default for the Windows binary),
Chris@719: # whereas setting the tag to NO uses a Unix-style encoding (the default for
Chris@719: # all platforms other than Windows).
Chris@719: 
Chris@719: USE_WINDOWS_ENCODING   = NO
Chris@719: 
Chris@719: # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
Chris@719: # include brief member descriptions after the members that are listed in
Chris@719: # the file and class documentation (similar to JavaDoc).
Chris@719: # Set to NO to disable this.
Chris@719: 
Chris@719: BRIEF_MEMBER_DESC      = YES
Chris@719: 
Chris@719: # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
Chris@719: # the brief description of a member or function before the detailed description.
Chris@719: # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
Chris@719: # brief descriptions will be completely suppressed.
Chris@719: 
Chris@719: REPEAT_BRIEF           = YES
Chris@719: 
Chris@719: # This tag implements a quasi-intelligent brief description abbreviator
Chris@719: # that is used to form the text in various listings. Each string
Chris@719: # in this list, if found as the leading text of the brief description, will be
Chris@719: # stripped from the text and the result after processing the whole list, is
Chris@719: # used as the annotated text. Otherwise, the brief description is used as-is.
Chris@719: # If left blank, the following values are used ("$name" is automatically
Chris@719: # replaced with the name of the entity): "The $name class" "The $name widget"
Chris@719: # "The $name file" "is" "provides" "specifies" "contains"
Chris@719: # "represents" "a" "an" "the"
Chris@719: 
Chris@719: ABBREVIATE_BRIEF       =
Chris@719: 
Chris@719: # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
Chris@719: # Doxygen will generate a detailed section even if there is only a brief
Chris@719: # description.
Chris@719: 
Chris@719: ALWAYS_DETAILED_SEC    = NO
Chris@719: 
Chris@719: # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
Chris@719: # inherited members of a class in the documentation of that class as if those
Chris@719: # members were ordinary class members. Constructors, destructors and assignment
Chris@719: # operators of the base classes will not be shown.
Chris@719: 
Chris@719: INLINE_INHERITED_MEMB  = YES
Chris@719: 
Chris@719: # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
Chris@719: # path before files name in the file list and in the header files. If set
Chris@719: # to NO the shortest path that makes the file name unique will be used
Chris@719: 
Chris@719: FULL_PATH_NAMES        = NO
Chris@719: 
Chris@719: # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
Chris@719: # can be used to strip a user-defined part of the path. Stripping is
Chris@719: # only done if one of the specified strings matches the left-hand part of
Chris@719: # the path. The tag can be used to show relative paths in the file list.
Chris@719: # If left blank the directory from which doxygen is run is used as the
Chris@719: # path to strip.
Chris@719: 
Chris@719: STRIP_FROM_PATH        =
Chris@719: 
Chris@719: # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
Chris@719: # the path mentioned in the documentation of a class, which tells
Chris@719: # the reader which header file to include in order to use a class.
Chris@719: # If left blank only the name of the header file containing the class
Chris@719: # definition is used. Otherwise one should specify the include paths that
Chris@719: # are normally passed to the compiler using the -I flag.
Chris@719: 
Chris@719: STRIP_FROM_INC_PATH    =
Chris@719: 
Chris@719: # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
Chris@719: # (but less readable) file names. This can be useful is your file systems
Chris@719: # doesn't support long names like on DOS, Mac, or CD-ROM.
Chris@719: 
Chris@719: SHORT_NAMES            = NO
Chris@719: 
Chris@719: # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
Chris@719: # will interpret the first line (until the first dot) of a JavaDoc-style
Chris@719: # comment as the brief description. If set to NO, the JavaDoc
Chris@719: # comments will behave just like the Qt-style comments (thus requiring an
Chris@719: # explicit @brief command for a brief description.
Chris@719: 
Chris@719: JAVADOC_AUTOBRIEF      = YES
Chris@719: 
Chris@719: # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
Chris@719: # treat a multi-line C++ special comment block (i.e. a block of //! or ///
Chris@719: # comments) as a brief description. This used to be the default behaviour.
Chris@719: # The new default is to treat a multi-line C++ comment block as a detailed
Chris@719: # description. Set this tag to YES if you prefer the old behaviour instead.
Chris@719: 
Chris@719: MULTILINE_CPP_IS_BRIEF = NO
Chris@719: 
Chris@719: # If the DETAILS_AT_TOP tag is set to YES then Doxygen
Chris@719: # will output the detailed description near the top, like JavaDoc.
Chris@719: # If set to NO, the detailed description appears after the member
Chris@719: # documentation.
Chris@719: 
Chris@719: DETAILS_AT_TOP         = YES
Chris@719: 
Chris@719: # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
Chris@719: # member inherits the documentation from any documented member that it
Chris@719: # re-implements.
Chris@719: 
Chris@719: INHERIT_DOCS           = YES
Chris@719: 
Chris@719: # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
Chris@719: # tag is set to YES, then doxygen will reuse the documentation of the first
Chris@719: # member in the group (if any) for the other members of the group. By default
Chris@719: # all members of a group must be documented explicitly.
Chris@719: 
Chris@719: DISTRIBUTE_GROUP_DOC   = NO
Chris@719: 
Chris@719: # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
Chris@719: # a new page for each member. If set to NO, the documentation of a member will
Chris@719: # be part of the file/class/namespace that contains it.
Chris@719: 
Chris@719: SEPARATE_MEMBER_PAGES  = NO
Chris@719: 
Chris@719: # The TAB_SIZE tag can be used to set the number of spaces in a tab.
Chris@719: # Doxygen uses this value to replace tabs by spaces in code fragments.
Chris@719: 
Chris@719: TAB_SIZE               = 8
Chris@719: 
Chris@719: # This tag can be used to specify a number of aliases that acts
Chris@719: # as commands in the documentation. An alias has the form "name=value".
Chris@719: # For example adding "sideeffect=\par Side Effects:\n" will allow you to
Chris@719: # put the command \sideeffect (or @sideeffect) in the documentation, which
Chris@719: # will result in a user-defined paragraph with heading "Side Effects:".
Chris@719: # You can put \n's in the value part of an alias to insert newlines.
Chris@719: 
Chris@719: ALIASES                =
Chris@719: 
Chris@719: # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
Chris@719: # sources only. Doxygen will then generate output that is more tailored for C.
Chris@719: # For instance, some of the names that are used will be different. The list
Chris@719: # of all members will be omitted, etc.
Chris@719: 
Chris@719: OPTIMIZE_OUTPUT_FOR_C  = NO
Chris@719: 
Chris@719: # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
Chris@719: # only. Doxygen will then generate output that is more tailored for Java.
Chris@719: # For instance, namespaces will be presented as packages, qualified scopes
Chris@719: # will look different, etc.
Chris@719: 
Chris@719: OPTIMIZE_OUTPUT_JAVA   = NO
Chris@719: 
Chris@719: # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
Chris@719: # the same type (for instance a group of public functions) to be put as a
Chris@719: # subgroup of that type (e.g. under the Public Functions section). Set it to
Chris@719: # NO to prevent subgrouping. Alternatively, this can be done per class using
Chris@719: # the \nosubgrouping command.
Chris@719: 
Chris@719: SUBGROUPING            = YES
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Build related configuration options
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
Chris@719: # documentation are documented, even if no documentation was available.
Chris@719: # Private class members and static file members will be hidden unless
Chris@719: # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
Chris@719: 
Chris@719: EXTRACT_ALL            = YES
Chris@719: 
Chris@719: # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
Chris@719: # will be included in the documentation.
Chris@719: 
Chris@719: EXTRACT_PRIVATE        = YES
Chris@719: 
Chris@719: # If the EXTRACT_STATIC tag is set to YES all static members of a file
Chris@719: # will be included in the documentation.
Chris@719: 
Chris@719: EXTRACT_STATIC         = YES
Chris@719: 
Chris@719: # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
Chris@719: # defined locally in source files will be included in the documentation.
Chris@719: # If set to NO only classes defined in header files are included.
Chris@719: 
Chris@719: EXTRACT_LOCAL_CLASSES  = YES
Chris@719: 
Chris@719: # This flag is only useful for Objective-C code. When set to YES local
Chris@719: # methods, which are defined in the implementation section but not in
Chris@719: # the interface are included in the documentation.
Chris@719: # If set to NO (the default) only methods in the interface are included.
Chris@719: 
Chris@719: EXTRACT_LOCAL_METHODS  = NO
Chris@719: 
Chris@719: # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
Chris@719: # undocumented members of documented classes, files or namespaces.
Chris@719: # If set to NO (the default) these members will be included in the
Chris@719: # various overviews, but no documentation section is generated.
Chris@719: # This option has no effect if EXTRACT_ALL is enabled.
Chris@719: 
Chris@719: HIDE_UNDOC_MEMBERS     = NO
Chris@719: 
Chris@719: # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
Chris@719: # undocumented classes that are normally visible in the class hierarchy.
Chris@719: # If set to NO (the default) these classes will be included in the various
Chris@719: # overviews. This option has no effect if EXTRACT_ALL is enabled.
Chris@719: 
Chris@719: HIDE_UNDOC_CLASSES     = NO
Chris@719: 
Chris@719: # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
Chris@719: # friend (class|struct|union) declarations.
Chris@719: # If set to NO (the default) these declarations will be included in the
Chris@719: # documentation.
Chris@719: 
Chris@719: HIDE_FRIEND_COMPOUNDS  = NO
Chris@719: 
Chris@719: # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
Chris@719: # documentation blocks found inside the body of a function.
Chris@719: # If set to NO (the default) these blocks will be appended to the
Chris@719: # function's detailed documentation block.
Chris@719: 
Chris@719: HIDE_IN_BODY_DOCS      = NO
Chris@719: 
Chris@719: # The INTERNAL_DOCS tag determines if documentation
Chris@719: # that is typed after a \internal command is included. If the tag is set
Chris@719: # to NO (the default) then the documentation will be excluded.
Chris@719: # Set it to YES to include the internal documentation.
Chris@719: 
Chris@719: INTERNAL_DOCS          = NO
Chris@719: 
Chris@719: # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
Chris@719: # file names in lower-case letters. If set to YES upper-case letters are also
Chris@719: # allowed. This is useful if you have classes or files whose names only differ
Chris@719: # in case and if your file system supports case sensitive file names. Windows
Chris@719: # and Mac users are advised to set this option to NO.
Chris@719: 
Chris@719: CASE_SENSE_NAMES       = YES
Chris@719: 
Chris@719: # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
Chris@719: # will show members with their full class and namespace scopes in the
Chris@719: # documentation. If set to YES the scope will be hidden.
Chris@719: 
Chris@719: HIDE_SCOPE_NAMES       = NO
Chris@719: 
Chris@719: # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
Chris@719: # will put a list of the files that are included by a file in the documentation
Chris@719: # of that file.
Chris@719: 
Chris@719: SHOW_INCLUDE_FILES     = YES
Chris@719: 
Chris@719: # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
Chris@719: # is inserted in the documentation for inline members.
Chris@719: 
Chris@719: INLINE_INFO            = YES
Chris@719: 
Chris@719: # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
Chris@719: # will sort the (detailed) documentation of file and class members
Chris@719: # alphabetically by member name. If set to NO the members will appear in
Chris@719: # declaration order.
Chris@719: 
Chris@719: SORT_MEMBER_DOCS       = NO
Chris@719: 
Chris@719: # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
Chris@719: # brief documentation of file, namespace and class members alphabetically
Chris@719: # by member name. If set to NO (the default) the members will appear in
Chris@719: # declaration order.
Chris@719: 
Chris@719: SORT_BRIEF_DOCS        = NO
Chris@719: 
Chris@719: # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
Chris@719: # sorted by fully-qualified names, including namespaces. If set to
Chris@719: # NO (the default), the class list will be sorted only by class name,
Chris@719: # not including the namespace part.
Chris@719: # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
Chris@719: # Note: This option applies only to the class list, not to the
Chris@719: # alphabetical list.
Chris@719: 
Chris@719: SORT_BY_SCOPE_NAME     = NO
Chris@719: 
Chris@719: # The GENERATE_TODOLIST tag can be used to enable (YES) or
Chris@719: # disable (NO) the todo list. This list is created by putting \todo
Chris@719: # commands in the documentation.
Chris@719: 
Chris@719: GENERATE_TODOLIST      = YES
Chris@719: 
Chris@719: # The GENERATE_TESTLIST tag can be used to enable (YES) or
Chris@719: # disable (NO) the test list. This list is created by putting \test
Chris@719: # commands in the documentation.
Chris@719: 
Chris@719: GENERATE_TESTLIST      = YES
Chris@719: 
Chris@719: # The GENERATE_BUGLIST tag can be used to enable (YES) or
Chris@719: # disable (NO) the bug list. This list is created by putting \bug
Chris@719: # commands in the documentation.
Chris@719: 
Chris@719: GENERATE_BUGLIST       = YES
Chris@719: 
Chris@719: # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
Chris@719: # disable (NO) the deprecated list. This list is created by putting
Chris@719: # \deprecated commands in the documentation.
Chris@719: 
Chris@719: GENERATE_DEPRECATEDLIST= YES
Chris@719: 
Chris@719: # The ENABLED_SECTIONS tag can be used to enable conditional
Chris@719: # documentation sections, marked by \if sectionname ... \endif.
Chris@719: 
Chris@719: ENABLED_SECTIONS       =
Chris@719: 
Chris@719: # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
Chris@719: # the initial value of a variable or define consists of for it to appear in
Chris@719: # the documentation. If the initializer consists of more lines than specified
Chris@719: # here it will be hidden. Use a value of 0 to hide initializers completely.
Chris@719: # The appearance of the initializer of individual variables and defines in the
Chris@719: # documentation can be controlled using \showinitializer or \hideinitializer
Chris@719: # command in the documentation regardless of this setting.
Chris@719: 
Chris@719: MAX_INITIALIZER_LINES  = 30
Chris@719: 
Chris@719: # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
Chris@719: # at the bottom of the documentation of classes and structs. If set to YES the
Chris@719: # list will mention the files that were used to generate the documentation.
Chris@719: 
Chris@719: SHOW_USED_FILES        = YES
Chris@719: 
Chris@719: # If the sources in your project are distributed over multiple directories
Chris@719: # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
Chris@719: # in the documentation. The default is YES.
Chris@719: 
Chris@719: SHOW_DIRECTORIES       = YES
Chris@719: 
Chris@719: # The FILE_VERSION_FILTER tag can be used to specify a program or script that
Chris@719: # doxygen should invoke to get the current version for each file (typically from the
Chris@719: # version control system). Doxygen will invoke the program by executing (via
Chris@719: # popen()) the command <command> <input-file>, where <command> is the value of
Chris@719: # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
Chris@719: # provided by doxygen. Whatever the progam writes to standard output
Chris@719: # is used as the file version. See the manual for examples.
Chris@719: 
Chris@719: FILE_VERSION_FILTER    =
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to warning and progress messages
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # The QUIET tag can be used to turn on/off the messages that are generated
Chris@719: # by doxygen. Possible values are YES and NO. If left blank NO is used.
Chris@719: 
Chris@719: QUIET                  = NO
Chris@719: 
Chris@719: # The WARNINGS tag can be used to turn on/off the warning messages that are
Chris@719: # generated by doxygen. Possible values are YES and NO. If left blank
Chris@719: # NO is used.
Chris@719: 
Chris@719: WARNINGS               = YES
Chris@719: 
Chris@719: # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
Chris@719: # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
Chris@719: # automatically be disabled.
Chris@719: 
Chris@719: WARN_IF_UNDOCUMENTED   = YES
Chris@719: 
Chris@719: # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
Chris@719: # potential errors in the documentation, such as not documenting some
Chris@719: # parameters in a documented function, or documenting parameters that
Chris@719: # don't exist or using markup commands wrongly.
Chris@719: 
Chris@719: WARN_IF_DOC_ERROR      = YES
Chris@719: 
Chris@719: # This WARN_NO_PARAMDOC option can be abled to get warnings for
Chris@719: # functions that are documented, but have no documentation for their parameters
Chris@719: # or return value. If set to NO (the default) doxygen will only warn about
Chris@719: # wrong or incomplete parameter documentation, but not about the absence of
Chris@719: # documentation.
Chris@719: 
Chris@719: WARN_NO_PARAMDOC       = YES
Chris@719: 
Chris@719: # The WARN_FORMAT tag determines the format of the warning messages that
Chris@719: # doxygen can produce. The string should contain the $file, $line, and $text
Chris@719: # tags, which will be replaced by the file and line number from which the
Chris@719: # warning originated and the warning text. Optionally the format may contain
Chris@719: # $version, which will be replaced by the version of the file (if it could
Chris@719: # be obtained via FILE_VERSION_FILTER)
Chris@719: 
Chris@719: WARN_FORMAT            = "$file:$line: $text"
Chris@719: 
Chris@719: # The WARN_LOGFILE tag can be used to specify a file to which warning
Chris@719: # and error messages should be written. If left blank the output is written
Chris@719: # to stderr.
Chris@719: 
Chris@719: WARN_LOGFILE           = docs/doxygen/warning.log
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the input files
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # The INPUT tag can be used to specify the files and/or directories that contain
Chris@719: # documented source files. You may enter file names like "myfile.cpp" or
Chris@719: # directories like "/usr/src/myproject". Separate the files or directories
Chris@719: # with spaces.
Chris@719: 
Chris@719: INPUT                  = base data/fft data/fileio data/midi data/model data/osc plugin plugin/plugins transform rdf system 
Chris@719: 
Chris@719: # If the value of the INPUT tag contains directories, you can use the
Chris@719: # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
Chris@719: # and *.h) to filter out the source-files in the directories. If left
Chris@719: # blank the following patterns are tested:
Chris@719: # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
Chris@719: # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
Chris@719: 
Chris@719: FILE_PATTERNS          = *.h \
Chris@719:                          *.C \
Chris@719:                          *.cpp \
Chris@719:                          *.cc
Chris@719: 
Chris@719: # The RECURSIVE tag can be used to turn specify whether or not subdirectories
Chris@719: # should be searched for input files as well. Possible values are YES and NO.
Chris@719: # If left blank NO is used.
Chris@719: 
Chris@719: RECURSIVE              = NO
Chris@719: 
Chris@719: # The EXCLUDE tag can be used to specify files and/or directories that should
Chris@719: # excluded from the INPUT source files. This way you can easily exclude a
Chris@719: # subdirectory from a directory tree whose root is specified with the INPUT tag.
Chris@719: 
Chris@719: EXCLUDE                =
Chris@719: 
Chris@719: # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
Chris@719: # directories that are symbolic links (a Unix filesystem feature) are excluded
Chris@719: # from the input.
Chris@719: 
Chris@719: EXCLUDE_SYMLINKS       = NO
Chris@719: 
Chris@719: # If the value of the INPUT tag contains directories, you can use the
Chris@719: # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
Chris@719: # certain files from those directories. Note that the wildcards are matched
Chris@719: # against the file with absolute path, so to exclude all test directories
Chris@719: # for example use the pattern */test/*
Chris@719: 
Chris@719: EXCLUDE_PATTERNS       = qrc_*.cpp \
Chris@719:                          moc_*.cpp \
Chris@719:                          *.moc.cpp \
Chris@719:                          *_skel.cpp
Chris@719: 
Chris@719: # The EXAMPLE_PATH tag can be used to specify one or more files or
Chris@719: # directories that contain example code fragments that are included (see
Chris@719: # the \include command).
Chris@719: 
Chris@719: EXAMPLE_PATH           =
Chris@719: 
Chris@719: # If the value of the EXAMPLE_PATH tag contains directories, you can use the
Chris@719: # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
Chris@719: # and *.h) to filter out the source-files in the directories. If left
Chris@719: # blank all files are included.
Chris@719: 
Chris@719: EXAMPLE_PATTERNS       =
Chris@719: 
Chris@719: # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
Chris@719: # searched for input files to be used with the \include or \dontinclude
Chris@719: # commands irrespective of the value of the RECURSIVE tag.
Chris@719: # Possible values are YES and NO. If left blank NO is used.
Chris@719: 
Chris@719: EXAMPLE_RECURSIVE      = NO
Chris@719: 
Chris@719: # The IMAGE_PATH tag can be used to specify one or more files or
Chris@719: # directories that contain image that are included in the documentation (see
Chris@719: # the \image command).
Chris@719: 
Chris@719: IMAGE_PATH             =
Chris@719: 
Chris@719: # The INPUT_FILTER tag can be used to specify a program that doxygen should
Chris@719: # invoke to filter for each input file. Doxygen will invoke the filter program
Chris@719: # by executing (via popen()) the command <filter> <input-file>, where <filter>
Chris@719: # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
Chris@719: # input file. Doxygen will then use the output that the filter program writes
Chris@719: # to standard output.  If FILTER_PATTERNS is specified, this tag will be
Chris@719: # ignored.
Chris@719: 
Chris@719: INPUT_FILTER           =
Chris@719: 
Chris@719: # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
Chris@719: # basis.  Doxygen will compare the file name with each pattern and apply the
Chris@719: # filter if there is a match.  The filters are a list of the form:
Chris@719: # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
Chris@719: # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
Chris@719: # is applied to all files.
Chris@719: 
Chris@719: FILTER_PATTERNS        =
Chris@719: 
Chris@719: # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
Chris@719: # INPUT_FILTER) will be used to filter the input files when producing source
Chris@719: # files to browse (i.e. when SOURCE_BROWSER is set to YES).
Chris@719: 
Chris@719: FILTER_SOURCE_FILES    = NO
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to source browsing
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the SOURCE_BROWSER tag is set to YES then a list of source files will
Chris@719: # be generated. Documented entities will be cross-referenced with these sources.
Chris@719: # Note: To get rid of all source code in the generated output, make sure also
Chris@719: # VERBATIM_HEADERS is set to NO.
Chris@719: 
Chris@719: SOURCE_BROWSER         = YES
Chris@719: 
Chris@719: # Setting the INLINE_SOURCES tag to YES will include the body
Chris@719: # of functions and classes directly in the documentation.
Chris@719: 
Chris@719: INLINE_SOURCES         = NO
Chris@719: 
Chris@719: # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
Chris@719: # doxygen to hide any special comment blocks from generated source code
Chris@719: # fragments. Normal C and C++ comments will always remain visible.
Chris@719: 
Chris@719: STRIP_CODE_COMMENTS    = YES
Chris@719: 
Chris@719: # If the REFERENCED_BY_RELATION tag is set to YES (the default)
Chris@719: # then for each documented function all documented
Chris@719: # functions referencing it will be listed.
Chris@719: 
Chris@719: REFERENCED_BY_RELATION = YES
Chris@719: 
Chris@719: # If the REFERENCES_RELATION tag is set to YES (the default)
Chris@719: # then for each documented function all documented entities
Chris@719: # called/used by that function will be listed.
Chris@719: 
Chris@719: REFERENCES_RELATION    = YES
Chris@719: 
Chris@719: # If the USE_HTAGS tag is set to YES then the references to source code
Chris@719: # will point to the HTML generated by the htags(1) tool instead of doxygen
Chris@719: # built-in source browser. The htags tool is part of GNU's global source
Chris@719: # tagging system (see http://www.gnu.org/software/global/global.html). You
Chris@719: # will need version 4.8.6 or higher.
Chris@719: 
Chris@719: #USE_HTAGS              = NO
Chris@719: 
Chris@719: # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
Chris@719: # will generate a verbatim copy of the header file for each class for
Chris@719: # which an include is specified. Set to NO to disable this.
Chris@719: 
Chris@719: VERBATIM_HEADERS       = YES
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the alphabetical class index
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
Chris@719: # of all compounds will be generated. Enable this if the project
Chris@719: # contains a lot of classes, structs, unions or interfaces.
Chris@719: 
Chris@719: ALPHABETICAL_INDEX     = YES
Chris@719: 
Chris@719: # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
Chris@719: # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
Chris@719: # in which this list will be split (can be a number in the range [1..20])
Chris@719: 
Chris@719: COLS_IN_ALPHA_INDEX    = 3
Chris@719: 
Chris@719: # In case all classes in a project start with a common prefix, all
Chris@719: # classes will be put under the same header in the alphabetical index.
Chris@719: # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
Chris@719: # should be ignored while generating the index headers.
Chris@719: 
Chris@719: IGNORE_PREFIX          =
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the HTML output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
Chris@719: # generate HTML output.
Chris@719: 
Chris@719: GENERATE_HTML          = YES
Chris@719: 
Chris@719: # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
Chris@719: # If a relative path is entered the value of OUTPUT_DIRECTORY will be
Chris@719: # put in front of it. If left blank `html' will be used as the default path.
Chris@719: 
Chris@719: HTML_OUTPUT            = html
Chris@719: 
Chris@719: # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
Chris@719: # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
Chris@719: # doxygen will generate files with .html extension.
Chris@719: 
Chris@719: HTML_FILE_EXTENSION    = .html
Chris@719: 
Chris@719: # The HTML_HEADER tag can be used to specify a personal HTML header for
Chris@719: # each generated HTML page. If it is left blank doxygen will generate a
Chris@719: # standard header.
Chris@719: 
Chris@719: HTML_HEADER            =
Chris@719: 
Chris@719: # The HTML_FOOTER tag can be used to specify a personal HTML footer for
Chris@719: # each generated HTML page. If it is left blank doxygen will generate a
Chris@719: # standard footer.
Chris@719: 
Chris@719: HTML_FOOTER            =
Chris@719: 
Chris@719: # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
Chris@719: # style sheet that is used by each HTML page. It can be used to
Chris@719: # fine-tune the look of the HTML output. If the tag is left blank doxygen
Chris@719: # will generate a default style sheet. Note that doxygen will try to copy
Chris@719: # the style sheet file to the HTML output directory, so don't put your own
Chris@719: # stylesheet in the HTML output directory as well, or it will be erased!
Chris@719: 
Chris@719: HTML_STYLESHEET        =
Chris@719: 
Chris@719: # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
Chris@719: # files or namespaces will be aligned in HTML using tables. If set to
Chris@719: # NO a bullet list will be used.
Chris@719: 
Chris@719: HTML_ALIGN_MEMBERS     = YES
Chris@719: 
Chris@719: # If the GENERATE_HTMLHELP tag is set to YES, additional index files
Chris@719: # will be generated that can be used as input for tools like the
Chris@719: # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
Chris@719: # of the generated HTML documentation.
Chris@719: 
Chris@719: GENERATE_HTMLHELP      = NO
Chris@719: 
Chris@719: # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
Chris@719: # be used to specify the file name of the resulting .chm file. You
Chris@719: # can add a path in front of the file if the result should not be
Chris@719: # written to the html output directory.
Chris@719: 
Chris@719: CHM_FILE               =
Chris@719: 
Chris@719: # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
Chris@719: # be used to specify the location (absolute path including file name) of
Chris@719: # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
Chris@719: # the HTML help compiler on the generated index.hhp.
Chris@719: 
Chris@719: HHC_LOCATION           =
Chris@719: 
Chris@719: # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
Chris@719: # controls if a separate .chi index file is generated (YES) or that
Chris@719: # it should be included in the master .chm file (NO).
Chris@719: 
Chris@719: GENERATE_CHI           = NO
Chris@719: 
Chris@719: # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
Chris@719: # controls whether a binary table of contents is generated (YES) or a
Chris@719: # normal table of contents (NO) in the .chm file.
Chris@719: 
Chris@719: BINARY_TOC             = NO
Chris@719: 
Chris@719: # The TOC_EXPAND flag can be set to YES to add extra items for group members
Chris@719: # to the contents of the HTML help documentation and to the tree view.
Chris@719: 
Chris@719: TOC_EXPAND             = NO
Chris@719: 
Chris@719: # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
Chris@719: # top of each HTML page. The value NO (the default) enables the index and
Chris@719: # the value YES disables it.
Chris@719: 
Chris@719: DISABLE_INDEX          = NO
Chris@719: 
Chris@719: # This tag can be used to set the number of enum values (range [1..20])
Chris@719: # that doxygen will group on one line in the generated HTML documentation.
Chris@719: 
Chris@719: ENUM_VALUES_PER_LINE   = 4
Chris@719: 
Chris@719: # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
Chris@719: # generated containing a tree-like index structure (just like the one that
Chris@719: # is generated for HTML Help). For this to work a browser that supports
Chris@719: # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
Chris@719: # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
Chris@719: # probably better off using the HTML help feature.
Chris@719: 
Chris@719: GENERATE_TREEVIEW      = YES
Chris@719: 
Chris@719: # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
Chris@719: # used to set the initial width (in pixels) of the frame in which the tree
Chris@719: # is shown.
Chris@719: 
Chris@719: TREEVIEW_WIDTH         = 250
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the LaTeX output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
Chris@719: # generate Latex output.
Chris@719: 
Chris@719: GENERATE_LATEX         = NO
Chris@719: 
Chris@719: # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
Chris@719: # If a relative path is entered the value of OUTPUT_DIRECTORY will be
Chris@719: # put in front of it. If left blank `latex' will be used as the default path.
Chris@719: 
Chris@719: LATEX_OUTPUT           = latex
Chris@719: 
Chris@719: # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
Chris@719: # invoked. If left blank `latex' will be used as the default command name.
Chris@719: 
Chris@719: LATEX_CMD_NAME         = latex
Chris@719: 
Chris@719: # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
Chris@719: # generate index for LaTeX. If left blank `makeindex' will be used as the
Chris@719: # default command name.
Chris@719: 
Chris@719: MAKEINDEX_CMD_NAME     = makeindex
Chris@719: 
Chris@719: # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
Chris@719: # LaTeX documents. This may be useful for small projects and may help to
Chris@719: # save some trees in general.
Chris@719: 
Chris@719: COMPACT_LATEX          = NO
Chris@719: 
Chris@719: # The PAPER_TYPE tag can be used to set the paper type that is used
Chris@719: # by the printer. Possible values are: a4, a4wide, letter, legal and
Chris@719: # executive. If left blank a4wide will be used.
Chris@719: 
Chris@719: PAPER_TYPE             = a4wide
Chris@719: 
Chris@719: # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
Chris@719: # packages that should be included in the LaTeX output.
Chris@719: 
Chris@719: EXTRA_PACKAGES         =
Chris@719: 
Chris@719: # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
Chris@719: # the generated latex document. The header should contain everything until
Chris@719: # the first chapter. If it is left blank doxygen will generate a
Chris@719: # standard header. Notice: only use this tag if you know what you are doing!
Chris@719: 
Chris@719: LATEX_HEADER           =
Chris@719: 
Chris@719: # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
Chris@719: # is prepared for conversion to pdf (using ps2pdf). The pdf file will
Chris@719: # contain links (just like the HTML output) instead of page references
Chris@719: # This makes the output suitable for online browsing using a pdf viewer.
Chris@719: 
Chris@719: PDF_HYPERLINKS         = NO
Chris@719: 
Chris@719: # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
Chris@719: # plain latex in the generated Makefile. Set this option to YES to get a
Chris@719: # higher quality PDF documentation.
Chris@719: 
Chris@719: USE_PDFLATEX           = NO
Chris@719: 
Chris@719: # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
Chris@719: # command to the generated LaTeX files. This will instruct LaTeX to keep
Chris@719: # running if errors occur, instead of asking the user for help.
Chris@719: # This option is also used when generating formulas in HTML.
Chris@719: 
Chris@719: LATEX_BATCHMODE        = NO
Chris@719: 
Chris@719: # If LATEX_HIDE_INDICES is set to YES then doxygen will not
Chris@719: # include the index chapters (such as File Index, Compound Index, etc.)
Chris@719: # in the output.
Chris@719: 
Chris@719: LATEX_HIDE_INDICES     = NO
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the RTF output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
Chris@719: # The RTF output is optimized for Word 97 and may not look very pretty with
Chris@719: # other RTF readers or editors.
Chris@719: 
Chris@719: GENERATE_RTF           = NO
Chris@719: 
Chris@719: # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
Chris@719: # If a relative path is entered the value of OUTPUT_DIRECTORY will be
Chris@719: # put in front of it. If left blank `rtf' will be used as the default path.
Chris@719: 
Chris@719: RTF_OUTPUT             = rtf
Chris@719: 
Chris@719: # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
Chris@719: # RTF documents. This may be useful for small projects and may help to
Chris@719: # save some trees in general.
Chris@719: 
Chris@719: COMPACT_RTF            = NO
Chris@719: 
Chris@719: # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
Chris@719: # will contain hyperlink fields. The RTF file will
Chris@719: # contain links (just like the HTML output) instead of page references.
Chris@719: # This makes the output suitable for online browsing using WORD or other
Chris@719: # programs which support those fields.
Chris@719: # Note: wordpad (write) and others do not support links.
Chris@719: 
Chris@719: RTF_HYPERLINKS         = NO
Chris@719: 
Chris@719: # Load stylesheet definitions from file. Syntax is similar to doxygen's
Chris@719: # config file, i.e. a series of assignments. You only have to provide
Chris@719: # replacements, missing definitions are set to their default value.
Chris@719: 
Chris@719: RTF_STYLESHEET_FILE    =
Chris@719: 
Chris@719: # Set optional variables used in the generation of an rtf document.
Chris@719: # Syntax is similar to doxygen's config file.
Chris@719: 
Chris@719: RTF_EXTENSIONS_FILE    =
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the man page output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
Chris@719: # generate man pages
Chris@719: 
Chris@719: GENERATE_MAN           = NO
Chris@719: 
Chris@719: # The MAN_OUTPUT tag is used to specify where the man pages will be put.
Chris@719: # If a relative path is entered the value of OUTPUT_DIRECTORY will be
Chris@719: # put in front of it. If left blank `man' will be used as the default path.
Chris@719: 
Chris@719: MAN_OUTPUT             = man
Chris@719: 
Chris@719: # The MAN_EXTENSION tag determines the extension that is added to
Chris@719: # the generated man pages (default is the subroutine's section .3)
Chris@719: 
Chris@719: MAN_EXTENSION          = .3
Chris@719: 
Chris@719: # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
Chris@719: # then it will generate one additional man file for each entity
Chris@719: # documented in the real man page(s). These additional files
Chris@719: # only source the real man page, but without them the man command
Chris@719: # would be unable to find the correct page. The default is NO.
Chris@719: 
Chris@719: MAN_LINKS              = NO
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the XML output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_XML tag is set to YES Doxygen will
Chris@719: # generate an XML file that captures the structure of
Chris@719: # the code including all documentation.
Chris@719: 
Chris@719: GENERATE_XML           = NO
Chris@719: 
Chris@719: # The XML_OUTPUT tag is used to specify where the XML pages will be put.
Chris@719: # If a relative path is entered the value of OUTPUT_DIRECTORY will be
Chris@719: # put in front of it. If left blank `xml' will be used as the default path.
Chris@719: 
Chris@719: XML_OUTPUT             = xml
Chris@719: 
Chris@719: # The XML_SCHEMA tag can be used to specify an XML schema,
Chris@719: # which can be used by a validating XML parser to check the
Chris@719: # syntax of the XML files.
Chris@719: 
Chris@719: XML_SCHEMA             =
Chris@719: 
Chris@719: # The XML_DTD tag can be used to specify an XML DTD,
Chris@719: # which can be used by a validating XML parser to check the
Chris@719: # syntax of the XML files.
Chris@719: 
Chris@719: XML_DTD                =
Chris@719: 
Chris@719: # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
Chris@719: # dump the program listings (including syntax highlighting
Chris@719: # and cross-referencing information) to the XML output. Note that
Chris@719: # enabling this will significantly increase the size of the XML output.
Chris@719: 
Chris@719: XML_PROGRAMLISTING     = YES
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options for the AutoGen Definitions output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
Chris@719: # generate an AutoGen Definitions (see autogen.sf.net) file
Chris@719: # that captures the structure of the code including all
Chris@719: # documentation. Note that this feature is still experimental
Chris@719: # and incomplete at the moment.
Chris@719: 
Chris@719: GENERATE_AUTOGEN_DEF   = NO
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # configuration options related to the Perl module output
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the GENERATE_PERLMOD tag is set to YES Doxygen will
Chris@719: # generate a Perl module file that captures the structure of
Chris@719: # the code including all documentation. Note that this
Chris@719: # feature is still experimental and incomplete at the
Chris@719: # moment.
Chris@719: 
Chris@719: GENERATE_PERLMOD       = NO
Chris@719: 
Chris@719: # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
Chris@719: # the necessary Makefile rules, Perl scripts and LaTeX code to be able
Chris@719: # to generate PDF and DVI output from the Perl module output.
Chris@719: 
Chris@719: PERLMOD_LATEX          = NO
Chris@719: 
Chris@719: # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
Chris@719: # nicely formatted so it can be parsed by a human reader.  This is useful
Chris@719: # if you want to understand what is going on.  On the other hand, if this
Chris@719: # tag is set to NO the size of the Perl module output will be much smaller
Chris@719: # and Perl will parse it just the same.
Chris@719: 
Chris@719: PERLMOD_PRETTY         = YES
Chris@719: 
Chris@719: # The names of the make variables in the generated doxyrules.make file
Chris@719: # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
Chris@719: # This is useful so different doxyrules.make files included by the same
Chris@719: # Makefile don't overwrite each other's variables.
Chris@719: 
Chris@719: PERLMOD_MAKEVAR_PREFIX =
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Configuration options related to the preprocessor
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
Chris@719: # evaluate all C-preprocessor directives found in the sources and include
Chris@719: # files.
Chris@719: 
Chris@719: ENABLE_PREPROCESSING   = YES
Chris@719: 
Chris@719: # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
Chris@719: # names in the source code. If set to NO (the default) only conditional
Chris@719: # compilation will be performed. Macro expansion can be done in a controlled
Chris@719: # way by setting EXPAND_ONLY_PREDEF to YES.
Chris@719: 
Chris@719: MACRO_EXPANSION        = NO
Chris@719: 
Chris@719: # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
Chris@719: # then the macro expansion is limited to the macros specified with the
Chris@719: # PREDEFINED and EXPAND_AS_PREDEFINED tags.
Chris@719: 
Chris@719: EXPAND_ONLY_PREDEF     = NO
Chris@719: 
Chris@719: # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
Chris@719: # in the INCLUDE_PATH (see below) will be search if a #include is found.
Chris@719: 
Chris@719: SEARCH_INCLUDES        = YES
Chris@719: 
Chris@719: # The INCLUDE_PATH tag can be used to specify one or more directories that
Chris@719: # contain include files that are not input files but should be processed by
Chris@719: # the preprocessor.
Chris@719: 
Chris@719: INCLUDE_PATH           = /home/studio/code/qt-433-static/include/Qt /home/studio/code/qt-433-static/include/QtCore /home/studio/code/qt-433-static/include/QtGui /home/studio/code/qt-433-static/include/QtXml /home/studio/code/qt-433-static/include/QtNetwork /home/studio/code/vamp-plugin-sdk /home/studio/code/vamp-plugin-sdk/vamp-sdk
Chris@719: 
Chris@719: # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
Chris@719: # patterns (like *.h and *.hpp) to filter out the header-files in the
Chris@719: # directories. If left blank, the patterns specified with FILE_PATTERNS will
Chris@719: # be used.
Chris@719: 
Chris@719: INCLUDE_FILE_PATTERNS  = Q* *.h
Chris@719: 
Chris@719: # The PREDEFINED tag can be used to specify one or more macro names that
Chris@719: # are defined before the preprocessor is started (similar to the -D option of
Chris@719: # gcc). The argument of the tag is a list of macros of the form: name
Chris@719: # or name=definition (no spaces). If the definition and the = are
Chris@719: # omitted =1 is assumed. To prevent a macro definition from being
Chris@719: # undefined via #undef or recursively expanded use the := operator
Chris@719: # instead of the = operator.
Chris@719: 
Chris@719: PREDEFINED             = HAVE_FFTW3F HAVE_FISHSOUND HAVE_JACK HAVE_LIBLO HAVE_LRDF HAVE_MAD HAVE_OGGZ HAVE_PORTAUDIO HAVE_SAMPLERATE HAVE_SNDFILE HAVE_VAMP
Chris@719: 
Chris@719: # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
Chris@719: # this tag can be used to specify a list of macro names that should be expanded.
Chris@719: # The macro definition that is found in the sources will be used.
Chris@719: # Use the PREDEFINED tag if you want to use a different macro definition.
Chris@719: 
Chris@719: EXPAND_AS_DEFINED      =
Chris@719: 
Chris@719: # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
Chris@719: # doxygen's preprocessor will remove all function-like macros that are alone
Chris@719: # on a line, have an all uppercase name, and do not end with a semicolon. Such
Chris@719: # function macros are typically used for boiler-plate code, and will confuse
Chris@719: # the parser if not removed.
Chris@719: 
Chris@719: SKIP_FUNCTION_MACROS   = YES
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Configuration::additions related to external references
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # The TAGFILES option can be used to specify one or more tagfiles.
Chris@719: # Optionally an initial location of the external documentation
Chris@719: # can be added for each tagfile. The format of a tag file without
Chris@719: # this location is as follows:
Chris@719: #   TAGFILES = file1 file2 ...
Chris@719: # Adding location for the tag files is done as follows:
Chris@719: #   TAGFILES = file1=loc1 "file2 = loc2" ...
Chris@719: # where "loc1" and "loc2" can be relative or absolute paths or
Chris@719: # URLs. If a location is present for each tag, the installdox tool
Chris@719: # does not have to be run to correct the links.
Chris@719: # Note that each tag file must have a unique name
Chris@719: # (where the name does NOT include the path)
Chris@719: # If a tag file is not located in the directory in which doxygen
Chris@719: # is run, you must also specify the path to the tagfile here.
Chris@719: 
Chris@719: TAGFILES               =
Chris@719: 
Chris@719: # When a file name is specified after GENERATE_TAGFILE, doxygen will create
Chris@719: # a tag file that is based on the input files it reads.
Chris@719: 
Chris@719: GENERATE_TAGFILE       =
Chris@719: 
Chris@719: # If the ALLEXTERNALS tag is set to YES all external classes will be listed
Chris@719: # in the class index. If set to NO only the inherited external classes
Chris@719: # will be listed.
Chris@719: 
Chris@719: ALLEXTERNALS           = NO
Chris@719: 
Chris@719: # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
Chris@719: # in the modules index. If set to NO, only the current project's groups will
Chris@719: # be listed.
Chris@719: 
Chris@719: EXTERNAL_GROUPS        = YES
Chris@719: 
Chris@719: # The PERL_PATH should be the absolute path and name of the perl script
Chris@719: # interpreter (i.e. the result of `which perl').
Chris@719: 
Chris@719: PERL_PATH              = /usr/bin/perl
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Configuration options related to the dot tool
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
Chris@719: # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
Chris@719: # or super classes. Setting the tag to NO turns the diagrams off. Note that
Chris@719: # this option is superseded by the HAVE_DOT option below. This is only a
Chris@719: # fallback. It is recommended to install and use dot, since it yields more
Chris@719: # powerful graphs.
Chris@719: 
Chris@719: CLASS_DIAGRAMS         = NO
Chris@719: 
Chris@719: # If set to YES, the inheritance and collaboration graphs will hide
Chris@719: # inheritance and usage relations if the target is undocumented
Chris@719: # or is not a class.
Chris@719: 
Chris@719: HIDE_UNDOC_RELATIONS   = YES
Chris@719: 
Chris@719: # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
Chris@719: # available from the path. This tool is part of Graphviz, a graph visualization
Chris@719: # toolkit from AT&T and Lucent Bell Labs. The other options in this section
Chris@719: # have no effect if this option is set to NO (the default)
Chris@719: 
Chris@719: HAVE_DOT               = YES
Chris@719: 
Chris@719: # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
Chris@719: # will generate a graph for each documented class showing the direct and
Chris@719: # indirect inheritance relations. Setting this tag to YES will force the
Chris@719: # the CLASS_DIAGRAMS tag to NO.
Chris@719: 
Chris@719: CLASS_GRAPH            = YES
Chris@719: 
Chris@719: # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
Chris@719: # will generate a graph for each documented class showing the direct and
Chris@719: # indirect implementation dependencies (inheritance, containment, and
Chris@719: # class references variables) of the class with other documented classes.
Chris@719: 
Chris@719: COLLABORATION_GRAPH    = YES
Chris@719: 
Chris@719: # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
Chris@719: # will generate a graph for groups, showing the direct groups dependencies
Chris@719: 
Chris@719: GROUP_GRAPHS           = YES
Chris@719: 
Chris@719: # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
Chris@719: # collaboration diagrams in a style similar to the OMG's Unified Modeling
Chris@719: # Language.
Chris@719: 
Chris@719: UML_LOOK               = NO
Chris@719: 
Chris@719: # If set to YES, the inheritance and collaboration graphs will show the
Chris@719: # relations between templates and their instances.
Chris@719: 
Chris@719: TEMPLATE_RELATIONS     = NO
Chris@719: 
Chris@719: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
Chris@719: # tags are set to YES then doxygen will generate a graph for each documented
Chris@719: # file showing the direct and indirect include dependencies of the file with
Chris@719: # other documented files.
Chris@719: 
Chris@719: INCLUDE_GRAPH          = YES
Chris@719: 
Chris@719: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
Chris@719: # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
Chris@719: # documented header file showing the documented files that directly or
Chris@719: # indirectly include this file.
Chris@719: 
Chris@719: INCLUDED_BY_GRAPH      = YES
Chris@719: 
Chris@719: # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
Chris@719: # generate a call dependency graph for every global function or class method.
Chris@719: # Note that enabling this option will significantly increase the time of a run.
Chris@719: # So in most cases it will be better to enable call graphs for selected
Chris@719: # functions only using the \callgraph command.
Chris@719: 
Chris@719: CALL_GRAPH             = NO
Chris@719: 
Chris@719: # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
Chris@719: # will graphical hierarchy of all classes instead of a textual one.
Chris@719: 
Chris@719: GRAPHICAL_HIERARCHY    = YES
Chris@719: 
Chris@719: # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
Chris@719: # then doxygen will show the dependencies a directory has on other directories
Chris@719: # in a graphical way. The dependency relations are determined by the #include
Chris@719: # relations between the files in the directories.
Chris@719: 
Chris@719: DIRECTORY_GRAPH        = YES
Chris@719: 
Chris@719: # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
Chris@719: # generated by dot. Possible values are png, jpg, or gif
Chris@719: # If left blank png will be used.
Chris@719: 
Chris@719: DOT_IMAGE_FORMAT       = png
Chris@719: 
Chris@719: # The tag DOT_PATH can be used to specify the path where the dot tool can be
Chris@719: # found. If left blank, it is assumed the dot tool can be found in the path.
Chris@719: 
Chris@719: DOT_PATH               =
Chris@719: 
Chris@719: # The DOTFILE_DIRS tag can be used to specify one or more directories that
Chris@719: # contain dot files that are included in the documentation (see the
Chris@719: # \dotfile command).
Chris@719: 
Chris@719: DOTFILE_DIRS           =
Chris@719: 
Chris@719: # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
Chris@719: # (in pixels) of the graphs generated by dot. If a graph becomes larger than
Chris@719: # this value, doxygen will try to truncate the graph, so that it fits within
Chris@719: # the specified constraint. Beware that most browsers cannot cope with very
Chris@719: # large images.
Chris@719: 
Chris@719: MAX_DOT_GRAPH_WIDTH    = 1024
Chris@719: 
Chris@719: # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
Chris@719: # (in pixels) of the graphs generated by dot. If a graph becomes larger than
Chris@719: # this value, doxygen will try to truncate the graph, so that it fits within
Chris@719: # the specified constraint. Beware that most browsers cannot cope with very
Chris@719: # large images.
Chris@719: 
Chris@719: MAX_DOT_GRAPH_HEIGHT   = 1024
Chris@719: 
Chris@719: # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
Chris@719: # graphs generated by dot. A depth value of 3 means that only nodes reachable
Chris@719: # from the root by following a path via at most 3 edges will be shown. Nodes
Chris@719: # that lay further from the root node will be omitted. Note that setting this
Chris@719: # option to 1 or 2 may greatly reduce the computation time needed for large
Chris@719: # code bases. Also note that a graph may be further truncated if the graph's
Chris@719: # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
Chris@719: # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
Chris@719: # the graph is not depth-constrained.
Chris@719: 
Chris@719: MAX_DOT_GRAPH_DEPTH    = 0
Chris@719: 
Chris@719: # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
Chris@719: # background. This is disabled by default, which results in a white background.
Chris@719: # Warning: Depending on the platform used, enabling this option may lead to
Chris@719: # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
Chris@719: # read).
Chris@719: 
Chris@719: DOT_TRANSPARENT        = NO
Chris@719: 
Chris@719: # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
Chris@719: # files in one run (i.e. multiple -o and -T options on the command line). This
Chris@719: # makes dot run faster, but since only newer versions of dot (>1.8.10)
Chris@719: # support this, this feature is disabled by default.
Chris@719: 
Chris@719: DOT_MULTI_TARGETS      = YES
Chris@719: 
Chris@719: # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
Chris@719: # generate a legend page explaining the meaning of the various boxes and
Chris@719: # arrows in the dot generated graphs.
Chris@719: 
Chris@719: GENERATE_LEGEND        = YES
Chris@719: 
Chris@719: # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
Chris@719: # remove the intermediate dot files that are used to generate
Chris@719: # the various graphs.
Chris@719: 
Chris@719: DOT_CLEANUP            = YES
Chris@719: 
Chris@719: #---------------------------------------------------------------------------
Chris@719: # Configuration::additions related to the search engine
Chris@719: #---------------------------------------------------------------------------
Chris@719: 
Chris@719: # The SEARCHENGINE tag specifies whether or not a search engine should be
Chris@719: # used. If set to NO the values of all tags below this one will be ignored.
Chris@719: 
Chris@719: SEARCHENGINE           = NO