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