IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 9, 2004, 3:58:06 PM (22 years ago)
Author:
desonia
Message:

Added doxygen group tags.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/psLib/src/Doxyfile

    r648 r974  
    2020PROJECT_NAME           = "Pan-STARRS Foundation Library"
    2121
    22 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 
    23 # This could be handy for archiving the generated documentation or 
     22# The PROJECT_NUMBER tag can be used to enter a project or revision number.
     23# This could be handy for archiving the generated documentation or
    2424# if some version control system is used.
    2525
    2626PROJECT_NUMBER         = "$Name: not supported by cvs2svn $"
    2727
    28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
    29 # base path where the generated documentation will be put. 
    30 # If a relative path is entered, it will be relative to the location 
     28# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
     29# base path where the generated documentation will be put.
     30# If a relative path is entered, it will be relative to the location
    3131# where doxygen was started. If left blank the current directory will be used.
    3232
    3333OUTPUT_DIRECTORY       = ../docs
    3434
    35 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    36 # documentation generated by doxygen is written. Doxygen will use this 
    37 # information to generate all constant output in the proper language. 
    38 # The default language is English, other supported languages are: 
    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, 
     35# The OUTPUT_LANGUAGE tag is used to specify the language in which all
     36# documentation generated by doxygen is written. Doxygen will use this
     37# information to generate all constant output in the proper language.
     38# The default language is English, other supported languages are:
     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,
    4242# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
    4343
    4444OUTPUT_LANGUAGE        = English
    4545
    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 
     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
    5252# all platforms other than Windows).
    5353
    5454USE_WINDOWS_ENCODING   = NO
    5555
    56 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
    57 # include brief member descriptions after the members that are listed in 
    58 # the file and class documentation (similar to JavaDoc). 
     56# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
     57# include brief member descriptions after the members that are listed in
     58# the file and class documentation (similar to JavaDoc).
    5959# Set to NO to disable this.
    6060
    6161BRIEF_MEMBER_DESC      = YES
    6262
    63 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
    64 # the brief description of a member or function before the detailed description. 
    65 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
     63# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
     64# the brief description of a member or function before the detailed description.
     65# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
    6666# brief descriptions will be completely suppressed.
    6767
    6868REPEAT_BRIEF           = YES
    6969
    70 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
    71 # Doxygen will generate a detailed section even if there is only a brief 
     70# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
     71# Doxygen will generate a detailed section even if there is only a brief
    7272# description.
    7373
    7474ALWAYS_DETAILED_SEC    = YES
    7575
    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 
     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
    7979# the base classes will not be shown.
    8080
    8181INLINE_INHERITED_MEMB  = NO
    8282
    83 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
    84 # path before files name in the file list and in the header files. If set 
     83# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
     84# path before files name in the file list and in the header files. If set
    8585# to NO the shortest path that makes the file name unique will be used.
    8686
    8787FULL_PATH_NAMES        = NO
    8888
    89 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
    90 # can be used to strip a user-defined part of the path. Stripping is 
    91 # only done if one of the specified strings matches the left-hand part of 
     89# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
     90# can be used to strip a user-defined part of the path. Stripping is
     91# only done if one of the specified strings matches the left-hand part of
    9292# the path. It is allowed to use relative paths in the argument list.
    9393
    94 STRIP_FROM_PATH        = 
    95 
    96 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
    97 # (but less readable) file names. This can be useful is your file systems 
     94STRIP_FROM_PATH        =
     95
     96# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
     97# (but less readable) file names. This can be useful is your file systems
    9898# doesn't support long names like on DOS, Mac, or CD-ROM.
    9999
    100100SHORT_NAMES            = NO
    101101
    102 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
    103 # will interpret the first line (until the first dot) of a JavaDoc-style 
    104 # comment as the brief description. If set to NO, the JavaDoc 
    105 # comments will behave just like the Qt-style comments (thus requiring an 
     102# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
     103# will interpret the first line (until the first dot) of a JavaDoc-style
     104# comment as the brief description. If set to NO, the JavaDoc
     105# comments will behave just like the Qt-style comments (thus requiring an
    106106# explict @brief command for a brief description.
    107107
    108108JAVADOC_AUTOBRIEF      = YES
    109109
    110 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
    111 # treat a multi-line C++ special comment block (i.e. a block of //! or /// 
    112 # comments) as a brief description. This used to be the default behaviour. 
    113 # The new default is to treat a multi-line C++ comment block as a detailed 
     110# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
     111# treat a multi-line C++ special comment block (i.e. a block of //! or ///
     112# comments) as a brief description. This used to be the default behaviour.
     113# The new default is to treat a multi-line C++ comment block as a detailed
    114114# description. Set this tag to YES if you prefer the old behaviour instead.
    115115
    116116MULTILINE_CPP_IS_BRIEF = NO
    117117
    118 # If the DETAILS_AT_TOP tag is set to YES then Doxygen 
     118# If the DETAILS_AT_TOP tag is set to YES then Doxygen
    119119# will output the detailed description near the top, like JavaDoc.
    120 # If set to NO, the detailed description appears after the member 
     120# If set to NO, the detailed description appears after the member
    121121# documentation.
    122122
    123123DETAILS_AT_TOP         = YES
    124124
    125 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
    126 # member inherits the documentation from any documented member that it 
     125# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
     126# member inherits the documentation from any documented member that it
    127127# reimplements.
    128128
    129129INHERIT_DOCS           = YES
    130130
    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 
     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
    134134# all members of a group must be documented explicitly.
    135135
    136136DISTRIBUTE_GROUP_DOC   = NO
    137137
    138 # The TAB_SIZE tag can be used to set the number of spaces in a tab. 
     138# The TAB_SIZE tag can be used to set the number of spaces in a tab.
    139139# Doxygen uses this value to replace tabs by spaces in code fragments.
    140140
    141141TAB_SIZE               = 4
    142142
    143 # This tag can be used to specify a number of aliases that acts 
    144 # as commands in the documentation. An alias has the form "name=value". 
    145 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 
     143# This tag can be used to specify a number of aliases that acts
     144# as commands in the documentation. An alias has the form "name=value".
     145# For example adding "sideeffect=\par Side Effects:\n" will allow you to
    146146# put the command \sideeffect (or @sideeffect) in the documentation, which
    147 # will result in a user-defined paragraph with heading "Side Effects:". 
     147# will result in a user-defined paragraph with heading "Side Effects:".
    148148# You can put \n's in the value part of an alias to insert newlines.
    149149
    150150ALIASES                =
    151151
    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. 
    154 # For instance, some of the names that are used will be different. The list 
     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.
     154# For instance, some of the names that are used will be different. The list
    155155# of all members will be omitted, etc.
    156156
    157157OPTIMIZE_OUTPUT_FOR_C  = YES
    158158
    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. 
    161 # For instance, namespaces will be presented as packages, qualified scopes 
     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.
     161# For instance, namespaces will be presented as packages, qualified scopes
    162162# will look different, etc.
    163163
     
    165165
    166166# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
    167 # the same type (for instance a group of public functions) to be put as a 
    168 # subgroup of that type (e.g. under the Public Functions section). Set it to 
    169 # NO to prevent subgrouping. Alternatively, this can be done per class using 
     167# the same type (for instance a group of public functions) to be put as a
     168# subgroup of that type (e.g. under the Public Functions section). Set it to
     169# NO to prevent subgrouping. Alternatively, this can be done per class using
    170170# the \nosubgrouping command.
    171171
     
    176176#---------------------------------------------------------------------------
    177177
    178 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
    179 # documentation are documented, even if no documentation was available. 
    180 # Private class members and static file members will be hidden unless 
     178# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
     179# documentation are documented, even if no documentation was available.
     180# Private class members and static file members will be hidden unless
    181181# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
    182182
    183183EXTRACT_ALL            = YES
    184184
    185 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
     185# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
    186186# will be included in the documentation.
    187187
    188188EXTRACT_PRIVATE        = NO
    189189
    190 # If the EXTRACT_STATIC tag is set to YES all static members of a file 
     190# If the EXTRACT_STATIC tag is set to YES all static members of a file
    191191# will be included in the documentation.
    192192
    193193EXTRACT_STATIC         = NO
    194194
    195 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
    196 # defined locally in source files will be included in the documentation. 
     195# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
     196# defined locally in source files will be included in the documentation.
    197197# If set to NO only classes defined in header files are included.
    198198
    199199EXTRACT_LOCAL_CLASSES  = NO
    200200
    201 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
    202 # undocumented members of documented classes, files or namespaces. 
    203 # If set to NO (the default) these members will be included in the 
    204 # various overviews, but no documentation section is generated. 
     201# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
     202# undocumented members of documented classes, files or namespaces.
     203# If set to NO (the default) these members will be included in the
     204# various overviews, but no documentation section is generated.
    205205# This option has no effect if EXTRACT_ALL is enabled.
    206206
    207207HIDE_UNDOC_MEMBERS     = NO
    208208
    209 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
    210 # undocumented classes that are normally visible in the class hierarchy. 
    211 # If set to NO (the default) these classes will be included in the various 
     209# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
     210# undocumented classes that are normally visible in the class hierarchy.
     211# If set to NO (the default) these classes will be included in the various
    212212# overviews. This option has no effect if EXTRACT_ALL is enabled.
    213213
    214214HIDE_UNDOC_CLASSES     = NO
    215215
    216 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
    217 # friend (class|struct|union) declarations. 
    218 # If set to NO (the default) these declarations will be included in the 
     216# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
     217# friend (class|struct|union) declarations.
     218# If set to NO (the default) these declarations will be included in the
    219219# documentation.
    220220
     
    230230# The INTERNAL_DOCS tag determines if documentation
    231231# that is typed after a \internal command is included. If the tag is set
    232 # to NO (the default) then the documentation will be excluded. 
     232# to NO (the default) then the documentation will be excluded.
    233233# Set it to YES to include the internal documentation.
    234234
     
    298298# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
    299299# the initial value of a variable or define consists of for it to appear in
    300 # the documentation. If the initializer consists of more lines than specified 
     300# the documentation. If the initializer consists of more lines than specified
    301301# here it will be hidden. Use a value of 0 to hide initializers completely.
    302302# The appearance of the initializer of individual variables and defines in the
     
    322322
    323323# The WARNINGS tag can be used to turn on/off the warning messages that are
    324 # generated by doxygen. Possible values are YES and NO. If left blank 
     324# generated by doxygen. Possible values are YES and NO. If left blank
    325325# NO is used.
    326326
     
    362362# with spaces.
    363363
    364 INPUT                  = mainpage.dox \
     364INPUT                  = pslib.h \
     365                         mainpage.dox \
    365366                         sysUtils \
    366367                         dataManip \
     
    374375# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
    375376
    376 FILE_PATTERNS          = 
     377FILE_PATTERNS          =
    377378
    378379# The RECURSIVE tag can be used to turn specify whether or not subdirectories
     
    382383RECURSIVE              = YES
    383384
    384 # The EXCLUDE tag can be used to specify files and/or directories that should 
     385# The EXCLUDE tag can be used to specify files and/or directories that should
    385386# excluded from the INPUT source files. This way you can easily exclude a
    386387# subdirectory from a directory tree whose root is specified with the INPUT tag.
Note: See TracChangeset for help on using the changeset viewer.