Peter M. Groen / hueplusplus

Commit 337e7c8070d73fa24db66979a3155df3fd684a26

Authored by Nodeduino
Committed by Moritz Wirger
1 parent 4e480a3a

Update Doxyfile to exclude jsoncpp from documentation

Inline Side-by-side
Showing 1 changed file with 68 additions and 66 deletions
Doxyfile
  View file @337e7c8
... ... @@ -38,20 +38,20 @@ PROJECT_NAME = hueplusplus
38 38 # could be handy for archiving the generated documentation or if some version
39 39 # control system is used.
40 40  
41   -PROJECT_NUMBER =
  41 +PROJECT_NUMBER =
42 42  
43 43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
44 44 # for a project that appears at the top of each page and should give viewer a
45 45 # quick idea about the purpose of the project. Keep the description short.
46 46  
47   -PROJECT_BRIEF =
  47 +PROJECT_BRIEF =
48 48  
49 49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
50 50 # in the documentation. The maximum height of the logo should not exceed 55
51 51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
52 52 # the logo to the output directory.
53 53  
54   -PROJECT_LOGO =
  54 +PROJECT_LOGO =
55 55  
56 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
57 57 # into which the generated documentation will be written. If a relative path is
... ... @@ -162,7 +162,7 @@ FULL_PATH_NAMES = YES
162 162 # will be relative from the directory where doxygen is started.
163 163 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
164 164  
165   -STRIP_FROM_PATH =
  165 +STRIP_FROM_PATH =
166 166  
167 167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
168 168 # path mentioned in the documentation of a class, which tells the reader which
... ... @@ -171,7 +171,7 @@ STRIP_FROM_PATH =
171 171 # specify the list of include paths that are normally passed to the compiler
172 172 # using the -I flag.
173 173  
174   -STRIP_FROM_INC_PATH =
  174 +STRIP_FROM_INC_PATH =
175 175  
176 176 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
177 177 # less readable) file names. This can be useful is your file systems doesn't
... ... @@ -238,13 +238,13 @@ TAB_SIZE = 4
238 238 # "Side Effects:". You can put \n's in the value part of an alias to insert
239 239 # newlines.
240 240  
241   -ALIASES =
  241 +ALIASES =
242 242  
243 243 # This tag can be used to specify a number of word-keyword mappings (TCL only).
244 244 # A mapping has the form "name=value". For example adding "class=itcl::class"
245 245 # will allow you to use the command class in the itcl::class meaning.
246 246  
247   -TCL_SUBST =
  247 +TCL_SUBST =
248 248  
249 249 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
250 250 # only. Doxygen will then generate output that is more tailored for C. For
... ... @@ -291,7 +291,7 @@ OPTIMIZE_OUTPUT_VHDL = NO
291 291 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
292 292 # the files are not read by doxygen.
293 293  
294   -EXTENSION_MAPPING =
  294 +EXTENSION_MAPPING =
295 295  
296 296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
297 297 # according to the Markdown format, which allows for more readable
... ... @@ -648,7 +648,7 @@ GENERATE_DEPRECATEDLIST= YES
648 648 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
649 649 # ... \endcond blocks.
650 650  
651   -ENABLED_SECTIONS =
  651 +ENABLED_SECTIONS =
652 652  
653 653 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
654 654 # initial value of a variable or macro / define can have for it to appear in the
... ... @@ -690,7 +690,7 @@ SHOW_NAMESPACES = YES
690 690 # by doxygen. Whatever the program writes to standard output is used as the file
691 691 # version. For an example see the documentation.
692 692  
693   -FILE_VERSION_FILTER =
  693 +FILE_VERSION_FILTER =
694 694  
695 695 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
696 696 # by doxygen. The layout file controls the global structure of the generated
... ... @@ -703,7 +703,7 @@ FILE_VERSION_FILTER =
703 703 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
704 704 # tag is left empty.
705 705  
706   -LAYOUT_FILE =
  706 +LAYOUT_FILE =
707 707  
708 708 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
709 709 # the reference definitions. This must be a list of .bib files. The .bib
... ... @@ -713,7 +713,7 @@ LAYOUT_FILE =
713 713 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
714 714 # search path. See also \cite for info how to create references.
715 715  
716   -CITE_BIB_FILES =
  716 +CITE_BIB_FILES =
