├── .gitignore ├── LICENSE.txt ├── Makefile.am ├── README.md ├── api ├── Doxyfile.in └── Makefile.am ├── autogen.sh ├── configure.ac ├── include └── Audio.H ├── js ├── AudioProcessor.js ├── post.js └── pre.js ├── m4 └── emscripten.m4 ├── madChopsCoderAu.png ├── src ├── Audio.C └── Makefile.am ├── test ├── Makefile.am └── RunTest.js ├── tools ├── autotools.sh └── autotoolsClean.sh └── webApp ├── demo ├── index.html └── libwasmaudio.js ├── index.html ├── libwasmaudio.js ├── package.json └── test-element.js /.gitignore: -------------------------------------------------------------------------------- 1 | config.* 2 | configure 3 | Makefile 4 | Makefile.in 5 | aclocal.m4 6 | Doxyfile 7 | *.stamp 8 | api/html 9 | autom4te.cache 10 | compile 11 | depcomp 12 | install-sh 13 | libtool 14 | ltmain.sh 15 | missing 16 | .deps 17 | .libs 18 | *.la 19 | *.lo 20 | *.o 21 | a.out 22 | stamp-h1 23 | test/*Test 24 | m4 25 | a.out.js 26 | a.out.js.mem 27 | contest.* 28 | confdefs.h 29 | bower_components 30 | node_modules 31 | package-lock.json 32 | a.out* 33 | *.pem -------------------------------------------------------------------------------- /LICENSE.txt: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASMAudio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | -------------------------------------------------------------------------------- /Makefile.am: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2017-2018 The WASMAudio Authors. All rights reserved. 2 | # 3 | # Redistribution and use in source and binary forms, with or without 4 | # modification, are permitted provided that the following conditions are 5 | # met: 6 | # 7 | # * Redistributions of source code must retain the above copyright 8 | # notice, this list of conditions and the following disclaimer. 9 | # * Redistributions in binary form must reproduce the above 10 | # copyright notice, this list of conditions and the following disclaimer 11 | # in the documentation and/or other materials provided with the 12 | # distribution. 13 | # * Neither the name of mad chops coder AU nor the names of its 14 | # contributors may be used to endorse or promote products derived from 15 | # this software without specific prior written permission. 16 | # 17 | # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | # A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | # OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | # THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | AUTOMAKE_OPTIONS = foreign subdir-objects 30 | SUBDIRS = src test api 31 | 32 | ACLOCAL_AMFLAGS = -I m4 33 | 34 | EXTRA_DIST = README.md LICENSE.txt 35 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # WASMAudio 2 | 3 | Example project for processing AudioWorklet audio in WASM code. 4 | 5 | # Prerequisites 6 | 7 | This project uses the Eigen headers : http://eigen.tuxfamily.org 8 | The Eigen package allows the handling of audio in matrices and is a powerful 9 | numerical processing in C++ tool. 10 | 11 | # Building 12 | ## Initial Setup 13 | 14 | ./tools/autotools.sh 15 | 16 | ## configuring 17 | ### native C++ 18 | ./configure 19 | 20 | ### WASM 21 | emconfigure ./configure 22 | 23 | ## building 24 | ### native C++ 25 | make 26 | ### WASM 27 | emmake make 28 | 29 | ## installing 30 | 31 | Really ? 32 | 33 | # Running the webapp 34 | 35 | cd webApp 36 | 37 | ### installing 38 | 39 | npm install 40 | 41 | ### running 42 | 43 | npm start 44 | 45 | # Reference 46 | 47 | The original mad chops coder AU 48 | ![mad chops coder AU icon](https://raw.githubusercontent.com/flatmax/WASMAudio/master/madChopsCoderAu.png) 49 | -------------------------------------------------------------------------------- /api/Doxyfile.in: -------------------------------------------------------------------------------- 1 | # Doxyfile 1.8.1.2 2 | # Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 3 | # 4 | # Redistribution and use in source and binary forms, with or without 5 | # modification, are permitted provided that the following conditions are 6 | # met: 7 | # 8 | # * Redistributions of source code must retain the above copyright 9 | # notice, this list of conditions and the following disclaimer. 10 | # * Redistributions in binary form must reproduce the above 11 | # copyright notice, this list of conditions and the following disclaimer 12 | # in the documentation and/or other materials provided with the 13 | # distribution. 14 | # * Neither the name of mad chops coder AU nor the names of its 15 | # contributors may be used to endorse or promote products derived from 16 | # this software without specific prior written permission. 17 | # 18 | # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 19 | # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 20 | # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 21 | # A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 22 | # OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 23 | # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 24 | # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 25 | # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 26 | # THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 27 | # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 28 | # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 29 | 30 | # This file describes the settings to be used by the documentation system 31 | # doxygen (www.doxygen.org) for a project 32 | # 33 | # All text after a hash (#) is considered a comment and will be ignored 34 | # The format is: 35 | # TAG = value [value, ...] 36 | # For lists items can also be appended using: 37 | # TAG += value [value, ...] 38 | # Values that contain spaces should be placed between quotes (" ") 39 | 40 | #--------------------------------------------------------------------------- 41 | # Project related configuration options 42 | #--------------------------------------------------------------------------- 43 | 44 | # This tag specifies the encoding used for all characters in the config file 45 | # that follow. The default is UTF-8 which is also the encoding used for all 46 | # text before the first occurrence of this tag. Doxygen uses libiconv (or the 47 | # iconv built into libc) for the transcoding. See 48 | # http://www.gnu.org/software/libiconv for the list of possible encodings. 49 | 50 | DOXYFILE_ENCODING = UTF-8 51 | 52 | # The PROJECT_NAME tag is a single word (or sequence of words) that should 53 | # identify the project. Note that if you do not use Doxywizard you need 54 | # to put quotes around the project name if it contains spaces. 55 | 56 | PROJECT_NAME = @PACKAGE_NAME@ 57 | 58 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. 59 | # This could be handy for archiving the generated documentation or 60 | # if some version control system is used. 61 | 62 | PROJECT_NUMBER = @PACKAGE_VERSION@ 63 | 64 | # Using the PROJECT_BRIEF tag one can provide an optional one line description 65 | # for a project that appears at the top of each page and should give viewer 66 | # a quick idea about the purpose of the project. Keep the description short. 67 | 68 | PROJECT_BRIEF = 69 | 70 | # With the PROJECT_LOGO tag one can specify an logo or icon that is 71 | # included in the documentation. The maximum height of the logo should not 72 | # exceed 55 pixels and the maximum width should not exceed 200 pixels. 73 | # Doxygen will copy the logo to the output directory. 74 | 75 | PROJECT_LOGO = 76 | 77 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 78 | # base path where the generated documentation will be put. 79 | # If a relative path is entered, it will be relative to the location 80 | # where doxygen was started. If left blank the current directory will be used. 81 | 82 | OUTPUT_DIRECTORY = 83 | 84 | # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 85 | # 4096 sub-directories (in 2 levels) under the output directory of each output 86 | # format and will distribute the generated files over these directories. 87 | # Enabling this option can be useful when feeding doxygen a huge amount of 88 | # source files, where putting all generated files in the same directory would 89 | # otherwise cause performance problems for the file system. 90 | 91 | CREATE_SUBDIRS = NO 92 | 93 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all 94 | # documentation generated by doxygen is written. Doxygen will use this 95 | # information to generate all constant output in the proper language. 96 | # The default language is English, other supported languages are: 97 | # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 98 | # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 99 | # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 100 | # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 101 | # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, 102 | # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 103 | 104 | OUTPUT_LANGUAGE = English 105 | 106 | # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 107 | # include brief member descriptions after the members that are listed in 108 | # the file and class documentation (similar to JavaDoc). 109 | # Set to NO to disable this. 110 | 111 | BRIEF_MEMBER_DESC = YES 112 | 113 | # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 114 | # the brief description of a member or function before the detailed description. 115 | # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 116 | # brief descriptions will be completely suppressed. 117 | 118 | REPEAT_BRIEF = YES 119 | 120 | # This tag implements a quasi-intelligent brief description abbreviator 121 | # that is used to form the text in various listings. Each string 122 | # in this list, if found as the leading text of the brief description, will be 123 | # stripped from the text and the result after processing the whole list, is 124 | # used as the annotated text. Otherwise, the brief description is used as-is. 125 | # If left blank, the following values are used ("$name" is automatically 126 | # replaced with the name of the entity): "The $name class" "The $name widget" 127 | # "The $name file" "is" "provides" "specifies" "contains" 128 | # "represents" "a" "an" "the" 129 | 130 | ABBREVIATE_BRIEF = 131 | 132 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 133 | # Doxygen will generate a detailed section even if there is only a brief 134 | # description. 135 | 136 | ALWAYS_DETAILED_SEC = NO 137 | 138 | # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 139 | # inherited members of a class in the documentation of that class as if those 140 | # members were ordinary class members. Constructors, destructors and assignment 141 | # operators of the base classes will not be shown. 142 | 143 | INLINE_INHERITED_MEMB = NO 144 | 145 | # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 146 | # path before files name in the file list and in the header files. If set 147 | # to NO the shortest path that makes the file name unique will be used. 148 | 149 | FULL_PATH_NAMES = YES 150 | 151 | # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 152 | # can be used to strip a user-defined part of the path. Stripping is 153 | # only done if one of the specified strings matches the left-hand part of 154 | # the path. The tag can be used to show relative paths in the file list. 155 | # If left blank the directory from which doxygen is run is used as the 156 | # path to strip. 157 | 158 | STRIP_FROM_PATH = 159 | 160 | # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 161 | # the path mentioned in the documentation of a class, which tells 162 | # the reader which header file to include in order to use a class. 163 | # If left blank only the name of the header file containing the class 164 | # definition is used. Otherwise one should specify the include paths that 165 | # are normally passed to the compiler using the -I flag. 166 | 167 | STRIP_FROM_INC_PATH = 168 | 169 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 170 | # (but less readable) file names. This can be useful if your file system 171 | # doesn't support long names like on DOS, Mac, or CD-ROM. 172 | 173 | SHORT_NAMES = NO 174 | 175 | # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 176 | # will interpret the first line (until the first dot) of a JavaDoc-style 177 | # comment as the brief description. If set to NO, the JavaDoc 178 | # comments will behave just like regular Qt-style comments 179 | # (thus requiring an explicit @brief command for a brief description.) 180 | 181 | JAVADOC_AUTOBRIEF = NO 182 | 183 | # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 184 | # interpret the first line (until the first dot) of a Qt-style 185 | # comment as the brief description. If set to NO, the comments 186 | # will behave just like regular Qt-style comments (thus requiring 187 | # an explicit \brief command for a brief description.) 188 | 189 | QT_AUTOBRIEF = NO 190 | 191 | # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 192 | # treat a multi-line C++ special comment block (i.e. a block of //! or /// 193 | # comments) as a brief description. This used to be the default behaviour. 194 | # The new default is to treat a multi-line C++ comment block as a detailed 195 | # description. Set this tag to YES if you prefer the old behaviour instead. 196 | 197 | MULTILINE_CPP_IS_BRIEF = NO 198 | 199 | # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 200 | # member inherits the documentation from any documented member that it 201 | # re-implements. 202 | 203 | INHERIT_DOCS = YES 204 | 205 | # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 206 | # a new page for each member. If set to NO, the documentation of a member will 207 | # be part of the file/class/namespace that contains it. 208 | 209 | SEPARATE_MEMBER_PAGES = NO 210 | 211 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. 212 | # Doxygen uses this value to replace tabs by spaces in code fragments. 213 | 214 | TAB_SIZE = 8 215 | 216 | # This tag can be used to specify a number of aliases that acts 217 | # as commands in the documentation. An alias has the form "name=value". 218 | # For example adding "sideeffect=\par Side Effects:\n" will allow you to 219 | # put the command \sideeffect (or @sideeffect) in the documentation, which 220 | # will result in a user-defined paragraph with heading "Side Effects:". 221 | # You can put \n's in the value part of an alias to insert newlines. 222 | 223 | ALIASES = 224 | 225 | # This tag can be used to specify a number of word-keyword mappings (TCL only). 226 | # A mapping has the form "name=value". For example adding 227 | # "class=itcl::class" will allow you to use the command class in the 228 | # itcl::class meaning. 229 | 230 | TCL_SUBST = 231 | 232 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 233 | # sources only. Doxygen will then generate output that is more tailored for C. 234 | # For instance, some of the names that are used will be different. The list 235 | # of all members will be omitted, etc. 236 | 237 | OPTIMIZE_OUTPUT_FOR_C = NO 238 | 239 | # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 240 | # sources only. Doxygen will then generate output that is more tailored for 241 | # Java. For instance, namespaces will be presented as packages, qualified 242 | # scopes will look different, etc. 243 | 244 | OPTIMIZE_OUTPUT_JAVA = NO 245 | 246 | # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 247 | # sources only. Doxygen will then generate output that is more tailored for 248 | # Fortran. 249 | 250 | OPTIMIZE_FOR_FORTRAN = NO 251 | 252 | # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 253 | # sources. Doxygen will then generate output that is tailored for 254 | # VHDL. 255 | 256 | OPTIMIZE_OUTPUT_VHDL = NO 257 | 258 | # Doxygen selects the parser to use depending on the extension of the files it 259 | # parses. With this tag you can assign which parser to use for a given extension. 260 | # Doxygen has a built-in mapping, but you can override or extend it using this 261 | # tag. The format is ext=language, where ext is a file extension, and language 262 | # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, 263 | # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make 264 | # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C 265 | # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions 266 | # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. 267 | 268 | EXTENSION_MAPPING = .ice=C++ 269 | 270 | # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all 271 | # comments according to the Markdown format, which allows for more readable 272 | # documentation. See http://daringfireball.net/projects/markdown/ for details. 273 | # The output of markdown processing is further processed by doxygen, so you 274 | # can mix doxygen, HTML, and XML commands with Markdown formatting. 275 | # Disable only in case of backward compatibilities issues. 276 | 277 | MARKDOWN_SUPPORT = YES 278 | 279 | # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 280 | # to include (a tag file for) the STL sources as input, then you should 281 | # set this tag to YES in order to let doxygen match functions declarations and 282 | # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 283 | # func(std::string) {}). This also makes the inheritance and collaboration 284 | # diagrams that involve STL classes more complete and accurate. 285 | 286 | BUILTIN_STL_SUPPORT = YES 287 | 288 | # If you use Microsoft's C++/CLI language, you should set this option to YES to 289 | # enable parsing support. 290 | 291 | CPP_CLI_SUPPORT = NO 292 | 293 | # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 294 | # Doxygen will parse them like normal C++ but will assume all classes use public 295 | # instead of private inheritance when no explicit protection keyword is present. 296 | 297 | SIP_SUPPORT = NO 298 | 299 | # For Microsoft's IDL there are propget and propput attributes to indicate getter 300 | # and setter methods for a property. Setting this option to YES (the default) 301 | # will make doxygen replace the get and set methods by a property in the 302 | # documentation. This will only work if the methods are indeed getting or 303 | # setting a simple type. If this is not the case, or you want to show the 304 | # methods anyway, you should set this option to NO. 305 | 306 | IDL_PROPERTY_SUPPORT = YES 307 | 308 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 309 | # tag is set to YES, then doxygen will reuse the documentation of the first 310 | # member in the group (if any) for the other members of the group. By default 311 | # all members of a group must be documented explicitly. 312 | 313 | DISTRIBUTE_GROUP_DOC = NO 314 | 315 | # Set the SUBGROUPING tag to YES (the default) to allow class member groups of 316 | # the same type (for instance a group of public functions) to be put as a 317 | # subgroup of that type (e.g. under the Public Functions section). Set it to 318 | # NO to prevent subgrouping. Alternatively, this can be done per class using 319 | # the \nosubgrouping command. 320 | 321 | SUBGROUPING = YES 322 | 323 | # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and 324 | # unions are shown inside the group in which they are included (e.g. using 325 | # @ingroup) instead of on a separate page (for HTML and Man pages) or 326 | # section (for LaTeX and RTF). 327 | 328 | INLINE_GROUPED_CLASSES = NO 329 | 330 | # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and 331 | # unions with only public data fields will be shown inline in the documentation 332 | # of the scope in which they are defined (i.e. file, namespace, or group 333 | # documentation), provided this scope is documented. If set to NO (the default), 334 | # structs, classes, and unions are shown on a separate page (for HTML and Man 335 | # pages) or section (for LaTeX and RTF). 336 | 337 | INLINE_SIMPLE_STRUCTS = NO 338 | 339 | # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 340 | # is documented as struct, union, or enum with the name of the typedef. So 341 | # typedef struct TypeS {} TypeT, will appear in the documentation as a struct 342 | # with name TypeT. When disabled the typedef will appear as a member of a file, 343 | # namespace, or class. And the struct will be named TypeS. This can typically 344 | # be useful for C code in case the coding convention dictates that all compound 345 | # types are typedef'ed and only the typedef is referenced, never the tag name. 346 | 347 | TYPEDEF_HIDES_STRUCT = NO 348 | 349 | # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 350 | # determine which symbols to keep in memory and which to flush to disk. 351 | # When the cache is full, less often used symbols will be written to disk. 352 | # For small to medium size projects (<1000 input files) the default value is 353 | # probably good enough. For larger projects a too small cache size can cause 354 | # doxygen to be busy swapping symbols to and from disk most of the time 355 | # causing a significant performance penalty. 356 | # If the system has enough physical memory increasing the cache will improve the 357 | # performance by keeping more symbols in memory. Note that the value works on 358 | # a logarithmic scale so increasing the size by one will roughly double the 359 | # memory usage. The cache size is given by this formula: 360 | # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 361 | # corresponding to a cache size of 2^16 = 65536 symbols. 362 | 363 | SYMBOL_CACHE_SIZE = 0 364 | 365 | # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be 366 | # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given 367 | # their name and scope. Since this can be an expensive process and often the 368 | # same symbol appear multiple times in the code, doxygen keeps a cache of 369 | # pre-resolved symbols. If the cache is too small doxygen will become slower. 370 | # If the cache is too large, memory is wasted. The cache size is given by this 371 | # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, 372 | # corresponding to a cache size of 2^16 = 65536 symbols. 373 | 374 | LOOKUP_CACHE_SIZE = 0 375 | 376 | #--------------------------------------------------------------------------- 377 | # Build related configuration options 378 | #--------------------------------------------------------------------------- 379 | 380 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 381 | # documentation are documented, even if no documentation was available. 382 | # Private class members and static file members will be hidden unless 383 | # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 384 | 385 | EXTRACT_ALL = YES 386 | 387 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 388 | # will be included in the documentation. 389 | 390 | EXTRACT_PRIVATE = YES 391 | 392 | # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal 393 | # scope will be included in the documentation. 394 | 395 | EXTRACT_PACKAGE = NO 396 | 397 | # If the EXTRACT_STATIC tag is set to YES all static members of a file 398 | # will be included in the documentation. 399 | 400 | EXTRACT_STATIC = YES 401 | 402 | # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 403 | # defined locally in source files will be included in the documentation. 404 | # If set to NO only classes defined in header files are included. 405 | 406 | EXTRACT_LOCAL_CLASSES = YES 407 | 408 | # This flag is only useful for Objective-C code. When set to YES local 409 | # methods, which are defined in the implementation section but not in 410 | # the interface are included in the documentation. 411 | # If set to NO (the default) only methods in the interface are included. 412 | 413 | EXTRACT_LOCAL_METHODS = YES 414 | 415 | # If this flag is set to YES, the members of anonymous namespaces will be 416 | # extracted and appear in the documentation as a namespace called 417 | # 'anonymous_namespace{file}', where file will be replaced with the base 418 | # name of the file that contains the anonymous namespace. By default 419 | # anonymous namespaces are hidden. 420 | 421 | EXTRACT_ANON_NSPACES = YES 422 | 423 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 424 | # undocumented members of documented classes, files or namespaces. 425 | # If set to NO (the default) these members will be included in the 426 | # various overviews, but no documentation section is generated. 427 | # This option has no effect if EXTRACT_ALL is enabled. 428 | 429 | HIDE_UNDOC_MEMBERS = NO 430 | 431 | # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 432 | # undocumented classes that are normally visible in the class hierarchy. 433 | # If set to NO (the default) these classes will be included in the various 434 | # overviews. This option has no effect if EXTRACT_ALL is enabled. 435 | 436 | HIDE_UNDOC_CLASSES = NO 437 | 438 | # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 439 | # friend (class|struct|union) declarations. 440 | # If set to NO (the default) these declarations will be included in the 441 | # documentation. 442 | 443 | HIDE_FRIEND_COMPOUNDS = NO 444 | 445 | # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 446 | # documentation blocks found inside the body of a function. 447 | # If set to NO (the default) these blocks will be appended to the 448 | # function's detailed documentation block. 449 | 450 | HIDE_IN_BODY_DOCS = NO 451 | 452 | # The INTERNAL_DOCS tag determines if documentation 453 | # that is typed after a \internal command is included. If the tag is set 454 | # to NO (the default) then the documentation will be excluded. 455 | # Set it to YES to include the internal documentation. 456 | 457 | INTERNAL_DOCS = NO 458 | 459 | # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 460 | # file names in lower-case letters. If set to YES upper-case letters are also 461 | # allowed. This is useful if you have classes or files whose names only differ 462 | # in case and if your file system supports case sensitive file names. Windows 463 | # and Mac users are advised to set this option to NO. 464 | 465 | CASE_SENSE_NAMES = YES 466 | 467 | # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 468 | # will show members with their full class and namespace scopes in the 469 | # documentation. If set to YES the scope will be hidden. 470 | 471 | HIDE_SCOPE_NAMES = NO 472 | 473 | # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 474 | # will put a list of the files that are included by a file in the documentation 475 | # of that file. 476 | 477 | SHOW_INCLUDE_FILES = YES 478 | 479 | # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 480 | # will list include files with double quotes in the documentation 481 | # rather than with sharp brackets. 482 | 483 | FORCE_LOCAL_INCLUDES = NO 484 | 485 | # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 486 | # is inserted in the documentation for inline members. 487 | 488 | INLINE_INFO = YES 489 | 490 | # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 491 | # will sort the (detailed) documentation of file and class members 492 | # alphabetically by member name. If set to NO the members will appear in 493 | # declaration order. 494 | 495 | SORT_MEMBER_DOCS = YES 496 | 497 | # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 498 | # brief documentation of file, namespace and class members alphabetically 499 | # by member name. If set to NO (the default) the members will appear in 500 | # declaration order. 501 | 502 | SORT_BRIEF_DOCS = NO 503 | 504 | # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 505 | # will sort the (brief and detailed) documentation of class members so that 506 | # constructors and destructors are listed first. If set to NO (the default) 507 | # the constructors will appear in the respective orders defined by 508 | # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 509 | # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 510 | # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 511 | 512 | SORT_MEMBERS_CTORS_1ST = NO 513 | 514 | # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 515 | # hierarchy of group names into alphabetical order. If set to NO (the default) 516 | # the group names will appear in their defined order. 517 | 518 | SORT_GROUP_NAMES = NO 519 | 520 | # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 521 | # sorted by fully-qualified names, including namespaces. If set to 522 | # NO (the default), the class list will be sorted only by class name, 523 | # not including the namespace part. 524 | # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 525 | # Note: This option applies only to the class list, not to the 526 | # alphabetical list. 527 | 528 | SORT_BY_SCOPE_NAME = NO 529 | 530 | # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to 531 | # do proper type resolution of all parameters of a function it will reject a 532 | # match between the prototype and the implementation of a member function even 533 | # if there is only one candidate or it is obvious which candidate to choose 534 | # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen 535 | # will still accept a match between prototype and implementation in such cases. 536 | 537 | STRICT_PROTO_MATCHING = NO 538 | 539 | # The GENERATE_TODOLIST tag can be used to enable (YES) or 540 | # disable (NO) the todo list. This list is created by putting \todo 541 | # commands in the documentation. 542 | 543 | GENERATE_TODOLIST = YES 544 | 545 | # The GENERATE_TESTLIST tag can be used to enable (YES) or 546 | # disable (NO) the test list. This list is created by putting \test 547 | # commands in the documentation. 548 | 549 | GENERATE_TESTLIST = YES 550 | 551 | # The GENERATE_BUGLIST tag can be used to enable (YES) or 552 | # disable (NO) the bug list. This list is created by putting \bug 553 | # commands in the documentation. 554 | 555 | GENERATE_BUGLIST = YES 556 | 557 | # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 558 | # disable (NO) the deprecated list. This list is created by putting 559 | # \deprecated commands in the documentation. 560 | 561 | GENERATE_DEPRECATEDLIST= YES 562 | 563 | # The ENABLED_SECTIONS tag can be used to enable conditional 564 | # documentation sections, marked by \if sectionname ... \endif. 565 | 566 | ENABLED_SECTIONS = 567 | 568 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 569 | # the initial value of a variable or macro consists of for it to appear in 570 | # the documentation. If the initializer consists of more lines than specified 571 | # here it will be hidden. Use a value of 0 to hide initializers completely. 572 | # The appearance of the initializer of individual variables and macros in the 573 | # documentation can be controlled using \showinitializer or \hideinitializer 574 | # command in the documentation regardless of this setting. 575 | 576 | MAX_INITIALIZER_LINES = 30 577 | 578 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 579 | # at the bottom of the documentation of classes and structs. If set to YES the 580 | # list will mention the files that were used to generate the documentation. 581 | 582 | SHOW_USED_FILES = YES 583 | 584 | # Set the SHOW_FILES tag to NO to disable the generation of the Files page. 585 | # This will remove the Files entry from the Quick Index and from the 586 | # Folder Tree View (if specified). The default is YES. 587 | 588 | SHOW_FILES = YES 589 | 590 | # Set the SHOW_NAMESPACES tag to NO to disable the generation of the 591 | # Namespaces page. This will remove the Namespaces entry from the Quick Index 592 | # and from the Folder Tree View (if specified). The default is YES. 593 | 594 | SHOW_NAMESPACES = YES 595 | 596 | # The FILE_VERSION_FILTER tag can be used to specify a program or script that 597 | # doxygen should invoke to get the current version for each file (typically from 598 | # the version control system). Doxygen will invoke the program by executing (via 599 | # popen()) the command , where is the value of 600 | # the FILE_VERSION_FILTER tag, and is the name of an input file 601 | # provided by doxygen. Whatever the program writes to standard output 602 | # is used as the file version. See the manual for examples. 603 | 604 | FILE_VERSION_FILTER = 605 | 606 | # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 607 | # by doxygen. The layout file controls the global structure of the generated 608 | # output files in an output format independent way. To create the layout file 609 | # that represents doxygen's defaults, run doxygen with the -l option. 610 | # You can optionally specify a file name after the option, if omitted 611 | # DoxygenLayout.xml will be used as the name of the layout file. 612 | 613 | LAYOUT_FILE = 614 | 615 | # The CITE_BIB_FILES tag can be used to specify one or more bib files 616 | # containing the references data. This must be a list of .bib files. The 617 | # .bib extension is automatically appended if omitted. Using this command 618 | # requires the bibtex tool to be installed. See also 619 | # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style 620 | # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this 621 | # feature you need bibtex and perl available in the search path. 622 | 623 | CITE_BIB_FILES = 624 | 625 | #--------------------------------------------------------------------------- 626 | # configuration options related to warning and progress messages 627 | #--------------------------------------------------------------------------- 628 | 629 | # The QUIET tag can be used to turn on/off the messages that are generated 630 | # by doxygen. Possible values are YES and NO. If left blank NO is used. 631 | 632 | QUIET = NO 633 | 634 | # The WARNINGS tag can be used to turn on/off the warning messages that are 635 | # generated by doxygen. Possible values are YES and NO. If left blank 636 | # NO is used. 637 | 638 | WARNINGS = YES 639 | 640 | # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 641 | # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 642 | # automatically be disabled. 643 | 644 | WARN_IF_UNDOCUMENTED = YES 645 | 646 | # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 647 | # potential errors in the documentation, such as not documenting some 648 | # parameters in a documented function, or documenting parameters that 649 | # don't exist or using markup commands wrongly. 650 | 651 | WARN_IF_DOC_ERROR = YES 652 | 653 | # The WARN_NO_PARAMDOC option can be enabled to get warnings for 654 | # functions that are documented, but have no documentation for their parameters 655 | # or return value. If set to NO (the default) doxygen will only warn about 656 | # wrong or incomplete parameter documentation, but not about the absence of 657 | # documentation. 658 | 659 | WARN_NO_PARAMDOC = NO 660 | 661 | # The WARN_FORMAT tag determines the format of the warning messages that 662 | # doxygen can produce. The string should contain the $file, $line, and $text 663 | # tags, which will be replaced by the file and line number from which the 664 | # warning originated and the warning text. Optionally the format may contain 665 | # $version, which will be replaced by the version of the file (if it could 666 | # be obtained via FILE_VERSION_FILTER) 667 | 668 | WARN_FORMAT = "$file:$line: $text" 669 | 670 | # The WARN_LOGFILE tag can be used to specify a file to which warning 671 | # and error messages should be written. If left blank the output is written 672 | # to stderr. 673 | 674 | WARN_LOGFILE = 675 | 676 | #--------------------------------------------------------------------------- 677 | # configuration options related to the input files 678 | #--------------------------------------------------------------------------- 679 | 680 | # The INPUT tag can be used to specify the files and/or directories that contain 681 | # documented source files. You may enter file names like "myfile.cpp" or 682 | # directories like "/usr/src/myproject". Separate the files or directories 683 | # with spaces. 684 | 685 | INPUT = @top_srcdir@ 686 | 687 | # This tag can be used to specify the character encoding of the source files 688 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 689 | # also the default input encoding. Doxygen uses libiconv (or the iconv built 690 | # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 691 | # the list of possible encodings. 692 | 693 | INPUT_ENCODING = UTF-8 694 | 695 | # If the value of the INPUT tag contains directories, you can use the 696 | # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 697 | # and *.h) to filter out the source-files in the directories. If left 698 | # blank the following patterns are tested: 699 | # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh 700 | # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py 701 | # *.f90 *.f *.for *.vhd *.vhdl 702 | 703 | FILE_PATTERNS = *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py *.f90 *.f *.for *.vhd *.vhdl *.ice *.C *.H 704 | 705 | # The RECURSIVE tag can be used to turn specify whether or not subdirectories 706 | # should be searched for input files as well. Possible values are YES and NO. 707 | # If left blank NO is used. 708 | 709 | RECURSIVE = YES 710 | 711 | # The EXCLUDE tag can be used to specify files and/or directories that should be 712 | # excluded from the INPUT source files. This way you can easily exclude a 713 | # subdirectory from a directory tree whose root is specified with the INPUT tag. 714 | # Note that relative paths are relative to the directory from which doxygen is 715 | # run. 716 | 717 | EXCLUDE = ../gtkiostream 718 | 719 | # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or 720 | # directories that are symbolic links (a Unix file system feature) are excluded 721 | # from the input. 722 | 723 | EXCLUDE_SYMLINKS = NO 724 | 725 | # If the value of the INPUT tag contains directories, you can use the 726 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 727 | # certain files from those directories. Note that the wildcards are matched 728 | # against the file with absolute path, so to exclude all test directories 729 | # for example use the pattern */test/* 730 | 731 | EXCLUDE_PATTERNS = 732 | 733 | # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 734 | # (namespaces, classes, functions, etc.) that should be excluded from the 735 | # output. The symbol name can be a fully qualified name, a word, or if the 736 | # wildcard * is used, a substring. Examples: ANamespace, AClass, 737 | # AClass::ANamespace, ANamespace::*Test 738 | 739 | EXCLUDE_SYMBOLS = 740 | 741 | # The EXAMPLE_PATH tag can be used to specify one or more files or 742 | # directories that contain example code fragments that are included (see 743 | # the \include command). 744 | 745 | EXAMPLE_PATH = 746 | 747 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the 748 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 749 | # and *.h) to filter out the source-files in the directories. If left 750 | # blank all files are included. 751 | 752 | EXAMPLE_PATTERNS = 753 | 754 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 755 | # searched for input files to be used with the \include or \dontinclude 756 | # commands irrespective of the value of the RECURSIVE tag. 757 | # Possible values are YES and NO. If left blank NO is used. 758 | 759 | EXAMPLE_RECURSIVE = NO 760 | 761 | # The IMAGE_PATH tag can be used to specify one or more files or 762 | # directories that contain image that are included in the documentation (see 763 | # the \image command). 764 | 765 | IMAGE_PATH = 766 | 767 | # The INPUT_FILTER tag can be used to specify a program that doxygen should 768 | # invoke to filter for each input file. Doxygen will invoke the filter program 769 | # by executing (via popen()) the command , where 770 | # is the value of the INPUT_FILTER tag, and is the name of an 771 | # input file. Doxygen will then use the output that the filter program writes 772 | # to standard output. If FILTER_PATTERNS is specified, this tag will be 773 | # ignored. 774 | 775 | INPUT_FILTER = 776 | 777 | # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 778 | # basis. Doxygen will compare the file name with each pattern and apply the 779 | # filter if there is a match. The filters are a list of the form: 780 | # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 781 | # info on how filters are used. If FILTER_PATTERNS is empty or if 782 | # non of the patterns match the file name, INPUT_FILTER is applied. 783 | 784 | FILTER_PATTERNS = 785 | 786 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 787 | # INPUT_FILTER) will be used to filter the input files when producing source 788 | # files to browse (i.e. when SOURCE_BROWSER is set to YES). 789 | 790 | FILTER_SOURCE_FILES = NO 791 | 792 | # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 793 | # pattern. A pattern will override the setting for FILTER_PATTERN (if any) 794 | # and it is also possible to disable source filtering for a specific pattern 795 | # using *.ext= (so without naming a filter). This option only has effect when 796 | # FILTER_SOURCE_FILES is enabled. 797 | 798 | FILTER_SOURCE_PATTERNS = 799 | 800 | #--------------------------------------------------------------------------- 801 | # configuration options related to source browsing 802 | #--------------------------------------------------------------------------- 803 | 804 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will 805 | # be generated. Documented entities will be cross-referenced with these sources. 806 | # Note: To get rid of all source code in the generated output, make sure also 807 | # VERBATIM_HEADERS is set to NO. 808 | 809 | SOURCE_BROWSER = YES 810 | 811 | # Setting the INLINE_SOURCES tag to YES will include the body 812 | # of functions and classes directly in the documentation. 813 | 814 | INLINE_SOURCES = NO 815 | 816 | # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 817 | # doxygen to hide any special comment blocks from generated source code 818 | # fragments. Normal C, C++ and Fortran comments will always remain visible. 819 | 820 | STRIP_CODE_COMMENTS = YES 821 | 822 | # If the REFERENCED_BY_RELATION tag is set to YES 823 | # then for each documented function all documented 824 | # functions referencing it will be listed. 825 | 826 | REFERENCED_BY_RELATION = NO 827 | 828 | # If the REFERENCES_RELATION tag is set to YES 829 | # then for each documented function all documented entities 830 | # called/used by that function will be listed. 831 | 832 | REFERENCES_RELATION = NO 833 | 834 | # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 835 | # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 836 | # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 837 | # link to the source code. Otherwise they will link to the documentation. 838 | 839 | REFERENCES_LINK_SOURCE = YES 840 | 841 | # If the USE_HTAGS tag is set to YES then the references to source code 842 | # will point to the HTML generated by the htags(1) tool instead of doxygen 843 | # built-in source browser. The htags tool is part of GNU's global source 844 | # tagging system (see http://www.gnu.org/software/global/global.html). You 845 | # will need version 4.8.6 or higher. 846 | 847 | USE_HTAGS = NO 848 | 849 | # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 850 | # will generate a verbatim copy of the header file for each class for 851 | # which an include is specified. Set to NO to disable this. 852 | 853 | VERBATIM_HEADERS = YES 854 | 855 | #--------------------------------------------------------------------------- 856 | # configuration options related to the alphabetical class index 857 | #--------------------------------------------------------------------------- 858 | 859 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 860 | # of all compounds will be generated. Enable this if the project 861 | # contains a lot of classes, structs, unions or interfaces. 862 | 863 | ALPHABETICAL_INDEX = YES 864 | 865 | # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 866 | # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 867 | # in which this list will be split (can be a number in the range [1..20]) 868 | 869 | COLS_IN_ALPHA_INDEX = 5 870 | 871 | # In case all classes in a project start with a common prefix, all 872 | # classes will be put under the same header in the alphabetical index. 873 | # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 874 | # should be ignored while generating the index headers. 875 | 876 | IGNORE_PREFIX = 877 | 878 | #--------------------------------------------------------------------------- 879 | # configuration options related to the HTML output 880 | #--------------------------------------------------------------------------- 881 | 882 | # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 883 | # generate HTML output. 884 | 885 | GENERATE_HTML = YES 886 | 887 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 888 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be 889 | # put in front of it. If left blank `html' will be used as the default path. 890 | 891 | HTML_OUTPUT = html 892 | 893 | # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 894 | # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 895 | # doxygen will generate files with .html extension. 896 | 897 | HTML_FILE_EXTENSION = .html 898 | 899 | # The HTML_HEADER tag can be used to specify a personal HTML header for 900 | # each generated HTML page. If it is left blank doxygen will generate a 901 | # standard header. Note that when using a custom header you are responsible 902 | # for the proper inclusion of any scripts and style sheets that doxygen 903 | # needs, which is dependent on the configuration options used. 904 | # It is advised to generate a default header using "doxygen -w html 905 | # header.html footer.html stylesheet.css YourConfigFile" and then modify 906 | # that header. Note that the header is subject to change so you typically 907 | # have to redo this when upgrading to a newer version of doxygen or when 908 | # changing the value of configuration settings such as GENERATE_TREEVIEW! 909 | 910 | HTML_HEADER = 911 | 912 | # The HTML_FOOTER tag can be used to specify a personal HTML footer for 913 | # each generated HTML page. If it is left blank doxygen will generate a 914 | # standard footer. 915 | 916 | HTML_FOOTER = 917 | 918 | # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 919 | # style sheet that is used by each HTML page. It can be used to 920 | # fine-tune the look of the HTML output. If the tag is left blank doxygen 921 | # will generate a default style sheet. Note that doxygen will try to copy 922 | # the style sheet file to the HTML output directory, so don't put your own 923 | # style sheet in the HTML output directory as well, or it will be erased! 924 | 925 | HTML_STYLESHEET = 926 | 927 | # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 928 | # other source files which should be copied to the HTML output directory. Note 929 | # that these files will be copied to the base HTML output directory. Use the 930 | # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 931 | # files. In the HTML_STYLESHEET file, use the file name only. Also note that 932 | # the files will be copied as-is; there are no commands or markers available. 933 | 934 | HTML_EXTRA_FILES = 935 | 936 | # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 937 | # Doxygen will adjust the colors in the style sheet and background images 938 | # according to this color. Hue is specified as an angle on a colorwheel, 939 | # see http://en.wikipedia.org/wiki/Hue for more information. 940 | # For instance the value 0 represents red, 60 is yellow, 120 is green, 941 | # 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 942 | # The allowed range is 0 to 359. 943 | 944 | HTML_COLORSTYLE_HUE = 220 945 | 946 | # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 947 | # the colors in the HTML output. For a value of 0 the output will use 948 | # grayscales only. A value of 255 will produce the most vivid colors. 949 | 950 | HTML_COLORSTYLE_SAT = 100 951 | 952 | # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 953 | # the luminance component of the colors in the HTML output. Values below 954 | # 100 gradually make the output lighter, whereas values above 100 make 955 | # the output darker. The value divided by 100 is the actual gamma applied, 956 | # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 957 | # and 100 does not change the gamma. 958 | 959 | HTML_COLORSTYLE_GAMMA = 80 960 | 961 | # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 962 | # page will contain the date and time when the page was generated. Setting 963 | # this to NO can help when comparing the output of multiple runs. 964 | 965 | HTML_TIMESTAMP = YES 966 | 967 | # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 968 | # documentation will contain sections that can be hidden and shown after the 969 | # page has loaded. 970 | 971 | HTML_DYNAMIC_SECTIONS = NO 972 | 973 | # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of 974 | # entries shown in the various tree structured indices initially; the user 975 | # can expand and collapse entries dynamically later on. Doxygen will expand 976 | # the tree to such a level that at most the specified number of entries are 977 | # visible (unless a fully collapsed tree already exceeds this amount). 978 | # So setting the number of entries 1 will produce a full collapsed tree by 979 | # default. 0 is a special value representing an infinite number of entries 980 | # and will result in a full expanded tree by default. 981 | 982 | HTML_INDEX_NUM_ENTRIES = 100 983 | 984 | # If the GENERATE_DOCSET tag is set to YES, additional index files 985 | # will be generated that can be used as input for Apple's Xcode 3 986 | # integrated development environment, introduced with OSX 10.5 (Leopard). 987 | # To create a documentation set, doxygen will generate a Makefile in the 988 | # HTML output directory. Running make will produce the docset in that 989 | # directory and running "make install" will install the docset in 990 | # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 991 | # it at startup. 992 | # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 993 | # for more information. 994 | 995 | GENERATE_DOCSET = NO 996 | 997 | # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 998 | # feed. A documentation feed provides an umbrella under which multiple 999 | # documentation sets from a single provider (such as a company or product suite) 1000 | # can be grouped. 1001 | 1002 | DOCSET_FEEDNAME = "Doxygen generated docs" 1003 | 1004 | # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 1005 | # should uniquely identify the documentation set bundle. This should be a 1006 | # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 1007 | # will append .docset to the name. 1008 | 1009 | DOCSET_BUNDLE_ID = org.doxygen.Project 1010 | 1011 | # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify 1012 | # the documentation publisher. This should be a reverse domain-name style 1013 | # string, e.g. com.mycompany.MyDocSet.documentation. 1014 | 1015 | DOCSET_PUBLISHER_ID = org.doxygen.Publisher 1016 | 1017 | # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. 1018 | 1019 | DOCSET_PUBLISHER_NAME = Publisher 1020 | 1021 | # If the GENERATE_HTMLHELP tag is set to YES, additional index files 1022 | # will be generated that can be used as input for tools like the 1023 | # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 1024 | # of the generated HTML documentation. 1025 | 1026 | GENERATE_HTMLHELP = NO 1027 | 1028 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 1029 | # be used to specify the file name of the resulting .chm file. You 1030 | # can add a path in front of the file if the result should not be 1031 | # written to the html output directory. 1032 | 1033 | CHM_FILE = 1034 | 1035 | # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 1036 | # be used to specify the location (absolute path including file name) of 1037 | # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 1038 | # the HTML help compiler on the generated index.hhp. 1039 | 1040 | HHC_LOCATION = 1041 | 1042 | # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 1043 | # controls if a separate .chi index file is generated (YES) or that 1044 | # it should be included in the master .chm file (NO). 1045 | 1046 | GENERATE_CHI = NO 1047 | 1048 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 1049 | # is used to encode HtmlHelp index (hhk), content (hhc) and project file 1050 | # content. 1051 | 1052 | CHM_INDEX_ENCODING = 1053 | 1054 | # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 1055 | # controls whether a binary table of contents is generated (YES) or a 1056 | # normal table of contents (NO) in the .chm file. 1057 | 1058 | BINARY_TOC = NO 1059 | 1060 | # The TOC_EXPAND flag can be set to YES to add extra items for group members 1061 | # to the contents of the HTML help documentation and to the tree view. 1062 | 1063 | TOC_EXPAND = NO 1064 | 1065 | # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 1066 | # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 1067 | # that can be used as input for Qt's qhelpgenerator to generate a 1068 | # Qt Compressed Help (.qch) of the generated HTML documentation. 1069 | 1070 | GENERATE_QHP = NO 1071 | 1072 | # If the QHG_LOCATION tag is specified, the QCH_FILE tag can 1073 | # be used to specify the file name of the resulting .qch file. 1074 | # The path specified is relative to the HTML output folder. 1075 | 1076 | QCH_FILE = 1077 | 1078 | # The QHP_NAMESPACE tag specifies the namespace to use when generating 1079 | # Qt Help Project output. For more information please see 1080 | # http://doc.trolltech.com/qthelpproject.html#namespace 1081 | 1082 | QHP_NAMESPACE = org.doxygen.Project 1083 | 1084 | # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 1085 | # Qt Help Project output. For more information please see 1086 | # http://doc.trolltech.com/qthelpproject.html#virtual-folders 1087 | 1088 | QHP_VIRTUAL_FOLDER = doc 1089 | 1090 | # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 1091 | # add. For more information please see 1092 | # http://doc.trolltech.com/qthelpproject.html#custom-filters 1093 | 1094 | QHP_CUST_FILTER_NAME = 1095 | 1096 | # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 1097 | # custom filter to add. For more information please see 1098 | # 1099 | # Qt Help Project / Custom Filters. 1100 | 1101 | QHP_CUST_FILTER_ATTRS = 1102 | 1103 | # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 1104 | # project's 1105 | # filter section matches. 1106 | # 1107 | # Qt Help Project / Filter Attributes. 1108 | 1109 | QHP_SECT_FILTER_ATTRS = 1110 | 1111 | # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 1112 | # be used to specify the location of Qt's qhelpgenerator. 1113 | # If non-empty doxygen will try to run qhelpgenerator on the generated 1114 | # .qhp file. 1115 | 1116 | QHG_LOCATION = 1117 | 1118 | # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files 1119 | # will be generated, which together with the HTML files, form an Eclipse help 1120 | # plugin. To install this plugin and make it available under the help contents 1121 | # menu in Eclipse, the contents of the directory containing the HTML and XML 1122 | # files needs to be copied into the plugins directory of eclipse. The name of 1123 | # the directory within the plugins directory should be the same as 1124 | # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 1125 | # the help appears. 1126 | 1127 | GENERATE_ECLIPSEHELP = NO 1128 | 1129 | # A unique identifier for the eclipse help plugin. When installing the plugin 1130 | # the directory name containing the HTML and XML files should also have 1131 | # this name. 1132 | 1133 | ECLIPSE_DOC_ID = org.doxygen.Project 1134 | 1135 | # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) 1136 | # at top of each HTML page. The value NO (the default) enables the index and 1137 | # the value YES disables it. Since the tabs have the same information as the 1138 | # navigation tree you can set this option to NO if you already set 1139 | # GENERATE_TREEVIEW to YES. 1140 | 1141 | DISABLE_INDEX = NO 1142 | 1143 | # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 1144 | # structure should be generated to display hierarchical information. 1145 | # If the tag value is set to YES, a side panel will be generated 1146 | # containing a tree-like index structure (just like the one that 1147 | # is generated for HTML Help). For this to work a browser that supports 1148 | # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 1149 | # Windows users are probably better off using the HTML help feature. 1150 | # Since the tree basically has the same information as the tab index you 1151 | # could consider to set DISABLE_INDEX to NO when enabling this option. 1152 | 1153 | GENERATE_TREEVIEW = YES 1154 | 1155 | # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values 1156 | # (range [0,1..20]) that doxygen will group on one line in the generated HTML 1157 | # documentation. Note that a value of 0 will completely suppress the enum 1158 | # values from appearing in the overview section. 1159 | 1160 | ENUM_VALUES_PER_LINE = 4 1161 | 1162 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 1163 | # used to set the initial width (in pixels) of the frame in which the tree 1164 | # is shown. 1165 | 1166 | TREEVIEW_WIDTH = 250 1167 | 1168 | # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 1169 | # links to external symbols imported via tag files in a separate window. 1170 | 1171 | EXT_LINKS_IN_WINDOW = NO 1172 | 1173 | # Use this tag to change the font size of Latex formulas included 1174 | # as images in the HTML documentation. The default is 10. Note that 1175 | # when you change the font size after a successful doxygen run you need 1176 | # to manually remove any form_*.png images from the HTML output directory 1177 | # to force them to be regenerated. 1178 | 1179 | FORMULA_FONTSIZE = 10 1180 | 1181 | # Use the FORMULA_TRANPARENT tag to determine whether or not the images 1182 | # generated for formulas are transparent PNGs. Transparent PNGs are 1183 | # not supported properly for IE 6.0, but are supported on all modern browsers. 1184 | # Note that when changing this option you need to delete any form_*.png files 1185 | # in the HTML output before the changes have effect. 1186 | 1187 | FORMULA_TRANSPARENT = YES 1188 | 1189 | # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax 1190 | # (see http://www.mathjax.org) which uses client side Javascript for the 1191 | # rendering instead of using prerendered bitmaps. Use this if you do not 1192 | # have LaTeX installed or if you want to formulas look prettier in the HTML 1193 | # output. When enabled you may also need to install MathJax separately and 1194 | # configure the path to it using the MATHJAX_RELPATH option. 1195 | 1196 | USE_MATHJAX = NO 1197 | 1198 | # When MathJax is enabled you need to specify the location relative to the 1199 | # HTML output directory using the MATHJAX_RELPATH option. The destination 1200 | # directory should contain the MathJax.js script. For instance, if the mathjax 1201 | # directory is located at the same level as the HTML output directory, then 1202 | # MATHJAX_RELPATH should be ../mathjax. The default value points to 1203 | # the MathJax Content Delivery Network so you can quickly see the result without 1204 | # installing MathJax. However, it is strongly recommended to install a local 1205 | # copy of MathJax from http://www.mathjax.org before deployment. 1206 | 1207 | MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest 1208 | 1209 | # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension 1210 | # names that should be enabled during MathJax rendering. 1211 | 1212 | MATHJAX_EXTENSIONS = 1213 | 1214 | # When the SEARCHENGINE tag is enabled doxygen will generate a search box 1215 | # for the HTML output. The underlying search engine uses javascript 1216 | # and DHTML and should work on any modern browser. Note that when using 1217 | # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 1218 | # (GENERATE_DOCSET) there is already a search function so this one should 1219 | # typically be disabled. For large projects the javascript based search engine 1220 | # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. 1221 | 1222 | SEARCHENGINE = YES 1223 | 1224 | # When the SERVER_BASED_SEARCH tag is enabled the search engine will be 1225 | # implemented using a PHP enabled web server instead of at the web client 1226 | # using Javascript. Doxygen will generate the search PHP script and index 1227 | # file to put on the web server. The advantage of the server 1228 | # based approach is that it scales better to large projects and allows 1229 | # full text search. The disadvantages are that it is more difficult to setup 1230 | # and does not have live searching capabilities. 1231 | 1232 | SERVER_BASED_SEARCH = NO 1233 | 1234 | #--------------------------------------------------------------------------- 1235 | # configuration options related to the LaTeX output 1236 | #--------------------------------------------------------------------------- 1237 | 1238 | # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 1239 | # generate Latex output. 1240 | 1241 | GENERATE_LATEX = NO 1242 | 1243 | # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 1244 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1245 | # put in front of it. If left blank `latex' will be used as the default path. 1246 | 1247 | LATEX_OUTPUT = latex 1248 | 1249 | # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 1250 | # invoked. If left blank `latex' will be used as the default command name. 1251 | # Note that when enabling USE_PDFLATEX this option is only used for 1252 | # generating bitmaps for formulas in the HTML output, but not in the 1253 | # Makefile that is written to the output directory. 1254 | 1255 | LATEX_CMD_NAME = latex 1256 | 1257 | # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 1258 | # generate index for LaTeX. If left blank `makeindex' will be used as the 1259 | # default command name. 1260 | 1261 | MAKEINDEX_CMD_NAME = makeindex 1262 | 1263 | # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 1264 | # LaTeX documents. This may be useful for small projects and may help to 1265 | # save some trees in general. 1266 | 1267 | COMPACT_LATEX = NO 1268 | 1269 | # The PAPER_TYPE tag can be used to set the paper type that is used 1270 | # by the printer. Possible values are: a4, letter, legal and 1271 | # executive. If left blank a4wide will be used. 1272 | 1273 | PAPER_TYPE = a4 1274 | 1275 | # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 1276 | # packages that should be included in the LaTeX output. 1277 | 1278 | EXTRA_PACKAGES = 1279 | 1280 | # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 1281 | # the generated latex document. The header should contain everything until 1282 | # the first chapter. If it is left blank doxygen will generate a 1283 | # standard header. Notice: only use this tag if you know what you are doing! 1284 | 1285 | LATEX_HEADER = 1286 | 1287 | # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for 1288 | # the generated latex document. The footer should contain everything after 1289 | # the last chapter. If it is left blank doxygen will generate a 1290 | # standard footer. Notice: only use this tag if you know what you are doing! 1291 | 1292 | LATEX_FOOTER = 1293 | 1294 | # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 1295 | # is prepared for conversion to pdf (using ps2pdf). The pdf file will 1296 | # contain links (just like the HTML output) instead of page references 1297 | # This makes the output suitable for online browsing using a pdf viewer. 1298 | 1299 | PDF_HYPERLINKS = YES 1300 | 1301 | # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 1302 | # plain latex in the generated Makefile. Set this option to YES to get a 1303 | # higher quality PDF documentation. 1304 | 1305 | USE_PDFLATEX = YES 1306 | 1307 | # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 1308 | # command to the generated LaTeX files. This will instruct LaTeX to keep 1309 | # running if errors occur, instead of asking the user for help. 1310 | # This option is also used when generating formulas in HTML. 1311 | 1312 | LATEX_BATCHMODE = NO 1313 | 1314 | # If LATEX_HIDE_INDICES is set to YES then doxygen will not 1315 | # include the index chapters (such as File Index, Compound Index, etc.) 1316 | # in the output. 1317 | 1318 | LATEX_HIDE_INDICES = NO 1319 | 1320 | # If LATEX_SOURCE_CODE is set to YES then doxygen will include 1321 | # source code with syntax highlighting in the LaTeX output. 1322 | # Note that which sources are shown also depends on other settings 1323 | # such as SOURCE_BROWSER. 1324 | 1325 | LATEX_SOURCE_CODE = NO 1326 | 1327 | # The LATEX_BIB_STYLE tag can be used to specify the style to use for the 1328 | # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See 1329 | # http://en.wikipedia.org/wiki/BibTeX for more info. 1330 | 1331 | LATEX_BIB_STYLE = plain 1332 | 1333 | #--------------------------------------------------------------------------- 1334 | # configuration options related to the RTF output 1335 | #--------------------------------------------------------------------------- 1336 | 1337 | # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 1338 | # The RTF output is optimized for Word 97 and may not look very pretty with 1339 | # other RTF readers or editors. 1340 | 1341 | GENERATE_RTF = NO 1342 | 1343 | # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 1344 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1345 | # put in front of it. If left blank `rtf' will be used as the default path. 1346 | 1347 | RTF_OUTPUT = rtf 1348 | 1349 | # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 1350 | # RTF documents. This may be useful for small projects and may help to 1351 | # save some trees in general. 1352 | 1353 | COMPACT_RTF = NO 1354 | 1355 | # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 1356 | # will contain hyperlink fields. The RTF file will 1357 | # contain links (just like the HTML output) instead of page references. 1358 | # This makes the output suitable for online browsing using WORD or other 1359 | # programs which support those fields. 1360 | # Note: wordpad (write) and others do not support links. 1361 | 1362 | RTF_HYPERLINKS = NO 1363 | 1364 | # Load style sheet definitions from file. Syntax is similar to doxygen's 1365 | # config file, i.e. a series of assignments. You only have to provide 1366 | # replacements, missing definitions are set to their default value. 1367 | 1368 | RTF_STYLESHEET_FILE = 1369 | 1370 | # Set optional variables used in the generation of an rtf document. 1371 | # Syntax is similar to doxygen's config file. 1372 | 1373 | RTF_EXTENSIONS_FILE = 1374 | 1375 | #--------------------------------------------------------------------------- 1376 | # configuration options related to the man page output 1377 | #--------------------------------------------------------------------------- 1378 | 1379 | # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 1380 | # generate man pages 1381 | 1382 | GENERATE_MAN = NO 1383 | 1384 | # The MAN_OUTPUT tag is used to specify where the man pages will be put. 1385 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1386 | # put in front of it. If left blank `man' will be used as the default path. 1387 | 1388 | MAN_OUTPUT = man 1389 | 1390 | # The MAN_EXTENSION tag determines the extension that is added to 1391 | # the generated man pages (default is the subroutine's section .3) 1392 | 1393 | MAN_EXTENSION = .3 1394 | 1395 | # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 1396 | # then it will generate one additional man file for each entity 1397 | # documented in the real man page(s). These additional files 1398 | # only source the real man page, but without them the man command 1399 | # would be unable to find the correct page. The default is NO. 1400 | 1401 | MAN_LINKS = NO 1402 | 1403 | #--------------------------------------------------------------------------- 1404 | # configuration options related to the XML output 1405 | #--------------------------------------------------------------------------- 1406 | 1407 | # If the GENERATE_XML tag is set to YES Doxygen will 1408 | # generate an XML file that captures the structure of 1409 | # the code including all documentation. 1410 | 1411 | GENERATE_XML = NO 1412 | 1413 | # The XML_OUTPUT tag is used to specify where the XML pages will be put. 1414 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1415 | # put in front of it. If left blank `xml' will be used as the default path. 1416 | 1417 | XML_OUTPUT = xml 1418 | 1419 | # The XML_SCHEMA tag can be used to specify an XML schema, 1420 | # which can be used by a validating XML parser to check the 1421 | # syntax of the XML files. 1422 | 1423 | XML_SCHEMA = 1424 | 1425 | # The XML_DTD tag can be used to specify an XML DTD, 1426 | # which can be used by a validating XML parser to check the 1427 | # syntax of the XML files. 1428 | 1429 | XML_DTD = 1430 | 1431 | # If the XML_PROGRAMLISTING tag is set to YES Doxygen will 1432 | # dump the program listings (including syntax highlighting 1433 | # and cross-referencing information) to the XML output. Note that 1434 | # enabling this will significantly increase the size of the XML output. 1435 | 1436 | XML_PROGRAMLISTING = YES 1437 | 1438 | #--------------------------------------------------------------------------- 1439 | # configuration options for the AutoGen Definitions output 1440 | #--------------------------------------------------------------------------- 1441 | 1442 | # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 1443 | # generate an AutoGen Definitions (see autogen.sf.net) file 1444 | # that captures the structure of the code including all 1445 | # documentation. Note that this feature is still experimental 1446 | # and incomplete at the moment. 1447 | 1448 | GENERATE_AUTOGEN_DEF = NO 1449 | 1450 | #--------------------------------------------------------------------------- 1451 | # configuration options related to the Perl module output 1452 | #--------------------------------------------------------------------------- 1453 | 1454 | # If the GENERATE_PERLMOD tag is set to YES Doxygen will 1455 | # generate a Perl module file that captures the structure of 1456 | # the code including all documentation. Note that this 1457 | # feature is still experimental and incomplete at the 1458 | # moment. 1459 | 1460 | GENERATE_PERLMOD = NO 1461 | 1462 | # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 1463 | # the necessary Makefile rules, Perl scripts and LaTeX code to be able 1464 | # to generate PDF and DVI output from the Perl module output. 1465 | 1466 | PERLMOD_LATEX = NO 1467 | 1468 | # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 1469 | # nicely formatted so it can be parsed by a human reader. This is useful 1470 | # if you want to understand what is going on. On the other hand, if this 1471 | # tag is set to NO the size of the Perl module output will be much smaller 1472 | # and Perl will parse it just the same. 1473 | 1474 | PERLMOD_PRETTY = YES 1475 | 1476 | # The names of the make variables in the generated doxyrules.make file 1477 | # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 1478 | # This is useful so different doxyrules.make files included by the same 1479 | # Makefile don't overwrite each other's variables. 1480 | 1481 | PERLMOD_MAKEVAR_PREFIX = 1482 | 1483 | #--------------------------------------------------------------------------- 1484 | # Configuration options related to the preprocessor 1485 | #--------------------------------------------------------------------------- 1486 | 1487 | # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 1488 | # evaluate all C-preprocessor directives found in the sources and include 1489 | # files. 1490 | 1491 | ENABLE_PREPROCESSING = YES 1492 | 1493 | # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 1494 | # names in the source code. If set to NO (the default) only conditional 1495 | # compilation will be performed. Macro expansion can be done in a controlled 1496 | # way by setting EXPAND_ONLY_PREDEF to YES. 1497 | 1498 | MACRO_EXPANSION = NO 1499 | 1500 | # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 1501 | # then the macro expansion is limited to the macros specified with the 1502 | # PREDEFINED and EXPAND_AS_DEFINED tags. 1503 | 1504 | EXPAND_ONLY_PREDEF = NO 1505 | 1506 | # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 1507 | # pointed to by INCLUDE_PATH will be searched when a #include is found. 1508 | 1509 | SEARCH_INCLUDES = YES 1510 | 1511 | # The INCLUDE_PATH tag can be used to specify one or more directories that 1512 | # contain include files that are not input files but should be processed by 1513 | # the preprocessor. 1514 | 1515 | INCLUDE_PATH = 1516 | 1517 | # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 1518 | # patterns (like *.h and *.hpp) to filter out the header-files in the 1519 | # directories. If left blank, the patterns specified with FILE_PATTERNS will 1520 | # be used. 1521 | 1522 | INCLUDE_FILE_PATTERNS = 1523 | 1524 | # The PREDEFINED tag can be used to specify one or more macro names that 1525 | # are defined before the preprocessor is started (similar to the -D option of 1526 | # gcc). The argument of the tag is a list of macros of the form: name 1527 | # or name=definition (no spaces). If the definition and the = are 1528 | # omitted =1 is assumed. To prevent a macro definition from being 1529 | # undefined via #undef or recursively expanded use the := operator 1530 | # instead of the = operator. 1531 | 1532 | PREDEFINED = 1533 | 1534 | # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 1535 | # this tag can be used to specify a list of macro names that should be expanded. 1536 | # The macro definition that is found in the sources will be used. 1537 | # Use the PREDEFINED tag if you want to use a different macro definition that 1538 | # overrules the definition found in the source code. 1539 | 1540 | EXPAND_AS_DEFINED = 1541 | 1542 | # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 1543 | # doxygen's preprocessor will remove all references to function-like macros 1544 | # that are alone on a line, have an all uppercase name, and do not end with a 1545 | # semicolon, because these will confuse the parser if not removed. 1546 | 1547 | SKIP_FUNCTION_MACROS = YES 1548 | 1549 | #--------------------------------------------------------------------------- 1550 | # Configuration::additions related to external references 1551 | #--------------------------------------------------------------------------- 1552 | 1553 | # The TAGFILES option can be used to specify one or more tagfiles. For each 1554 | # tag file the location of the external documentation should be added. The 1555 | # format of a tag file without this location is as follows: 1556 | # TAGFILES = file1 file2 ... 1557 | # Adding location for the tag files is done as follows: 1558 | # TAGFILES = file1=loc1 "file2 = loc2" ... 1559 | # where "loc1" and "loc2" can be relative or absolute paths 1560 | # or URLs. Note that each tag file must have a unique name (where the name does 1561 | # NOT include the path). If a tag file is not located in the directory in which 1562 | # doxygen is run, you must also specify the path to the tagfile here. 1563 | 1564 | TAGFILES = 1565 | 1566 | # When a file name is specified after GENERATE_TAGFILE, doxygen will create 1567 | # a tag file that is based on the input files it reads. 1568 | 1569 | GENERATE_TAGFILE = 1570 | 1571 | # If the ALLEXTERNALS tag is set to YES all external classes will be listed 1572 | # in the class index. If set to NO only the inherited external classes 1573 | # will be listed. 1574 | 1575 | ALLEXTERNALS = NO 1576 | 1577 | # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 1578 | # in the modules index. If set to NO, only the current project's groups will 1579 | # be listed. 1580 | 1581 | EXTERNAL_GROUPS = YES 1582 | 1583 | # The PERL_PATH should be the absolute path and name of the perl script 1584 | # interpreter (i.e. the result of `which perl'). 1585 | 1586 | PERL_PATH = /usr/bin/perl 1587 | 1588 | #--------------------------------------------------------------------------- 1589 | # Configuration options related to the dot tool 1590 | #--------------------------------------------------------------------------- 1591 | 1592 | # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 1593 | # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 1594 | # or super classes. Setting the tag to NO turns the diagrams off. Note that 1595 | # this option also works with HAVE_DOT disabled, but it is recommended to 1596 | # install and use dot, since it yields more powerful graphs. 1597 | 1598 | CLASS_DIAGRAMS = YES 1599 | 1600 | # You can define message sequence charts within doxygen comments using the \msc 1601 | # command. Doxygen will then run the mscgen tool (see 1602 | # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 1603 | # documentation. The MSCGEN_PATH tag allows you to specify the directory where 1604 | # the mscgen tool resides. If left empty the tool is assumed to be found in the 1605 | # default search path. 1606 | 1607 | MSCGEN_PATH = 1608 | 1609 | # If set to YES, the inheritance and collaboration graphs will hide 1610 | # inheritance and usage relations if the target is undocumented 1611 | # or is not a class. 1612 | 1613 | HIDE_UNDOC_RELATIONS = YES 1614 | 1615 | # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 1616 | # available from the path. This tool is part of Graphviz, a graph visualization 1617 | # toolkit from AT&T and Lucent Bell Labs. The other options in this section 1618 | # have no effect if this option is set to NO (the default) 1619 | 1620 | HAVE_DOT = YES 1621 | 1622 | # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 1623 | # allowed to run in parallel. When set to 0 (the default) doxygen will 1624 | # base this on the number of processors available in the system. You can set it 1625 | # explicitly to a value larger than 0 to get control over the balance 1626 | # between CPU load and processing speed. 1627 | 1628 | DOT_NUM_THREADS = 0 1629 | 1630 | # By default doxygen will use the Helvetica font for all dot files that 1631 | # doxygen generates. When you want a differently looking font you can specify 1632 | # the font name using DOT_FONTNAME. You need to make sure dot is able to find 1633 | # the font, which can be done by putting it in a standard location or by setting 1634 | # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the 1635 | # directory containing the font. 1636 | 1637 | DOT_FONTNAME = Helvetica 1638 | 1639 | # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 1640 | # The default size is 10pt. 1641 | 1642 | DOT_FONTSIZE = 10 1643 | 1644 | # By default doxygen will tell dot to use the Helvetica font. 1645 | # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to 1646 | # set the path where dot can find it. 1647 | 1648 | DOT_FONTPATH = 1649 | 1650 | # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 1651 | # will generate a graph for each documented class showing the direct and 1652 | # indirect inheritance relations. Setting this tag to YES will force the 1653 | # CLASS_DIAGRAMS tag to NO. 1654 | 1655 | CLASS_GRAPH = YES 1656 | 1657 | # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 1658 | # will generate a graph for each documented class showing the direct and 1659 | # indirect implementation dependencies (inheritance, containment, and 1660 | # class references variables) of the class with other documented classes. 1661 | 1662 | COLLABORATION_GRAPH = YES 1663 | 1664 | # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 1665 | # will generate a graph for groups, showing the direct groups dependencies 1666 | 1667 | GROUP_GRAPHS = YES 1668 | 1669 | # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 1670 | # collaboration diagrams in a style similar to the OMG's Unified Modeling 1671 | # Language. 1672 | 1673 | UML_LOOK = NO 1674 | 1675 | # If the UML_LOOK tag is enabled, the fields and methods are shown inside 1676 | # the class node. If there are many fields or methods and many nodes the 1677 | # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS 1678 | # threshold limits the number of items for each type to make the size more 1679 | # managable. Set this to 0 for no limit. Note that the threshold may be 1680 | # exceeded by 50% before the limit is enforced. 1681 | 1682 | UML_LIMIT_NUM_FIELDS = 10 1683 | 1684 | # If set to YES, the inheritance and collaboration graphs will show the 1685 | # relations between templates and their instances. 1686 | 1687 | TEMPLATE_RELATIONS = NO 1688 | 1689 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 1690 | # tags are set to YES then doxygen will generate a graph for each documented 1691 | # file showing the direct and indirect include dependencies of the file with 1692 | # other documented files. 1693 | 1694 | INCLUDE_GRAPH = YES 1695 | 1696 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 1697 | # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 1698 | # documented header file showing the documented files that directly or 1699 | # indirectly include this file. 1700 | 1701 | INCLUDED_BY_GRAPH = YES 1702 | 1703 | # If the CALL_GRAPH and HAVE_DOT options are set to YES then 1704 | # doxygen will generate a call dependency graph for every global function 1705 | # or class method. Note that enabling this option will significantly increase 1706 | # the time of a run. So in most cases it will be better to enable call graphs 1707 | # for selected functions only using the \callgraph command. 1708 | 1709 | CALL_GRAPH = YES 1710 | 1711 | # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 1712 | # doxygen will generate a caller dependency graph for every global function 1713 | # or class method. Note that enabling this option will significantly increase 1714 | # the time of a run. So in most cases it will be better to enable caller 1715 | # graphs for selected functions only using the \callergraph command. 1716 | 1717 | CALLER_GRAPH = YES 1718 | 1719 | # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 1720 | # will generate a graphical hierarchy of all classes instead of a textual one. 1721 | 1722 | GRAPHICAL_HIERARCHY = YES 1723 | 1724 | # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES 1725 | # then doxygen will show the dependencies a directory has on other directories 1726 | # in a graphical way. The dependency relations are determined by the #include 1727 | # relations between the files in the directories. 1728 | 1729 | DIRECTORY_GRAPH = YES 1730 | 1731 | # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 1732 | # generated by dot. Possible values are svg, png, jpg, or gif. 1733 | # If left blank png will be used. If you choose svg you need to set 1734 | # HTML_FILE_EXTENSION to xhtml in order to make the SVG files 1735 | # visible in IE 9+ (other browsers do not have this requirement). 1736 | 1737 | DOT_IMAGE_FORMAT = png 1738 | 1739 | # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to 1740 | # enable generation of interactive SVG images that allow zooming and panning. 1741 | # Note that this requires a modern browser other than Internet Explorer. 1742 | # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you 1743 | # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files 1744 | # visible. Older versions of IE do not have SVG support. 1745 | 1746 | INTERACTIVE_SVG = NO 1747 | 1748 | # The tag DOT_PATH can be used to specify the path where the dot tool can be 1749 | # found. If left blank, it is assumed the dot tool can be found in the path. 1750 | 1751 | DOT_PATH = 1752 | 1753 | # The DOTFILE_DIRS tag can be used to specify one or more directories that 1754 | # contain dot files that are included in the documentation (see the 1755 | # \dotfile command). 1756 | 1757 | DOTFILE_DIRS = 1758 | 1759 | # The MSCFILE_DIRS tag can be used to specify one or more directories that 1760 | # contain msc files that are included in the documentation (see the 1761 | # \mscfile command). 1762 | 1763 | MSCFILE_DIRS = 1764 | 1765 | # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 1766 | # nodes that will be shown in the graph. If the number of nodes in a graph 1767 | # becomes larger than this value, doxygen will truncate the graph, which is 1768 | # visualized by representing a node as a red box. Note that doxygen if the 1769 | # number of direct children of the root node in a graph is already larger than 1770 | # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 1771 | # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 1772 | 1773 | DOT_GRAPH_MAX_NODES = 50 1774 | 1775 | # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 1776 | # graphs generated by dot. A depth value of 3 means that only nodes reachable 1777 | # from the root by following a path via at most 3 edges will be shown. Nodes 1778 | # that lay further from the root node will be omitted. Note that setting this 1779 | # option to 1 or 2 may greatly reduce the computation time needed for large 1780 | # code bases. Also note that the size of a graph can be further restricted by 1781 | # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 1782 | 1783 | MAX_DOT_GRAPH_DEPTH = 0 1784 | 1785 | # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 1786 | # background. This is disabled by default, because dot on Windows does not 1787 | # seem to support this out of the box. Warning: Depending on the platform used, 1788 | # enabling this option may lead to badly anti-aliased labels on the edges of 1789 | # a graph (i.e. they become hard to read). 1790 | 1791 | DOT_TRANSPARENT = NO 1792 | 1793 | # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 1794 | # files in one run (i.e. multiple -o and -T options on the command line). This 1795 | # makes dot run faster, but since only newer versions of dot (>1.8.10) 1796 | # support this, this feature is disabled by default. 1797 | 1798 | DOT_MULTI_TARGETS = YES 1799 | 1800 | # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 1801 | # generate a legend page explaining the meaning of the various boxes and 1802 | # arrows in the dot generated graphs. 1803 | 1804 | GENERATE_LEGEND = YES 1805 | 1806 | # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 1807 | # remove the intermediate dot files that are used to generate 1808 | # the various graphs. 1809 | 1810 | DOT_CLEANUP = YES 1811 | -------------------------------------------------------------------------------- /api/Makefile.am: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | # 3 | # Redistribution and use in source and binary forms, with or without 4 | # modification, are permitted provided that the following conditions are 5 | # met: 6 | # 7 | # * Redistributions of source code must retain the above copyright 8 | # notice, this list of conditions and the following disclaimer. 9 | # * Redistributions in binary form must reproduce the above 10 | # copyright notice, this list of conditions and the following disclaimer 11 | # in the documentation and/or other materials provided with the 12 | # distribution. 13 | # * Neither the name of mad chops coder AU nor the names of its 14 | # contributors may be used to endorse or promote products derived from 15 | # this software without specific prior written permission. 16 | # 17 | # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | # A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | # OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | # THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | if HAVE_DOXYGEN 29 | dist_man_MANS = html 30 | html: doxyfile.stamp 31 | 32 | doxyfile.stamp: 33 | $(DOXYGEN) Doxyfile 34 | echo Timestamp > doxyfile.stamp 35 | 36 | CLEANFILES = doxyfile.stamp 37 | 38 | all-local: doxyfile.stamp 39 | clean-local: 40 | -rm -rf html 41 | 42 | install-data-local: 43 | $(MKDIR_P) $(DESTDIR)$(docdir) 44 | cp -r html $(DESTDIR)$(docdir) 45 | 46 | uninstall-local: 47 | $(RM) -fr $(DESTDIR)$(docdir)/html 48 | endif 49 | -------------------------------------------------------------------------------- /autogen.sh: -------------------------------------------------------------------------------- 1 | tools/autotools.sh -------------------------------------------------------------------------------- /configure.ac: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2017-2018 The WASMAudio Authors. All rights reserved. 2 | # 3 | # Redistribution and use in source and binary forms, with or without 4 | # modification, are permitted provided that the following conditions are 5 | # met: 6 | # 7 | # * Redistributions of source code must retain the above copyright 8 | # notice, this list of conditions and the following disclaimer. 9 | # * Redistributions in binary form must reproduce the above 10 | # copyright notice, this list of conditions and the following disclaimer 11 | # in the documentation and/or other materials provided with the 12 | # distribution. 13 | # * Neither the name of mad chops coder AU nor the names of its 14 | # contributors may be used to endorse or promote products derived from 15 | # this software without specific prior written permission. 16 | # 17 | # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | # A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | # OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | # THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | m4_define([wasm_audio_current_version], [0]) # ++ if API added (age++), removed, or changed (age=0) 30 | m4_define([wasm_audio_revision_version], [0]) # ++ if API same but src code change 31 | m4_define([wasm_audio_age_version], [0]) # ++ if API added since last release, if API removed or changed then age=0 32 | m4_define([wasm_audio_version], [wasm_audio_current_version.wasm_audio_revision_version.wasm_audio_age_version]) 33 | 34 | AC_INIT( wasm_audio, [wasm_audio_version], [ https://github.com/madChopsCoderAu/WASMAudio/issues ]) 35 | AM_INIT_AUTOMAKE 36 | AC_CONFIG_SRCDIR([include/Audio.H]) 37 | AC_CONFIG_HEADERS([config.h]) 38 | AC_CONFIG_MACRO_DIR([m4]) 39 | AC_PREFIX_DEFAULT(/usr) 40 | 41 | LT_INIT 42 | AC_SUBST(LT_RELEASE, [wasm_audio_version]) 43 | AC_SUBST(LT_CURRENT, [wasm_audio_current_version:wasm_audio_revision_version:wasm_audio_age_version]) 44 | 45 | AC_PROG_CXX 46 | 47 | # doxygen support 48 | AC_ARG_ENABLE(doc, AS_HELP_STRING([--disable-doc], 49 | [Disable API documentation generation (default: auto)]), 50 | [DOC=$enableval], [DOC=auto]) 51 | if test "x$DOC" = xauto ; then 52 | AC_CHECK_PROGS([DOXYGEN], [doxygen]) 53 | if test -z "$DOXYGEN"; 54 | then AC_MSG_WARN([Doxygen not found - continuing without Doxygen support]) 55 | fi 56 | fi 57 | # Checks for documentation 58 | AM_CONDITIONAL([HAVE_DOXYGEN],[test -n "$DOXYGEN"]) 59 | AM_COND_IF([HAVE_DOXYGEN], [AC_CONFIG_FILES([api/Doxyfile])]) 60 | 61 | # check for emscripten compilation 62 | m4_ifdef([AM_EMSCRIPTEN], [AM_EMSCRIPTEN]) 63 | AM_CONDITIONAL(HAVE_EMSCRIPTEN, test x$emscripten_compiler = xyes) 64 | if test "x$emscripten_compiler" = xyes; then 65 | AC_SUBST([AM_CXXFLAGS], ["-s DEMANGLE_SUPPORT=1 -std=c++11 -O3 -fno-exceptions -s NO_EXIT_RUNTIME=1 --bind -s EXPORTED_FUNCTIONS='["_malloc"]'"]) 66 | AC_DEFINE(HAVE_EMSCRIPTEN, [], [whether building for emsdk]) 67 | fi 68 | 69 | # eigen3 70 | PKG_CHECK_MODULES(EIGEN, eigen3 >= 3.0.0, HAVE_EIGEN="yes", HAVE_EIGEN="no") 71 | AC_SUBST(EIGEN_CFLAGS) 72 | AC_SUBST(EIGEN_LIBS) 73 | AM_CONDITIONAL(HAVE_EIGEN, test x$HAVE_EIGEN = xyes) 74 | if test "x$HAVE_EIGEN" == xyes ; then 75 | AC_DEFINE(HAVE_EIGEN, [], [whether to build in Eigen support]) 76 | fi 77 | 78 | # gtkiostream 79 | #PKG_CHECK_MODULES([GTKIOSTREAM], [gtkIOStream],, AC_MSG_ERROR("gtkiostream is required for building this code")) 80 | PKG_CHECK_MODULES([GTKIOSTREAM], [gtkIOStream], HAVE_GTKIOSTREAM="yes", HAVE_GTKIOSTREAM="no") 81 | AC_SUBST([GTKIOSTREAM_CFLAGS]) 82 | AC_SUBST([GTKIOSTREAM_LIBS]) 83 | AM_CONDITIONAL(HAVE_GTKIOSTREAM, test x$HAVE_ALSA = xyes) 84 | if test "x$HAVE_GTKIOSTREAM" == xyes ; then 85 | AC_DEFINE(HAVE_GTKIOSTREAM, [], [whether to build in gtkIOStream support]) 86 | fi 87 | 88 | AC_C_INLINE 89 | AC_FUNC_ERROR_AT_LINE 90 | 91 | AC_CONFIG_FILES([Makefile api/Makefile src/Makefile test/Makefile]) 92 | AC_OUTPUT 93 | 94 | AM_COND_IF(HAVE_EIGEN, [AC_MSG_NOTICE([Eigen ....................................... Present])], [AC_MSG_NOTICE([Eigen ......................................... Not present 95 | Eigen tests and applications will not be built.])]) 96 | -------------------------------------------------------------------------------- /include/Audio.H: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | #ifndef AUDIO_H_ 30 | #define AUDIO_H_ 31 | 32 | #include "config.h" 33 | #include 34 | 35 | /** Class to test the wasm setup 36 | */ 37 | class Audio { 38 | public: 39 | /** Constructor 40 | */ 41 | Audio(); 42 | 43 | /** Destructor 44 | */ 45 | virtual ~Audio(); 46 | 47 | #ifdef HAVE_EMSCRIPTEN 48 | /** process method - processes the input audio to the output audio 49 | \param input the input audio pointer 50 | \param Min the number of input audio channels 51 | \param Nin the number of input audio frames (samples) 52 | \param output the output audio pointer 53 | \param Mout the number of output audio channels 54 | \param Nout the number of output audio frames (samples) 55 | */ 56 | bool process(intptr_t input, unsigned int Min, unsigned int Nin, intptr_t output, unsigned int Mout, unsigned int Nout); 57 | #endif 58 | }; 59 | 60 | #endif // AUDIO_H_ 61 | -------------------------------------------------------------------------------- /js/AudioProcessor.js: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | /** A simple js based audio processor for running WASM processing using the 30 | AudioWorkletProcessor. 31 | */ 32 | class AudioProcessor extends AudioWorkletProcessor { 33 | constructor(){ 34 | super(); 35 | // this.audioProcessor = new libwasmaudio.Audio; 36 | this.audioProcessor = new Module.Audio; 37 | } 38 | 39 | /** malloc a WASM heap based on an audio matrix size. If the audio buffer 40 | channel count or frame count is changed, then free and malloc again. 41 | We remember size here to check if the heap frame count is different. 42 | \param audioMatrix Array[Array[Float32Array]] 43 | \param heapName For example 'inBufs' 44 | */ 45 | mallocHEAP(audioMatrix, heapName){ 46 | let Nb=audioMatrix[0][0].byteLength; // number of bytes 47 | let M=audioMatrix.length; // number of channels 48 | let N=M*Nb; // total byte count 49 | // resize memory if required 50 | if (this[heapName]==null || this[heapName+'Size']!=N){ 51 | if (this[heapName]!=null) 52 | Module.free(this[heapName]); 53 | this[heapName] = Module._malloc(N); 54 | this[heapName+'Size']=N; 55 | } 56 | return Nb; 57 | } 58 | 59 | /** Given audio input, call the WASM process method and load the output. 60 | \param inputs The AudioWorklet input audio data 61 | \param outputs The AudioWorklet output audio data 62 | \param paramteres The AudioWorklet parameters (currently unused) 63 | */ 64 | process(inputs, outputs, parameters) { 65 | let Nb = this.mallocHEAP(inputs, 'inBufs'); // resize the heap if necessary 66 | for (var i=0; i>2, (this.inBufs+this.inBufsSize)>>2).set(inputs[i][0], i*inputs[i][0].length); 68 | 69 | Nb = this.mallocHEAP(outputs, 'outBufs'); // resize the heap if necessary 70 | 71 | // process the audio 72 | let ret=this.audioProcessor.process(this.inBufs, inputs.length, inputs[0][0].length, this.outBufs, outputs.length, outputs[0][0].length); 73 | if (ret==true) // if processing was good, load the output audio 74 | for (var i=0; i>2, (this.outBufs+i*Nb+Nb)>>2)); 76 | return ret; 77 | } 78 | } 79 | 80 | registerProcessor('audio-processor', AudioProcessor); 81 | -------------------------------------------------------------------------------- /js/post.js: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | // libwasmaudio(); 30 | -------------------------------------------------------------------------------- /js/pre.js: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | // Check if `atob` is missing and polyfill it 30 | if (typeof atob === 'undefined') { 31 | var chars = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/='; 32 | 33 | var atob = function(input) { 34 | let str = input.replace(/=+$/, ''); 35 | let output = ''; 36 | 37 | if (str.length % 4 == 1) { 38 | throw new Error("'atob' failed: The string to be decoded is not correctly encoded."); 39 | } 40 | 41 | for (let bc = 0, bs = 0, buffer, idx = 0; 42 | (buffer = str.charAt(idx++)); 43 | ~buffer && (bs = bc % 4 ? bs * 64 + buffer : buffer, bc++ % 4) ? 44 | output += String.fromCharCode(255 & bs >> (-2 * bc & 6)) : 0) { 45 | buffer = chars.indexOf(buffer); 46 | } 47 | 48 | return output; 49 | }; 50 | } 51 | 52 | Module['ENVIRONMENT'] = 'WORKER'; 53 | Module['onRuntimeInitialized'] = function(){console.log('WASM initalised')}; 54 | -------------------------------------------------------------------------------- /m4/emscripten.m4: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2017 The WASMAudio Authors. All rights reserved. 2 | # 3 | # Redistribution and use in source and binary forms, with or without 4 | # modification, are permitted provided that the following conditions are 5 | # met: 6 | # 7 | # * Redistributions of source code must retain the above copyright 8 | # notice, this list of conditions and the following disclaimer. 9 | # * Redistributions in binary form must reproduce the above 10 | # copyright notice, this list of conditions and the following disclaimer 11 | # in the documentation and/or other materials provided with the 12 | # distribution. 13 | # * Neither the name of mad chops coder AU nor the names of its 14 | # contributors may be used to endorse or promote products derived from 15 | # this software without specific prior written permission. 16 | # 17 | # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | # A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | # OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | # LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | # THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | # OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | AC_DEFUN([AM_EMSCRIPTEN], 30 | [ 31 | AC_MSG_CHECKING(for emscripten compiler) 32 | emscripten_compiler=no 33 | AC_TRY_COMPILE([ 34 | #ifndef EMSCRIPTEN 35 | #error "not an emscripten compiler" 36 | #endif 37 | ],[ 38 | ],[ 39 | host=javascript-web-emscripten 40 | emscripten_compiler=yes 41 | cross_compiling=yes 42 | ]) 43 | AC_MSG_RESULT($emscripten_compiler) 44 | AM_CONDITIONAL(EMSCRIPTEN, [test "x$emscripten_compiler" = "xyes"]) 45 | ]) 46 | -------------------------------------------------------------------------------- /madChopsCoderAu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flatmax/WASMAudio/2499ffac1ac3ac6a4ed04b388aa202d78c06f5d2/madChopsCoderAu.png -------------------------------------------------------------------------------- /src/Audio.C: -------------------------------------------------------------------------------- 1 | // Copyright (c) 2017-2018 The WASM audio Authors. All rights reserved. 2 | // 3 | // Redistribution and use in source and binary forms, with or without 4 | // modification, are permitted provided that the following conditions are 5 | // met: 6 | // 7 | // * Redistributions of source code must retain the above copyright 8 | // notice, this list of conditions and the following disclaimer. 9 | // * Redistributions in binary form must reproduce the above 10 | // copyright notice, this list of conditions and the following disclaimer 11 | // in the documentation and/or other materials provided with the 12 | // distribution. 13 | // * Neither the name of mad chops coder AU nor the names of its 14 | // contributors may be used to endorse or promote products derived from 15 | // this software without specific prior written permission. 16 | // 17 | // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 18 | // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 19 | // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 20 | // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 21 | // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 22 | // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 23 | // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 24 | // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 25 | // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 26 | // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 27 | // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 28 | 29 | #include "Audio.H" 30 | #include 31 | 32 | #include 33 | 34 | Audio::Audio(){ 35 | printf("Audio constructed\n"); 36 | } 37 | 38 | Audio::~Audio(){ 39 | printf("Audio destructed\n"); 40 | } 41 | 42 | bool Audio::process(intptr_t input, unsigned int Min, unsigned int Nin, intptr_t output, unsigned int Mout, unsigned int Nout){ 43 | float *in=(float*)input, *out = (float*)output; 44 | if (Nin!=Nout){ 45 | printf("Input and output sample count mismatch : Nin = %d, Nout = %d\n", Nin, Nout); 46 | return false; 47 | } 48 | 49 | Eigen::Map, Eigen::Unaligned > 50 | inAudio((float*)input, Nin, Min), 51 | outAudio((float*)output, Nout, Mout); 52 | 53 | unsigned int M = ((MinM) 56 | outAudio.rightCols(outAudio.cols()-M).setZero(); 57 | return true; 58 | } 59 | 60 | 61 | #include "config.h" 62 | #ifdef HAVE_EMSCRIPTEN 63 | #include 64 | EMSCRIPTEN_BINDINGS(Audio_ex) { 65 | emscripten::class_