ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/REPOS_ERICCA/magic/documentation/docmagic
(Generate patch)

Comparing magic/documentation/docmagic (file contents):
Revision 1061 by francois, Thu May 27 18:50:20 2021 UTC vs.
Revision 1088 by francois, Tue Jan 11 15:38:32 2022 UTC

# Line 1 | Line 1
1 < # Doxyfile 1.8.13
1 > # Doxyfile 1.8.17
2  
3   # This file describes the settings to be used by the documentation system
4   # doxygen (www.doxygen.org) for a project.
# Line 17 | Line 17
17   # Project related configuration options
18   #---------------------------------------------------------------------------
19  
20 < # This tag specifies the encoding used for all characters in the config file
21 < # that follow. The default is UTF-8 which is also the encoding used for all text
22 < # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 < # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 < # for the list of possible encodings.
20 > # This tag specifies the encoding used for all characters in the configuration
21 > # file that follow. The default is UTF-8 which is also the encoding used for all
22 > # text before the first occurrence of this tag. Doxygen uses libiconv (or the
23 > # iconv built into libc) for the transcoding. See
24 > # https://www.gnu.org/software/libiconv/ for the list of possible encodings.
25   # The default value is: UTF-8.
26  
27   DOXYFILE_ENCODING      = UTF-8
# Line 44 | Line 44 | PROJECT_NUMBER         = v4
44   # for a project that appears at the top of each page and should give viewer a
45   # quick idea about the purpose of the project. Keep the description short.
46  
47 < PROJECT_BRIEF          =
47 > PROJECT_BRIEF          = "Mailleurs Automatiques de Géometries intégrés à la Cao"
48  
49   # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
50   # in the documentation. The maximum height of the logo should not exceed 55
51   # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
52   # the logo to the output directory.
53  
54 < PROJECT_LOGO           =
54 > PROJECT_LOGO           = /home/francois/dev/magic/documentation/logomagic.jpg
55  
56   # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
57   # into which the generated documentation will be written. If a relative path is
# Line 93 | Line 93 | ALLOW_UNICODE_NAMES    = NO
93  
94   OUTPUT_LANGUAGE        = French
95  
96 + # The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
97 + # documentation generated by doxygen is written. Doxygen will use this
98 + # information to generate all generated output in the proper direction.
99 + # Possible values are: None, LTR, RTL and Context.
100 + # The default value is: None.
101 +
102 + OUTPUT_TEXT_DIRECTION  = None
103 +
104   # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
105   # descriptions after the members that are listed in the file and class
106   # documentation (similar to Javadoc). Set to NO to disable this.
# Line 171 | Line 179 | STRIP_FROM_PATH        = "C:/Documents a
179   # specify the list of include paths that are normally passed to the compiler
180   # using the -I flag.
181  
182 < STRIP_FROM_INC_PATH    =
182 > STRIP_FROM_INC_PATH    =
183  
184   # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
185   # less readable) file names. This can be useful is your file systems doesn't
# Line 189 | Line 197 | SHORT_NAMES            = NO
197  
198   JAVADOC_AUTOBRIEF      = NO
199  
200 + # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
201 + # such as
202 + # /***************
203 + # as being the beginning of a Javadoc-style comment "banner". If set to NO, the
204 + # Javadoc-style will behave just like regular comments and it will not be
205 + # interpreted by doxygen.
206 + # The default value is: NO.
207 +
208 + JAVADOC_BANNER         = NO
209 +
210   # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
211   # line (until the first dot) of a Qt-style comment as the brief description. If
212   # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
# Line 236 | Line 254 | TAB_SIZE               = 8
254   # will allow you to put the command \sideeffect (or @sideeffect) in the
255   # documentation, which will result in a user-defined paragraph with heading
256   # "Side Effects:". You can put \n's in the value part of an alias to insert
257 < # newlines.
257 > # newlines (in the resulting output). You can put ^^ in the value part of an
258 > # alias to insert a newline as if a physical newline was in the original file.
259 > # When you need a literal { or } or , in the value part of an alias you have to
260 > # escape them by means of a backslash (\), this can lead to conflicts with the
261 > # commands \{ and \} for these it is advised to use the version @{ and @} or use
262 > # a double escape (\\{ and \\})
263  
264 < ALIASES                =
264 > ALIASES                =
265  
266   # This tag can be used to specify a number of word-keyword mappings (TCL only).
267   # A mapping has the form "name=value". For example adding "class=itcl::class"
268   # will allow you to use the command class in the itcl::class meaning.
269  
270 < TCL_SUBST              =
270 > TCL_SUBST              =
271  
272   # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
273   # only. Doxygen will then generate output that is more tailored for C. For
# Line 274 | Line 297 | OPTIMIZE_FOR_FORTRAN   = NO
297  
298   OPTIMIZE_OUTPUT_VHDL   = NO
299  
300 + # Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
301 + # sources only. Doxygen will then generate output that is more tailored for that
302 + # language. For instance, namespaces will be presented as modules, types will be
303 + # separated into more groups, etc.
304 + # The default value is: NO.
305 +
306 + OPTIMIZE_OUTPUT_SLICE  = NO
307 +
308   # Doxygen selects the parser to use depending on the extension of the files it
309   # parses. With this tag you can assign which parser to use for a given
310   # extension. Doxygen has a built-in mapping, but you can override or extend it
311   # using this tag. The format is ext=language, where ext is a file extension, and
312 < # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
313 < # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
314 < # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
315 < # Fortran. In the later case the parser tries to guess whether the code is fixed
316 < # or free formatted code, this is the default for Fortran type files), VHDL. For
317 < # instance to make doxygen treat .inc files as Fortran files (default is PHP),
318 < # and .f files as C (default is Fortran), use: inc=Fortran f=C.
312 > # language is one of the parsers supported by doxygen: IDL, Java, JavaScript,
313 > # Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice,
314 > # Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
315 > # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
316 > # tries to guess whether the code is fixed or free formatted code, this is the
317 > # default for Fortran type files), VHDL, tcl. For instance to make doxygen treat
318 > # .inc files as Fortran files (default is PHP), and .f files as C (default is
319 > # Fortran), use: inc=Fortran f=C.
320   #
321   # Note: For files without extension you can use no_extension as a placeholder.
322   #
323   # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
324   # the files are not read by doxygen.
325  
326 < EXTENSION_MAPPING      =
326 > EXTENSION_MAPPING      =
327  
328   # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
329   # according to the Markdown format, which allows for more readable
330 < # documentation. See http://daringfireball.net/projects/markdown/ for details.
330 > # documentation. See https://daringfireball.net/projects/markdown/ for details.
331   # The output of markdown processing is further processed by doxygen, so you can
332   # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
333   # case of backward compatibilities issues.
# Line 307 | Line 339 | MARKDOWN_SUPPORT       = YES
339   # to that level are automatically included in the table of contents, even if
340   # they do not have an id attribute.
341   # Note: This feature currently applies only to Markdown headings.
342 < # Minimum value: 0, maximum value: 99, default value: 0.
342 > # Minimum value: 0, maximum value: 99, default value: 5.
343   # This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
344  
345   TOC_INCLUDE_HEADINGS   = 0
# Line 337 | Line 369 | BUILTIN_STL_SUPPORT    = NO
369   CPP_CLI_SUPPORT        = NO
370  
371   # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
372 < # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
372 > # https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen
373   # will parse them like normal C++ but will assume all classes use public instead
374   # of private inheritance when no explicit protection keyword is present.
375   # The default value is: NO.
# Line 443 | Line 475 | EXTRACT_ALL            = YES
475  
476   EXTRACT_PRIVATE        = YES
477  
478 + # If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
479 + # methods of a class will be included in the documentation.
480 + # The default value is: NO.
481 +
482 + EXTRACT_PRIV_VIRTUAL   = YES
483 +
484   # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
485   # scope will be included in the documentation.
486   # The default value is: NO.
# Line 497 | Line 535 | HIDE_UNDOC_MEMBERS     = NO
535   HIDE_UNDOC_CLASSES     = NO
536  
537   # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
538 < # (class|struct|union) declarations. If set to NO, these declarations will be
539 < # included in the documentation.
538 > # declarations. If set to NO, these declarations will be included in the
539 > # documentation.
540   # The default value is: NO.
541  
542   HIDE_FRIEND_COMPOUNDS  = NO
# Line 521 | Line 559 | INTERNAL_DOCS          = NO
559   # names in lower-case letters. If set to YES, upper-case letters are also
560   # allowed. This is useful if you have classes or files whose names only differ
561   # in case and if your file system supports case sensitive file names. Windows
562 < # and Mac users are advised to set this option to NO.
562 > # (including Cygwin) ands Mac users are advised to set this option to NO.
563   # The default value is: system dependent.
564  
565   CASE_SENSE_NAMES       = NO
# Line 648 | Line 686 | GENERATE_DEPRECATEDLIST= YES
686   # sections, marked by \if <section_label> ... \endif and \cond <section_label>
687   # ... \endcond blocks.
688  
689 < ENABLED_SECTIONS       =
689 > ENABLED_SECTIONS       =
690  
691   # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
692   # initial value of a variable or macro / define can have for it to appear in the
# Line 690 | Line 728 | SHOW_NAMESPACES        = YES
728   # by doxygen. Whatever the program writes to standard output is used as the file
729   # version. For an example see the documentation.
730  
731 < FILE_VERSION_FILTER    =
731 > FILE_VERSION_FILTER    =
732  
733   # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
734   # by doxygen. The layout file controls the global structure of the generated
# Line 703 | Line 741 | FILE_VERSION_FILTER    =
741   # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
742   # tag is left empty.
743  
744 < LAYOUT_FILE            =
744 > LAYOUT_FILE            =
745  
746   # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
747   # the reference definitions. This must be a list of .bib files. The .bib
748   # extension is automatically appended if omitted. This requires the bibtex tool
749 < # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
749 > # to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
750   # For LaTeX the style of the bibliography can be controlled using
751   # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
752   # search path. See also \cite for info how to create references.
753  
754 < CITE_BIB_FILES         =
754 > CITE_BIB_FILES         =
755  
756   #---------------------------------------------------------------------------
757   # Configuration options related to warning and progress messages
# Line 753 | Line 791 | WARN_IF_DOC_ERROR      = YES
791   # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
792   # are documented, but have no documentation for their parameters or return
793   # value. If set to NO, doxygen will only warn about wrong or incomplete
794 < # parameter documentation, but not about the absence of documentation.
794 > # parameter documentation, but not about the absence of documentation. If
795 > # EXTRACT_ALL is set to YES then this flag will automatically be disabled.
796   # The default value is: NO.
797  
798   WARN_NO_PARAMDOC       = NO
# Line 778 | Line 817 | WARN_FORMAT            = "$file:$line: $
817   # messages should be written. If left blank the output is written to standard
818   # error (stderr).
819  
820 < WARN_LOGFILE           =
820 > WARN_LOGFILE           =
821  
822   #---------------------------------------------------------------------------
823   # Configuration options related to the input files
# Line 790 | Line 829 | WARN_LOGFILE           =
829   # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
830   # Note: If this tag is empty the current directory is searched.
831  
832 < INPUT                  = ../lib \
833 <                         ../app/magic_application/src/aide.h \
834 <                         ../addin
832 > INPUT                  = . \
833 >                         ../addin \
834 >                         ../app/aide \
835 >                         ../lib
836  
837   # This tag can be used to specify the character encoding of the source files
838   # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
839   # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
840 < # documentation (see: http://www.gnu.org/software/libiconv) for the list of
840 > # documentation (see: https://www.gnu.org/software/libiconv/) for the list of
841   # possible encodings.
842   # The default value is: UTF-8.
843  
# Line 814 | Line 854 | INPUT_ENCODING         = UTF-8
854   # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
855   # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
856   # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
857 < # *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
858 < # *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf and *.qsf.
857 > # *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C comment),
858 > # *.doc (to be provided as doxygen C comment), *.txt (to be provided as doxygen
859 > # C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f, *.for, *.tcl, *.vhd,
860 > # *.vhdl, *.ucf, *.qsf and *.ice.
861  
862   FILE_PATTERNS          = *.c \
863                           *.cc \
# Line 859 | Line 901 | RECURSIVE              = YES
901   EXCLUDE                = ../lib/OCC_Fonction \
902                           ../lib/geometrie/Imports \
903                           ../lib/diamesh \
904 <                         ../addin/poly_occ/voro++-0.4.6
904 >                         ../addin/poly_occ/voro++-0.4.6 \
905 >                         ../addin/vtkdisplay \
906 >                         ../lib/solveur
907  
908   # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
909   # directories that are symbolic links (a Unix file system feature) are excluded
# Line 875 | Line 919 | EXCLUDE_SYMLINKS       = NO
919   # Note that the wildcards are matched against the file with absolute path, so to
920   # exclude all test directories for example use the pattern */test/*
921  
922 < EXCLUDE_PATTERNS       =
922 > EXCLUDE_PATTERNS       =
923  
924   # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
925   # (namespaces, classes, functions, etc.) that should be excluded from the
# Line 886 | Line 930 | EXCLUDE_PATTERNS       =
930   # Note that the wildcards are matched against the file with absolute path, so to
931   # exclude all test directories use the pattern */test/*
932  
933 < EXCLUDE_SYMBOLS        =
933 > EXCLUDE_SYMBOLS        =
934  
935   # The EXAMPLE_PATH tag can be used to specify one or more files or directories
936   # that contain example code fragments that are included (see the \include
937   # command).
938  
939 < EXAMPLE_PATH           =
939 > EXAMPLE_PATH           =
940  
941   # If the value of the EXAMPLE_PATH tag contains directories, you can use the
942   # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
# Line 912 | Line 956 | EXAMPLE_RECURSIVE      = NO
956   # that contain images that are to be included in the documentation (see the
957   # \image command).
958  
959 < IMAGE_PATH             =
959 > IMAGE_PATH             = ../documentation
960  
961   # The INPUT_FILTER tag can be used to specify a program that doxygen should
962   # invoke to filter for each input file. Doxygen will invoke the filter program
# Line 933 | Line 977 | IMAGE_PATH             =
977   # need to set EXTENSION_MAPPING for the extension otherwise the files are not
978   # properly processed by doxygen.
979  
980 < INPUT_FILTER           =
980 > INPUT_FILTER           =
981  
982   # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
983   # basis. Doxygen will compare the file name with each pattern and apply the
# Line 946 | Line 990 | INPUT_FILTER           =
990   # need to set EXTENSION_MAPPING for the extension otherwise the files are not
991   # properly processed by doxygen.
992  
993 < FILTER_PATTERNS        =
993 > FILTER_PATTERNS        =
994  
995   # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
996   # INPUT_FILTER) will also be used to filter the input files that are used for
# Line 961 | Line 1005 | FILTER_SOURCE_FILES    = NO
1005   # *.ext= (so without naming a filter).
1006   # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
1007  
1008 < FILTER_SOURCE_PATTERNS =
1008 > FILTER_SOURCE_PATTERNS =
1009  
1010   # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1011   # is part of the input, its contents will be placed on the main page
1012   # (index.html). This can be useful if you have a project on for instance GitHub
1013   # and want to reuse the introduction page also for the doxygen output.
1014  
1015 < USE_MDFILE_AS_MAINPAGE =
1015 > USE_MDFILE_AS_MAINPAGE =
1016  
1017   #---------------------------------------------------------------------------
1018   # Configuration options related to source browsing
# Line 997 | Line 1041 | INLINE_SOURCES         = NO
1041   STRIP_CODE_COMMENTS    = YES
1042  
1043   # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1044 < # function all documented functions referencing it will be listed.
1044 > # entity all documented functions referencing it will be listed.
1045   # The default value is: NO.
1046  
1047   REFERENCED_BY_RELATION = YES
# Line 1029 | Line 1073 | SOURCE_TOOLTIPS        = YES
1073   # If the USE_HTAGS tag is set to YES then the references to source code will
1074   # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1075   # source browser. The htags tool is part of GNU's global source tagging system
1076 < # (see http://www.gnu.org/software/global/global.html). You will need version
1076 > # (see https://www.gnu.org/software/global/global.html). You will need version
1077   # 4.8.6 or higher.
1078   #
1079   # To use it do the following:
1080   # - Install the latest version of global
1081 < # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1081 > # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1082   # - Make sure the INPUT points to the root of the source tree
1083   # - Run doxygen as normal
1084   #
# Line 1062 | Line 1106 | VERBATIM_HEADERS       = YES
1106   # rich C++ code for which doxygen's built-in parser lacks the necessary type
1107   # information.
1108   # Note: The availability of this option depends on whether or not doxygen was
1109 < # generated with the -Duse-libclang=ON option for CMake.
1109 > # generated with the -Duse_libclang=ON option for CMake.
1110   # The default value is: NO.
1111  
1112   CLANG_ASSISTED_PARSING = NO
# Line 1073 | Line 1117 | CLANG_ASSISTED_PARSING = NO
1117   # specified with INPUT and INCLUDE_PATH.
1118   # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
1119  
1120 < CLANG_OPTIONS          =
1120 > CLANG_OPTIONS          =
1121 >
1122 > # If clang assisted parsing is enabled you can provide the clang parser with the
1123 > # path to the compilation database (see:
1124 > # http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) used when the files
1125 > # were built. This is equivalent to specifying the "-p" option to a clang tool,
1126 > # such as clang-check. These options will then be passed to the parser.
1127 > # Note: The availability of this option depends on whether or not doxygen was
1128 > # generated with the -Duse_libclang=ON option for CMake.
1129 >
1130 > CLANG_DATABASE_PATH    =
1131  
1132   #---------------------------------------------------------------------------
1133   # Configuration options related to the alphabetical class index
# Line 1099 | Line 1153 | COLS_IN_ALPHA_INDEX    = 5
1153   # while generating the index headers.
1154   # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1155  
1156 < IGNORE_PREFIX          =
1156 > IGNORE_PREFIX          =
1157  
1158   #---------------------------------------------------------------------------
1159   # Configuration options related to the HTML output
# Line 1143 | Line 1197 | HTML_FILE_EXTENSION    = .html
1197   # of the possible markers and block names see the documentation.
1198   # This tag requires that the tag GENERATE_HTML is set to YES.
1199  
1200 < HTML_HEADER            =
1200 > HTML_HEADER            =
1201  
1202   # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1203   # generated HTML page. If the tag is left blank doxygen will generate a standard
# Line 1153 | Line 1207 | HTML_HEADER            =
1207   # that doxygen normally uses.
1208   # This tag requires that the tag GENERATE_HTML is set to YES.
1209  
1210 < HTML_FOOTER            =
1210 > HTML_FOOTER            =
1211  
1212   # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1213   # sheet that is used by each HTML page. It can be used to fine-tune the look of
# Line 1165 | Line 1219 | HTML_FOOTER            =
1219   # obsolete.
1220   # This tag requires that the tag GENERATE_HTML is set to YES.
1221  
1222 < HTML_STYLESHEET        =
1222 > HTML_STYLESHEET        =
1223  
1224   # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1225   # cascading style sheets that are included after the standard style sheets
# Line 1178 | Line 1232 | HTML_STYLESHEET        =
1232   # list). For an example see the documentation.
1233   # This tag requires that the tag GENERATE_HTML is set to YES.
1234  
1235 < HTML_EXTRA_STYLESHEET  =
1235 > HTML_EXTRA_STYLESHEET  =
1236  
1237   # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1238   # other source files which should be copied to the HTML output directory. Note
# Line 1188 | Line 1242 | HTML_EXTRA_STYLESHEET  =
1242   # files will be copied as-is; there are no commands or markers available.
1243   # This tag requires that the tag GENERATE_HTML is set to YES.
1244  
1245 < HTML_EXTRA_FILES       =
1245 > HTML_EXTRA_FILES       = ../documentation/logoericca.jpg \
1246 >                         ../documentation/logomagic.jpg
1247  
1248   # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1249   # will adjust the colors in the style sheet and background images according to
1250   # this color. Hue is specified as an angle on a colorwheel, see
1251 < # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1251 > # https://en.wikipedia.org/wiki/Hue for more information. For instance the value
1252   # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1253   # purple, and 360 is red again.
1254   # Minimum value: 0, maximum value: 359, default value: 220.
1255   # This tag requires that the tag GENERATE_HTML is set to YES.
1256  
1257 < HTML_COLORSTYLE_HUE    = 220
1257 > HTML_COLORSTYLE_HUE    = 131
1258  
1259   # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1260   # in the HTML output. For a value of 0 the output will use grayscales only. A
# Line 1229 | Line 1284 | HTML_COLORSTYLE_GAMMA  = 84
1284  
1285   HTML_TIMESTAMP         = YES
1286  
1287 + # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
1288 + # documentation will contain a main index with vertical navigation menus that
1289 + # are dynamically created via JavaScript. If disabled, the navigation index will
1290 + # consists of multiple levels of tabs that are statically embedded in every HTML
1291 + # page. Disable this option to support browsers that do not have JavaScript,
1292 + # like the Qt help browser.
1293 + # The default value is: YES.
1294 + # This tag requires that the tag GENERATE_HTML is set to YES.
1295 +
1296 + HTML_DYNAMIC_MENUS     = YES
1297 +
1298   # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1299   # documentation will contain sections that can be hidden and shown after the
1300   # page has loaded.
# Line 1252 | Line 1318 | HTML_INDEX_NUM_ENTRIES = 100
1318  
1319   # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1320   # generated that can be used as input for Apple's Xcode 3 integrated development
1321 < # environment (see: http://developer.apple.com/tools/xcode/), introduced with
1322 < # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1321 > # environment (see: https://developer.apple.com/xcode/), introduced with OSX
1322 > # 10.5 (Leopard). To create a documentation set, doxygen will generate a
1323   # Makefile in the HTML output directory. Running make will produce the docset in
1324   # that directory and running make install will install the docset in
1325   # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1326 < # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1327 < # for more information.
1326 > # startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
1327 > # genXcode/_index.html for more information.
1328   # The default value is: NO.
1329   # This tag requires that the tag GENERATE_HTML is set to YES.
1330  
# Line 1297 | Line 1363 | DOCSET_PUBLISHER_NAME  = Publisher
1363   # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1364   # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1365   # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1366 < # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1366 > # (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1367   # Windows.
1368   #
1369   # The HTML Help Workshop contains a compiler that can convert all HTML output
# Line 1317 | Line 1383 | GENERATE_HTMLHELP      = NO
1383   # written to the html output directory.
1384   # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1385  
1386 < CHM_FILE               =
1386 > CHM_FILE               =
1387  
1388   # The HHC_LOCATION tag can be used to specify the location (absolute path
1389   # including file name) of the HTML help compiler (hhc.exe). If non-empty,
# Line 1325 | Line 1391 | CHM_FILE               =
1391   # The file has to be specified with full path.
1392   # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1393  
1394 < HHC_LOCATION           =
1394 > HHC_LOCATION           =
1395  
1396   # The GENERATE_CHI flag controls if a separate .chi index file is generated
1397   # (YES) or that it should be included in the master .chm file (NO).
# Line 1338 | Line 1404 | GENERATE_CHI           = NO
1404   # and project file content.
1405   # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1406  
1407 < CHM_INDEX_ENCODING     =
1407 > CHM_INDEX_ENCODING     =
1408  
1409   # The BINARY_TOC flag controls whether a binary table of contents is generated
1410   # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
# Line 1369 | Line 1435 | GENERATE_QHP           = NO
1435   # the HTML output folder.
1436   # This tag requires that the tag GENERATE_QHP is set to YES.
1437  
1438 < QCH_FILE               =
1438 > QCH_FILE               =
1439  
1440   # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1441   # Project output. For more information please see Qt Help Project / Namespace
1442 < # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1442 > # (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1443   # The default value is: org.doxygen.Project.
1444   # This tag requires that the tag GENERATE_QHP is set to YES.
1445  
# Line 1381 | Line 1447 | QHP_NAMESPACE          = org.doxygen.Pro
1447  
1448   # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1449   # Help Project output. For more information please see Qt Help Project / Virtual
1450 < # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1450 > # Folders (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-
1451   # folders).
1452   # The default value is: doc.
1453   # This tag requires that the tag GENERATE_QHP is set to YES.
# Line 1390 | Line 1456 | QHP_VIRTUAL_FOLDER     = doc
1456  
1457   # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1458   # filter to add. For more information please see Qt Help Project / Custom
1459 < # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1459 > # Filters (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
1460   # filters).
1461   # This tag requires that the tag GENERATE_QHP is set to YES.
1462  
1463 < QHP_CUST_FILTER_NAME   =
1463 > QHP_CUST_FILTER_NAME   =
1464  
1465   # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1466   # custom filter to add. For more information please see Qt Help Project / Custom
1467 < # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1467 > # Filters (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
1468   # filters).
1469   # This tag requires that the tag GENERATE_QHP is set to YES.
1470  
1471 < QHP_CUST_FILTER_ATTRS  =
1471 > QHP_CUST_FILTER_ATTRS  =
1472  
1473   # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1474   # project's filter section matches. Qt Help Project / Filter Attributes (see:
1475 < # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1475 > # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1476   # This tag requires that the tag GENERATE_QHP is set to YES.
1477  
1478 < QHP_SECT_FILTER_ATTRS  =
1478 > QHP_SECT_FILTER_ATTRS  =
1479  
1480   # The QHG_LOCATION tag can be used to specify the location of Qt's
1481   # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1482   # generated .qhp file.
1483   # This tag requires that the tag GENERATE_QHP is set to YES.
1484  
1485 < QHG_LOCATION           =
1485 > QHG_LOCATION           =
1486  
1487   # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1488   # generated, together with the HTML files, they form an Eclipse help plugin. To
# Line 1499 | Line 1565 | EXT_LINKS_IN_WINDOW    = NO
1565  
1566   FORMULA_FONTSIZE       = 10
1567  
1568 < # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1568 > # Use the FORMULA_TRANSPARENT tag to determine whether or not the images
1569   # generated for formulas are transparent PNGs. Transparent PNGs are not
1570   # supported properly for IE 6.0, but are supported on all modern browsers.
1571   #
# Line 1510 | Line 1576 | FORMULA_FONTSIZE       = 10
1576  
1577   FORMULA_TRANSPARENT    = YES
1578  
1579 + # The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
1580 + # to create new LaTeX commands to be used in formulas as building blocks. See
1581 + # the section "Including formulas" for details.
1582 +
1583 + FORMULA_MACROFILE      =
1584 +
1585   # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1586 < # http://www.mathjax.org) which uses client side Javascript for the rendering
1586 > # https://www.mathjax.org) which uses client side JavaScript for the rendering
1587   # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1588   # installed or if you want to formulas look prettier in the HTML output. When
1589   # enabled you may also need to install MathJax separately and configure the path
# Line 1538 | Line 1610 | MATHJAX_FORMAT         = HTML-CSS
1610   # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1611   # Content Delivery Network so you can quickly see the result without installing
1612   # MathJax. However, it is strongly recommended to install a local copy of
1613 < # MathJax from http://www.mathjax.org before deployment.
1614 < # The default value is: http://cdn.mathjax.org/mathjax/latest.
1613 > # MathJax from https://www.mathjax.org before deployment.
1614 > # The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/.
1615   # This tag requires that the tag USE_MATHJAX is set to YES.
1616  
1617   MATHJAX_RELPATH        = http://www.mathjax.org/mathjax
# Line 1549 | Line 1621 | MATHJAX_RELPATH        = http://www.math
1621   # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1622   # This tag requires that the tag USE_MATHJAX is set to YES.
1623  
1624 < MATHJAX_EXTENSIONS     =
1624 > MATHJAX_EXTENSIONS     =
1625  
1626   # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1627   # of code that will be used on startup of the MathJax code. See the MathJax site
# Line 1557 | Line 1629 | MATHJAX_EXTENSIONS     =
1629   # example see the documentation.
1630   # This tag requires that the tag USE_MATHJAX is set to YES.
1631  
1632 < MATHJAX_CODEFILE       =
1632 > MATHJAX_CODEFILE       =
1633  
1634   # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1635   # the HTML output. The underlying search engine uses javascript and DHTML and
# Line 1581 | Line 1653 | MATHJAX_CODEFILE       =
1653   SEARCHENGINE           = YES
1654  
1655   # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1656 < # implemented using a web server instead of a web client using Javascript. There
1656 > # implemented using a web server instead of a web client using JavaScript. There
1657   # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1658   # setting. When disabled, doxygen will generate a PHP script for searching and
1659   # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
# Line 1600 | Line 1672 | SERVER_BASED_SEARCH    = NO
1672   #
1673   # Doxygen ships with an example indexer (doxyindexer) and search engine
1674   # (doxysearch.cgi) which are based on the open source search engine library
1675 < # Xapian (see: http://xapian.org/).
1675 > # Xapian (see: https://xapian.org/).
1676   #
1677   # See the section "External Indexing and Searching" for details.
1678   # The default value is: NO.
# Line 1613 | Line 1685 | EXTERNAL_SEARCH        = NO
1685   #
1686   # Doxygen ships with an example indexer (doxyindexer) and search engine
1687   # (doxysearch.cgi) which are based on the open source search engine library
1688 < # Xapian (see: http://xapian.org/). See the section "External Indexing and
1688 > # Xapian (see: https://xapian.org/). See the section "External Indexing and
1689   # Searching" for details.
1690   # This tag requires that the tag SEARCHENGINE is set to YES.
1691  
1692 < SEARCHENGINE_URL       =
1692 > SEARCHENGINE_URL       =
1693  
1694   # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1695   # search data is written to a file for indexing by an external tool. With the
# Line 1633 | Line 1705 | SEARCHDATA_FILE        = searchdata.xml
1705   # projects and redirect the results back to the right project.
1706   # This tag requires that the tag SEARCHENGINE is set to YES.
1707  
1708 < EXTERNAL_SEARCH_ID     =
1708 > EXTERNAL_SEARCH_ID     =
1709  
1710   # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1711   # projects other than the one defined by this configuration file, but that are
# Line 1643 | Line 1715 | EXTERNAL_SEARCH_ID     =
1715   # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1716   # This tag requires that the tag SEARCHENGINE is set to YES.
1717  
1718 < EXTRA_SEARCH_MAPPINGS  =
1718 > EXTRA_SEARCH_MAPPINGS  =
1719  
1720   #---------------------------------------------------------------------------
1721   # Configuration options related to the LaTeX output
# Line 1665 | Line 1737 | LATEX_OUTPUT           = latex
1737   # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1738   # invoked.
1739   #
1740 < # Note that when enabling USE_PDFLATEX this option is only used for generating
1741 < # bitmaps for formulas in the HTML output, but not in the Makefile that is
1742 < # written to the output directory.
1743 < # The default file is: latex.
1740 > # Note that when not enabling USE_PDFLATEX the default is latex when enabling
1741 > # USE_PDFLATEX the default is pdflatex and when in the later case latex is
1742 > # chosen this is overwritten by pdflatex. For specific output languages the
1743 > # default can have been set differently, this depends on the implementation of
1744 > # the output language.
1745   # This tag requires that the tag GENERATE_LATEX is set to YES.
1746  
1747   LATEX_CMD_NAME         = latex
1748  
1749   # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1750   # index for LaTeX.
1751 + # Note: This tag is used in the Makefile / make.bat.
1752 + # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1753 + # (.tex).
1754   # The default file is: makeindex.
1755   # This tag requires that the tag GENERATE_LATEX is set to YES.
1756  
1757   MAKEINDEX_CMD_NAME     = makeindex
1758  
1759 + # The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
1760 + # generate index for LaTeX. In case there is no backslash (\) as first character
1761 + # it will be automatically added in the LaTeX code.
1762 + # Note: This tag is used in the generated output file (.tex).
1763 + # See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
1764 + # The default value is: makeindex.
1765 + # This tag requires that the tag GENERATE_LATEX is set to YES.
1766 +
1767 + LATEX_MAKEINDEX_CMD    = makeindex
1768 +
1769   # If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
1770   # documents. This may be useful for small projects and may help to save some
1771   # trees in general.
# Line 1707 | Line 1793 | PAPER_TYPE             = a4wide
1793   # If left blank no extra packages will be included.
1794   # This tag requires that the tag GENERATE_LATEX is set to YES.
1795  
1796 < EXTRA_PACKAGES         =
1796 > EXTRA_PACKAGES         =
1797  
1798   # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1799   # generated LaTeX document. The header should contain everything until the first
# Line 1723 | Line 1809 | EXTRA_PACKAGES         =
1809   # to HTML_HEADER.
1810   # This tag requires that the tag GENERATE_LATEX is set to YES.
1811  
1812 < LATEX_HEADER           =
1812 > LATEX_HEADER           =
1813  
1814   # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1815   # generated LaTeX document. The footer should contain everything after the last
# Line 1734 | Line 1820 | LATEX_HEADER           =
1820   # Note: Only use a user-defined footer if you know what you are doing!
1821   # This tag requires that the tag GENERATE_LATEX is set to YES.
1822  
1823 < LATEX_FOOTER           =
1823 > LATEX_FOOTER           =
1824  
1825   # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1826   # LaTeX style sheets that are included after the standard style sheets created
# Line 1745 | Line 1831 | LATEX_FOOTER           =
1831   # list).
1832   # This tag requires that the tag GENERATE_LATEX is set to YES.
1833  
1834 < LATEX_EXTRA_STYLESHEET =
1834 > LATEX_EXTRA_STYLESHEET =
1835  
1836   # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1837   # other source files which should be copied to the LATEX_OUTPUT output
# Line 1753 | Line 1839 | LATEX_EXTRA_STYLESHEET =
1839   # markers available.
1840   # This tag requires that the tag GENERATE_LATEX is set to YES.
1841  
1842 < LATEX_EXTRA_FILES      =
1842 > LATEX_EXTRA_FILES      =
1843  
1844   # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1845   # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
# Line 1800 | Line 1886 | LATEX_SOURCE_CODE      = NO
1886  
1887   # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1888   # bibliography, e.g. plainnat, or ieeetr. See
1889 < # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1889 > # https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1890   # The default value is: plain.
1891   # This tag requires that the tag GENERATE_LATEX is set to YES.
1892  
# Line 1814 | Line 1900 | LATEX_BIB_STYLE        = plain
1900  
1901   LATEX_TIMESTAMP        = NO
1902  
1903 + # The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
1904 + # path from which the emoji images will be read. If a relative path is entered,
1905 + # it will be relative to the LATEX_OUTPUT directory. If left blank the
1906 + # LATEX_OUTPUT directory will be used.
1907 + # This tag requires that the tag GENERATE_LATEX is set to YES.
1908 +
1909 + LATEX_EMOJI_DIRECTORY  =
1910 +
1911   #---------------------------------------------------------------------------
1912   # Configuration options related to the RTF output
1913   #---------------------------------------------------------------------------
# Line 1853 | Line 1947 | COMPACT_RTF            = NO
1947  
1948   RTF_HYPERLINKS         = NO
1949  
1950 < # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1951 < # file, i.e. a series of assignments. You only have to provide replacements,
1952 < # missing definitions are set to their default value.
1950 > # Load stylesheet definitions from file. Syntax is similar to doxygen's
1951 > # configuration file, i.e. a series of assignments. You only have to provide
1952 > # replacements, missing definitions are set to their default value.
1953   #
1954   # See also section "Doxygen usage" for information on how to generate the
1955   # default style sheet that doxygen normally uses.
1956   # This tag requires that the tag GENERATE_RTF is set to YES.
1957  
1958 < RTF_STYLESHEET_FILE    =
1958 > RTF_STYLESHEET_FILE    =
1959  
1960   # Set optional variables used in the generation of an RTF document. Syntax is
1961 < # similar to doxygen's config file. A template extensions file can be generated
1962 < # using doxygen -e rtf extensionFile.
1961 > # similar to doxygen's configuration file. A template extensions file can be
1962 > # generated using doxygen -e rtf extensionFile.
1963   # This tag requires that the tag GENERATE_RTF is set to YES.
1964  
1965 < RTF_EXTENSIONS_FILE    =
1965 > RTF_EXTENSIONS_FILE    =
1966  
1967   # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1968   # with syntax highlighting in the RTF output.
# Line 1913 | Line 2007 | MAN_EXTENSION          = .3
2007   # MAN_EXTENSION with the initial . removed.
2008   # This tag requires that the tag GENERATE_MAN is set to YES.
2009  
2010 < MAN_SUBDIR             =
2010 > MAN_SUBDIR             =
2011  
2012   # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2013   # will generate one additional man file for each entity documented in the real
# Line 1951 | Line 2045 | XML_OUTPUT             = xml
2045  
2046   XML_PROGRAMLISTING     = YES
2047  
2048 + # If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
2049 + # namespace members in file scope as well, matching the HTML output.
2050 + # The default value is: NO.
2051 + # This tag requires that the tag GENERATE_XML is set to YES.
2052 +
2053 + XML_NS_MEMB_FILE_SCOPE = NO
2054 +
2055   #---------------------------------------------------------------------------
2056   # Configuration options related to the DOCBOOK output
2057   #---------------------------------------------------------------------------
# Line 1983 | Line 2084 | DOCBOOK_PROGRAMLISTING = NO
2084   #---------------------------------------------------------------------------
2085  
2086   # If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
2087 < # AutoGen Definitions (see http://autogen.sf.net) file that captures the
2088 < # structure of the code including all documentation. Note that this feature is
2089 < # still experimental and incomplete at the moment.
2087 > # AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
2088 > # the structure of the code including all documentation. Note that this feature
2089 > # is still experimental and incomplete at the moment.
2090   # The default value is: NO.
2091  
2092   GENERATE_AUTOGEN_DEF   = NO
# Line 2026 | Line 2127 | PERLMOD_PRETTY         = YES
2127   # overwrite each other's variables.
2128   # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2129  
2130 < PERLMOD_MAKEVAR_PREFIX =
2130 > PERLMOD_MAKEVAR_PREFIX =
2131  
2132   #---------------------------------------------------------------------------
2133   # Configuration options related to the preprocessor
# Line 2067 | Line 2168 | SEARCH_INCLUDES        = YES
2168   # preprocessor.
2169   # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2170  
2171 < INCLUDE_PATH           =
2171 > INCLUDE_PATH           =
2172  
2173   # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2174   # patterns (like *.h and *.hpp) to filter out the header-files in the
# Line 2075 | Line 2176 | INCLUDE_PATH           =
2176   # used.
2177   # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2178  
2179 < INCLUDE_FILE_PATTERNS  =
2179 > INCLUDE_FILE_PATTERNS  =
2180  
2181   # The PREDEFINED tag can be used to specify one or more macro names that are
2182   # defined before the preprocessor is started (similar to the -D option of e.g.
# Line 2088 | Line 2189 | INCLUDE_FILE_PATTERNS  =
2189   PREDEFINED             = BREP_SAT \
2190                           BREP_STEP \
2191                           BREP_SLD \
2192 <                         BREP_OCC
2192 >                         BREP_OCC \
2193 >                         ALL_OCC
2194  
2195   # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2196   # tag can be used to specify a list of macro names that should be expanded. The
# Line 2097 | Line 2199 | PREDEFINED             = BREP_SAT \
2199   # definition found in the source code.
2200   # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2201  
2202 < EXPAND_AS_DEFINED      =
2202 > EXPAND_AS_DEFINED      =
2203  
2204   # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2205   # remove all references to function-like macros that are alone on a line, have
# Line 2126 | Line 2228 | SKIP_FUNCTION_MACROS   = NO
2228   # the path). If a tag file is not located in the directory in which doxygen is
2229   # run, you must also specify the path to the tagfile here.
2230  
2231 < TAGFILES               =
2231 > TAGFILES               =
2232  
2233   # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2234   # tag file that is based on the input files it reads. See section "Linking to
2235   # external documentation" for more information about the usage of tag files.
2236  
2237 < GENERATE_TAGFILE       =
2237 > GENERATE_TAGFILE       =
2238  
2239   # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2240   # the class index. If set to NO, only the inherited external classes will be
# Line 2155 | Line 2257 | EXTERNAL_GROUPS        = YES
2257  
2258   EXTERNAL_PAGES         = YES
2259  
2158 # The PERL_PATH should be the absolute path and name of the perl script
2159 # interpreter (i.e. the result of 'which perl').
2160 # The default file (with absolute path) is: /usr/bin/perl.
2161
2162 PERL_PATH              = /usr/bin/perl
2163
2260   #---------------------------------------------------------------------------
2261   # Configuration options related to the dot tool
2262   #---------------------------------------------------------------------------
# Line 2174 | Line 2270 | PERL_PATH              = /usr/bin/perl
2270  
2271   CLASS_DIAGRAMS         = YES
2272  
2177 # You can define message sequence charts within doxygen comments using the \msc
2178 # command. Doxygen will then run the mscgen tool (see:
2179 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2180 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2181 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2182 # default search path.
2183
2184 MSCGEN_PATH            =
2185
2273   # You can include diagrams made with dia in doxygen documentation. Doxygen will
2274   # then run dia to produce the diagram and insert it in the documentation. The
2275   # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2276   # If left empty dia is assumed to be found in the default search path.
2277  
2278 < DIA_PATH               =
2278 > DIA_PATH               =
2279  
2280   # If set to YES the inheritance and collaboration graphs will hide inheritance
2281   # and usage relations if the target is undocumented or is not a class.
# Line 2237 | Line 2324 | DOT_FONTSIZE           = 10
2324   # the path where dot can find it using this tag.
2325   # This tag requires that the tag HAVE_DOT is set to YES.
2326  
2327 < DOT_FONTPATH           =
2327 > DOT_FONTPATH           =
2328  
2329   # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2330   # each documented class showing the direct and indirect inheritance relations.
# Line 2383 | Line 2470 | INTERACTIVE_SVG        = NO
2470   # found. If left blank, it is assumed the dot tool can be found in the path.
2471   # This tag requires that the tag HAVE_DOT is set to YES.
2472  
2473 < DOT_PATH               =
2473 > DOT_PATH               =
2474  
2475   # The DOTFILE_DIRS tag can be used to specify one or more directories that
2476   # contain dot files that are included in the documentation (see the \dotfile
2477   # command).
2478   # This tag requires that the tag HAVE_DOT is set to YES.
2479  
2480 < DOTFILE_DIRS           =
2480 > DOTFILE_DIRS           =
2481  
2482   # The MSCFILE_DIRS tag can be used to specify one or more directories that
2483   # contain msc files that are included in the documentation (see the \mscfile
2484   # command).
2485  
2486 < MSCFILE_DIRS           =
2486 > MSCFILE_DIRS           =
2487  
2488   # The DIAFILE_DIRS tag can be used to specify one or more directories that
2489   # contain dia files that are included in the documentation (see the \diafile
2490   # command).
2491  
2492 < DIAFILE_DIRS           =
2492 > DIAFILE_DIRS           =
2493  
2494   # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2495   # path where java can find the plantuml.jar file. If left blank, it is assumed
# Line 2410 | Line 2497 | DIAFILE_DIRS           =
2497   # generate a warning when it encounters a \startuml command in this case and
2498   # will not generate output for the diagram.
2499  
2500 < PLANTUML_JAR_PATH      =
2500 > PLANTUML_JAR_PATH      =
2501  
2502   # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2503   # configuration file for plantuml.
2504  
2505 < PLANTUML_CFG_FILE      =
2505 > PLANTUML_CFG_FILE      =
2506  
2507   # When using plantuml, the specified paths are searched for files specified by
2508   # the !include statement in a plantuml block.
2509  
2510 < PLANTUML_INCLUDE_PATH  =
2510 > PLANTUML_INCLUDE_PATH  =
2511  
2512   # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2513   # that will be shown in the graph. If the number of nodes in a graph becomes

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines