flatmax@597: # Doxyfile 1.7.6.1 flatmax@597: flatmax@597: # This file describes the settings to be used by the documentation system flatmax@597: # doxygen (www.doxygen.org) for a project flatmax@597: # flatmax@597: # All text after a hash (#) is considered a comment and will be ignored flatmax@597: # The format is: flatmax@597: # TAG = value [value, ...] flatmax@597: # For lists items can also be appended using: flatmax@597: # TAG += value [value, ...] flatmax@597: # Values that contain spaces should be placed between quotes (" ") flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # Project related configuration options flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # This tag specifies the encoding used for all characters in the config file flatmax@597: # that follow. The default is UTF-8 which is also the encoding used for all flatmax@597: # text before the first occurrence of this tag. Doxygen uses libiconv (or the flatmax@597: # iconv built into libc) for the transcoding. See flatmax@597: # http://www.gnu.org/software/libiconv for the list of possible encodings. flatmax@597: flatmax@597: DOXYFILE_ENCODING = UTF-8 flatmax@597: flatmax@597: # The PROJECT_NAME tag is a single word (or sequence of words) that should flatmax@597: # identify the project. Note that if you do not use Doxywizard you need flatmax@597: # to put quotes around the project name if it contains spaces. flatmax@597: flatmax@597: PROJECT_NAME = "CARFAC C++" flatmax@597: flatmax@597: # The PROJECT_NUMBER tag can be used to enter a project or revision number. flatmax@597: # This could be handy for archiving the generated documentation or flatmax@597: # if some version control system is used. flatmax@597: flatmax@597: PROJECT_NUMBER = flatmax@597: flatmax@597: # Using the PROJECT_BRIEF tag one can provide an optional one line description flatmax@597: # for a project that appears at the top of each page and should give viewer flatmax@597: # a quick idea about the purpose of the project. Keep the description short. flatmax@597: flatmax@597: PROJECT_BRIEF = "C++ implementation of CARFAC" flatmax@597: flatmax@597: # With the PROJECT_LOGO tag one can specify an logo or icon that is flatmax@597: # included in the documentation. The maximum height of the logo should not flatmax@597: # exceed 55 pixels and the maximum width should not exceed 200 pixels. flatmax@597: # Doxygen will copy the logo to the output directory. flatmax@597: flatmax@597: PROJECT_LOGO = /home/flatmax/work.orig/DickLyon/aimc/C++/figs/icon.png flatmax@597: flatmax@597: # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) flatmax@597: # base path where the generated documentation will be put. flatmax@597: # If a relative path is entered, it will be relative to the location flatmax@597: # where doxygen was started. If left blank the current directory will be used. flatmax@597: flatmax@597: OUTPUT_DIRECTORY = api flatmax@597: flatmax@597: # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create flatmax@597: # 4096 sub-directories (in 2 levels) under the output directory of each output flatmax@597: # format and will distribute the generated files over these directories. flatmax@597: # Enabling this option can be useful when feeding doxygen a huge amount of flatmax@597: # source files, where putting all generated files in the same directory would flatmax@597: # otherwise cause performance problems for the file system. flatmax@597: flatmax@597: CREATE_SUBDIRS = NO flatmax@597: flatmax@597: # The OUTPUT_LANGUAGE tag is used to specify the language in which all flatmax@597: # documentation generated by doxygen is written. Doxygen will use this flatmax@597: # information to generate all constant output in the proper language. flatmax@597: # The default language is English, other supported languages are: flatmax@597: # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, flatmax@597: # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, flatmax@597: # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English flatmax@597: # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, flatmax@597: # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, flatmax@597: # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. flatmax@597: flatmax@597: OUTPUT_LANGUAGE = English flatmax@597: flatmax@597: # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will flatmax@597: # include brief member descriptions after the members that are listed in flatmax@597: # the file and class documentation (similar to JavaDoc). flatmax@597: # Set to NO to disable this. flatmax@597: flatmax@597: BRIEF_MEMBER_DESC = YES flatmax@597: flatmax@597: # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend flatmax@597: # the brief description of a member or function before the detailed description. flatmax@597: # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the flatmax@597: # brief descriptions will be completely suppressed. flatmax@597: flatmax@597: REPEAT_BRIEF = YES flatmax@597: flatmax@597: # This tag implements a quasi-intelligent brief description abbreviator flatmax@597: # that is used to form the text in various listings. Each string flatmax@597: # in this list, if found as the leading text of the brief description, will be flatmax@597: # stripped from the text and the result after processing the whole list, is flatmax@597: # used as the annotated text. Otherwise, the brief description is used as-is. flatmax@597: # If left blank, the following values are used ("$name" is automatically flatmax@597: # replaced with the name of the entity): "The $name class" "The $name widget" flatmax@597: # "The $name file" "is" "provides" "specifies" "contains" flatmax@597: # "represents" "a" "an" "the" flatmax@597: flatmax@597: ABBREVIATE_BRIEF = flatmax@597: flatmax@597: # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then flatmax@597: # Doxygen will generate a detailed section even if there is only a brief flatmax@597: # description. flatmax@597: flatmax@597: ALWAYS_DETAILED_SEC = NO flatmax@597: flatmax@597: # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all flatmax@597: # inherited members of a class in the documentation of that class as if those flatmax@597: # members were ordinary class members. Constructors, destructors and assignment flatmax@597: # operators of the base classes will not be shown. flatmax@597: flatmax@597: INLINE_INHERITED_MEMB = NO flatmax@597: flatmax@597: # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full flatmax@597: # path before files name in the file list and in the header files. If set flatmax@597: # to NO the shortest path that makes the file name unique will be used. flatmax@597: flatmax@597: FULL_PATH_NAMES = YES flatmax@597: flatmax@597: # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag flatmax@597: # can be used to strip a user-defined part of the path. Stripping is flatmax@597: # only done if one of the specified strings matches the left-hand part of flatmax@597: # the path. The tag can be used to show relative paths in the file list. flatmax@597: # If left blank the directory from which doxygen is run is used as the flatmax@597: # path to strip. flatmax@597: flatmax@597: STRIP_FROM_PATH = flatmax@597: flatmax@597: # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of flatmax@597: # the path mentioned in the documentation of a class, which tells flatmax@597: # the reader which header file to include in order to use a class. flatmax@597: # If left blank only the name of the header file containing the class flatmax@597: # definition is used. Otherwise one should specify the include paths that flatmax@597: # are normally passed to the compiler using the -I flag. flatmax@597: flatmax@597: STRIP_FROM_INC_PATH = flatmax@597: flatmax@597: # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter flatmax@597: # (but less readable) file names. This can be useful if your file system flatmax@597: # doesn't support long names like on DOS, Mac, or CD-ROM. flatmax@597: flatmax@597: SHORT_NAMES = NO flatmax@597: flatmax@597: # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen flatmax@597: # will interpret the first line (until the first dot) of a JavaDoc-style flatmax@597: # comment as the brief description. If set to NO, the JavaDoc flatmax@597: # comments will behave just like regular Qt-style comments flatmax@597: # (thus requiring an explicit @brief command for a brief description.) flatmax@597: flatmax@597: JAVADOC_AUTOBRIEF = NO flatmax@597: flatmax@597: # If the QT_AUTOBRIEF tag is set to YES then Doxygen will flatmax@597: # interpret the first line (until the first dot) of a Qt-style flatmax@597: # comment as the brief description. If set to NO, the comments flatmax@597: # will behave just like regular Qt-style comments (thus requiring flatmax@597: # an explicit \brief command for a brief description.) flatmax@597: flatmax@597: QT_AUTOBRIEF = NO flatmax@597: flatmax@597: # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen flatmax@597: # treat a multi-line C++ special comment block (i.e. a block of //! or /// flatmax@597: # comments) as a brief description. This used to be the default behaviour. flatmax@597: # The new default is to treat a multi-line C++ comment block as a detailed flatmax@597: # description. Set this tag to YES if you prefer the old behaviour instead. flatmax@597: flatmax@597: MULTILINE_CPP_IS_BRIEF = NO flatmax@597: flatmax@597: # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented flatmax@597: # member inherits the documentation from any documented member that it flatmax@597: # re-implements. flatmax@597: flatmax@597: INHERIT_DOCS = YES flatmax@597: flatmax@597: # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce flatmax@597: # a new page for each member. If set to NO, the documentation of a member will flatmax@597: # be part of the file/class/namespace that contains it. flatmax@597: flatmax@597: SEPARATE_MEMBER_PAGES = NO flatmax@597: flatmax@597: # The TAB_SIZE tag can be used to set the number of spaces in a tab. flatmax@597: # Doxygen uses this value to replace tabs by spaces in code fragments. flatmax@597: flatmax@597: TAB_SIZE = 8 flatmax@597: flatmax@597: # This tag can be used to specify a number of aliases that acts flatmax@597: # as commands in the documentation. An alias has the form "name=value". flatmax@597: # For example adding "sideeffect=\par Side Effects:\n" will allow you to flatmax@597: # put the command \sideeffect (or @sideeffect) in the documentation, which flatmax@597: # will result in a user-defined paragraph with heading "Side Effects:". flatmax@597: # You can put \n's in the value part of an alias to insert newlines. flatmax@597: flatmax@597: ALIASES = flatmax@597: flatmax@597: # This tag can be used to specify a number of word-keyword mappings (TCL only). flatmax@597: # A mapping has the form "name=value". For example adding flatmax@597: # "class=itcl::class" will allow you to use the command class in the flatmax@597: # itcl::class meaning. flatmax@597: flatmax@597: TCL_SUBST = flatmax@597: flatmax@597: # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C flatmax@597: # sources only. Doxygen will then generate output that is more tailored for C. flatmax@597: # For instance, some of the names that are used will be different. The list flatmax@597: # of all members will be omitted, etc. flatmax@597: flatmax@597: OPTIMIZE_OUTPUT_FOR_C = NO flatmax@597: flatmax@597: # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java flatmax@597: # sources only. Doxygen will then generate output that is more tailored for flatmax@597: # Java. For instance, namespaces will be presented as packages, qualified flatmax@597: # scopes will look different, etc. flatmax@597: flatmax@597: OPTIMIZE_OUTPUT_JAVA = NO flatmax@597: flatmax@597: # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran flatmax@597: # sources only. Doxygen will then generate output that is more tailored for flatmax@597: # Fortran. flatmax@597: flatmax@597: OPTIMIZE_FOR_FORTRAN = NO flatmax@597: flatmax@597: # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL flatmax@597: # sources. Doxygen will then generate output that is tailored for flatmax@597: # VHDL. flatmax@597: flatmax@597: OPTIMIZE_OUTPUT_VHDL = NO flatmax@597: flatmax@597: # Doxygen selects the parser to use depending on the extension of the files it flatmax@597: # parses. With this tag you can assign which parser to use for a given extension. flatmax@597: # Doxygen has a built-in mapping, but you can override or extend it using this flatmax@597: # tag. The format is ext=language, where ext is a file extension, and language flatmax@597: # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, flatmax@597: # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make flatmax@597: # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C flatmax@597: # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions flatmax@597: # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. flatmax@597: flatmax@597: EXTENSION_MAPPING = flatmax@597: flatmax@597: # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want flatmax@597: # to include (a tag file for) the STL sources as input, then you should flatmax@597: # set this tag to YES in order to let doxygen match functions declarations and flatmax@597: # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. flatmax@597: # func(std::string) {}). This also makes the inheritance and collaboration flatmax@597: # diagrams that involve STL classes more complete and accurate. flatmax@597: flatmax@597: BUILTIN_STL_SUPPORT = NO flatmax@597: flatmax@597: # If you use Microsoft's C++/CLI language, you should set this option to YES to flatmax@597: # enable parsing support. flatmax@597: flatmax@597: CPP_CLI_SUPPORT = NO flatmax@597: flatmax@597: # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. flatmax@597: # Doxygen will parse them like normal C++ but will assume all classes use public flatmax@597: # instead of private inheritance when no explicit protection keyword is present. flatmax@597: flatmax@597: SIP_SUPPORT = NO flatmax@597: flatmax@597: # For Microsoft's IDL there are propget and propput attributes to indicate getter flatmax@597: # and setter methods for a property. Setting this option to YES (the default) flatmax@597: # will make doxygen replace the get and set methods by a property in the flatmax@597: # documentation. This will only work if the methods are indeed getting or flatmax@597: # setting a simple type. If this is not the case, or you want to show the flatmax@597: # methods anyway, you should set this option to NO. flatmax@597: flatmax@597: IDL_PROPERTY_SUPPORT = YES flatmax@597: flatmax@597: # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC flatmax@597: # tag is set to YES, then doxygen will reuse the documentation of the first flatmax@597: # member in the group (if any) for the other members of the group. By default flatmax@597: # all members of a group must be documented explicitly. flatmax@597: flatmax@597: DISTRIBUTE_GROUP_DOC = NO flatmax@597: flatmax@597: # Set the SUBGROUPING tag to YES (the default) to allow class member groups of flatmax@597: # the same type (for instance a group of public functions) to be put as a flatmax@597: # subgroup of that type (e.g. under the Public Functions section). Set it to flatmax@597: # NO to prevent subgrouping. Alternatively, this can be done per class using flatmax@597: # the \nosubgrouping command. flatmax@597: flatmax@597: SUBGROUPING = YES flatmax@597: flatmax@597: # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and flatmax@597: # unions are shown inside the group in which they are included (e.g. using flatmax@597: # @ingroup) instead of on a separate page (for HTML and Man pages) or flatmax@597: # section (for LaTeX and RTF). flatmax@597: flatmax@597: INLINE_GROUPED_CLASSES = NO flatmax@597: flatmax@597: # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and flatmax@597: # unions with only public data fields will be shown inline in the documentation flatmax@597: # of the scope in which they are defined (i.e. file, namespace, or group flatmax@597: # documentation), provided this scope is documented. If set to NO (the default), flatmax@597: # structs, classes, and unions are shown on a separate page (for HTML and Man flatmax@597: # pages) or section (for LaTeX and RTF). flatmax@597: flatmax@597: INLINE_SIMPLE_STRUCTS = NO flatmax@597: flatmax@597: # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum flatmax@597: # is documented as struct, union, or enum with the name of the typedef. So flatmax@597: # typedef struct TypeS {} TypeT, will appear in the documentation as a struct flatmax@597: # with name TypeT. When disabled the typedef will appear as a member of a file, flatmax@597: # namespace, or class. And the struct will be named TypeS. This can typically flatmax@597: # be useful for C code in case the coding convention dictates that all compound flatmax@597: # types are typedef'ed and only the typedef is referenced, never the tag name. flatmax@597: flatmax@597: TYPEDEF_HIDES_STRUCT = NO flatmax@597: flatmax@597: # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to flatmax@597: # determine which symbols to keep in memory and which to flush to disk. flatmax@597: # When the cache is full, less often used symbols will be written to disk. flatmax@597: # For small to medium size projects (<1000 input files) the default value is flatmax@597: # probably good enough. For larger projects a too small cache size can cause flatmax@597: # doxygen to be busy swapping symbols to and from disk most of the time flatmax@597: # causing a significant performance penalty. flatmax@597: # If the system has enough physical memory increasing the cache will improve the flatmax@597: # performance by keeping more symbols in memory. Note that the value works on flatmax@597: # a logarithmic scale so increasing the size by one will roughly double the flatmax@597: # memory usage. The cache size is given by this formula: flatmax@597: # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, flatmax@597: # corresponding to a cache size of 2^16 = 65536 symbols. flatmax@597: flatmax@597: SYMBOL_CACHE_SIZE = 0 flatmax@597: flatmax@597: # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be flatmax@597: # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given flatmax@597: # their name and scope. Since this can be an expensive process and often the flatmax@597: # same symbol appear multiple times in the code, doxygen keeps a cache of flatmax@597: # pre-resolved symbols. If the cache is too small doxygen will become slower. flatmax@597: # If the cache is too large, memory is wasted. The cache size is given by this flatmax@597: # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, flatmax@597: # corresponding to a cache size of 2^16 = 65536 symbols. flatmax@597: flatmax@597: LOOKUP_CACHE_SIZE = 0 flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # Build related configuration options flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in flatmax@597: # documentation are documented, even if no documentation was available. flatmax@597: # Private class members and static file members will be hidden unless flatmax@597: # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES flatmax@597: flatmax@597: EXTRACT_ALL = YES flatmax@597: flatmax@597: # If the EXTRACT_PRIVATE tag is set to YES all private members of a class flatmax@597: # will be included in the documentation. flatmax@597: flatmax@597: EXTRACT_PRIVATE = YES flatmax@597: flatmax@597: # If the EXTRACT_STATIC tag is set to YES all static members of a file flatmax@597: # will be included in the documentation. flatmax@597: flatmax@597: EXTRACT_STATIC = YES flatmax@597: flatmax@597: # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) flatmax@597: # defined locally in source files will be included in the documentation. flatmax@597: # If set to NO only classes defined in header files are included. flatmax@597: flatmax@597: EXTRACT_LOCAL_CLASSES = YES flatmax@597: flatmax@597: # This flag is only useful for Objective-C code. When set to YES local flatmax@597: # methods, which are defined in the implementation section but not in flatmax@597: # the interface are included in the documentation. flatmax@597: # If set to NO (the default) only methods in the interface are included. flatmax@597: flatmax@597: EXTRACT_LOCAL_METHODS = NO flatmax@597: flatmax@597: # If this flag is set to YES, the members of anonymous namespaces will be flatmax@597: # extracted and appear in the documentation as a namespace called flatmax@597: # 'anonymous_namespace{file}', where file will be replaced with the base flatmax@597: # name of the file that contains the anonymous namespace. By default flatmax@597: # anonymous namespaces are hidden. flatmax@597: flatmax@597: EXTRACT_ANON_NSPACES = NO flatmax@597: flatmax@597: # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all flatmax@597: # undocumented members of documented classes, files or namespaces. flatmax@597: # If set to NO (the default) these members will be included in the flatmax@597: # various overviews, but no documentation section is generated. flatmax@597: # This option has no effect if EXTRACT_ALL is enabled. flatmax@597: flatmax@597: HIDE_UNDOC_MEMBERS = NO flatmax@597: flatmax@597: # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all flatmax@597: # undocumented classes that are normally visible in the class hierarchy. flatmax@597: # If set to NO (the default) these classes will be included in the various flatmax@597: # overviews. This option has no effect if EXTRACT_ALL is enabled. flatmax@597: flatmax@597: HIDE_UNDOC_CLASSES = NO flatmax@597: flatmax@597: # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all flatmax@597: # friend (class|struct|union) declarations. flatmax@597: # If set to NO (the default) these declarations will be included in the flatmax@597: # documentation. flatmax@597: flatmax@597: HIDE_FRIEND_COMPOUNDS = NO flatmax@597: flatmax@597: # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any flatmax@597: # documentation blocks found inside the body of a function. flatmax@597: # If set to NO (the default) these blocks will be appended to the flatmax@597: # function's detailed documentation block. flatmax@597: flatmax@597: HIDE_IN_BODY_DOCS = NO flatmax@597: flatmax@597: # The INTERNAL_DOCS tag determines if documentation flatmax@597: # that is typed after a \internal command is included. If the tag is set flatmax@597: # to NO (the default) then the documentation will be excluded. flatmax@597: # Set it to YES to include the internal documentation. flatmax@597: flatmax@597: INTERNAL_DOCS = NO flatmax@597: flatmax@597: # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate flatmax@597: # file names in lower-case letters. If set to YES upper-case letters are also flatmax@597: # allowed. This is useful if you have classes or files whose names only differ flatmax@597: # in case and if your file system supports case sensitive file names. Windows flatmax@597: # and Mac users are advised to set this option to NO. flatmax@597: flatmax@597: CASE_SENSE_NAMES = YES flatmax@597: flatmax@597: # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen flatmax@597: # will show members with their full class and namespace scopes in the flatmax@597: # documentation. If set to YES the scope will be hidden. flatmax@597: flatmax@597: HIDE_SCOPE_NAMES = NO flatmax@597: flatmax@597: # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen flatmax@597: # will put a list of the files that are included by a file in the documentation flatmax@597: # of that file. flatmax@597: flatmax@597: SHOW_INCLUDE_FILES = YES flatmax@597: flatmax@597: # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen flatmax@597: # will list include files with double quotes in the documentation flatmax@597: # rather than with sharp brackets. flatmax@597: flatmax@597: FORCE_LOCAL_INCLUDES = NO flatmax@597: flatmax@597: # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] flatmax@597: # is inserted in the documentation for inline members. flatmax@597: flatmax@597: INLINE_INFO = YES flatmax@597: flatmax@597: # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen flatmax@597: # will sort the (detailed) documentation of file and class members flatmax@597: # alphabetically by member name. If set to NO the members will appear in flatmax@597: # declaration order. flatmax@597: flatmax@597: SORT_MEMBER_DOCS = YES flatmax@597: flatmax@597: # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the flatmax@597: # brief documentation of file, namespace and class members alphabetically flatmax@597: # by member name. If set to NO (the default) the members will appear in flatmax@597: # declaration order. flatmax@597: flatmax@597: SORT_BRIEF_DOCS = NO flatmax@597: flatmax@597: # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen flatmax@597: # will sort the (brief and detailed) documentation of class members so that flatmax@597: # constructors and destructors are listed first. If set to NO (the default) flatmax@597: # the constructors will appear in the respective orders defined by flatmax@597: # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. flatmax@597: # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO flatmax@597: # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. flatmax@597: flatmax@597: SORT_MEMBERS_CTORS_1ST = NO flatmax@597: flatmax@597: # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the flatmax@597: # hierarchy of group names into alphabetical order. If set to NO (the default) flatmax@597: # the group names will appear in their defined order. flatmax@597: flatmax@597: SORT_GROUP_NAMES = NO flatmax@597: flatmax@597: # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be flatmax@597: # sorted by fully-qualified names, including namespaces. If set to flatmax@597: # NO (the default), the class list will be sorted only by class name, flatmax@597: # not including the namespace part. flatmax@597: # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. flatmax@597: # Note: This option applies only to the class list, not to the flatmax@597: # alphabetical list. flatmax@597: flatmax@597: SORT_BY_SCOPE_NAME = NO flatmax@597: flatmax@597: # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to flatmax@597: # do proper type resolution of all parameters of a function it will reject a flatmax@597: # match between the prototype and the implementation of a member function even flatmax@597: # if there is only one candidate or it is obvious which candidate to choose flatmax@597: # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen flatmax@597: # will still accept a match between prototype and implementation in such cases. flatmax@597: flatmax@597: STRICT_PROTO_MATCHING = NO flatmax@597: flatmax@597: # The GENERATE_TODOLIST tag can be used to enable (YES) or flatmax@597: # disable (NO) the todo list. This list is created by putting \todo flatmax@597: # commands in the documentation. flatmax@597: flatmax@597: GENERATE_TODOLIST = YES flatmax@597: flatmax@597: # The GENERATE_TESTLIST tag can be used to enable (YES) or flatmax@597: # disable (NO) the test list. This list is created by putting \test flatmax@597: # commands in the documentation. flatmax@597: flatmax@597: GENERATE_TESTLIST = YES flatmax@597: flatmax@597: # The GENERATE_BUGLIST tag can be used to enable (YES) or flatmax@597: # disable (NO) the bug list. This list is created by putting \bug flatmax@597: # commands in the documentation. flatmax@597: flatmax@597: GENERATE_BUGLIST = YES flatmax@597: flatmax@597: # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or flatmax@597: # disable (NO) the deprecated list. This list is created by putting flatmax@597: # \deprecated commands in the documentation. flatmax@597: flatmax@597: GENERATE_DEPRECATEDLIST= YES flatmax@597: flatmax@597: # The ENABLED_SECTIONS tag can be used to enable conditional flatmax@597: # documentation sections, marked by \if sectionname ... \endif. flatmax@597: flatmax@597: ENABLED_SECTIONS = flatmax@597: flatmax@597: # The MAX_INITIALIZER_LINES tag determines the maximum number of lines flatmax@597: # the initial value of a variable or macro consists of for it to appear in flatmax@597: # the documentation. If the initializer consists of more lines than specified flatmax@597: # here it will be hidden. Use a value of 0 to hide initializers completely. flatmax@597: # The appearance of the initializer of individual variables and macros in the flatmax@597: # documentation can be controlled using \showinitializer or \hideinitializer flatmax@597: # command in the documentation regardless of this setting. flatmax@597: flatmax@597: MAX_INITIALIZER_LINES = 30 flatmax@597: flatmax@597: # Set the SHOW_USED_FILES tag to NO to disable the list of files generated flatmax@597: # at the bottom of the documentation of classes and structs. If set to YES the flatmax@597: # list will mention the files that were used to generate the documentation. flatmax@597: flatmax@597: SHOW_USED_FILES = YES flatmax@597: flatmax@597: # If the sources in your project are distributed over multiple directories flatmax@597: # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy flatmax@597: # in the documentation. The default is NO. flatmax@597: flatmax@597: SHOW_DIRECTORIES = NO flatmax@597: flatmax@597: # Set the SHOW_FILES tag to NO to disable the generation of the Files page. flatmax@597: # This will remove the Files entry from the Quick Index and from the flatmax@597: # Folder Tree View (if specified). The default is YES. flatmax@597: flatmax@597: SHOW_FILES = YES flatmax@597: flatmax@597: # Set the SHOW_NAMESPACES tag to NO to disable the generation of the flatmax@597: # Namespaces page. This will remove the Namespaces entry from the Quick Index flatmax@597: # and from the Folder Tree View (if specified). The default is YES. flatmax@597: flatmax@597: SHOW_NAMESPACES = YES flatmax@597: flatmax@597: # The FILE_VERSION_FILTER tag can be used to specify a program or script that flatmax@597: # doxygen should invoke to get the current version for each file (typically from flatmax@597: # the version control system). Doxygen will invoke the program by executing (via flatmax@597: # popen()) the command , where is the value of flatmax@597: # the FILE_VERSION_FILTER tag, and is the name of an input file flatmax@597: # provided by doxygen. Whatever the program writes to standard output flatmax@597: # is used as the file version. See the manual for examples. flatmax@597: flatmax@597: FILE_VERSION_FILTER = flatmax@597: flatmax@597: # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed flatmax@597: # by doxygen. The layout file controls the global structure of the generated flatmax@597: # output files in an output format independent way. The create the layout file flatmax@597: # that represents doxygen's defaults, run doxygen with the -l option. flatmax@597: # You can optionally specify a file name after the option, if omitted flatmax@597: # DoxygenLayout.xml will be used as the name of the layout file. flatmax@597: flatmax@597: LAYOUT_FILE = flatmax@597: flatmax@597: # The CITE_BIB_FILES tag can be used to specify one or more bib files flatmax@597: # containing the references data. This must be a list of .bib files. The flatmax@597: # .bib extension is automatically appended if omitted. Using this command flatmax@597: # requires the bibtex tool to be installed. See also flatmax@597: # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style flatmax@597: # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this flatmax@597: # feature you need bibtex and perl available in the search path. flatmax@597: flatmax@597: CITE_BIB_FILES = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to warning and progress messages flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # The QUIET tag can be used to turn on/off the messages that are generated flatmax@597: # by doxygen. Possible values are YES and NO. If left blank NO is used. flatmax@597: flatmax@597: QUIET = NO flatmax@597: flatmax@597: # The WARNINGS tag can be used to turn on/off the warning messages that are flatmax@597: # generated by doxygen. Possible values are YES and NO. If left blank flatmax@597: # NO is used. flatmax@597: flatmax@597: WARNINGS = YES flatmax@597: flatmax@597: # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings flatmax@597: # for undocumented members. If EXTRACT_ALL is set to YES then this flag will flatmax@597: # automatically be disabled. flatmax@597: flatmax@597: WARN_IF_UNDOCUMENTED = YES flatmax@597: flatmax@597: # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for flatmax@597: # potential errors in the documentation, such as not documenting some flatmax@597: # parameters in a documented function, or documenting parameters that flatmax@597: # don't exist or using markup commands wrongly. flatmax@597: flatmax@597: WARN_IF_DOC_ERROR = YES flatmax@597: flatmax@597: # The WARN_NO_PARAMDOC option can be enabled to get warnings for flatmax@597: # functions that are documented, but have no documentation for their parameters flatmax@597: # or return value. If set to NO (the default) doxygen will only warn about flatmax@597: # wrong or incomplete parameter documentation, but not about the absence of flatmax@597: # documentation. flatmax@597: flatmax@597: WARN_NO_PARAMDOC = NO flatmax@597: flatmax@597: # The WARN_FORMAT tag determines the format of the warning messages that flatmax@597: # doxygen can produce. The string should contain the $file, $line, and $text flatmax@597: # tags, which will be replaced by the file and line number from which the flatmax@597: # warning originated and the warning text. Optionally the format may contain flatmax@597: # $version, which will be replaced by the version of the file (if it could flatmax@597: # be obtained via FILE_VERSION_FILTER) flatmax@597: flatmax@597: WARN_FORMAT = "$file:$line: $text" flatmax@597: flatmax@597: # The WARN_LOGFILE tag can be used to specify a file to which warning flatmax@597: # and error messages should be written. If left blank the output is written flatmax@597: # to stderr. flatmax@597: flatmax@597: WARN_LOGFILE = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the input files flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # The INPUT tag can be used to specify the files and/or directories that contain flatmax@597: # documented source files. You may enter file names like "myfile.cpp" or flatmax@597: # directories like "/usr/src/myproject". Separate the files or directories flatmax@597: # with spaces. flatmax@597: flatmax@597: INPUT = . flatmax@597: flatmax@597: # This tag can be used to specify the character encoding of the source files flatmax@597: # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is flatmax@597: # also the default input encoding. Doxygen uses libiconv (or the iconv built flatmax@597: # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for flatmax@597: # the list of possible encodings. flatmax@597: flatmax@597: INPUT_ENCODING = UTF-8 flatmax@597: flatmax@597: # If the value of the INPUT tag contains directories, you can use the flatmax@597: # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp flatmax@597: # and *.h) to filter out the source-files in the directories. If left flatmax@597: # blank the following patterns are tested: flatmax@597: # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh flatmax@597: # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py flatmax@597: # *.f90 *.f *.for *.vhd *.vhdl flatmax@597: flatmax@597: FILE_PATTERNS = flatmax@597: flatmax@597: # The RECURSIVE tag can be used to turn specify whether or not subdirectories flatmax@597: # should be searched for input files as well. Possible values are YES and NO. flatmax@597: # If left blank NO is used. flatmax@597: flatmax@597: RECURSIVE = NO flatmax@597: flatmax@597: # The EXCLUDE tag can be used to specify files and/or directories that should be flatmax@597: # excluded from the INPUT source files. This way you can easily exclude a flatmax@597: # subdirectory from a directory tree whose root is specified with the INPUT tag. flatmax@597: # Note that relative paths are relative to the directory from which doxygen is flatmax@597: # run. flatmax@597: flatmax@597: EXCLUDE = flatmax@597: flatmax@597: # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or flatmax@597: # directories that are symbolic links (a Unix file system feature) are excluded flatmax@597: # from the input. flatmax@597: flatmax@597: EXCLUDE_SYMLINKS = NO flatmax@597: flatmax@597: # If the value of the INPUT tag contains directories, you can use the flatmax@597: # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude flatmax@597: # certain files from those directories. Note that the wildcards are matched flatmax@597: # against the file with absolute path, so to exclude all test directories flatmax@597: # for example use the pattern */test/* flatmax@597: flatmax@597: EXCLUDE_PATTERNS = flatmax@597: flatmax@597: # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names flatmax@597: # (namespaces, classes, functions, etc.) that should be excluded from the flatmax@597: # output. The symbol name can be a fully qualified name, a word, or if the flatmax@597: # wildcard * is used, a substring. Examples: ANamespace, AClass, flatmax@597: # AClass::ANamespace, ANamespace::*Test flatmax@597: flatmax@597: EXCLUDE_SYMBOLS = flatmax@597: flatmax@597: # The EXAMPLE_PATH tag can be used to specify one or more files or flatmax@597: # directories that contain example code fragments that are included (see flatmax@597: # the \include command). flatmax@597: flatmax@597: EXAMPLE_PATH = flatmax@597: flatmax@597: # If the value of the EXAMPLE_PATH tag contains directories, you can use the flatmax@597: # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp flatmax@597: # and *.h) to filter out the source-files in the directories. If left flatmax@597: # blank all files are included. flatmax@597: flatmax@597: EXAMPLE_PATTERNS = flatmax@597: flatmax@597: # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be flatmax@597: # searched for input files to be used with the \include or \dontinclude flatmax@597: # commands irrespective of the value of the RECURSIVE tag. flatmax@597: # Possible values are YES and NO. If left blank NO is used. flatmax@597: flatmax@597: EXAMPLE_RECURSIVE = NO flatmax@597: flatmax@597: # The IMAGE_PATH tag can be used to specify one or more files or flatmax@597: # directories that contain image that are included in the documentation (see flatmax@597: # the \image command). flatmax@597: flatmax@597: IMAGE_PATH = flatmax@597: flatmax@597: # The INPUT_FILTER tag can be used to specify a program that doxygen should flatmax@597: # invoke to filter for each input file. Doxygen will invoke the filter program flatmax@597: # by executing (via popen()) the command , where flatmax@597: # is the value of the INPUT_FILTER tag, and is the name of an flatmax@597: # input file. Doxygen will then use the output that the filter program writes flatmax@597: # to standard output. If FILTER_PATTERNS is specified, this tag will be flatmax@597: # ignored. flatmax@597: flatmax@597: INPUT_FILTER = flatmax@597: flatmax@597: # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern flatmax@597: # basis. Doxygen will compare the file name with each pattern and apply the flatmax@597: # filter if there is a match. The filters are a list of the form: flatmax@597: # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further flatmax@597: # info on how filters are used. If FILTER_PATTERNS is empty or if flatmax@597: # non of the patterns match the file name, INPUT_FILTER is applied. flatmax@597: flatmax@597: FILTER_PATTERNS = flatmax@597: flatmax@597: # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using flatmax@597: # INPUT_FILTER) will be used to filter the input files when producing source flatmax@597: # files to browse (i.e. when SOURCE_BROWSER is set to YES). flatmax@597: flatmax@597: FILTER_SOURCE_FILES = NO flatmax@597: flatmax@597: # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file flatmax@597: # pattern. A pattern will override the setting for FILTER_PATTERN (if any) flatmax@597: # and it is also possible to disable source filtering for a specific pattern flatmax@597: # using *.ext= (so without naming a filter). This option only has effect when flatmax@597: # FILTER_SOURCE_FILES is enabled. flatmax@597: flatmax@597: FILTER_SOURCE_PATTERNS = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to source browsing flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the SOURCE_BROWSER tag is set to YES then a list of source files will flatmax@597: # be generated. Documented entities will be cross-referenced with these sources. flatmax@597: # Note: To get rid of all source code in the generated output, make sure also flatmax@597: # VERBATIM_HEADERS is set to NO. flatmax@597: flatmax@597: SOURCE_BROWSER = NO flatmax@597: flatmax@597: # Setting the INLINE_SOURCES tag to YES will include the body flatmax@597: # of functions and classes directly in the documentation. flatmax@597: flatmax@597: INLINE_SOURCES = NO flatmax@597: flatmax@597: # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct flatmax@597: # doxygen to hide any special comment blocks from generated source code flatmax@597: # fragments. Normal C and C++ comments will always remain visible. flatmax@597: flatmax@597: STRIP_CODE_COMMENTS = YES flatmax@597: flatmax@597: # If the REFERENCED_BY_RELATION tag is set to YES flatmax@597: # then for each documented function all documented flatmax@597: # functions referencing it will be listed. flatmax@597: flatmax@597: REFERENCED_BY_RELATION = NO flatmax@597: flatmax@597: # If the REFERENCES_RELATION tag is set to YES flatmax@597: # then for each documented function all documented entities flatmax@597: # called/used by that function will be listed. flatmax@597: flatmax@597: REFERENCES_RELATION = NO flatmax@597: flatmax@597: # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) flatmax@597: # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from flatmax@597: # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will flatmax@597: # link to the source code. Otherwise they will link to the documentation. flatmax@597: flatmax@597: REFERENCES_LINK_SOURCE = YES flatmax@597: flatmax@597: # If the USE_HTAGS tag is set to YES then the references to source code flatmax@597: # will point to the HTML generated by the htags(1) tool instead of doxygen flatmax@597: # built-in source browser. The htags tool is part of GNU's global source flatmax@597: # tagging system (see http://www.gnu.org/software/global/global.html). You flatmax@597: # will need version 4.8.6 or higher. flatmax@597: flatmax@597: USE_HTAGS = NO flatmax@597: flatmax@597: # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen flatmax@597: # will generate a verbatim copy of the header file for each class for flatmax@597: # which an include is specified. Set to NO to disable this. flatmax@597: flatmax@597: VERBATIM_HEADERS = YES flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the alphabetical class index flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index flatmax@597: # of all compounds will be generated. Enable this if the project flatmax@597: # contains a lot of classes, structs, unions or interfaces. flatmax@597: flatmax@597: ALPHABETICAL_INDEX = YES flatmax@597: flatmax@597: # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then flatmax@597: # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns flatmax@597: # in which this list will be split (can be a number in the range [1..20]) flatmax@597: flatmax@597: COLS_IN_ALPHA_INDEX = 5 flatmax@597: flatmax@597: # In case all classes in a project start with a common prefix, all flatmax@597: # classes will be put under the same header in the alphabetical index. flatmax@597: # The IGNORE_PREFIX tag can be used to specify one or more prefixes that flatmax@597: # should be ignored while generating the index headers. flatmax@597: flatmax@597: IGNORE_PREFIX = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the HTML output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_HTML tag is set to YES (the default) Doxygen will flatmax@597: # generate HTML output. flatmax@597: flatmax@597: GENERATE_HTML = YES flatmax@597: flatmax@597: # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. flatmax@597: # If a relative path is entered the value of OUTPUT_DIRECTORY will be flatmax@597: # put in front of it. If left blank `html' will be used as the default path. flatmax@597: flatmax@597: HTML_OUTPUT = html flatmax@597: flatmax@597: # The HTML_FILE_EXTENSION tag can be used to specify the file extension for flatmax@597: # each generated HTML page (for example: .htm,.php,.asp). If it is left blank flatmax@597: # doxygen will generate files with .html extension. flatmax@597: flatmax@597: HTML_FILE_EXTENSION = .html flatmax@597: flatmax@597: # The HTML_HEADER tag can be used to specify a personal HTML header for flatmax@597: # each generated HTML page. If it is left blank doxygen will generate a flatmax@597: # standard header. Note that when using a custom header you are responsible flatmax@597: # for the proper inclusion of any scripts and style sheets that doxygen flatmax@597: # needs, which is dependent on the configuration options used. flatmax@597: # It is advised to generate a default header using "doxygen -w html flatmax@597: # header.html footer.html stylesheet.css YourConfigFile" and then modify flatmax@597: # that header. Note that the header is subject to change so you typically flatmax@597: # have to redo this when upgrading to a newer version of doxygen or when flatmax@597: # changing the value of configuration settings such as GENERATE_TREEVIEW! flatmax@597: flatmax@597: HTML_HEADER = flatmax@597: flatmax@597: # The HTML_FOOTER tag can be used to specify a personal HTML footer for flatmax@597: # each generated HTML page. If it is left blank doxygen will generate a flatmax@597: # standard footer. flatmax@597: flatmax@597: HTML_FOOTER = flatmax@597: flatmax@597: # The HTML_STYLESHEET tag can be used to specify a user-defined cascading flatmax@597: # style sheet that is used by each HTML page. It can be used to flatmax@597: # fine-tune the look of the HTML output. If the tag is left blank doxygen flatmax@597: # will generate a default style sheet. Note that doxygen will try to copy flatmax@597: # the style sheet file to the HTML output directory, so don't put your own flatmax@597: # style sheet in the HTML output directory as well, or it will be erased! flatmax@597: flatmax@597: HTML_STYLESHEET = flatmax@597: flatmax@597: # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or flatmax@597: # other source files which should be copied to the HTML output directory. Note flatmax@597: # that these files will be copied to the base HTML output directory. Use the flatmax@597: # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these flatmax@597: # files. In the HTML_STYLESHEET file, use the file name only. Also note that flatmax@597: # the files will be copied as-is; there are no commands or markers available. flatmax@597: flatmax@597: HTML_EXTRA_FILES = flatmax@597: flatmax@597: # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. flatmax@597: # Doxygen will adjust the colors in the style sheet and background images flatmax@597: # according to this color. Hue is specified as an angle on a colorwheel, flatmax@597: # see http://en.wikipedia.org/wiki/Hue for more information. flatmax@597: # For instance the value 0 represents red, 60 is yellow, 120 is green, flatmax@597: # 180 is cyan, 240 is blue, 300 purple, and 360 is red again. flatmax@597: # The allowed range is 0 to 359. flatmax@597: flatmax@597: HTML_COLORSTYLE_HUE = 220 flatmax@597: flatmax@597: # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of flatmax@597: # the colors in the HTML output. For a value of 0 the output will use flatmax@597: # grayscales only. A value of 255 will produce the most vivid colors. flatmax@597: flatmax@597: HTML_COLORSTYLE_SAT = 100 flatmax@597: flatmax@597: # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to flatmax@597: # the luminance component of the colors in the HTML output. Values below flatmax@597: # 100 gradually make the output lighter, whereas values above 100 make flatmax@597: # the output darker. The value divided by 100 is the actual gamma applied, flatmax@597: # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, flatmax@597: # and 100 does not change the gamma. flatmax@597: flatmax@597: HTML_COLORSTYLE_GAMMA = 80 flatmax@597: flatmax@597: # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML flatmax@597: # page will contain the date and time when the page was generated. Setting flatmax@597: # this to NO can help when comparing the output of multiple runs. flatmax@597: flatmax@597: HTML_TIMESTAMP = YES flatmax@597: flatmax@597: # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, flatmax@597: # files or namespaces will be aligned in HTML using tables. If set to flatmax@597: # NO a bullet list will be used. flatmax@597: flatmax@597: HTML_ALIGN_MEMBERS = YES flatmax@597: flatmax@597: # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML flatmax@597: # documentation will contain sections that can be hidden and shown after the flatmax@597: # page has loaded. For this to work a browser that supports flatmax@597: # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox flatmax@597: # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). flatmax@597: flatmax@597: HTML_DYNAMIC_SECTIONS = NO flatmax@597: flatmax@597: # If the GENERATE_DOCSET tag is set to YES, additional index files flatmax@597: # will be generated that can be used as input for Apple's Xcode 3 flatmax@597: # integrated development environment, introduced with OSX 10.5 (Leopard). flatmax@597: # To create a documentation set, doxygen will generate a Makefile in the flatmax@597: # HTML output directory. Running make will produce the docset in that flatmax@597: # directory and running "make install" will install the docset in flatmax@597: # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find flatmax@597: # it at startup. flatmax@597: # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html flatmax@597: # for more information. flatmax@597: flatmax@597: GENERATE_DOCSET = NO flatmax@597: flatmax@597: # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the flatmax@597: # feed. A documentation feed provides an umbrella under which multiple flatmax@597: # documentation sets from a single provider (such as a company or product suite) flatmax@597: # can be grouped. flatmax@597: flatmax@597: DOCSET_FEEDNAME = "Doxygen generated docs" flatmax@597: flatmax@597: # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that flatmax@597: # should uniquely identify the documentation set bundle. This should be a flatmax@597: # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen flatmax@597: # will append .docset to the name. flatmax@597: flatmax@597: DOCSET_BUNDLE_ID = org.doxygen.Project flatmax@597: flatmax@597: # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify flatmax@597: # the documentation publisher. This should be a reverse domain-name style flatmax@597: # string, e.g. com.mycompany.MyDocSet.documentation. flatmax@597: flatmax@597: DOCSET_PUBLISHER_ID = org.doxygen.Publisher flatmax@597: flatmax@597: # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. flatmax@597: flatmax@597: DOCSET_PUBLISHER_NAME = Publisher flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, additional index files flatmax@597: # will be generated that can be used as input for tools like the flatmax@597: # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) flatmax@597: # of the generated HTML documentation. flatmax@597: flatmax@597: GENERATE_HTMLHELP = NO flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can flatmax@597: # be used to specify the file name of the resulting .chm file. You flatmax@597: # can add a path in front of the file if the result should not be flatmax@597: # written to the html output directory. flatmax@597: flatmax@597: CHM_FILE = flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can flatmax@597: # be used to specify the location (absolute path including file name) of flatmax@597: # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run flatmax@597: # the HTML help compiler on the generated index.hhp. flatmax@597: flatmax@597: HHC_LOCATION = flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag flatmax@597: # controls if a separate .chi index file is generated (YES) or that flatmax@597: # it should be included in the master .chm file (NO). flatmax@597: flatmax@597: GENERATE_CHI = NO flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING flatmax@597: # is used to encode HtmlHelp index (hhk), content (hhc) and project file flatmax@597: # content. flatmax@597: flatmax@597: CHM_INDEX_ENCODING = flatmax@597: flatmax@597: # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag flatmax@597: # controls whether a binary table of contents is generated (YES) or a flatmax@597: # normal table of contents (NO) in the .chm file. flatmax@597: flatmax@597: BINARY_TOC = NO flatmax@597: flatmax@597: # The TOC_EXPAND flag can be set to YES to add extra items for group members flatmax@597: # to the contents of the HTML help documentation and to the tree view. flatmax@597: flatmax@597: TOC_EXPAND = NO flatmax@597: flatmax@597: # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and flatmax@597: # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated flatmax@597: # that can be used as input for Qt's qhelpgenerator to generate a flatmax@597: # Qt Compressed Help (.qch) of the generated HTML documentation. flatmax@597: flatmax@597: GENERATE_QHP = NO flatmax@597: flatmax@597: # If the QHG_LOCATION tag is specified, the QCH_FILE tag can flatmax@597: # be used to specify the file name of the resulting .qch file. flatmax@597: # The path specified is relative to the HTML output folder. flatmax@597: flatmax@597: QCH_FILE = flatmax@597: flatmax@597: # The QHP_NAMESPACE tag specifies the namespace to use when generating flatmax@597: # Qt Help Project output. For more information please see flatmax@597: # http://doc.trolltech.com/qthelpproject.html#namespace flatmax@597: flatmax@597: QHP_NAMESPACE = org.doxygen.Project flatmax@597: flatmax@597: # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating flatmax@597: # Qt Help Project output. For more information please see flatmax@597: # http://doc.trolltech.com/qthelpproject.html#virtual-folders flatmax@597: flatmax@597: QHP_VIRTUAL_FOLDER = doc flatmax@597: flatmax@597: # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to flatmax@597: # add. For more information please see flatmax@597: # http://doc.trolltech.com/qthelpproject.html#custom-filters flatmax@597: flatmax@597: QHP_CUST_FILTER_NAME = flatmax@597: flatmax@597: # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the flatmax@597: # custom filter to add. For more information please see flatmax@597: # flatmax@597: # Qt Help Project / Custom Filters. flatmax@597: flatmax@597: QHP_CUST_FILTER_ATTRS = flatmax@597: flatmax@597: # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this flatmax@597: # project's flatmax@597: # filter section matches. flatmax@597: # flatmax@597: # Qt Help Project / Filter Attributes. flatmax@597: flatmax@597: QHP_SECT_FILTER_ATTRS = flatmax@597: flatmax@597: # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can flatmax@597: # be used to specify the location of Qt's qhelpgenerator. flatmax@597: # If non-empty doxygen will try to run qhelpgenerator on the generated flatmax@597: # .qhp file. flatmax@597: flatmax@597: QHG_LOCATION = flatmax@597: flatmax@597: # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files flatmax@597: # will be generated, which together with the HTML files, form an Eclipse help flatmax@597: # plugin. To install this plugin and make it available under the help contents flatmax@597: # menu in Eclipse, the contents of the directory containing the HTML and XML flatmax@597: # files needs to be copied into the plugins directory of eclipse. The name of flatmax@597: # the directory within the plugins directory should be the same as flatmax@597: # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before flatmax@597: # the help appears. flatmax@597: flatmax@597: GENERATE_ECLIPSEHELP = NO flatmax@597: flatmax@597: # A unique identifier for the eclipse help plugin. When installing the plugin flatmax@597: # the directory name containing the HTML and XML files should also have flatmax@597: # this name. flatmax@597: flatmax@597: ECLIPSE_DOC_ID = org.doxygen.Project flatmax@597: flatmax@597: # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) flatmax@597: # at top of each HTML page. The value NO (the default) enables the index and flatmax@597: # the value YES disables it. Since the tabs have the same information as the flatmax@597: # navigation tree you can set this option to NO if you already set flatmax@597: # GENERATE_TREEVIEW to YES. flatmax@597: flatmax@597: DISABLE_INDEX = NO flatmax@597: flatmax@597: # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index flatmax@597: # structure should be generated to display hierarchical information. flatmax@597: # If the tag value is set to YES, a side panel will be generated flatmax@597: # containing a tree-like index structure (just like the one that flatmax@597: # is generated for HTML Help). For this to work a browser that supports flatmax@597: # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). flatmax@597: # Windows users are probably better off using the HTML help feature. flatmax@597: # Since the tree basically has the same information as the tab index you flatmax@597: # could consider to set DISABLE_INDEX to NO when enabling this option. flatmax@597: flatmax@597: GENERATE_TREEVIEW = YES flatmax@597: flatmax@597: # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values flatmax@597: # (range [0,1..20]) that doxygen will group on one line in the generated HTML flatmax@597: # documentation. Note that a value of 0 will completely suppress the enum flatmax@597: # values from appearing in the overview section. flatmax@597: flatmax@597: ENUM_VALUES_PER_LINE = 4 flatmax@597: flatmax@597: # By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, flatmax@597: # and Class Hierarchy pages using a tree view instead of an ordered list. flatmax@597: flatmax@597: USE_INLINE_TREES = NO flatmax@597: flatmax@597: # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be flatmax@597: # used to set the initial width (in pixels) of the frame in which the tree flatmax@597: # is shown. flatmax@597: flatmax@597: TREEVIEW_WIDTH = 250 flatmax@597: flatmax@597: # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open flatmax@597: # links to external symbols imported via tag files in a separate window. flatmax@597: flatmax@597: EXT_LINKS_IN_WINDOW = NO flatmax@597: flatmax@597: # Use this tag to change the font size of Latex formulas included flatmax@597: # as images in the HTML documentation. The default is 10. Note that flatmax@597: # when you change the font size after a successful doxygen run you need flatmax@597: # to manually remove any form_*.png images from the HTML output directory flatmax@597: # to force them to be regenerated. flatmax@597: flatmax@597: FORMULA_FONTSIZE = 10 flatmax@597: flatmax@597: # Use the FORMULA_TRANPARENT tag to determine whether or not the images flatmax@597: # generated for formulas are transparent PNGs. Transparent PNGs are flatmax@597: # not supported properly for IE 6.0, but are supported on all modern browsers. flatmax@597: # Note that when changing this option you need to delete any form_*.png files flatmax@597: # in the HTML output before the changes have effect. flatmax@597: flatmax@597: FORMULA_TRANSPARENT = YES flatmax@597: flatmax@597: # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax flatmax@597: # (see http://www.mathjax.org) which uses client side Javascript for the flatmax@597: # rendering instead of using prerendered bitmaps. Use this if you do not flatmax@597: # have LaTeX installed or if you want to formulas look prettier in the HTML flatmax@597: # output. When enabled you also need to install MathJax separately and flatmax@597: # configure the path to it using the MATHJAX_RELPATH option. flatmax@597: flatmax@597: USE_MATHJAX = NO flatmax@597: flatmax@597: # When MathJax is enabled you need to specify the location relative to the flatmax@597: # HTML output directory using the MATHJAX_RELPATH option. The destination flatmax@597: # directory should contain the MathJax.js script. For instance, if the mathjax flatmax@597: # directory is located at the same level as the HTML output directory, then flatmax@597: # MATHJAX_RELPATH should be ../mathjax. The default value points to the flatmax@597: # mathjax.org site, so you can quickly see the result without installing flatmax@597: # MathJax, but it is strongly recommended to install a local copy of MathJax flatmax@597: # before deployment. flatmax@597: flatmax@597: MATHJAX_RELPATH = http://www.mathjax.org/mathjax flatmax@597: flatmax@597: # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension flatmax@597: # names that should be enabled during MathJax rendering. flatmax@597: flatmax@597: MATHJAX_EXTENSIONS = flatmax@597: flatmax@597: # When the SEARCHENGINE tag is enabled doxygen will generate a search box flatmax@597: # for the HTML output. The underlying search engine uses javascript flatmax@597: # and DHTML and should work on any modern browser. Note that when using flatmax@597: # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets flatmax@597: # (GENERATE_DOCSET) there is already a search function so this one should flatmax@597: # typically be disabled. For large projects the javascript based search engine flatmax@597: # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. flatmax@597: flatmax@597: SEARCHENGINE = YES flatmax@597: flatmax@597: # When the SERVER_BASED_SEARCH tag is enabled the search engine will be flatmax@597: # implemented using a PHP enabled web server instead of at the web client flatmax@597: # using Javascript. Doxygen will generate the search PHP script and index flatmax@597: # file to put on the web server. The advantage of the server flatmax@597: # based approach is that it scales better to large projects and allows flatmax@597: # full text search. The disadvantages are that it is more difficult to setup flatmax@597: # and does not have live searching capabilities. flatmax@597: flatmax@597: SERVER_BASED_SEARCH = NO flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the LaTeX output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will flatmax@597: # generate Latex output. flatmax@597: flatmax@597: GENERATE_LATEX = NO flatmax@597: flatmax@597: # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. flatmax@597: # If a relative path is entered the value of OUTPUT_DIRECTORY will be flatmax@597: # put in front of it. If left blank `latex' will be used as the default path. flatmax@597: flatmax@597: LATEX_OUTPUT = latex flatmax@597: flatmax@597: # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be flatmax@597: # invoked. If left blank `latex' will be used as the default command name. flatmax@597: # Note that when enabling USE_PDFLATEX this option is only used for flatmax@597: # generating bitmaps for formulas in the HTML output, but not in the flatmax@597: # Makefile that is written to the output directory. flatmax@597: flatmax@597: LATEX_CMD_NAME = latex flatmax@597: flatmax@597: # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to flatmax@597: # generate index for LaTeX. If left blank `makeindex' will be used as the flatmax@597: # default command name. flatmax@597: flatmax@597: MAKEINDEX_CMD_NAME = makeindex flatmax@597: flatmax@597: # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact flatmax@597: # LaTeX documents. This may be useful for small projects and may help to flatmax@597: # save some trees in general. flatmax@597: flatmax@597: COMPACT_LATEX = NO flatmax@597: flatmax@597: # The PAPER_TYPE tag can be used to set the paper type that is used flatmax@597: # by the printer. Possible values are: a4, letter, legal and flatmax@597: # executive. If left blank a4wide will be used. flatmax@597: flatmax@597: PAPER_TYPE = a4 flatmax@597: flatmax@597: # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX flatmax@597: # packages that should be included in the LaTeX output. flatmax@597: flatmax@597: EXTRA_PACKAGES = flatmax@597: flatmax@597: # The LATEX_HEADER tag can be used to specify a personal LaTeX header for flatmax@597: # the generated latex document. The header should contain everything until flatmax@597: # the first chapter. If it is left blank doxygen will generate a flatmax@597: # standard header. Notice: only use this tag if you know what you are doing! flatmax@597: flatmax@597: LATEX_HEADER = flatmax@597: flatmax@597: # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for flatmax@597: # the generated latex document. The footer should contain everything after flatmax@597: # the last chapter. If it is left blank doxygen will generate a flatmax@597: # standard footer. Notice: only use this tag if you know what you are doing! flatmax@597: flatmax@597: LATEX_FOOTER = flatmax@597: flatmax@597: # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated flatmax@597: # is prepared for conversion to pdf (using ps2pdf). The pdf file will flatmax@597: # contain links (just like the HTML output) instead of page references flatmax@597: # This makes the output suitable for online browsing using a pdf viewer. flatmax@597: flatmax@597: PDF_HYPERLINKS = YES flatmax@597: flatmax@597: # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of flatmax@597: # plain latex in the generated Makefile. Set this option to YES to get a flatmax@597: # higher quality PDF documentation. flatmax@597: flatmax@597: USE_PDFLATEX = YES flatmax@597: flatmax@597: # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. flatmax@597: # command to the generated LaTeX files. This will instruct LaTeX to keep flatmax@597: # running if errors occur, instead of asking the user for help. flatmax@597: # This option is also used when generating formulas in HTML. flatmax@597: flatmax@597: LATEX_BATCHMODE = NO flatmax@597: flatmax@597: # If LATEX_HIDE_INDICES is set to YES then doxygen will not flatmax@597: # include the index chapters (such as File Index, Compound Index, etc.) flatmax@597: # in the output. flatmax@597: flatmax@597: LATEX_HIDE_INDICES = NO flatmax@597: flatmax@597: # If LATEX_SOURCE_CODE is set to YES then doxygen will include flatmax@597: # source code with syntax highlighting in the LaTeX output. flatmax@597: # Note that which sources are shown also depends on other settings flatmax@597: # such as SOURCE_BROWSER. flatmax@597: flatmax@597: LATEX_SOURCE_CODE = NO flatmax@597: flatmax@597: # The LATEX_BIB_STYLE tag can be used to specify the style to use for the flatmax@597: # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See flatmax@597: # http://en.wikipedia.org/wiki/BibTeX for more info. flatmax@597: flatmax@597: LATEX_BIB_STYLE = plain flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the RTF output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output flatmax@597: # The RTF output is optimized for Word 97 and may not look very pretty with flatmax@597: # other RTF readers or editors. flatmax@597: flatmax@597: GENERATE_RTF = NO flatmax@597: flatmax@597: # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. flatmax@597: # If a relative path is entered the value of OUTPUT_DIRECTORY will be flatmax@597: # put in front of it. If left blank `rtf' will be used as the default path. flatmax@597: flatmax@597: RTF_OUTPUT = rtf flatmax@597: flatmax@597: # If the COMPACT_RTF tag is set to YES Doxygen generates more compact flatmax@597: # RTF documents. This may be useful for small projects and may help to flatmax@597: # save some trees in general. flatmax@597: flatmax@597: COMPACT_RTF = NO flatmax@597: flatmax@597: # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated flatmax@597: # will contain hyperlink fields. The RTF file will flatmax@597: # contain links (just like the HTML output) instead of page references. flatmax@597: # This makes the output suitable for online browsing using WORD or other flatmax@597: # programs which support those fields. flatmax@597: # Note: wordpad (write) and others do not support links. flatmax@597: flatmax@597: RTF_HYPERLINKS = NO flatmax@597: flatmax@597: # Load style sheet definitions from file. Syntax is similar to doxygen's flatmax@597: # config file, i.e. a series of assignments. You only have to provide flatmax@597: # replacements, missing definitions are set to their default value. flatmax@597: flatmax@597: RTF_STYLESHEET_FILE = flatmax@597: flatmax@597: # Set optional variables used in the generation of an rtf document. flatmax@597: # Syntax is similar to doxygen's config file. flatmax@597: flatmax@597: RTF_EXTENSIONS_FILE = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the man page output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_MAN tag is set to YES (the default) Doxygen will flatmax@597: # generate man pages flatmax@597: flatmax@597: GENERATE_MAN = NO flatmax@597: flatmax@597: # The MAN_OUTPUT tag is used to specify where the man pages will be put. flatmax@597: # If a relative path is entered the value of OUTPUT_DIRECTORY will be flatmax@597: # put in front of it. If left blank `man' will be used as the default path. flatmax@597: flatmax@597: MAN_OUTPUT = man flatmax@597: flatmax@597: # The MAN_EXTENSION tag determines the extension that is added to flatmax@597: # the generated man pages (default is the subroutine's section .3) flatmax@597: flatmax@597: MAN_EXTENSION = .3 flatmax@597: flatmax@597: # If the MAN_LINKS tag is set to YES and Doxygen generates man output, flatmax@597: # then it will generate one additional man file for each entity flatmax@597: # documented in the real man page(s). These additional files flatmax@597: # only source the real man page, but without them the man command flatmax@597: # would be unable to find the correct page. The default is NO. flatmax@597: flatmax@597: MAN_LINKS = NO flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the XML output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_XML tag is set to YES Doxygen will flatmax@597: # generate an XML file that captures the structure of flatmax@597: # the code including all documentation. flatmax@597: flatmax@597: GENERATE_XML = NO flatmax@597: flatmax@597: # The XML_OUTPUT tag is used to specify where the XML pages will be put. flatmax@597: # If a relative path is entered the value of OUTPUT_DIRECTORY will be flatmax@597: # put in front of it. If left blank `xml' will be used as the default path. flatmax@597: flatmax@597: XML_OUTPUT = xml flatmax@597: flatmax@597: # The XML_SCHEMA tag can be used to specify an XML schema, flatmax@597: # which can be used by a validating XML parser to check the flatmax@597: # syntax of the XML files. flatmax@597: flatmax@597: XML_SCHEMA = flatmax@597: flatmax@597: # The XML_DTD tag can be used to specify an XML DTD, flatmax@597: # which can be used by a validating XML parser to check the flatmax@597: # syntax of the XML files. flatmax@597: flatmax@597: XML_DTD = flatmax@597: flatmax@597: # If the XML_PROGRAMLISTING tag is set to YES Doxygen will flatmax@597: # dump the program listings (including syntax highlighting flatmax@597: # and cross-referencing information) to the XML output. Note that flatmax@597: # enabling this will significantly increase the size of the XML output. flatmax@597: flatmax@597: XML_PROGRAMLISTING = YES flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options for the AutoGen Definitions output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will flatmax@597: # generate an AutoGen Definitions (see autogen.sf.net) file flatmax@597: # that captures the structure of the code including all flatmax@597: # documentation. Note that this feature is still experimental flatmax@597: # and incomplete at the moment. flatmax@597: flatmax@597: GENERATE_AUTOGEN_DEF = NO flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # configuration options related to the Perl module output flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the GENERATE_PERLMOD tag is set to YES Doxygen will flatmax@597: # generate a Perl module file that captures the structure of flatmax@597: # the code including all documentation. Note that this flatmax@597: # feature is still experimental and incomplete at the flatmax@597: # moment. flatmax@597: flatmax@597: GENERATE_PERLMOD = NO flatmax@597: flatmax@597: # If the PERLMOD_LATEX tag is set to YES Doxygen will generate flatmax@597: # the necessary Makefile rules, Perl scripts and LaTeX code to be able flatmax@597: # to generate PDF and DVI output from the Perl module output. flatmax@597: flatmax@597: PERLMOD_LATEX = NO flatmax@597: flatmax@597: # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be flatmax@597: # nicely formatted so it can be parsed by a human reader. This is useful flatmax@597: # if you want to understand what is going on. On the other hand, if this flatmax@597: # tag is set to NO the size of the Perl module output will be much smaller flatmax@597: # and Perl will parse it just the same. flatmax@597: flatmax@597: PERLMOD_PRETTY = YES flatmax@597: flatmax@597: # The names of the make variables in the generated doxyrules.make file flatmax@597: # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. flatmax@597: # This is useful so different doxyrules.make files included by the same flatmax@597: # Makefile don't overwrite each other's variables. flatmax@597: flatmax@597: PERLMOD_MAKEVAR_PREFIX = flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # Configuration options related to the preprocessor flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will flatmax@597: # evaluate all C-preprocessor directives found in the sources and include flatmax@597: # files. flatmax@597: flatmax@597: ENABLE_PREPROCESSING = YES flatmax@597: flatmax@597: # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro flatmax@597: # names in the source code. If set to NO (the default) only conditional flatmax@597: # compilation will be performed. Macro expansion can be done in a controlled flatmax@597: # way by setting EXPAND_ONLY_PREDEF to YES. flatmax@597: flatmax@597: MACRO_EXPANSION = NO flatmax@597: flatmax@597: # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES flatmax@597: # then the macro expansion is limited to the macros specified with the flatmax@597: # PREDEFINED and EXPAND_AS_DEFINED tags. flatmax@597: flatmax@597: EXPAND_ONLY_PREDEF = NO flatmax@597: flatmax@597: # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files flatmax@597: # pointed to by INCLUDE_PATH will be searched when a #include is found. flatmax@597: flatmax@597: SEARCH_INCLUDES = YES flatmax@597: flatmax@597: # The INCLUDE_PATH tag can be used to specify one or more directories that flatmax@597: # contain include files that are not input files but should be processed by flatmax@597: # the preprocessor. flatmax@597: flatmax@597: INCLUDE_PATH = flatmax@597: flatmax@597: # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard flatmax@597: # patterns (like *.h and *.hpp) to filter out the header-files in the flatmax@597: # directories. If left blank, the patterns specified with FILE_PATTERNS will flatmax@597: # be used. flatmax@597: flatmax@597: INCLUDE_FILE_PATTERNS = flatmax@597: flatmax@597: # The PREDEFINED tag can be used to specify one or more macro names that flatmax@597: # are defined before the preprocessor is started (similar to the -D option of flatmax@597: # gcc). The argument of the tag is a list of macros of the form: name flatmax@597: # or name=definition (no spaces). If the definition and the = are flatmax@597: # omitted =1 is assumed. To prevent a macro definition from being flatmax@597: # undefined via #undef or recursively expanded use the := operator flatmax@597: # instead of the = operator. flatmax@597: flatmax@597: PREDEFINED = flatmax@597: flatmax@597: # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then flatmax@597: # this tag can be used to specify a list of macro names that should be expanded. flatmax@597: # The macro definition that is found in the sources will be used. flatmax@597: # Use the PREDEFINED tag if you want to use a different macro definition that flatmax@597: # overrules the definition found in the source code. flatmax@597: flatmax@597: EXPAND_AS_DEFINED = flatmax@597: flatmax@597: # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then flatmax@597: # doxygen's preprocessor will remove all references to function-like macros flatmax@597: # that are alone on a line, have an all uppercase name, and do not end with a flatmax@597: # semicolon, because these will confuse the parser if not removed. flatmax@597: flatmax@597: SKIP_FUNCTION_MACROS = YES flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # Configuration::additions related to external references flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # The TAGFILES option can be used to specify one or more tagfiles. flatmax@597: # Optionally an initial location of the external documentation flatmax@597: # can be added for each tagfile. The format of a tag file without flatmax@597: # this location is as follows: flatmax@597: # TAGFILES = file1 file2 ... flatmax@597: # Adding location for the tag files is done as follows: flatmax@597: # TAGFILES = file1=loc1 "file2 = loc2" ... flatmax@597: # where "loc1" and "loc2" can be relative or absolute paths or flatmax@597: # URLs. If a location is present for each tag, the installdox tool flatmax@597: # does not have to be run to correct the links. flatmax@597: # Note that each tag file must have a unique name flatmax@597: # (where the name does NOT include the path) flatmax@597: # If a tag file is not located in the directory in which doxygen flatmax@597: # is run, you must also specify the path to the tagfile here. flatmax@597: flatmax@597: TAGFILES = flatmax@597: flatmax@597: # When a file name is specified after GENERATE_TAGFILE, doxygen will create flatmax@597: # a tag file that is based on the input files it reads. flatmax@597: flatmax@597: GENERATE_TAGFILE = flatmax@597: flatmax@597: # If the ALLEXTERNALS tag is set to YES all external classes will be listed flatmax@597: # in the class index. If set to NO only the inherited external classes flatmax@597: # will be listed. flatmax@597: flatmax@597: ALLEXTERNALS = NO flatmax@597: flatmax@597: # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed flatmax@597: # in the modules index. If set to NO, only the current project's groups will flatmax@597: # be listed. flatmax@597: flatmax@597: EXTERNAL_GROUPS = YES flatmax@597: flatmax@597: # The PERL_PATH should be the absolute path and name of the perl script flatmax@597: # interpreter (i.e. the result of `which perl'). flatmax@597: flatmax@597: PERL_PATH = /usr/bin/perl flatmax@597: flatmax@597: #--------------------------------------------------------------------------- flatmax@597: # Configuration options related to the dot tool flatmax@597: #--------------------------------------------------------------------------- flatmax@597: flatmax@597: # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will flatmax@597: # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base flatmax@597: # or super classes. Setting the tag to NO turns the diagrams off. Note that flatmax@597: # this option also works with HAVE_DOT disabled, but it is recommended to flatmax@597: # install and use dot, since it yields more powerful graphs. flatmax@597: flatmax@597: CLASS_DIAGRAMS = NO flatmax@597: flatmax@597: # You can define message sequence charts within doxygen comments using the \msc flatmax@597: # command. Doxygen will then run the mscgen tool (see flatmax@597: # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the flatmax@597: # documentation. The MSCGEN_PATH tag allows you to specify the directory where flatmax@597: # the mscgen tool resides. If left empty the tool is assumed to be found in the flatmax@597: # default search path. flatmax@597: flatmax@597: MSCGEN_PATH = flatmax@597: flatmax@597: # If set to YES, the inheritance and collaboration graphs will hide flatmax@597: # inheritance and usage relations if the target is undocumented flatmax@597: # or is not a class. flatmax@597: flatmax@597: HIDE_UNDOC_RELATIONS = YES flatmax@597: flatmax@597: # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is flatmax@597: # available from the path. This tool is part of Graphviz, a graph visualization flatmax@597: # toolkit from AT&T and Lucent Bell Labs. The other options in this section flatmax@597: # have no effect if this option is set to NO (the default) flatmax@597: flatmax@597: HAVE_DOT = YES flatmax@597: flatmax@597: # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is flatmax@597: # allowed to run in parallel. When set to 0 (the default) doxygen will flatmax@597: # base this on the number of processors available in the system. You can set it flatmax@597: # explicitly to a value larger than 0 to get control over the balance flatmax@597: # between CPU load and processing speed. flatmax@597: flatmax@597: DOT_NUM_THREADS = 0 flatmax@597: flatmax@597: # By default doxygen will use the Helvetica font for all dot files that flatmax@597: # doxygen generates. When you want a differently looking font you can specify flatmax@597: # the font name using DOT_FONTNAME. You need to make sure dot is able to find flatmax@597: # the font, which can be done by putting it in a standard location or by setting flatmax@597: # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the flatmax@597: # directory containing the font. flatmax@597: flatmax@597: DOT_FONTNAME = Helvetica flatmax@597: flatmax@597: # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. flatmax@597: # The default size is 10pt. flatmax@597: flatmax@597: DOT_FONTSIZE = 10 flatmax@597: flatmax@597: # By default doxygen will tell dot to use the Helvetica font. flatmax@597: # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to flatmax@597: # set the path where dot can find it. flatmax@597: flatmax@597: DOT_FONTPATH = flatmax@597: flatmax@597: # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen flatmax@597: # will generate a graph for each documented class showing the direct and flatmax@597: # indirect inheritance relations. Setting this tag to YES will force the flatmax@597: # CLASS_DIAGRAMS tag to NO. flatmax@597: flatmax@597: CLASS_GRAPH = YES flatmax@597: flatmax@597: # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen flatmax@597: # will generate a graph for each documented class showing the direct and flatmax@597: # indirect implementation dependencies (inheritance, containment, and flatmax@597: # class references variables) of the class with other documented classes. flatmax@597: flatmax@597: COLLABORATION_GRAPH = YES flatmax@597: flatmax@597: # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen flatmax@597: # will generate a graph for groups, showing the direct groups dependencies flatmax@597: flatmax@597: GROUP_GRAPHS = YES flatmax@597: flatmax@597: # If the UML_LOOK tag is set to YES doxygen will generate inheritance and flatmax@597: # collaboration diagrams in a style similar to the OMG's Unified Modeling flatmax@597: # Language. flatmax@597: flatmax@597: UML_LOOK = NO flatmax@597: flatmax@597: # If set to YES, the inheritance and collaboration graphs will show the flatmax@597: # relations between templates and their instances. flatmax@597: flatmax@597: TEMPLATE_RELATIONS = NO flatmax@597: flatmax@597: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT flatmax@597: # tags are set to YES then doxygen will generate a graph for each documented flatmax@597: # file showing the direct and indirect include dependencies of the file with flatmax@597: # other documented files. flatmax@597: flatmax@597: INCLUDE_GRAPH = YES flatmax@597: flatmax@597: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and flatmax@597: # HAVE_DOT tags are set to YES then doxygen will generate a graph for each flatmax@597: # documented header file showing the documented files that directly or flatmax@597: # indirectly include this file. flatmax@597: flatmax@597: INCLUDED_BY_GRAPH = YES flatmax@597: flatmax@597: # If the CALL_GRAPH and HAVE_DOT options are set to YES then flatmax@597: # doxygen will generate a call dependency graph for every global function flatmax@597: # or class method. Note that enabling this option will significantly increase flatmax@597: # the time of a run. So in most cases it will be better to enable call graphs flatmax@597: # for selected functions only using the \callgraph command. flatmax@597: flatmax@597: CALL_GRAPH = NO flatmax@597: flatmax@597: # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then flatmax@597: # doxygen will generate a caller dependency graph for every global function flatmax@597: # or class method. Note that enabling this option will significantly increase flatmax@597: # the time of a run. So in most cases it will be better to enable caller flatmax@597: # graphs for selected functions only using the \callergraph command. flatmax@597: flatmax@597: CALLER_GRAPH = NO flatmax@597: flatmax@597: # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen flatmax@597: # will generate a graphical hierarchy of all classes instead of a textual one. flatmax@597: flatmax@597: GRAPHICAL_HIERARCHY = YES flatmax@597: flatmax@597: # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES flatmax@597: # then doxygen will show the dependencies a directory has on other directories flatmax@597: # in a graphical way. The dependency relations are determined by the #include flatmax@597: # relations between the files in the directories. flatmax@597: flatmax@597: DIRECTORY_GRAPH = YES flatmax@597: flatmax@597: # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images flatmax@597: # generated by dot. Possible values are svg, png, jpg, or gif. flatmax@597: # If left blank png will be used. If you choose svg you need to set flatmax@597: # HTML_FILE_EXTENSION to xhtml in order to make the SVG files flatmax@597: # visible in IE 9+ (other browsers do not have this requirement). flatmax@597: flatmax@597: DOT_IMAGE_FORMAT = png flatmax@597: flatmax@597: # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to flatmax@597: # enable generation of interactive SVG images that allow zooming and panning. flatmax@597: # Note that this requires a modern browser other than Internet Explorer. flatmax@597: # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you flatmax@597: # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files flatmax@597: # visible. Older versions of IE do not have SVG support. flatmax@597: flatmax@597: INTERACTIVE_SVG = NO flatmax@597: flatmax@597: # The tag DOT_PATH can be used to specify the path where the dot tool can be flatmax@597: # found. If left blank, it is assumed the dot tool can be found in the path. flatmax@597: flatmax@597: DOT_PATH = flatmax@597: flatmax@597: # The DOTFILE_DIRS tag can be used to specify one or more directories that flatmax@597: # contain dot files that are included in the documentation (see the flatmax@597: # \dotfile command). flatmax@597: flatmax@597: DOTFILE_DIRS = flatmax@597: flatmax@597: # The MSCFILE_DIRS tag can be used to specify one or more directories that flatmax@597: # contain msc files that are included in the documentation (see the flatmax@597: # \mscfile command). flatmax@597: flatmax@597: MSCFILE_DIRS = flatmax@597: flatmax@597: # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of flatmax@597: # nodes that will be shown in the graph. If the number of nodes in a graph flatmax@597: # becomes larger than this value, doxygen will truncate the graph, which is flatmax@597: # visualized by representing a node as a red box. Note that doxygen if the flatmax@597: # number of direct children of the root node in a graph is already larger than flatmax@597: # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note flatmax@597: # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. flatmax@597: flatmax@597: DOT_GRAPH_MAX_NODES = 50 flatmax@597: flatmax@597: # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the flatmax@597: # graphs generated by dot. A depth value of 3 means that only nodes reachable flatmax@597: # from the root by following a path via at most 3 edges will be shown. Nodes flatmax@597: # that lay further from the root node will be omitted. Note that setting this flatmax@597: # option to 1 or 2 may greatly reduce the computation time needed for large flatmax@597: # code bases. Also note that the size of a graph can be further restricted by flatmax@597: # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. flatmax@597: flatmax@597: MAX_DOT_GRAPH_DEPTH = 0 flatmax@597: flatmax@597: # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent flatmax@597: # background. This is disabled by default, because dot on Windows does not flatmax@597: # seem to support this out of the box. Warning: Depending on the platform used, flatmax@597: # enabling this option may lead to badly anti-aliased labels on the edges of flatmax@597: # a graph (i.e. they become hard to read). flatmax@597: flatmax@597: DOT_TRANSPARENT = NO flatmax@597: flatmax@597: # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output flatmax@597: # files in one run (i.e. multiple -o and -T options on the command line). This flatmax@597: # makes dot run faster, but since only newer versions of dot (>1.8.10) flatmax@597: # support this, this feature is disabled by default. flatmax@597: flatmax@597: DOT_MULTI_TARGETS = YES flatmax@597: flatmax@597: # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will flatmax@597: # generate a legend page explaining the meaning of the various boxes and flatmax@597: # arrows in the dot generated graphs. flatmax@597: flatmax@597: GENERATE_LEGEND = YES flatmax@597: flatmax@597: # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will flatmax@597: # remove the intermediate dot files that are used to generate flatmax@597: # the various graphs. flatmax@597: flatmax@597: DOT_CLEANUP = YES