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