717 717  
718 718 #---------------------------------------------------------------------------
719 719 # Configuration options related to warning and progress messages
... ... @@ -778,7 +778,7 @@ WARN_FORMAT = &quot;$file:$line: $text&quot;
778 778 # messages should be written. If left blank the output is written to standard
779 779 # error (stderr).
780 780  
781   -WARN_LOGFILE =
  781 +WARN_LOGFILE =
782 782  
783 783 #---------------------------------------------------------------------------
784 784 # Configuration options related to the input files
... ... @@ -873,7 +873,9 @@ RECURSIVE = YES
873 873 # Note that relative paths are relative to the directory from which doxygen is
874 874 # run.
875 875  
876   -EXCLUDE =
  876 +EXCLUDE = hueplusplus/jsoncpp.cpp \
  877 + hueplusplus/include/json \
  878 + hueplusplus/test \
877 879  
878 880 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
879 881 # directories that are symbolic links (a Unix file system feature) are excluded
... ... @@ -889,7 +891,7 @@ EXCLUDE_SYMLINKS = NO
889 891 # Note that the wildcards are matched against the file with absolute path, so to
890 892 # exclude all test directories for example use the pattern */test/*
891 893  
892   -EXCLUDE_PATTERNS =
  894 +EXCLUDE_PATTERNS =
893 895  
894 896 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
895 897 # (namespaces, classes, functions, etc.) that should be excluded from the
... ... @@ -900,13 +902,13 @@ EXCLUDE_PATTERNS =
900 902 # Note that the wildcards are matched against the file with absolute path, so to
901 903 # exclude all test directories use the pattern */test/*
902 904  
903   -EXCLUDE_SYMBOLS =
  905 +EXCLUDE_SYMBOLS =
904 906  
905 907 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
906 908 # that contain example code fragments that are included (see the \include
907 909 # command).
908 910  
909   -EXAMPLE_PATH =
  911 +EXAMPLE_PATH =
910 912  
911 913 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
912 914 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
... ... @@ -926,7 +928,7 @@ EXAMPLE_RECURSIVE = NO
926 928 # that contain images that are to be included in the documentation (see the
927 929 # \image command).
928 930  
929   -IMAGE_PATH =
  931 +IMAGE_PATH =
930 932  
931 933 # The INPUT_FILTER tag can be used to specify a program that doxygen should
932 934 # invoke to filter for each input file. Doxygen will invoke the filter program
... ... @@ -947,7 +949,7 @@ IMAGE_PATH =
947 949 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
948 950 # properly processed by doxygen.
949 951  
950   -INPUT_FILTER =
  952 +INPUT_FILTER =
951 953  
952 954 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
953 955 # basis. Doxygen will compare the file name with each pattern and apply the
... ... @@ -960,7 +962,7 @@ INPUT_FILTER =
960 962 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
961 963 # properly processed by doxygen.
962 964  
963   -FILTER_PATTERNS =
  965 +FILTER_PATTERNS =
964 966  
965 967 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
966 968 # INPUT_FILTER) will also be used to filter the input files that are used for
... ... @@ -975,14 +977,14 @@ FILTER_SOURCE_FILES = NO
975 977 # *.ext= (so without naming a filter).
976 978 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
977 979  
978   -FILTER_SOURCE_PATTERNS =
  980 +FILTER_SOURCE_PATTERNS =
979 981  
980 982 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
981 983 # is part of the input, its contents will be placed on the main page
982 984 # (index.html). This can be useful if you have a project on for instance GitHub
983 985 # and want to reuse the introduction page also for the doxygen output.
984 986  
985   -USE_MDFILE_AS_MAINPAGE =
  987 +USE_MDFILE_AS_MAINPAGE =
986 988  
987 989 #---------------------------------------------------------------------------
988 990 # Configuration options related to source browsing
... ... @@ -1087,7 +1089,7 @@ CLANG_ASSISTED_PARSING = NO
1087 1089 # specified with INPUT and INCLUDE_PATH.
1088 1090 # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
1089 1091  
1090   -CLANG_OPTIONS =
  1092 +CLANG_OPTIONS =
