Changeset 87cc26db in rtems


Ignore:
Timestamp:
Jan 30, 2008, 1:50:53 AM (11 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.9, master
Children:
84ec364
Parents:
18ca4e8
Message:

2008-01-29 Joel Sherrill <joel.sherrill@…>

  • score/Doxyfile: Revert Doxygen version changes.
Location:
cpukit
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • cpukit/ChangeLog

    r18ca4e8 r87cc26db  
     12008-01-29      Joel Sherrill <joel.sherrill@oarcorp.com>
     2
     3        * score/Doxyfile: Revert Doxygen version changes.
     4
    152008-01-29      Joel Sherrill <joel.sherrill@oarcorp.com>
    26
  • cpukit/score/Doxyfile

    r18ca4e8 r87cc26db  
    1 # Doxyfile 1.5.4
     1# Doxyfile 1.3.4
    22
    33# This file describes the settings to be used by the documentation system
     
    1515#---------------------------------------------------------------------------
    1616
    17 # This tag specifies the encoding used for all characters in the config file that
    18 # follow. The default is UTF-8 which is also the encoding used for all text before
    19 # the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into
    20 # libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of
    21 # possible encodings.
    22 
    23 DOXYFILE_ENCODING      = UTF-8
    24 
    2517# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
    2618# by quotes) that should identify the project.
    2719
    28 PROJECT_NAME           = RTEMSSuperCore
     20PROJECT_NAME           = RTEMS SuperCore
    2921
    3022# The PROJECT_NUMBER tag can be used to enter a project or revision number.
     
    4133OUTPUT_DIRECTORY       = score_doxy
    4234
    43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
    44 # 4096 sub-directories (in 2 levels) under the output directory of each output
    45 # format and will distribute the generated files over these directories.
    46 # Enabling this option can be useful when feeding doxygen a huge amount of
    47 # source files, where putting all generated files in the same directory would
    48 # otherwise cause performance problems for the file system.
    49 
    50 CREATE_SUBDIRS         = NO
    51 
    5235# The OUTPUT_LANGUAGE tag is used to specify the language in which all
    5336# documentation generated by doxygen is written. Doxygen will use this
    5437# information to generate all constant output in the proper language.
    5538# The default language is English, other supported languages are:
    56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
    57 # Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian,
    58 # Italian, Japanese, Japanese-en (Japanese with English messages), Korean,
    59 # Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian,
    60 # Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
     39# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
     40# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
     41# (Japanese with English messages), Korean, Norwegian, Polish, Portuguese,
     42# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
    6143
    6244OUTPUT_LANGUAGE        = English
     45
     46# This tag can be used to specify the encoding used in the generated output.
     47# The encoding is not always determined by the language that is chosen,
     48# but also whether or not the output is meant for Windows or non-Windows users.
     49# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
     50# forces the Windows encoding (this is the default for the Windows binary),
     51# whereas setting the tag to NO uses a Unix-style encoding (the default for
     52# all platforms other than Windows).
     53
     54USE_WINDOWS_ENCODING   = NO
    6355
    6456# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
     
    7668REPEAT_BRIEF           = YES
    7769
    78 # This tag implements a quasi-intelligent brief description abbreviator
    79 # that is used to form the text in various listings. Each string
    80 # in this list, if found as the leading text of the brief description, will be
    81 # stripped from the text and the result after processing the whole list, is
    82 # used as the annotated text. Otherwise, the brief description is used as-is.
    83 # If left blank, the following values are used ("$name" is automatically
    84 # replaced with the name of the entity): "The $name class" "The $name widget"
    85 # "The $name file" "is" "provides" "specifies" "contains"
    86 # "represents" "a" "an" "the"
    87 
    88 ABBREVIATE_BRIEF       =
    89 
    9070# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
    9171# Doxygen will generate a detailed section even if there is only a brief
     
    9474ALWAYS_DETAILED_SEC    = NO
    9575
    96 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
    97 # inherited members of a class in the documentation of that class as if those
    98 # members were ordinary class members. Constructors, destructors and assignment
    99 # operators of the base classes will not be shown.
     76# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
     77# members of a class in the documentation of that class as if those members were
     78# ordinary class members. Constructors, destructors and assignment operators of
     79# the base classes will not be shown.
    10080
    10181INLINE_INHERITED_MEMB  = NO
     
    11090# can be used to strip a user-defined part of the path. Stripping is
    11191# only done if one of the specified strings matches the left-hand part of
    112 # the path. The tag can be used to show relative paths in the file list.
    113 # If left blank the directory from which doxygen is run is used as the
    114 # path to strip.
     92# the path. It is allowed to use relative paths in the argument list.
    11593
    11694STRIP_FROM_PATH        =
    117 
    118 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
    119 # the path mentioned in the documentation of a class, which tells
    120 # the reader which header file to include in order to use a class.
    121 # If left blank only the name of the header file containing the class
    122 # definition is used. Otherwise one should specify the include paths that
    123 # are normally passed to the compiler using the -I flag.
    124 
    125 STRIP_FROM_INC_PATH    =
    12695
    12796# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
     
    134103# will interpret the first line (until the first dot) of a JavaDoc-style
    135104# comment as the brief description. If set to NO, the JavaDoc
    136 # comments will behave just like regular Qt-style comments
    137 # (thus requiring an explicit @brief command for a brief description.)
     105# comments will behave just like the Qt-style comments (thus requiring an
     106# explict @brief command for a brief description.
    138107
    139108JAVADOC_AUTOBRIEF      = NO
    140 
    141 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
    142 # interpret the first line (until the first dot) of a Qt-style
    143 # comment as the brief description. If set to NO, the comments
    144 # will behave just like regular Qt-style comments (thus requiring
    145 # an explicit \brief command for a brief description.)
    146 
    147 QT_AUTOBRIEF           = NO
    148109
    149110# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
     
    164125# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
    165126# member inherits the documentation from any documented member that it
    166 # re-implements.
     127# reimplements.
    167128
    168129INHERIT_DOCS           = YES
    169130
    170 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
    171 # a new page for each member. If set to NO, the documentation of a member will
    172 # be part of the file/class/namespace that contains it.
    173 
    174 SEPARATE_MEMBER_PAGES  = NO
     131# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
     132# tag is set to YES, then doxygen will reuse the documentation of the first
     133# member in the group (if any) for the other members of the group. By default
     134# all members of a group must be documented explicitly.
     135
     136DISTRIBUTE_GROUP_DOC   = NO
    175137
    176138# The TAB_SIZE tag can be used to set the number of spaces in a tab.
     
    188150ALIASES                =
    189151
    190 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
    191 # sources only. Doxygen will then generate output that is more tailored for C.
     152# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
     153# only. Doxygen will then generate output that is more tailored for C.
    192154# For instance, some of the names that are used will be different. The list
    193155# of all members will be omitted, etc.
     
    195157OPTIMIZE_OUTPUT_FOR_C  = YES
    196158
    197 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
    198 # sources only. Doxygen will then generate output that is more tailored for Java.
     159# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
     160# only. Doxygen will then generate output that is more tailored for Java.
    199161# For instance, namespaces will be presented as packages, qualified scopes
    200162# will look different, etc.
    201163
    202164OPTIMIZE_OUTPUT_JAVA   = NO
    203 
    204 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to
    205 # include (a tag file for) the STL sources as input, then you should
    206 # set this tag to YES in order to let doxygen match functions declarations and
    207 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
    208 # func(std::string) {}). This also make the inheritance and collaboration
    209 # diagrams that involve STL classes more complete and accurate.
    210 
    211 BUILTIN_STL_SUPPORT    = NO
    212 
    213 # If you use Microsoft's C++/CLI language, you should set this option to YES to
    214 # enable parsing support.
    215 
    216 CPP_CLI_SUPPORT        = NO
    217 
    218 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
    219 # Doxygen will parse them like normal C++ but will assume all classes use public
    220 # instead of private inheritance when no explicit protection keyword is present.
    221 
    222 SIP_SUPPORT            = NO
    223 
    224 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
    225 # tag is set to YES, then doxygen will reuse the documentation of the first
    226 # member in the group (if any) for the other members of the group. By default
    227 # all members of a group must be documented explicitly.
    228 
    229 DISTRIBUTE_GROUP_DOC   = NO
    230165
    231166# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
     
    237172SUBGROUPING            = YES
    238173
    239 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct (or union) is
    240 # documented as struct with the name of the typedef. So
    241 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
    242 # with name TypeT. When disabled the typedef will appear as a member of a file,
    243 # namespace, or class. And the struct will be named TypeS. This can typically
    244 # be useful for C code where the coding convention is that all structs are
    245 # typedef'ed and only the typedef is referenced never the struct's name.
    246 
    247 TYPEDEF_HIDES_STRUCT   = NO
    248 
    249174#---------------------------------------------------------------------------
    250175# Build related configuration options
     
    273198
    274199EXTRACT_LOCAL_CLASSES  = YES
    275 
    276 # This flag is only useful for Objective-C code. When set to YES local
    277 # methods, which are defined in the implementation section but not in
    278 # the interface are included in the documentation.
    279 # If set to NO (the default) only methods in the interface are included.
    280 
    281 EXTRACT_LOCAL_METHODS  = NO
    282 
    283 # If this flag is set to YES, the members of anonymous namespaces will be extracted
    284 # and appear in the documentation as a namespace called 'anonymous_namespace{file}',
    285 # where file will be replaced with the base name of the file that contains the anonymous
    286 # namespace. By default anonymous namespace are hidden.
    287 
    288 EXTRACT_ANON_NSPACES   = NO
    289200
    290201# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
     
    328239# allowed. This is useful if you have classes or files whose names only differ
    329240# in case and if your file system supports case sensitive file names. Windows
    330 # and Mac users are advised to set this option to NO.
     241# users are advised to set this option to NO.
    331242
    332243CASE_SENSE_NAMES       = YES
     
    355266
    356267SORT_MEMBER_DOCS       = YES
    357 
    358 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
    359 # brief documentation of file, namespace and class members alphabetically
    360 # by member name. If set to NO (the default) the members will appear in
    361 # declaration order.
    362 
    363 SORT_BRIEF_DOCS        = NO
    364 
    365 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
    366 # sorted by fully-qualified names, including namespaces. If set to
    367 # NO (the default), the class list will be sorted only by class name,
    368 # not including the namespace part.
    369 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
    370 # Note: This option applies only to the class list, not to the
    371 # alphabetical list.
    372 
    373 SORT_BY_SCOPE_NAME     = NO
    374268
    375269# The GENERATE_TODOLIST tag can be used to enable (YES) or
     
    418312SHOW_USED_FILES        = YES
    419313
    420 # If the sources in your project are distributed over multiple directories
    421 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
    422 # in the documentation. The default is NO.
    423 
    424 SHOW_DIRECTORIES       = NO
    425 
    426 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
    427 # doxygen should invoke to get the current version for each file (typically from the
    428 # version control system). Doxygen will invoke the program by executing (via
    429 # popen()) the command <command> <input-file>, where <command> is the value of
    430 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
    431 # provided by doxygen. Whatever the program writes to standard output
    432 # is used as the file version. See the manual for examples.
    433 
    434 FILE_VERSION_FILTER    =
    435 
    436314#---------------------------------------------------------------------------
    437315# configuration options related to warning and progress messages
     
    462340WARN_IF_DOC_ERROR      = YES
    463341
    464 # This WARN_NO_PARAMDOC option can be abled to get warnings for
    465 # functions that are documented, but have no documentation for their parameters
    466 # or return value. If set to NO (the default) doxygen will only warn about
    467 # wrong or incomplete parameter documentation, but not about the absence of
    468 # documentation.
    469 
    470 WARN_NO_PARAMDOC       = NO
    471 
    472342# The WARN_FORMAT tag determines the format of the warning messages that
    473343# doxygen can produce. The string should contain the $file, $line, and $text
    474344# tags, which will be replaced by the file and line number from which the
    475 # warning originated and the warning text. Optionally the format may contain
    476 # $version, which will be replaced by the version of the file (if it could
    477 # be obtained via FILE_VERSION_FILTER)
    478 
    479 WARN_FORMAT            = "$file:$line: $text  "
     345# warning originated and the warning text.
     346
     347WARN_FORMAT            = "$file:$line: $text"
    480348
    481349# The WARN_LOGFILE tag can be used to specify a file to which warning
     
    494362# with spaces.
    495363
    496 INPUT                  = include \
    497                          inline \
    498                          cpu/no_cpu
    499 
    500 # This tag can be used to specify the character encoding of the source files that
    501 # doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default
    502 # input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding.
    503 # See http://www.gnu.org/software/libiconv for the list of possible encodings.
    504 
    505 INPUT_ENCODING         = UTF-8
     364INPUT                  = include inline cpu/no_cpu
    506365
    507366# If the value of the INPUT tag contains directories, you can use the
     
    509368# and *.h) to filter out the source-files in the directories. If left
    510369# blank the following patterns are tested:
    511 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
    512 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
    513 
    514 FILE_PATTERNS          = *.h \
    515                          *.inl
     370# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
     371# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
     372
     373FILE_PATTERNS          = *.h *.inl
    516374
    517375# The RECURSIVE tag can be used to turn specify whether or not subdirectories
     
    527385EXCLUDE                =
    528386
    529 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
    530 # directories that are symbolic links (a Unix filesystem feature) are excluded
    531 # from the input.
     387# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
     388# that are symbolic links (a Unix filesystem feature) are excluded from the input.
    532389
    533390EXCLUDE_SYMLINKS       = NO
     
    535392# If the value of the INPUT tag contains directories, you can use the
    536393# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
    537 # certain files from those directories. Note that the wildcards are matched
    538 # against the file with absolute path, so to exclude all test directories
    539 # for example use the pattern */test/*
     394# certain files from those directories.
    540395
    541396EXCLUDE_PATTERNS       =
    542 
    543 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
    544 # (namespaces, classes, functions, etc.) that should be excluded from the output.
    545 # The symbol name can be a fully qualified name, a word, or if the wildcard * is used,
    546 # a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test
    547 
    548 EXCLUDE_SYMBOLS        =
    549397
    550398# The EXAMPLE_PATH tag can be used to specify one or more files or
     
    579427# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
    580428# input file. Doxygen will then use the output that the filter program writes
    581 # to standard output.  If FILTER_PATTERNS is specified, this tag will be
    582 # ignored.
     429# to standard output.
    583430
    584431INPUT_FILTER           =
    585 
    586 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
    587 # basis.  Doxygen will compare the file name with each pattern and apply the
    588 # filter if there is a match.  The filters are a list of the form:
    589 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
    590 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
    591 # is applied to all files.
    592 
    593 FILTER_PATTERNS        =
    594432
    595433# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
     
    604442
    605443# If the SOURCE_BROWSER tag is set to YES then a list of source files will
    606 # be generated. Documented entities will be cross-referenced with these sources.
    607 # Note: To get rid of all source code in the generated output, make sure also
    608 # VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH
    609 # then you must also enable this option. If you don't then doxygen will produce
    610 # a warning and turn it on anyway
     444# be generated. Documented entities will be cross-referenced with these sources.
    611445
    612446SOURCE_BROWSER         = NO
     
    634468
    635469REFERENCES_RELATION    = YES
    636 
    637 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
    638 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
    639 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
    640 # link to the source code.  Otherwise they will link to the documentstion.
    641 
    642 REFERENCES_LINK_SOURCE = YES
    643 
    644 # If the USE_HTAGS tag is set to YES then the references to source code
    645 # will point to the HTML generated by the htags(1) tool instead of doxygen
    646 # built-in source browser. The htags tool is part of GNU's global source
    647 # tagging system (see http://www.gnu.org/software/global/global.html). You
    648 # will need version 4.8.6 or higher.
    649 
    650 USE_HTAGS              = NO
    651470
    652471# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
     
    715534# style sheet that is used by each HTML page. It can be used to
    716535# fine-tune the look of the HTML output. If the tag is left blank doxygen
    717 # will generate a default style sheet. Note that doxygen will try to copy
    718 # the style sheet file to the HTML output directory, so don't put your own
    719 # stylesheet in the HTML output directory as well, or it will be erased!
     536# will generate a default style sheet
    720537
    721538HTML_STYLESHEET        =
     
    734551GENERATE_HTMLHELP      = NO
    735552
    736 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
    737 # documentation will contain sections that can be hidden and shown after the
    738 # page has loaded. For this to work a browser that supports
    739 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
    740 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
    741 
    742 HTML_DYNAMIC_SECTIONS  = NO
    743 
    744553# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
    745554# be used to specify the file name of the resulting .chm file. You
    746555# can add a path in front of the file if the result should not be
    747 # written to the html output directory.
     556# written to the html output dir.
    748557
    749558CHM_FILE               =
     
    880689
    881690# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
    882 # The RTF output is optimized for Word 97 and may not look very pretty with
     691# The RTF output is optimised for Word 97 and may not look very pretty with
    883692# other RTF readers or editors.
    884693
     
    907716
    908717# Load stylesheet definitions from file. Syntax is similar to doxygen's
    909 # config file, i.e. a series of assignments. You only have to provide
     718# config file, i.e. a series of assigments. You only have to provide
    910719# replacements, missing definitions are set to their default value.
    911720
     
    951760# If the GENERATE_XML tag is set to YES Doxygen will
    952761# generate an XML file that captures the structure of
    953 # the code including all documentation.
     762# the code including all documentation. Note that this
     763# feature is still experimental and incomplete at the
     764# moment.
    954765
    955766GENERATE_XML           = NO
     
    972783
    973784XML_DTD                =
    974 
    975 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
    976 # dump the program listings (including syntax highlighting
    977 # and cross-referencing information) to the XML output. Note that
    978 # enabling this will significantly increase the size of the XML output.
    979 
    980 XML_PROGRAMLISTING     = YES
    981785
    982786#---------------------------------------------------------------------------
     
    1044848# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
    1045849# then the macro expansion is limited to the macros specified with the
    1046 # PREDEFINED and EXPAND_AS_DEFINED tags.
     850# PREDEFINED and EXPAND_AS_PREDEFINED tags.
    1047851
    1048852EXPAND_ONLY_PREDEF     = NO
     
    1070874# gcc). The argument of the tag is a list of macros of the form: name
    1071875# or name=definition (no spaces). If the definition and the = are
    1072 # omitted =1 is assumed. To prevent a macro definition from being
    1073 # undefined via #undef or recursively expanded use the := operator
    1074 # instead of the = operator.
     876# omitted =1 is assumed.
    1075877
    1076878PREDEFINED             = FALSE=0 \
    1077                          CPU_USE_GENERIC_BITFIELD_DATA=0
     879   CPU_USE_GENERIC_BITFIELD_DATA=0
    1078880
    1079881# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
     
    1087889# doxygen's preprocessor will remove all function-like macros that are alone
    1088890# on a line, have an all uppercase name, and do not end with a semicolon. Such
    1089 # function macros are typically used for boiler-plate code, and will confuse
    1090 # the parser if not removed.
     891# function macros are typically used for boiler-plate code, and will confuse the
     892# parser if not removed.
    1091893
    1092894SKIP_FUNCTION_MACROS   = YES
    1093895
    1094896#---------------------------------------------------------------------------
    1095 # Configuration::additions related to external references   
     897# Configuration::addtions related to external references   
    1096898#---------------------------------------------------------------------------
    1097899
     
    1140942
    1141943# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
    1142 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
    1143 # or super classes. Setting the tag to NO turns the diagrams off. Note that
    1144 # this option is superseded by the HAVE_DOT option below. This is only a
    1145 # fallback. It is recommended to install and use dot, since it yields more
    1146 # powerful graphs.
     944# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
     945# super classes. Setting the tag to NO turns the diagrams off. Note that this
     946# option is superceded by the HAVE_DOT option below. This is only a fallback. It is
     947# recommended to install and use dot, since it yields more powerful graphs.
    1147948
    1148949CLASS_DIAGRAMS         = YES
    1149 
    1150 # You can define message sequence charts within doxygen comments using the \msc
    1151 # command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to
    1152 # produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to
    1153 # specify the directory where the mscgen tool resides. If left empty the tool is assumed to
    1154 # be found in the default search path.
    1155 
    1156 MSCGEN_PATH            =
    1157950
    1158951# If set to YES, the inheritance and collaboration graphs will hide
     
    1183976COLLABORATION_GRAPH    = YES
    1184977
    1185 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
    1186 # will generate a graph for groups, showing the direct groups dependencies
    1187 
    1188 GROUP_GRAPHS           = YES
    1189 
    1190978# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
    1191 # collaboration diagrams in a style similar to the OMG's Unified Modeling
     979# collaboration diagrams in a style similiar to the OMG's Unified Modeling
    1192980# Language.
    1193981
     
    12131001INCLUDED_BY_GRAPH      = YES
    12141002
    1215 # If the CALL_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will
     1003# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
    12161004# generate a call dependency graph for every global function or class method.
    12171005# Note that enabling this option will significantly increase the time of a run.
     
    12211009CALL_GRAPH             = NO
    12221010
    1223 # If the CALLER_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will
    1224 # generate a caller dependency graph for every global function or class method.
    1225 # Note that enabling this option will significantly increase the time of a run.
    1226 # So in most cases it will be better to enable caller graphs for selected
    1227 # functions only using the \callergraph command.
    1228 
    1229 CALLER_GRAPH           = NO
    1230 
    12311011# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
    12321012# will graphical hierarchy of all classes instead of a textual one.
    12331013
    12341014GRAPHICAL_HIERARCHY    = YES
    1235 
    1236 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
    1237 # then doxygen will show the dependencies a directory has on other directories
    1238 # in a graphical way. The dependency relations are determined by the #include
    1239 # relations between the files in the directories.
    1240 
    1241 DIRECTORY_GRAPH        = YES
    12421015
    12431016# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
     
    12481021
    12491022# The tag DOT_PATH can be used to specify the path where the dot tool can be
    1250 # found. If left blank, it is assumed the dot tool can be found in the path.
     1023# found. If left blank, it is assumed the dot tool can be found on the path.
    12511024
    12521025DOT_PATH               =
     
    12581031DOTFILE_DIRS           =
    12591032
    1260 # The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
    1261 # nodes that will be shown in the graph. If the number of nodes in a graph
    1262 # becomes larger than this value, doxygen will truncate the graph, which is
    1263 # visualized by representing a node as a red box. Note that doxygen if the number
    1264 # of direct children of the root node in a graph is already larger than
    1265 # MAX_DOT_GRAPH_NOTES then the graph will not be shown at all. Also note
    1266 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
    1267 
    1268 DOT_GRAPH_MAX_NODES    = 50
     1033# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
     1034# (in pixels) of the graphs generated by dot. If a graph becomes larger than
     1035# this value, doxygen will try to truncate the graph, so that it fits within
     1036# the specified constraint. Beware that most browsers cannot cope with very
     1037# large images.
     1038
     1039MAX_DOT_GRAPH_WIDTH    = 1024
     1040
     1041# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
     1042# (in pixels) of the graphs generated by dot. If a graph becomes larger than
     1043# this value, doxygen will try to truncate the graph, so that it fits within
     1044# the specified constraint. Beware that most browsers cannot cope with very
     1045# large images.
     1046
     1047MAX_DOT_GRAPH_HEIGHT   = 1024
    12691048
    12701049# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
    12711050# graphs generated by dot. A depth value of 3 means that only nodes reachable
    1272 # from the root by following a path via at most 3 edges will be shown. Nodes
    1273 # that lay further from the root node will be omitted. Note that setting this
    1274 # option to 1 or 2 may greatly reduce the computation time needed for large
    1275 # code bases. Also note that the size of a graph can be further restricted by
    1276 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
     1051# from the root by following a path via at most 3 edges will be shown. Nodes that
     1052# lay further from the root node will be omitted. Note that setting this option to
     1053# 1 or 2 may greatly reduce the computation time needed for large code bases. Also
     1054# note that a graph may be further truncated if the graph's image dimensions are
     1055# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
     1056# If 0 is used for the depth value (the default), the graph is not depth-constrained.
    12771057
    12781058MAX_DOT_GRAPH_DEPTH    = 0
    1279 
    1280 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
    1281 # background. This is disabled by default, which results in a white background.
    1282 # Warning: Depending on the platform used, enabling this option may lead to
    1283 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
    1284 # read).
    1285 
    1286 DOT_TRANSPARENT        = YES
    1287 
    1288 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
    1289 # files in one run (i.e. multiple -o and -T options on the command line). This
    1290 # makes dot run faster, but since only newer versions of dot (>1.8.10)
    1291 # support this, this feature is disabled by default.
    1292 
    1293 DOT_MULTI_TARGETS      = NO
    12941059
    12951060# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
     
    13061071
    13071072#---------------------------------------------------------------------------
    1308 # Configuration::additions related to the search engine   
     1073# Configuration::addtions related to the search engine   
    13091074#---------------------------------------------------------------------------
    13101075
Note: See TracChangeset for help on using the changeset viewer.