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