1091 1093  
1092 1094 #---------------------------------------------------------------------------
1093 1095 # Configuration options related to the alphabetical class index
... ... @@ -1113,7 +1115,7 @@ COLS_IN_ALPHA_INDEX = 5
1113 1115 # while generating the index headers.
1114 1116 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1115 1117  
1116   -IGNORE_PREFIX =
  1118 +IGNORE_PREFIX =
1117 1119  
1118 1120 #---------------------------------------------------------------------------
1119 1121 # Configuration options related to the HTML output
... ... @@ -1157,7 +1159,7 @@ HTML_FILE_EXTENSION = .html
1157 1159 # of the possible markers and block names see the documentation.
1158 1160 # This tag requires that the tag GENERATE_HTML is set to YES.
1159 1161  
1160   -HTML_HEADER =
  1162 +HTML_HEADER =
1161 1163  
1162 1164 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1163 1165 # generated HTML page. If the tag is left blank doxygen will generate a standard
... ... @@ -1167,7 +1169,7 @@ HTML_HEADER =
1167 1169 # that doxygen normally uses.
1168 1170 # This tag requires that the tag GENERATE_HTML is set to YES.
1169 1171  
1170   -HTML_FOOTER =
  1172 +HTML_FOOTER =
1171 1173  
1172 1174 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1173 1175 # sheet that is used by each HTML page. It can be used to fine-tune the look of
... ... @@ -1179,7 +1181,7 @@ HTML_FOOTER =
1179 1181 # obsolete.
1180 1182 # This tag requires that the tag GENERATE_HTML is set to YES.
1181 1183  
1182   -HTML_STYLESHEET =
  1184 +HTML_STYLESHEET =
1183 1185  
1184 1186 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1185 1187 # cascading style sheets that are included after the standard style sheets
... ... @@ -1192,7 +1194,7 @@ HTML_STYLESHEET =
1192 1194 # list). For an example see the documentation.
1193 1195 # This tag requires that the tag GENERATE_HTML is set to YES.
1194 1196  
1195   -HTML_EXTRA_STYLESHEET =
  1197 +HTML_EXTRA_STYLESHEET =
1196 1198  
1197 1199 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1198 1200 # other source files which should be copied to the HTML output directory. Note
... ... @@ -1202,7 +1204,7 @@ HTML_EXTRA_STYLESHEET =
1202 1204 # files will be copied as-is; there are no commands or markers available.
1203 1205 # This tag requires that the tag GENERATE_HTML is set to YES.
1204 1206  
1205   -HTML_EXTRA_FILES =
  1207 +HTML_EXTRA_FILES =
1206 1208  
1207 1209 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1208 1210 # will adjust the colors in the style sheet and background images according to
... ... @@ -1331,7 +1333,7 @@ GENERATE_HTMLHELP = NO
1331 1333 # written to the html output directory.
1332 1334 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1333 1335  
1334   -CHM_FILE =
  1336 +CHM_FILE =
1335 1337  
1336 1338 # The HHC_LOCATION tag can be used to specify the location (absolute path
1337 1339 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
... ... @@ -1339,7 +1341,7 @@ CHM_FILE =
1339 1341 # The file has to be specified with full path.
1340 1342 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1341 1343  
1342   -HHC_LOCATION =
  1344 +HHC_LOCATION =
1343 1345  
1344 1346 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1345 1347 # (YES) or that it should be included in the master .chm file (NO).
... ... @@ -1352,7 +1354,7 @@ GENERATE_CHI = NO
1352 1354 # and project file content.
1353 1355 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1354 1356  
1355   -CHM_INDEX_ENCODING =
  1357 +CHM_INDEX_ENCODING =
1356 1358  
1357 1359 # The BINARY_TOC flag controls whether a binary table of contents is generated
1358 1360 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
... ... @@ -1383,7 +1385,7 @@ GENERATE_QHP = NO
1383 1385 # the HTML output folder.
1384 1386 # This tag requires that the tag GENERATE_QHP is set to YES.
1385 1387  
1386   -QCH_FILE =
  1388 +QCH_FILE =
1387 1389  
1388 1390 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1389 1391 # Project output. For more information please see Qt Help Project / Namespace
... ... @@ -1408,7 +1410,7 @@ QHP_VIRTUAL_FOLDER = doc
1408 1410 # filters).
1409 1411 # This tag requires that the tag GENERATE_QHP is set to YES.
1410 1412  
1411   -QHP_CUST_FILTER_NAME =
  1413 +QHP_CUST_FILTER_NAME =
