fp@0: #################################################################
fp@0: #
fp@0: #  Doxyfile
fp@0: #
fp@0: #  IgH EtherCAT-Treiber
fp@0: #
fp@0: #  $LastChangedDate$
fp@0: #  $Author$
fp@0: #
fp@0: #################################################################
fp@0: 
fp@0: # Doxyfile 1.2.18
fp@0: 
fp@0: # This file describes the settings to be used by the documentation system
fp@0: # doxygen (www.doxygen.org) for a project
fp@0: #
fp@0: # All text after a hash (#) is considered a comment and will be ignored
fp@0: # The format is:
fp@0: #       TAG = value [value, ...]
fp@0: # For lists items can also be appended using:
fp@0: #       TAG += value [value, ...]
fp@0: # Values that contain spaces should be placed between quotes (" ")
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # General configuration options
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
fp@0: # by quotes) that should identify the project.
fp@0: 
fp@0: PROJECT_NAME           = EtherCAT
fp@0: 
fp@0: # The PROJECT_NUMBER tag can be used to enter a project or revision number. 
fp@0: # This could be handy for archiving the generated documentation or 
fp@0: # if some version control system is used.
fp@0: 
fp@0: PROJECT_NUMBER         = 0.1
fp@0: 
fp@0: # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
fp@0: # base path where the generated documentation will be put. 
fp@0: # If a relative path is entered, it will be relative to the location 
fp@0: # where doxygen was started. If left blank the current directory will be used.
fp@0: 
fp@0: OUTPUT_DIRECTORY       = ../src-docs
fp@0: 
fp@0: # The OUTPUT_LANGUAGE tag is used to specify the language in which all 
fp@0: # documentation generated by doxygen is written. Doxygen will use this 
fp@0: # information to generate all constant output in the proper language. 
fp@0: # The default language is English, other supported languages are: 
fp@0: # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, 
fp@0: # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en 
fp@0: # (Japanese with english messages), Korean, Norwegian, Polish, Portuguese, 
fp@0: # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish and Ukrainian.
fp@0: 
fp@13: OUTPUT_LANGUAGE        =
fp@0: 
fp@0: # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
fp@0: # documentation are documented, even if no documentation was available. 
fp@0: # Private class members and static file members will be hidden unless 
fp@0: # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
fp@0: 
fp@0: EXTRACT_ALL            = YES
fp@0: 
fp@0: # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
fp@0: # will be included in the documentation.
fp@0: 
fp@0: EXTRACT_PRIVATE        = YES
fp@0: 
fp@0: # If the EXTRACT_STATIC tag is set to YES all static members of a file 
fp@0: # will be included in the documentation.
fp@0: 
fp@0: EXTRACT_STATIC         = YES
fp@0: 
fp@0: # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
fp@0: # defined locally in source files will be included in the documentation. 
fp@0: # If set to NO only classes defined in header files are included.
fp@0: 
fp@0: EXTRACT_LOCAL_CLASSES  = YES
fp@0: 
fp@0: # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
fp@0: # undocumented members of documented classes, files or namespaces. 
fp@0: # If set to NO (the default) these members will be included in the 
fp@0: # various overviews, but no documentation section is generated. 
fp@0: # This option has no effect if EXTRACT_ALL is enabled.
fp@0: 
fp@0: HIDE_UNDOC_MEMBERS     = NO
fp@0: 
fp@0: # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
fp@0: # undocumented classes that are normally visible in the class hierarchy. 
fp@0: # If set to NO (the default) these class will be included in the various 
fp@0: # overviews. This option has no effect if EXTRACT_ALL is enabled.
fp@0: 
fp@0: HIDE_UNDOC_CLASSES     = YES
fp@0: 
fp@0: # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
fp@0: # friend (class|struct|union) declarations. 
fp@0: # If set to NO (the default) these declarations will be included in the 
fp@0: # documentation.
fp@0: 
fp@0: HIDE_FRIEND_COMPOUNDS  = NO
fp@0: 
fp@0: # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
fp@0: # include brief member descriptions after the members that are listed in 
fp@0: # the file and class documentation (similar to JavaDoc). 
fp@0: # Set to NO to disable this.
fp@0: 
fp@0: BRIEF_MEMBER_DESC      = YES
fp@0: 
fp@0: # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
fp@0: # the brief description of a member or function before the detailed description. 
fp@0: # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
fp@0: # brief descriptions will be completely suppressed.
fp@0: 
fp@0: REPEAT_BRIEF           = YES
fp@0: 
fp@0: # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
fp@0: # Doxygen will generate a detailed section even if there is only a brief 
fp@0: # description.
fp@0: 
fp@0: ALWAYS_DETAILED_SEC    = NO
fp@0: 
fp@0: # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
fp@0: # members of a class in the documentation of that class as if those members were 
fp@0: # ordinary class members. Constructors, destructors and assignment operators of 
fp@0: # the base classes will not be shown.
fp@0: 
fp@0: INLINE_INHERITED_MEMB  = NO
fp@0: 
fp@0: # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
fp@0: # path before files name in the file list and in the header files. If set 
fp@0: # to NO the shortest path that makes the file name unique will be used.
fp@0: 
fp@0: FULL_PATH_NAMES        = NO
fp@0: 
fp@0: # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
fp@0: # can be used to strip a user defined part of the path. Stripping is 
fp@0: # only done if one of the specified strings matches the left-hand part of 
fp@0: # the path. It is allowed to use relative paths in the argument list.
fp@0: 
fp@0: STRIP_FROM_PATH        = 
fp@0: 
fp@0: # The INTERNAL_DOCS tag determines if documentation 
fp@0: # that is typed after a \internal command is included. If the tag is set 
fp@0: # to NO (the default) then the documentation will be excluded. 
fp@0: # Set it to YES to include the internal documentation.
fp@0: 
fp@0: INTERNAL_DOCS          = NO
fp@0: 
fp@0: # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
fp@0: # doxygen to hide any special comment blocks from generated source code 
fp@0: # fragments. Normal C and C++ comments will always remain visible.
fp@0: 
fp@0: STRIP_CODE_COMMENTS    = YES
fp@0: 
fp@0: # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
fp@0: # file names in lower case letters. If set to YES upper case letters are also 
fp@0: # allowed. This is useful if you have classes or files whose names only differ 
fp@0: # in case and if your file system supports case sensitive file names. Windows 
fp@0: # users are adviced to set this option to NO.
fp@0: 
fp@0: CASE_SENSE_NAMES       = YES
fp@0: 
fp@0: # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
fp@0: # (but less readable) file names. This can be useful is your file systems 
fp@0: # doesn't support long names like on DOS, Mac, or CD-ROM.
fp@0: 
fp@0: SHORT_NAMES            = NO
fp@0: 
fp@0: # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
fp@0: # will show members with their full class and namespace scopes in the 
fp@0: # documentation. If set to YES the scope will be hidden.
fp@0: 
fp@0: HIDE_SCOPE_NAMES       = NO
fp@0: 
fp@0: # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
fp@0: # will generate a verbatim copy of the header file for each class for 
fp@0: # which an include is specified. Set to NO to disable this.
fp@0: 
fp@0: VERBATIM_HEADERS       = YES
fp@0: 
fp@0: # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
fp@0: # will put list of the files that are included by a file in the documentation 
fp@0: # of that file.
fp@0: 
fp@0: SHOW_INCLUDE_FILES     = NO
fp@0: 
fp@0: # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
fp@0: # will interpret the first line (until the first dot) of a JavaDoc-style 
fp@0: # comment as the brief description. If set to NO, the JavaDoc 
fp@0: # comments  will behave just like the Qt-style comments (thus requiring an 
fp@0: # explict @brief command for a brief description.
fp@0: 
fp@0: JAVADOC_AUTOBRIEF      = YES
fp@0: 
fp@0: # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
fp@0: # treat a multi-line C++ special comment block (i.e. a block of //! or /// 
fp@0: # comments) as a brief description. This used to be the default behaviour. 
fp@0: # The new default is to treat a multi-line C++ comment block as a detailed 
fp@0: # description. Set this tag to YES if you prefer the old behaviour instead.
fp@0: 
fp@0: MULTILINE_CPP_IS_BRIEF = YES
fp@0: 
fp@0: # If the DETAILS_AT_TOP tag is set to YES then Doxygen 
fp@0: # will output the detailed description near the top, like JavaDoc.
fp@0: # If set to NO, the detailed description appears after the member 
fp@0: # documentation.
fp@0: 
fp@0: DETAILS_AT_TOP         = YES
fp@0: 
fp@0: # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
fp@0: # member inherits the documentation from any documented member that it 
fp@0: # reimplements.
fp@0: 
fp@0: INHERIT_DOCS           = YES
fp@0: 
fp@0: # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
fp@0: # is inserted in the documentation for inline members.
fp@0: 
fp@0: INLINE_INFO            = YES
fp@0: 
fp@0: # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
fp@0: # will sort the (detailed) documentation of file and class members 
fp@0: # alphabetically by member name. If set to NO the members will appear in 
fp@0: # declaration order.
fp@0: 
fp@0: SORT_MEMBER_DOCS       = NO
fp@0: 
fp@0: # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
fp@0: # tag is set to YES, then doxygen will reuse the documentation of the first 
fp@0: # member in the group (if any) for the other members of the group. By default 
fp@0: # all members of a group must be documented explicitly.
fp@0: 
fp@0: DISTRIBUTE_GROUP_DOC   = NO
fp@0: 
fp@0: # The TAB_SIZE tag can be used to set the number of spaces in a tab. 
fp@0: # Doxygen uses this value to replace tabs by spaces in code fragments.
fp@0: 
fp@0: TAB_SIZE               = 3
fp@0: 
fp@0: # The GENERATE_TODOLIST tag can be used to enable (YES) or 
fp@0: # disable (NO) the todo list. This list is created by putting \todo 
fp@0: # commands in the documentation.
fp@0: 
fp@0: GENERATE_TODOLIST      = YES
fp@0: 
fp@0: # The GENERATE_TESTLIST tag can be used to enable (YES) or 
fp@0: # disable (NO) the test list. This list is created by putting \test 
fp@0: # commands in the documentation.
fp@0: 
fp@0: GENERATE_TESTLIST      = NO
fp@0: 
fp@0: # The GENERATE_BUGLIST tag can be used to enable (YES) or 
fp@0: # disable (NO) the bug list. This list is created by putting \bug 
fp@0: # commands in the documentation.
fp@0: 
fp@0: GENERATE_BUGLIST       = NO
fp@0: 
fp@0: # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
fp@0: # disable (NO) the deprecated list. This list is created by putting \deprecated commands in the documentation.
fp@0: 
fp@0: GENERATE_DEPRECATEDLIST= NO
fp@0: 
fp@0: # This tag can be used to specify a number of aliases that acts 
fp@0: # as commands in the documentation. An alias has the form "name=value". 
fp@0: # For example adding "sideeffect=\par Side Effects:\n" will allow you to 
fp@0: # put the command \sideeffect (or @sideeffect) in the documentation, which 
fp@0: # will result in a user defined paragraph with heading "Side Effects:". 
fp@0: # You can put \n's in the value part of an alias to insert newlines.
fp@0: 
fp@0: ALIASES                = 
fp@0: 
fp@0: # The ENABLED_SECTIONS tag can be used to enable conditional 
fp@0: # documentation sections, marked by \if sectionname ... \endif.
fp@0: 
fp@0: ENABLED_SECTIONS       = 
fp@0: 
fp@0: # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
fp@0: # the initial value of a variable or define consist of for it to appear in 
fp@0: # the documentation. If the initializer consists of more lines than specified 
fp@0: # here it will be hidden. Use a value of 0 to hide initializers completely. 
fp@0: # The appearance of the initializer of individual variables and defines in the 
fp@0: # documentation can be controlled using \showinitializer or \hideinitializer 
fp@0: # command in the documentation regardless of this setting.
fp@0: 
fp@0: MAX_INITIALIZER_LINES  = 30
fp@0: 
fp@0: # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 
fp@0: # only. Doxygen will then generate output that is more tailored for C. 
fp@0: # For instance some of the names that are used will be different. The list 
fp@0: # of all members will be omitted, etc.
fp@0: 
fp@0: OPTIMIZE_OUTPUT_FOR_C  = YES
fp@0: 
fp@0: # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
fp@0: # only. Doxygen will then generate output that is more tailored for Java. 
fp@0: # For instance namespaces will be presented as packages, qualified scopes 
fp@0: # will look different, etc.
fp@0: 
fp@0: OPTIMIZE_OUTPUT_JAVA   = NO
fp@0: 
fp@0: # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
fp@0: # at the bottom of the documentation of classes and structs. If set to YES the 
fp@0: # list will mention the files that were used to generate the documentation.
fp@0: 
fp@0: SHOW_USED_FILES        = NO
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to warning and progress messages
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # The QUIET tag can be used to turn on/off the messages that are generated 
fp@0: # by doxygen. Possible values are YES and NO. If left blank NO is used.
fp@0: 
fp@0: QUIET                  = YES
fp@0: 
fp@0: # The WARNINGS tag can be used to turn on/off the warning messages that are 
fp@0: # generated by doxygen. Possible values are YES and NO. If left blank 
fp@0: # NO is used.
fp@0: 
fp@0: WARNINGS               = YES
fp@0: 
fp@0: # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
fp@0: # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
fp@0: # automatically be disabled.
fp@0: 
fp@0: WARN_IF_UNDOCUMENTED   = YES
fp@0: 
fp@0: # The WARN_FORMAT tag determines the format of the warning messages that 
fp@0: # doxygen can produce. The string should contain the $file, $line, and $text 
fp@0: # tags, which will be replaced by the file and line number from which the 
fp@0: # warning originated and the warning text.
fp@0: 
fp@0: WARN_FORMAT            = "$file:$line: $text"
fp@0: 
fp@0: # The WARN_LOGFILE tag can be used to specify a file to which warning 
fp@0: # and error messages should be written. If left blank the output is written 
fp@0: # to stderr.
fp@0: 
fp@0: WARN_LOGFILE           = 
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the input files
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # The INPUT tag can be used to specify the files and/or directories that contain 
fp@0: # documented source files. You may enter file names like "myfile.cpp" or 
fp@0: # directories like "/usr/src/myproject". Separate the files or directories 
fp@0: # with spaces.
fp@0: 
fp@0: INPUT                  = drivers
fp@0: 
fp@0: # If the value of the INPUT tag contains directories, you can use the 
fp@0: # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
fp@0: # and *.h) to filter out the source-files in the directories. If left 
fp@0: # blank the following patterns are tested: 
fp@0: # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp 
fp@0: # *.h++ *.idl *.odl
fp@0: 
fp@0: FILE_PATTERNS          = 
fp@0: 
fp@0: # The RECURSIVE tag can be used to turn specify whether or not subdirectories 
fp@0: # should be searched for input files as well. Possible values are YES and NO. 
fp@0: # If left blank NO is used.
fp@0: 
fp@0: RECURSIVE              = NO
fp@0: 
fp@0: # The EXCLUDE tag can be used to specify files and/or directories that should 
fp@0: # excluded from the INPUT source files. This way you can easily exclude a 
fp@0: # subdirectory from a directory tree whose root is specified with the INPUT tag.
fp@0: 
fp@0: EXCLUDE                = drivers/drv_8139too.c
fp@0: 
fp@0: # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
fp@0: # that are symbolic links (a Unix filesystem feature) are excluded from the input.
fp@0: 
fp@0: EXCLUDE_SYMLINKS       = NO
fp@0: 
fp@0: # If the value of the INPUT tag contains directories, you can use the 
fp@0: # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
fp@0: # certain files from those directories.
fp@0: 
fp@0: EXCLUDE_PATTERNS       = 
fp@0: 
fp@0: # The EXAMPLE_PATH tag can be used to specify one or more files or 
fp@0: # directories that contain example code fragments that are included (see 
fp@0: # the \include command).
fp@0: 
fp@0: EXAMPLE_PATH           = 
fp@0: 
fp@0: # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
fp@0: # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
fp@0: # and *.h) to filter out the source-files in the directories. If left 
fp@0: # blank all files are included.
fp@0: 
fp@0: EXAMPLE_PATTERNS       = 
fp@0: 
fp@0: # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
fp@0: # searched for input files to be used with the \include or \dontinclude 
fp@0: # commands irrespective of the value of the RECURSIVE tag. 
fp@0: # Possible values are YES and NO. If left blank NO is used.
fp@0: 
fp@0: EXAMPLE_RECURSIVE      = NO
fp@0: 
fp@0: # The IMAGE_PATH tag can be used to specify one or more files or 
fp@0: # directories that contain image that are included in the documentation (see 
fp@0: # the \image command).
fp@0: 
fp@0: IMAGE_PATH             = 
fp@0: 
fp@0: # The INPUT_FILTER tag can be used to specify a program that doxygen should 
fp@0: # invoke to filter for each input file. Doxygen will invoke the filter program 
fp@0: # by executing (via popen()) the command <filter> <input-file>, where <filter> 
fp@0: # is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
fp@0: # input file. Doxygen will then use the output that the filter program writes 
fp@0: # to standard output.
fp@0: 
fp@0: INPUT_FILTER           = 
fp@0: 
fp@0: # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
fp@0: # INPUT_FILTER) will be used to filter the input files when producing source 
fp@0: # files to browse (i.e. when SOURCE_BROWSER is set to YES).
fp@0: 
fp@0: FILTER_SOURCE_FILES    = NO
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to source browsing
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the SOURCE_BROWSER tag is set to YES then a list of source files will 
fp@0: # be generated. Documented entities will be cross-referenced with these sources.
fp@0: 
fp@0: SOURCE_BROWSER         = YES
fp@0: 
fp@0: # Setting the INLINE_SOURCES tag to YES will include the body 
fp@0: # of functions and classes directly in the documentation.
fp@0: 
fp@0: INLINE_SOURCES         = NO
fp@0: 
fp@0: # If the REFERENCED_BY_RELATION tag is set to YES (the default) 
fp@0: # then for each documented function all documented 
fp@0: # functions referencing it will be listed.
fp@0: 
fp@0: REFERENCED_BY_RELATION = YES
fp@0: 
fp@0: # If the REFERENCES_RELATION tag is set to YES (the default) 
fp@0: # then for each documented function all documented entities 
fp@0: # called/used by that function will be listed.
fp@0: 
fp@0: REFERENCES_RELATION    = YES
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the alphabetical class index
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
fp@0: # of all compounds will be generated. Enable this if the project 
fp@0: # contains a lot of classes, structs, unions or interfaces.
fp@0: 
fp@0: ALPHABETICAL_INDEX     = NO
fp@0: 
fp@0: # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
fp@0: # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
fp@0: # in which this list will be split (can be a number in the range [1..20])
fp@0: 
fp@0: COLS_IN_ALPHA_INDEX    = 5
fp@0: 
fp@0: # In case all classes in a project start with a common prefix, all 
fp@0: # classes will be put under the same header in the alphabetical index. 
fp@0: # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
fp@0: # should be ignored while generating the index headers.
fp@0: 
fp@0: IGNORE_PREFIX          = 
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the HTML output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
fp@0: # generate HTML output.
fp@0: 
fp@0: GENERATE_HTML          = YES
fp@0: 
fp@0: # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
fp@0: # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
fp@0: # put in front of it. If left blank `html' will be used as the default path.
fp@0: 
fp@0: HTML_OUTPUT            = html
fp@0: 
fp@0: # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
fp@0: # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
fp@0: # doxygen will generate files with .html extension.
fp@0: 
fp@0: HTML_FILE_EXTENSION    = .html
fp@0: 
fp@0: # The HTML_HEADER tag can be used to specify a personal HTML header for 
fp@0: # each generated HTML page. If it is left blank doxygen will generate a 
fp@0: # standard header.
fp@0: 
fp@0: HTML_HEADER            = 
fp@0: 
fp@0: # The HTML_FOOTER tag can be used to specify a personal HTML footer for 
fp@0: # each generated HTML page. If it is left blank doxygen will generate a 
fp@0: # standard footer.
fp@0: 
fp@0: HTML_FOOTER            = 
fp@0: 
fp@0: # The HTML_STYLESHEET tag can be used to specify a user defined cascading 
fp@0: # style sheet that is used by each HTML page. It can be used to 
fp@0: # fine-tune the look of the HTML output. If the tag is left blank doxygen 
fp@0: # will generate a default style sheet
fp@0: 
fp@0: HTML_STYLESHEET        = 
fp@0: 
fp@0: # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
fp@0: # files or namespaces will be aligned in HTML using tables. If set to 
fp@0: # NO a bullet list will be used.
fp@0: 
fp@0: HTML_ALIGN_MEMBERS     = YES
fp@0: 
fp@0: # If the GENERATE_HTMLHELP tag is set to YES, additional index files 
fp@0: # will be generated that can be used as input for tools like the 
fp@0: # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
fp@0: # of the generated HTML documentation.
fp@0: 
fp@0: GENERATE_HTMLHELP      = NO
fp@0: 
fp@0: # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
fp@0: # be used to specify the file name of the resulting .chm file. You 
fp@0: # can add a path in front of the file if the result should not be 
fp@0: # written to the html output dir.
fp@0: 
fp@0: CHM_FILE               = 
fp@0: 
fp@0: # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
fp@0: # be used to specify the location (absolute path including file name) of 
fp@0: # the HTML help compiler (hhc.exe). If non empty doxygen will try to run 
fp@0: # the html help compiler on the generated index.hhp.
fp@0: 
fp@0: HHC_LOCATION           = 
fp@0: 
fp@0: # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
fp@0: # controls if a separate .chi index file is generated (YES) or that 
fp@0: # it should be included in the master .chm file (NO).
fp@0: 
fp@0: GENERATE_CHI           = NO
fp@0: 
fp@0: # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
fp@0: # controls whether a binary table of contents is generated (YES) or a 
fp@0: # normal table of contents (NO) in the .chm file.
fp@0: 
fp@0: BINARY_TOC             = NO
fp@0: 
fp@0: # The TOC_EXPAND flag can be set to YES to add extra items for group members 
fp@0: # to the contents of the Html help documentation and to the tree view.
fp@0: 
fp@0: TOC_EXPAND             = NO
fp@0: 
fp@0: # The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
fp@0: # top of each HTML page. The value NO (the default) enables the index and 
fp@0: # the value YES disables it.
fp@0: 
fp@0: DISABLE_INDEX          = NO
fp@0: 
fp@0: # This tag can be used to set the number of enum values (range [1..20]) 
fp@0: # that doxygen will group on one line in the generated HTML documentation.
fp@0: 
fp@0: ENUM_VALUES_PER_LINE   = 4
fp@0: 
fp@0: # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
fp@0: # generated containing a tree-like index structure (just like the one that 
fp@0: # is generated for HTML Help). For this to work a browser that supports 
fp@0: # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+, 
fp@0: # or Internet explorer 4.0+). Note that for large projects the tree generation 
fp@0: # can take a very long time. In such cases it is better to disable this feature. 
fp@0: # Windows users are probably better off using the HTML help feature.
fp@0: 
fp@0: GENERATE_TREEVIEW      = YES
fp@0: 
fp@0: # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
fp@0: # used to set the initial width (in pixels) of the frame in which the tree 
fp@0: # is shown.
fp@0: 
fp@0: TREEVIEW_WIDTH         = 250
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the LaTeX output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
fp@0: # generate Latex output.
fp@0: 
fp@0: GENERATE_LATEX         = NO
fp@0: 
fp@0: # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
fp@0: # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
fp@0: # put in front of it. If left blank `latex' will be used as the default path.
fp@0: 
fp@0: LATEX_OUTPUT           = latex
fp@0: 
fp@0: # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be invoked. If left blank `latex' will be used as the default command name.
fp@0: 
fp@0: LATEX_CMD_NAME         = latex
fp@0: 
fp@0: # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
fp@0: # generate index for LaTeX. If left blank `makeindex' will be used as the 
fp@0: # default command name.
fp@0: 
fp@0: MAKEINDEX_CMD_NAME     = makeindex
fp@0: 
fp@0: # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
fp@0: # LaTeX documents. This may be useful for small projects and may help to 
fp@0: # save some trees in general.
fp@0: 
fp@0: COMPACT_LATEX          = NO
fp@0: 
fp@0: # The PAPER_TYPE tag can be used to set the paper type that is used 
fp@0: # by the printer. Possible values are: a4, a4wide, letter, legal and 
fp@0: # executive. If left blank a4wide will be used.
fp@0: 
fp@0: PAPER_TYPE             = a4wide
fp@0: 
fp@0: # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
fp@0: # packages that should be included in the LaTeX output.
fp@0: 
fp@0: EXTRA_PACKAGES         = 
fp@0: 
fp@0: # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
fp@0: # the generated latex document. The header should contain everything until 
fp@0: # the first chapter. If it is left blank doxygen will generate a 
fp@0: # standard header. Notice: only use this tag if you know what you are doing!
fp@0: 
fp@0: LATEX_HEADER           = 
fp@0: 
fp@0: # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
fp@0: # is prepared for conversion to pdf (using ps2pdf). The pdf file will 
fp@0: # contain links (just like the HTML output) instead of page references 
fp@0: # This makes the output suitable for online browsing using a pdf viewer.
fp@0: 
fp@0: PDF_HYPERLINKS         = NO
fp@0: 
fp@0: # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
fp@0: # plain latex in the generated Makefile. Set this option to YES to get a 
fp@0: # higher quality PDF documentation.
fp@0: 
fp@0: USE_PDFLATEX           = NO
fp@0: 
fp@0: # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
fp@0: # command to the generated LaTeX files. This will instruct LaTeX to keep 
fp@0: # running if errors occur, instead of asking the user for help. 
fp@0: # This option is also used when generating formulas in HTML.
fp@0: 
fp@0: LATEX_BATCHMODE        = NO
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the RTF output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
fp@0: # The RTF output is optimised for Word 97 and may not look very pretty with 
fp@0: # other RTF readers or editors.
fp@0: 
fp@0: GENERATE_RTF           = NO
fp@0: 
fp@0: # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
fp@0: # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
fp@0: # put in front of it. If left blank `rtf' will be used as the default path.
fp@0: 
fp@0: RTF_OUTPUT             = rtf
fp@0: 
fp@0: # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
fp@0: # RTF documents. This may be useful for small projects and may help to 
fp@0: # save some trees in general.
fp@0: 
fp@0: COMPACT_RTF            = NO
fp@0: 
fp@0: # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
fp@0: # will contain hyperlink fields. The RTF file will 
fp@0: # contain links (just like the HTML output) instead of page references. 
fp@0: # This makes the output suitable for online browsing using WORD or other 
fp@0: # programs which support those fields. 
fp@0: # Note: wordpad (write) and others do not support links.
fp@0: 
fp@0: RTF_HYPERLINKS         = NO
fp@0: 
fp@0: # Load stylesheet definitions from file. Syntax is similar to doxygen's 
fp@0: # config file, i.e. a series of assigments. You only have to provide 
fp@0: # replacements, missing definitions are set to their default value.
fp@0: 
fp@0: RTF_STYLESHEET_FILE    = 
fp@0: 
fp@0: # Set optional variables used in the generation of an rtf document. 
fp@0: # Syntax is similar to doxygen's config file.
fp@0: 
fp@0: RTF_EXTENSIONS_FILE    = 
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the man page output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
fp@0: # generate man pages
fp@0: 
fp@0: GENERATE_MAN           = NO
fp@0: 
fp@0: # The MAN_OUTPUT tag is used to specify where the man pages will be put. 
fp@0: # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
fp@0: # put in front of it. If left blank `man' will be used as the default path.
fp@0: 
fp@0: MAN_OUTPUT             = man
fp@0: 
fp@0: # The MAN_EXTENSION tag determines the extension that is added to 
fp@0: # the generated man pages (default is the subroutine's section .3)
fp@0: 
fp@0: MAN_EXTENSION          = .3
fp@0: 
fp@0: # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
fp@0: # then it will generate one additional man file for each entity 
fp@0: # documented in the real man page(s). These additional files 
fp@0: # only source the real man page, but without them the man command 
fp@0: # would be unable to find the correct page. The default is NO.
fp@0: 
fp@0: MAN_LINKS              = NO
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options related to the XML output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_XML tag is set to YES Doxygen will 
fp@0: # generate an XML file that captures the structure of 
fp@0: # the code including all documentation. Note that this 
fp@0: # feature is still experimental and incomplete at the 
fp@0: # moment.
fp@0: 
fp@0: GENERATE_XML           = NO
fp@0: 
fp@0: # The XML_SCHEMA tag can be used to specify an XML schema, 
fp@0: # which can be used by a validating XML parser to check the 
fp@0: # syntax of the XML files.
fp@0: 
fp@0: XML_SCHEMA             = 
fp@0: 
fp@0: # The XML_DTD tag can be used to specify an XML DTD, 
fp@0: # which can be used by a validating XML parser to check the 
fp@0: # syntax of the XML files.
fp@0: 
fp@0: XML_DTD                = 
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # configuration options for the AutoGen Definitions output
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
fp@0: # generate an AutoGen Definitions (see autogen.sf.net) file 
fp@0: # that captures the structure of the code including all 
fp@0: # documentation. Note that this feature is still experimental 
fp@0: # and incomplete at the moment.
fp@0: 
fp@0: GENERATE_AUTOGEN_DEF   = NO
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # Configuration options related to the preprocessor   
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
fp@0: # evaluate all C-preprocessor directives found in the sources and include 
fp@0: # files.
fp@0: 
fp@0: ENABLE_PREPROCESSING   = YES
fp@0: 
fp@0: # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
fp@0: # names in the source code. If set to NO (the default) only conditional 
fp@0: # compilation will be performed. Macro expansion can be done in a controlled 
fp@0: # way by setting EXPAND_ONLY_PREDEF to YES.
fp@0: 
fp@0: MACRO_EXPANSION        = NO
fp@0: 
fp@0: # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
fp@0: # then the macro expansion is limited to the macros specified with the 
fp@0: # PREDEFINED and EXPAND_AS_PREDEFINED tags.
fp@0: 
fp@0: EXPAND_ONLY_PREDEF     = NO
fp@0: 
fp@0: # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
fp@0: # in the INCLUDE_PATH (see below) will be search if a #include is found.
fp@0: 
fp@0: SEARCH_INCLUDES        = YES
fp@0: 
fp@0: # The INCLUDE_PATH tag can be used to specify one or more directories that 
fp@0: # contain include files that are not input files but should be processed by 
fp@0: # the preprocessor.
fp@0: 
fp@0: INCLUDE_PATH           = 
fp@0: 
fp@0: # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
fp@0: # patterns (like *.h and *.hpp) to filter out the header-files in the 
fp@0: # directories. If left blank, the patterns specified with FILE_PATTERNS will 
fp@0: # be used.
fp@0: 
fp@0: INCLUDE_FILE_PATTERNS  = 
fp@0: 
fp@0: # The PREDEFINED tag can be used to specify one or more macro names that 
fp@0: # are defined before the preprocessor is started (similar to the -D option of 
fp@0: # gcc). The argument of the tag is a list of macros of the form: name 
fp@0: # or name=definition (no spaces). If the definition and the = are 
fp@0: # omitted =1 is assumed.
fp@0: 
fp@0: PREDEFINED             = 
fp@0: 
fp@0: # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then 
fp@0: # this tag can be used to specify a list of macro names that should be expanded. 
fp@0: # The macro definition that is found in the sources will be used. 
fp@0: # Use the PREDEFINED tag if you want to use a different macro definition.
fp@0: 
fp@0: EXPAND_AS_DEFINED      = 
fp@0: 
fp@0: # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
fp@0: # doxygen's preprocessor will remove all function-like macros that are alone 
fp@0: # on a line, have an all uppercase name, and do not end with a semicolon. Such 
fp@0: # function macros are typically used for boiler-plate code, and will confuse the 
fp@0: # parser if not removed.
fp@0: 
fp@0: SKIP_FUNCTION_MACROS   = YES
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # Configuration::addtions related to external references   
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # The TAGFILES tag can be used to specify one or more tagfiles.
fp@0: 
fp@0: TAGFILES               = 
fp@0: 
fp@0: # When a file name is specified after GENERATE_TAGFILE, doxygen will create 
fp@0: # a tag file that is based on the input files it reads.
fp@0: 
fp@0: GENERATE_TAGFILE       = 
fp@0: 
fp@0: # If the ALLEXTERNALS tag is set to YES all external classes will be listed 
fp@0: # in the class index. If set to NO only the inherited external classes 
fp@0: # will be listed.
fp@0: 
fp@0: ALLEXTERNALS           = NO
fp@0: 
fp@0: # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
fp@0: # in the modules index. If set to NO, only the current project's groups will 
fp@0: # be listed.
fp@0: 
fp@0: EXTERNAL_GROUPS        = YES
fp@0: 
fp@0: # The PERL_PATH should be the absolute path and name of the perl script 
fp@0: # interpreter (i.e. the result of `which perl').
fp@0: 
fp@0: PERL_PATH              = /usr/bin/perl
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # Configuration options related to the dot tool   
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
fp@0: # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or 
fp@0: # super classes. Setting the tag to NO turns the diagrams off. Note that this 
fp@0: # option is superceded by the HAVE_DOT option below. This is only a fallback. It is 
fp@0: # recommended to install and use dot, since it yield more powerful graphs.
fp@0: 
fp@0: CLASS_DIAGRAMS         = YES
fp@0: 
fp@0: # If set to YES, the inheritance and collaboration graphs will hide 
fp@0: # inheritance and usage relations if the target is undocumented 
fp@0: # or is not a class.
fp@0: 
fp@0: HIDE_UNDOC_RELATIONS   = YES
fp@0: 
fp@0: # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
fp@0: # available from the path. This tool is part of Graphviz, a graph visualization 
fp@0: # toolkit from AT&T and Lucent Bell Labs. The other options in this section 
fp@0: # have no effect if this option is set to NO (the default)
fp@0: 
fp@0: HAVE_DOT               = NO
fp@0: 
fp@0: # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
fp@0: # will generate a graph for each documented class showing the direct and 
fp@0: # indirect inheritance relations. Setting this tag to YES will force the 
fp@0: # the CLASS_DIAGRAMS tag to NO.
fp@0: 
fp@0: CLASS_GRAPH            = YES
fp@0: 
fp@0: # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
fp@0: # will generate a graph for each documented class showing the direct and 
fp@0: # indirect implementation dependencies (inheritance, containment, and 
fp@0: # class references variables) of the class with other documented classes.
fp@0: 
fp@0: COLLABORATION_GRAPH    = YES
fp@0: 
fp@0: # If set to YES, the inheritance and collaboration graphs will show the 
fp@0: # relations between templates and their instances.
fp@0: 
fp@0: TEMPLATE_RELATIONS     = YES
fp@0: 
fp@0: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
fp@0: # tags are set to YES then doxygen will generate a graph for each documented 
fp@0: # file showing the direct and indirect include dependencies of the file with 
fp@0: # other documented files.
fp@0: 
fp@0: INCLUDE_GRAPH          = YES
fp@0: 
fp@0: # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
fp@0: # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
fp@0: # documented header file showing the documented files that directly or 
fp@0: # indirectly include this file.
fp@0: 
fp@0: INCLUDED_BY_GRAPH      = YES
fp@0: 
fp@0: # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
fp@0: # will graphical hierarchy of all classes instead of a textual one.
fp@0: 
fp@0: GRAPHICAL_HIERARCHY    = YES
fp@0: 
fp@0: # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
fp@0: # generated by dot. Possible values are png, jpg, or gif
fp@0: # If left blank png will be used.
fp@0: 
fp@0: DOT_IMAGE_FORMAT       = png
fp@0: 
fp@0: # The tag DOT_PATH can be used to specify the path where the dot tool can be 
fp@0: # found. If left blank, it is assumed the dot tool can be found on the path.
fp@0: 
fp@0: DOT_PATH               = 
fp@0: 
fp@0: # The DOTFILE_DIRS tag can be used to specify one or more directories that 
fp@0: # contain dot files that are included in the documentation (see the 
fp@0: # \dotfile command).
fp@0: 
fp@0: DOTFILE_DIRS           = 
fp@0: 
fp@0: # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 
fp@0: # (in pixels) of the graphs generated by dot. If a graph becomes larger than 
fp@0: # this value, doxygen will try to truncate the graph, so that it fits within 
fp@0: # the specified constraint. Beware that most browsers cannot cope with very 
fp@0: # large images.
fp@0: 
fp@0: MAX_DOT_GRAPH_WIDTH    = 1024
fp@0: 
fp@0: # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 
fp@0: # (in pixels) of the graphs generated by dot. If a graph becomes larger than 
fp@0: # this value, doxygen will try to truncate the graph, so that it fits within 
fp@0: # the specified constraint. Beware that most browsers cannot cope with very 
fp@0: # large images.
fp@0: 
fp@0: MAX_DOT_GRAPH_HEIGHT   = 1024
fp@0: 
fp@0: # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
fp@0: # generate a legend page explaining the meaning of the various boxes and 
fp@0: # arrows in the dot generated graphs.
fp@0: 
fp@0: GENERATE_LEGEND        = YES
fp@0: 
fp@0: # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
fp@0: # remove the intermedate dot files that are used to generate 
fp@0: # the various graphs.
fp@0: 
fp@0: DOT_CLEANUP            = YES
fp@0: 
fp@0: #---------------------------------------------------------------------------
fp@0: # Configuration::addtions related to the search engine   
fp@0: #---------------------------------------------------------------------------
fp@0: 
fp@0: # The SEARCHENGINE tag specifies whether or not a search engine should be 
fp@0: # used. If set to NO the values of all tags below this one will be ignored.
fp@0: 
fp@0: SEARCHENGINE           = NO
fp@0: 
fp@0: # The CGI_NAME tag should be the name of the CGI script that 
fp@0: # starts the search engine (doxysearch) with the correct parameters. 
fp@0: # A script with this name will be generated by doxygen.
fp@0: 
fp@0: CGI_NAME               = search.cgi
fp@0: 
fp@0: # The CGI_URL tag should be the absolute URL to the directory where the 
fp@0: # cgi binaries are located. See the documentation of your http daemon for 
fp@0: # details.
fp@0: 
fp@0: CGI_URL                = 
fp@0: 
fp@0: # The DOC_URL tag should be the absolute URL to the directory where the 
fp@0: # documentation is located. If left blank the absolute path to the 
fp@0: # documentation, with file:// prepended to it, will be used.
fp@0: 
fp@0: DOC_URL                = 
fp@0: 
fp@0: # The DOC_ABSPATH tag should be the absolute path to the directory where the 
fp@0: # documentation is located. If left blank the directory on the local machine 
fp@0: # will be used.
fp@0: 
fp@0: DOC_ABSPATH            = 
fp@0: 
fp@0: # The BIN_ABSPATH tag must point to the directory where the doxysearch binary 
fp@0: # is installed.
fp@0: 
fp@0: BIN_ABSPATH            = /usr/local/bin/
fp@0: 
fp@0: # The EXT_DOC_PATHS tag can be used to specify one or more paths to 
fp@0: # documentation generated for other projects. This allows doxysearch to search 
fp@0: # the documentation for these projects as well.
fp@0: 
fp@0: EXT_DOC_PATHS          =