annotate src/opus-1.3/doc/Doxyfile.in @ 83:ae30d91d2ffe

Replace these with versions built using an older toolset (so as to avoid ABI compatibilities when linking on Ubuntu 14.04 for packaging purposes)
author Chris Cannam
date Fri, 07 Feb 2020 11:51:13 +0000
parents 7aeed7906520
children
rev   line source
Chris@69 1 # Doxyfile 1.8.10
Chris@69 2
Chris@69 3 # This file describes the settings to be used by the documentation system
Chris@69 4 # doxygen (www.doxygen.org) for a project.
Chris@69 5 #
Chris@69 6 # All text after a double hash (##) is considered a comment and is placed in
Chris@69 7 # front of the TAG it is preceding.
Chris@69 8 #
Chris@69 9 # All text after a single hash (#) is considered a comment and will be ignored.
Chris@69 10 # The format is:
Chris@69 11 # TAG = value [value, ...]
Chris@69 12 # For lists, items can also be appended using:
Chris@69 13 # TAG += value [value, ...]
Chris@69 14 # Values that contain spaces should be placed between quotes (\" \").
Chris@69 15
Chris@69 16 # Only non-default options are included below to improve portability
Chris@69 17 # between doxygen versions.
Chris@69 18 #
Chris@69 19 #---------------------------------------------------------------------------
Chris@69 20 # Project related configuration options
Chris@69 21 #---------------------------------------------------------------------------
Chris@69 22
Chris@69 23 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
Chris@69 24 # double-quotes, unless you are using Doxywizard) that should identify the
Chris@69 25 # project for which the documentation is generated. This name is used in the
Chris@69 26 # title of most generated pages and in a few other places.
Chris@69 27 # The default value is: My Project.
Chris@69 28
Chris@69 29 PROJECT_NAME = Opus
Chris@69 30
Chris@69 31 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
Chris@69 32 # could be handy for archiving the generated documentation or if some version
Chris@69 33 # control system is used.
Chris@69 34
Chris@69 35 PROJECT_NUMBER = @VERSION@
Chris@69 36
Chris@69 37 # Using the PROJECT_BRIEF tag one can provide an optional one line description
Chris@69 38 # for a project that appears at the top of each page and should give viewer a
Chris@69 39 # quick idea about the purpose of the project. Keep the description short.
Chris@69 40
Chris@69 41 PROJECT_BRIEF = "Opus audio codec (RFC 6716): API and operations manual"
Chris@69 42
Chris@69 43 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
Chris@69 44 # in the documentation. The maximum height of the logo should not exceed 55
Chris@69 45 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
Chris@69 46 # the logo to the output directory.
Chris@69 47
Chris@69 48 PROJECT_LOGO =
Chris@69 49
Chris@69 50 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
Chris@69 51 # before files name in the file list and in the header files. If set to NO the
Chris@69 52 # shortest path that makes the file name unique will be used
Chris@69 53 # The default value is: YES.
Chris@69 54
Chris@69 55 FULL_PATH_NAMES = NO
Chris@69 56
Chris@69 57 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
Chris@69 58 # first line (until the first dot) of a Javadoc-style comment as the brief
Chris@69 59 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
Chris@69 60 # style comments (thus requiring an explicit @brief command for a brief
Chris@69 61 # description.)
Chris@69 62 # The default value is: NO.
Chris@69 63
Chris@69 64 JAVADOC_AUTOBRIEF = YES
Chris@69 65
Chris@69 66 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
Chris@69 67 # uses this value to replace tabs by spaces in code fragments.
Chris@69 68 # Minimum value: 1, maximum value: 16, default value: 4.
Chris@69 69
Chris@69 70 TAB_SIZE = 8
Chris@69 71
Chris@69 72 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
Chris@69 73 # only. Doxygen will then generate output that is more tailored for C. For
Chris@69 74 # instance, some of the names that are used will be different. The list of all
Chris@69 75 # members will be omitted, etc.
Chris@69 76 # The default value is: NO.
Chris@69 77
Chris@69 78 OPTIMIZE_OUTPUT_FOR_C = YES
Chris@69 79
Chris@69 80 #---------------------------------------------------------------------------
Chris@69 81 # Build related configuration options
Chris@69 82 #---------------------------------------------------------------------------
Chris@69 83
Chris@69 84 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
Chris@69 85 # documentation are documented, even if no documentation was available. Private
Chris@69 86 # class members and static file members will be hidden unless the
Chris@69 87 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
Chris@69 88 # Note: This will also disable the warnings about undocumented members that are
Chris@69 89 # normally produced when WARNINGS is set to YES.
Chris@69 90 # The default value is: NO.
Chris@69 91
Chris@69 92 EXTRACT_ALL = YES
Chris@69 93
Chris@69 94 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
Chris@69 95 # be included in the documentation.
Chris@69 96 # The default value is: NO.
Chris@69 97
Chris@69 98 EXTRACT_PRIVATE = NO
Chris@69 99
Chris@69 100 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
Chris@69 101 # names in lower-case letters. If set to YES, upper-case letters are also
Chris@69 102 # allowed. This is useful if you have classes or files whose names only differ
Chris@69 103 # in case and if your file system supports case sensitive file names. Windows
Chris@69 104 # and Mac users are advised to set this option to NO.
Chris@69 105 # The default value is: system dependent.
Chris@69 106
Chris@69 107 CASE_SENSE_NAMES = YES
Chris@69 108
Chris@69 109 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
Chris@69 110 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
Chris@69 111 # ... \endcond blocks.
Chris@69 112
Chris@69 113 ENABLED_SECTIONS =
Chris@69 114
Chris@69 115 #---------------------------------------------------------------------------
Chris@69 116 # Configuration options related to warning and progress messages
Chris@69 117 #---------------------------------------------------------------------------
Chris@69 118
Chris@69 119 # The QUIET tag can be used to turn on/off the messages that are generated to
Chris@69 120 # standard output by doxygen. If QUIET is set to YES this implies that the
Chris@69 121 # messages are off.
Chris@69 122 # The default value is: NO.
Chris@69 123
Chris@69 124 QUIET = YES
Chris@69 125
Chris@69 126 # The WARNINGS tag can be used to turn on/off the warning messages that are
Chris@69 127 # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
Chris@69 128 # this implies that the warnings are on.
Chris@69 129 #
Chris@69 130 # Tip: Turn warnings on while writing the documentation.
Chris@69 131 # The default value is: YES.
Chris@69 132
Chris@69 133 WARNINGS = YES
Chris@69 134
Chris@69 135 #---------------------------------------------------------------------------
Chris@69 136 # Configuration options related to the input files
Chris@69 137 #---------------------------------------------------------------------------
Chris@69 138
Chris@69 139 # The INPUT tag is used to specify the files and/or directories that contain
Chris@69 140 # documented source files. You may enter file names like myfile.cpp or
Chris@69 141 # directories like /usr/src/myproject. Separate the files or directories with
Chris@69 142 # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
Chris@69 143 # Note: If this tag is empty the current directory is searched.
Chris@69 144
Chris@69 145 INPUT = @top_srcdir@/include/opus.h \
Chris@69 146 @top_srcdir@/include/opus_types.h \
Chris@69 147 @top_srcdir@/include/opus_defines.h \
Chris@69 148 @top_srcdir@/include/opus_multistream.h \
Chris@69 149 @top_srcdir@/include/opus_custom.h
Chris@69 150
Chris@69 151 # The EXCLUDE tag can be used to specify files and/or directories that should be
Chris@69 152 # excluded from the INPUT source files. This way you can easily exclude a
Chris@69 153 # subdirectory from a directory tree whose root is specified with the INPUT tag.
Chris@69 154 #
Chris@69 155 # Note that relative paths are relative to the directory from which doxygen is
Chris@69 156 # run.
Chris@69 157
Chris@69 158 EXCLUDE =
Chris@69 159
Chris@69 160 #---------------------------------------------------------------------------
Chris@69 161 # Configuration options related to the alphabetical class index
Chris@69 162 #---------------------------------------------------------------------------
Chris@69 163
Chris@69 164 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
Chris@69 165 # compounds will be generated. Enable this if the project contains a lot of
Chris@69 166 # classes, structs, unions or interfaces.
Chris@69 167 # The default value is: YES.
Chris@69 168
Chris@69 169 ALPHABETICAL_INDEX = NO
Chris@69 170
Chris@69 171 #---------------------------------------------------------------------------
Chris@69 172 # Configuration options related to the HTML output
Chris@69 173 #---------------------------------------------------------------------------
Chris@69 174
Chris@69 175 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
Chris@69 176 # each generated HTML page. If the tag is left blank doxygen will generate a
Chris@69 177 # standard header.
Chris@69 178 #
Chris@69 179 # To get valid HTML the header file that includes any scripts and style sheets
Chris@69 180 # that doxygen needs, which is dependent on the configuration options used (e.g.
Chris@69 181 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
Chris@69 182 # default header using
Chris@69 183 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
Chris@69 184 # YourConfigFile
Chris@69 185 # and then modify the file new_header.html. See also section "Doxygen usage"
Chris@69 186 # for information on how to generate the default header that doxygen normally
Chris@69 187 # uses.
Chris@69 188 # Note: The header is subject to change so you typically have to regenerate the
Chris@69 189 # default header when upgrading to a newer version of doxygen. For a description
Chris@69 190 # of the possible markers and block names see the documentation.
Chris@69 191 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 192
Chris@69 193 HTML_HEADER = @top_srcdir@/doc/header.html
Chris@69 194
Chris@69 195 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
Chris@69 196 # generated HTML page. If the tag is left blank doxygen will generate a standard
Chris@69 197 # footer. See HTML_HEADER for more information on how to generate a default
Chris@69 198 # footer and what special commands can be used inside the footer. See also
Chris@69 199 # section "Doxygen usage" for information on how to generate the default footer
Chris@69 200 # that doxygen normally uses.
Chris@69 201 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 202
Chris@69 203 HTML_FOOTER = @top_srcdir@/doc/footer.html
Chris@69 204
Chris@69 205 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
Chris@69 206 # sheet that is used by each HTML page. It can be used to fine-tune the look of
Chris@69 207 # the HTML output. If left blank doxygen will generate a default style sheet.
Chris@69 208 # See also section "Doxygen usage" for information on how to generate the style
Chris@69 209 # sheet that doxygen normally uses.
Chris@69 210 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
Chris@69 211 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
Chris@69 212 # obsolete.
Chris@69 213 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 214
Chris@69 215 HTML_STYLESHEET = @top_srcdir@/doc/customdoxygen.css
Chris@69 216
Chris@69 217 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
Chris@69 218 # other source files which should be copied to the HTML output directory. Note
Chris@69 219 # that these files will be copied to the base HTML output directory. Use the
Chris@69 220 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
Chris@69 221 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
Chris@69 222 # files will be copied as-is; there are no commands or markers available.
Chris@69 223 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 224
Chris@69 225 HTML_EXTRA_FILES = @top_srcdir@/doc/opus_logo.svg
Chris@69 226
Chris@69 227 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
Chris@69 228 # in the HTML output. For a value of 0 the output will use grayscales only. A
Chris@69 229 # value of 255 will produce the most vivid colors.
Chris@69 230 # Minimum value: 0, maximum value: 255, default value: 100.
Chris@69 231 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 232
Chris@69 233 HTML_COLORSTYLE_SAT = 0
Chris@69 234
Chris@69 235 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
Chris@69 236 # page will contain the date and time when the page was generated. Setting this
Chris@69 237 # to YES can help to show when doxygen was last run and thus if the
Chris@69 238 # documentation is up to date.
Chris@69 239 # The default value is: NO.
Chris@69 240 # This tag requires that the tag GENERATE_HTML is set to YES.
Chris@69 241
Chris@69 242 HTML_TIMESTAMP = YES
Chris@69 243
Chris@69 244 # When MathJax is enabled you need to specify the location relative to the HTML
Chris@69 245 # output directory using the MATHJAX_RELPATH option. The destination directory
Chris@69 246 # should contain the MathJax.js script. For instance, if the mathjax directory
Chris@69 247 # is located at the same level as the HTML output directory, then
Chris@69 248 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
Chris@69 249 # Content Delivery Network so you can quickly see the result without installing
Chris@69 250 # MathJax. However, it is strongly recommended to install a local copy of
Chris@69 251 # MathJax from http://www.mathjax.org before deployment.
Chris@69 252 # The default value is: http://cdn.mathjax.org/mathjax/latest.
Chris@69 253 # This tag requires that the tag USE_MATHJAX is set to YES.
Chris@69 254
Chris@69 255 MATHJAX_RELPATH = https://www.mathjax.org/mathjax
Chris@69 256
Chris@69 257 #---------------------------------------------------------------------------
Chris@69 258 # Configuration options related to the LaTeX output
Chris@69 259 #---------------------------------------------------------------------------
Chris@69 260
Chris@69 261 # The PAPER_TYPE tag can be used to set the paper type that is used by the
Chris@69 262 # printer.
Chris@69 263 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
Chris@69 264 # 14 inches) and executive (7.25 x 10.5 inches).
Chris@69 265 # The default value is: a4.
Chris@69 266 # This tag requires that the tag GENERATE_LATEX is set to YES.
Chris@69 267
Chris@69 268 PAPER_TYPE = letter
Chris@69 269
Chris@69 270 #---------------------------------------------------------------------------
Chris@69 271 # Configuration options related to the man page output
Chris@69 272 #---------------------------------------------------------------------------
Chris@69 273
Chris@69 274 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
Chris@69 275 # classes and files.
Chris@69 276 # The default value is: NO.
Chris@69 277
Chris@69 278 GENERATE_MAN = YES
Chris@69 279
Chris@69 280 #---------------------------------------------------------------------------
Chris@69 281 # Configuration options related to the preprocessor
Chris@69 282 #---------------------------------------------------------------------------
Chris@69 283
Chris@69 284 # If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
Chris@69 285 # in the source code. If set to NO, only conditional compilation will be
Chris@69 286 # performed. Macro expansion can be done in a controlled way by setting
Chris@69 287 # EXPAND_ONLY_PREDEF to YES.
Chris@69 288 # The default value is: NO.
Chris@69 289 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
Chris@69 290
Chris@69 291 MACRO_EXPANSION = YES
Chris@69 292
Chris@69 293 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
Chris@69 294 # the macro expansion is limited to the macros specified with the PREDEFINED and
Chris@69 295 # EXPAND_AS_DEFINED tags.
Chris@69 296 # The default value is: NO.
Chris@69 297 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
Chris@69 298
Chris@69 299 EXPAND_ONLY_PREDEF = YES
Chris@69 300
Chris@69 301 # The INCLUDE_PATH tag can be used to specify one or more directories that
Chris@69 302 # contain include files that are not input files but should be processed by the
Chris@69 303 # preprocessor.
Chris@69 304 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
Chris@69 305
Chris@69 306 INCLUDE_PATH =
Chris@69 307
Chris@69 308 # The PREDEFINED tag can be used to specify one or more macro names that are
Chris@69 309 # defined before the preprocessor is started (similar to the -D option of e.g.
Chris@69 310 # gcc). The argument of the tag is a list of macros of the form: name or
Chris@69 311 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
Chris@69 312 # is assumed. To prevent a macro definition from being undefined via #undef or
Chris@69 313 # recursively expanded use the := operator instead of the = operator.
Chris@69 314 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
Chris@69 315
Chris@69 316 PREDEFINED = OPUS_EXPORT= \
Chris@69 317 OPUS_CUSTOM_EXPORT= \
Chris@69 318 OPUS_CUSTOM_EXPORT_STATIC= \
Chris@69 319 OPUS_WARN_UNUSED_RESULT= \
Chris@69 320 OPUS_ARG_NONNULL(_x)=
Chris@69 321
Chris@69 322 #---------------------------------------------------------------------------
Chris@69 323 # Configuration options related to the dot tool
Chris@69 324 #---------------------------------------------------------------------------
Chris@69 325
Chris@69 326 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
Chris@69 327 # available from the path. This tool is part of Graphviz (see:
Chris@69 328 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
Chris@69 329 # Bell Labs.
Chris@69 330
Chris@69 331 # Debian defaults to YES here, while Fedora and Homebrew default to NO.
Chris@69 332 # So we set this based on whether the graphviz package is available at
Chris@69 333 # configure time.
Chris@69 334 #
Chris@69 335 HAVE_DOT = @HAVE_DOT@