1412 1414  
1413 1415 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1414 1416 # custom filter to add. For more information please see Qt Help Project / Custom
... ... @@ -1416,21 +1418,21 @@ QHP_CUST_FILTER_NAME =
1416 1418 # filters).
1417 1419 # This tag requires that the tag GENERATE_QHP is set to YES.
1418 1420  
1419   -QHP_CUST_FILTER_ATTRS =
  1421 +QHP_CUST_FILTER_ATTRS =
1420 1422  
1421 1423 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1422 1424 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1423 1425 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1424 1426 # This tag requires that the tag GENERATE_QHP is set to YES.
1425 1427  
1426   -QHP_SECT_FILTER_ATTRS =
  1428 +QHP_SECT_FILTER_ATTRS =
1427 1429  
1428 1430 # The QHG_LOCATION tag can be used to specify the location of Qt's
1429 1431 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1430 1432 # generated .qhp file.
1431 1433 # This tag requires that the tag GENERATE_QHP is set to YES.
1432 1434  
1433   -QHG_LOCATION =
  1435 +QHG_LOCATION =
1434 1436  
1435 1437 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1436 1438 # generated, together with the HTML files, they form an Eclipse help plugin. To
... ... @@ -1563,7 +1565,7 @@ MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1563 1565 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1564 1566 # This tag requires that the tag USE_MATHJAX is set to YES.
1565 1567  
1566   -MATHJAX_EXTENSIONS =
  1568 +MATHJAX_EXTENSIONS =
1567 1569  
1568 1570 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1569 1571 # of code that will be used on startup of the MathJax code. See the MathJax site
... ... @@ -1571,7 +1573,7 @@ MATHJAX_EXTENSIONS =
1571 1573 # example see the documentation.
1572 1574 # This tag requires that the tag USE_MATHJAX is set to YES.
1573 1575  
1574   -MATHJAX_CODEFILE =
  1576 +MATHJAX_CODEFILE =
1575 1577  
1576 1578 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1577 1579 # the HTML output. The underlying search engine uses javascript and DHTML and
... ... @@ -1631,7 +1633,7 @@ EXTERNAL_SEARCH = NO
1631 1633 # Searching" for details.
1632 1634 # This tag requires that the tag SEARCHENGINE is set to YES.
1633 1635  
1634   -SEARCHENGINE_URL =
  1636 +SEARCHENGINE_URL =
1635 1637  
1636 1638 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1637 1639 # search data is written to a file for indexing by an external tool. With the
... ... @@ -1647,7 +1649,7 @@ SEARCHDATA_FILE = searchdata.xml
1647 1649 # projects and redirect the results back to the right project.
1648 1650 # This tag requires that the tag SEARCHENGINE is set to YES.
1649 1651  
1650   -EXTERNAL_SEARCH_ID =
  1652 +EXTERNAL_SEARCH_ID =
1651 1653  
1652 1654 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1653 1655 # projects other than the one defined by this configuration file, but that are
... ... @@ -1657,7 +1659,7 @@ EXTERNAL_SEARCH_ID =
1657 1659 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1658 1660 # This tag requires that the tag SEARCHENGINE is set to YES.
1659 1661  
1660   -EXTRA_SEARCH_MAPPINGS =
  1662 +EXTRA_SEARCH_MAPPINGS =
1661 1663  
1662 1664 #---------------------------------------------------------------------------
1663 1665 # Configuration options related to the LaTeX output
... ... @@ -1721,7 +1723,7 @@ PAPER_TYPE = a4
1721 1723 # If left blank no extra packages will be included.
1722 1724 # This tag requires that the tag GENERATE_LATEX is set to YES.
1723 1725  
1724   -EXTRA_PACKAGES =
  1726 +EXTRA_PACKAGES =
1725 1727  
1726 1728 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1727 1729 # generated LaTeX document. The header should contain everything until the first
... ... @@ -1737,7 +1739,7 @@ EXTRA_PACKAGES =
1737 1739 # to HTML_HEADER.
1738 1740 # This tag requires that the tag GENERATE_LATEX is set to YES.
1739 1741  
1740   -LATEX_HEADER =
  1742 +LATEX_HEADER =
1741 1743  
1742 1744 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1743 1745 # generated LaTeX document. The footer should contain everything after the last
... ... @@ -1748,7 +1750,7 @@ LATEX_HEADER =
1748 1750 # Note: Only use a user-defined footer if you know what you are doing!
1749 1751 # This tag requires that the tag GENERATE_LATEX is set to YES.
1750 1752  
1751   -LATEX_FOOTER =
  1753 +LATEX_FOOTER =
1752 1754  
1753 1755 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1754 1756 # LaTeX style sheets that are included after the standard style sheets created
... ... @@ -1759,7 +1761,7 @@ LATEX_FOOTER =
1759 1761 # list).
1760 1762 # This tag requires that the tag GENERATE_LATEX is set to YES.
1761 1763  
1762   -LATEX_EXTRA_STYLESHEET =
  1764 +LATEX_EXTRA_STYLESHEET =
1763 1765  
1764 1766 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1765 1767 # other source files which should be copied to the LATEX_OUTPUT output
... ... @@ -1767,7 +1769,7 @@ LATEX_EXTRA_STYLESHEET =
1767 1769 # markers available.
1768 1770 # This tag requires that the tag GENERATE_LATEX is set to YES.
1769 1771  
1770   -LATEX_EXTRA_FILES =
  1772 +LATEX_EXTRA_FILES =
1771 1773  
1772 1774 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1773 1775 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
... ... @@ -1875,14 +1877,14 @@ RTF_HYPERLINKS = NO
1875 1877 # default style sheet that doxygen normally uses.
1876 1878 # This tag requires that the tag GENERATE_RTF is set to YES.
1877 1879  
1878   -RTF_STYLESHEET_FILE =
  1880 +RTF_STYLESHEET_FILE =
1879 1881  
1880 1882 # Set optional variables used in the generation of an RTF document. Syntax is
1881 1883 # similar to doxygen's config file. A template extensions file can be generated
1882 1884 # using doxygen -e rtf extensionFile.
1883 1885 # This tag requires that the tag GENERATE_RTF is set to YES.
1884 1886  
1885   -RTF_EXTENSIONS_FILE =
  1887 +RTF_EXTENSIONS_FILE =
1886 1888  
1887 1889 # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1888 1890 # with syntax highlighting in the RTF output.
... ... @@ -1927,7 +1929,7 @@ MAN_EXTENSION = .3
1927 1929 # MAN_EXTENSION with the initial . removed.
1928 1930 # This tag requires that the tag GENERATE_MAN is set to YES.
1929 1931  
1930   -MAN_SUBDIR =
  1932 +MAN_SUBDIR =
1931 1933  
1932 1934 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1933 1935 # will generate one additional man file for each entity documented in the real
... ... @@ -2040,7 +2042,7 @@ PERLMOD_PRETTY = YES
2040 2042 # overwrite each other's variables.
2041 2043 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2042 2044  
2043   -PERLMOD_MAKEVAR_PREFIX =
  2045 +PERLMOD_MAKEVAR_PREFIX =
2044 2046  
2045 2047 #---------------------------------------------------------------------------
2046 2048 # Configuration options related to the preprocessor
... ... @@ -2081,7 +2083,7 @@ SEARCH_INCLUDES = YES
2081 2083 # preprocessor.
2082 2084 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2083 2085  
2084   -INCLUDE_PATH =
  2086 +INCLUDE_PATH =
2085 2087  
2086 2088 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2087 2089 # patterns (like *.h and *.hpp) to filter out the header-files in the
... ... @@ -2089,7 +2091,7 @@ INCLUDE_PATH =
2089 2091 # used.
2090 2092 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2091 2093  
2092   -INCLUDE_FILE_PATTERNS =
  2094 +INCLUDE_FILE_PATTERNS =
2093 2095  
2094 2096 # The PREDEFINED tag can be used to specify one or more macro names that are
2095 2097 # defined before the preprocessor is started (similar to the -D option of e.g.
... ... @@ -2099,7 +2101,7 @@ INCLUDE_FILE_PATTERNS =
2099 2101 # recursively expanded use the := operator instead of the = operator.
2100 2102 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2101 2103  
2102   -PREDEFINED =
  2104 +PREDEFINED =
2103 2105  
2104 2106 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2105 2107 # tag can be used to specify a list of macro names that should be expanded. The
... ... @@ -2108,7 +2110,7 @@ PREDEFINED =
2108 2110 # definition found in the source code.
2109 2111 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2110 2112  
2111   -EXPAND_AS_DEFINED =
  2113 +EXPAND_AS_DEFINED =
2112 2114  
2113 2115 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2114 2116 # remove all references to function-like macros that are alone on a line, have
... ... @@ -2137,13 +2139,13 @@ SKIP_FUNCTION_MACROS = YES
2137 2139 # the path). If a tag file is not located in the directory in which doxygen is
2138 2140 # run, you must also specify the path to the tagfile here.
2139 2141  
2140   -TAGFILES =
  2142 +TAGFILES =
2141 2143  
2142 2144 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2143 2145 # tag file that is based on the input files it reads. See section "Linking to
2144 2146 # external documentation" for more information about the usage of tag files.
2145 2147  
2146   -GENERATE_TAGFILE =
  2148 +GENERATE_TAGFILE =
2147 2149  
2148 2150 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2149 2151 # the class index. If set to NO, only the inherited external classes will be
... ... @@ -2192,14 +2194,14 @@ CLASS_DIAGRAMS = NO
2192 2194 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2193 2195 # default search path.
2194 2196  
2195   -MSCGEN_PATH =
  2197 +MSCGEN_PATH =
2196 2198  
2197 2199 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2198 2200 # then run dia to produce the diagram and insert it in the documentation. The
2199 2201 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2200 2202 # If left empty dia is assumed to be found in the default search path.
2201 2203  
2202   -DIA_PATH =
  2204 +DIA_PATH =
2203 2205  
2204 2206 # If set to YES the inheritance and collaboration graphs will hide inheritance
2205 2207 # and usage relations if the target is undocumented or is not a class.
... ... @@ -2248,7 +2250,7 @@ DOT_FONTSIZE = 10
2248 2250 # the path where dot can find it using this tag.
2249 2251 # This tag requires that the tag HAVE_DOT is set to YES.
2250 2252  
2251   -DOT_FONTPATH =
  2253 +DOT_FONTPATH =
2252 2254  
2253 2255 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2254 2256 # each documented class showing the direct and indirect inheritance relations.
... ... @@ -2399,19 +2401,19 @@ DOT_PATH = /usr/local/bin
2399 2401 # command).
2400 2402 # This tag requires that the tag HAVE_DOT is set to YES.
2401 2403  
2402   -DOTFILE_DIRS =
  2404 +DOTFILE_DIRS =
2403 2405  
2404 2406 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2405 2407 # contain msc files that are included in the documentation (see the \mscfile
2406 2408 # command).
2407 2409  
2408   -MSCFILE_DIRS =
  2410 +MSCFILE_DIRS =
2409 2411  
2410 2412 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2411 2413 # contain dia files that are included in the documentation (see the \diafile
2412 2414 # command).
2413 2415  
2414   -DIAFILE_DIRS =
  2416 +DIAFILE_DIRS =
2415 2417  
2416 2418 # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2417 2419 # path where java can find the plantuml.jar file. If left blank, it is assumed
... ... @@ -2419,17 +2421,17 @@ DIAFILE_DIRS =
2419 2421 # generate a warning when it encounters a \startuml command in this case and
2420 2422 # will not generate output for the diagram.
2421 2423  
2422   -PLANTUML_JAR_PATH =
  2424 +PLANTUML_JAR_PATH =
2423 2425  
2424 2426 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2425 2427 # configuration file for plantuml.
2426 2428  
2427   -PLANTUML_CFG_FILE =
  2429 +PLANTUML_CFG_FILE =
2428 2430  
2429 2431 # When using plantuml, the specified paths are searched for files specified by
2430 2432 # the !include statement in a plantuml block.
2431 2433  
2432   -PLANTUML_INCLUDE_PATH =
  2434 +PLANTUML_INCLUDE_PATH =
2433 2435  
2434 2436 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2435 2437 # that will be shown in the graph. If the number of nodes in a graph becomes
... ...