| 36 # documentation generated by doxygen is written. Doxygen will use this |
36 # documentation generated by doxygen is written. Doxygen will use this |
| 37 # information to generate all constant output in the proper language. |
37 # information to generate all constant output in the proper language. |
| 38 # The default language is English, other supported languages are: |
38 # The default language is English, other supported languages are: |
| 39 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, |
39 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, |
| 40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en |
40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en |
| 41 # (Japanese with english messages), Korean, Norwegian, Polish, Portuguese, |
41 # (Japanese with English messages), Korean, Norwegian, Polish, Portuguese, |
| 42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish and Ukrainian. |
42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. |
| 43 |
43 |
| 44 OUTPUT_LANGUAGE = English |
44 OUTPUT_LANGUAGE = English |
| |
45 |
| |
46 # This tag can be used to specify the encoding used in the generated output. |
| |
47 # The encoding is not always determined by the language that is chosen, |
| |
48 # but also whether or not the output is meant for Windows or non-Windows users. |
| |
49 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES |
| |
50 # forces the Windows encoding (this is the default for the Windows binary), |
| |
51 # whereas setting the tag to NO uses a Unix-style encoding (the default for |
| |
52 # all platforms other than Windows). |
| |
53 |
| |
54 USE_WINDOWS_ENCODING = NO |
| 45 |
55 |
| 46 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in |
56 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in |
| 47 # documentation are documented, even if no documentation was available. |
57 # documentation are documented, even if no documentation was available. |
| 48 # Private class members and static file members will be hidden unless |
58 # Private class members and static file members will be hidden unless |
| 49 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES |
59 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES |
| 134 # Set it to YES to include the internal documentation. |
151 # Set it to YES to include the internal documentation. |
| 135 |
152 |
| 136 INTERNAL_DOCS = NO |
153 INTERNAL_DOCS = NO |
| 137 |
154 |
| 138 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
155 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
| 139 # file names in lower case letters. If set to YES upper case letters are also |
156 # file names in lower-case letters. If set to YES upper-case letters are also |
| 140 # allowed. This is useful if you have classes or files whose names only differ |
157 # allowed. This is useful if you have classes or files whose names only differ |
| 141 # in case and if your file system supports case sensitive file names. Windows |
158 # in case and if your file system supports case sensitive file names. Windows |
| 142 # users are adviced to set this option to NO. |
159 # users are advised to set this option to NO. |
| 143 |
160 |
| 144 CASE_SENSE_NAMES = YES |
161 CASE_SENSE_NAMES = YES |
| 145 |
162 |
| 146 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
163 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
| 147 # (but less readable) file names. This can be useful is your file systems |
164 # (but less readable) file names. This can be useful is your file systems |
| 153 # will show members with their full class and namespace scopes in the |
170 # will show members with their full class and namespace scopes in the |
| 154 # documentation. If set to YES the scope will be hidden. |
171 # documentation. If set to YES the scope will be hidden. |
| 155 |
172 |
| 156 HIDE_SCOPE_NAMES = NO |
173 HIDE_SCOPE_NAMES = NO |
| 157 |
174 |
| 158 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen |
|
| 159 # will generate a verbatim copy of the header file for each class for |
|
| 160 # which an include is specified. Set to NO to disable this. |
|
| 161 |
|
| 162 VERBATIM_HEADERS = YES |
|
| 163 |
|
| 164 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen |
175 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen |
| 165 # will put list of the files that are included by a file in the documentation |
176 # will put a list of the files that are included by a file in the documentation |
| 166 # of that file. |
177 # of that file. |
| 167 |
178 |
| 168 SHOW_INCLUDE_FILES = YES |
179 SHOW_INCLUDE_FILES = YES |
| 169 |
180 |
| 170 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen |
181 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen |
| 171 # will interpret the first line (until the first dot) of a JavaDoc-style |
182 # will interpret the first line (until the first dot) of a JavaDoc-style |
| 172 # comment as the brief description. If set to NO, the JavaDoc |
183 # comment as the brief description. If set to NO, the JavaDoc |
| 173 # comments will behave just like the Qt-style comments (thus requiring an |
184 # comments will behave just like the Qt-style comments (thus requiring an |
| 174 # explict @brief command for a brief description. |
185 # explict @brief command for a brief description. |
| 175 |
186 |
| 176 JAVADOC_AUTOBRIEF = YES |
187 JAVADOC_AUTOBRIEF = YES |
| 177 |
188 |
| 178 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen |
189 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen |
| 237 # commands in the documentation. |
248 # commands in the documentation. |
| 238 |
249 |
| 239 GENERATE_BUGLIST = YES |
250 GENERATE_BUGLIST = YES |
| 240 |
251 |
| 241 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or |
252 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or |
| 242 # disable (NO) the deprecated list. This list is created by putting \deprecated commands in the documentation. |
253 # disable (NO) the deprecated list. This list is created by putting |
| |
254 # \deprecated commands in the documentation. |
| 243 |
255 |
| 244 GENERATE_DEPRECATEDLIST= YES |
256 GENERATE_DEPRECATEDLIST= YES |
| 245 |
257 |
| 246 # This tag can be used to specify a number of aliases that acts |
258 # This tag can be used to specify a number of aliases that acts |
| 247 # as commands in the documentation. An alias has the form "name=value". |
259 # as commands in the documentation. An alias has the form "name=value". |
| 248 # For example adding "sideeffect=\par Side Effects:\n" will allow you to |
260 # For example adding "sideeffect=\par Side Effects:\n" will allow you to |
| 249 # put the command \sideeffect (or @sideeffect) in the documentation, which |
261 # put the command \sideeffect (or @sideeffect) in the documentation, which |
| 250 # will result in a user defined paragraph with heading "Side Effects:". |
262 # will result in a user-defined paragraph with heading "Side Effects:". |
| 251 # You can put \n's in the value part of an alias to insert newlines. |
263 # You can put \n's in the value part of an alias to insert newlines. |
| 252 |
264 |
| 253 ALIASES = |
265 ALIASES = |
| 254 |
266 |
| 255 # The ENABLED_SECTIONS tag can be used to enable conditional |
267 # The ENABLED_SECTIONS tag can be used to enable conditional |
| 256 # documentation sections, marked by \if sectionname ... \endif. |
268 # documentation sections, marked by \if sectionname ... \endif. |
| 257 |
269 |
| 258 ENABLED_SECTIONS = |
270 ENABLED_SECTIONS = |
| 259 |
271 |
| 260 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines |
272 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines |
| 261 # the initial value of a variable or define consist of for it to appear in |
273 # the initial value of a variable or define consists of for it to appear in |
| 262 # the documentation. If the initializer consists of more lines than specified |
274 # the documentation. If the initializer consists of more lines than specified |
| 263 # here it will be hidden. Use a value of 0 to hide initializers completely. |
275 # here it will be hidden. Use a value of 0 to hide initializers completely. |
| 264 # The appearance of the initializer of individual variables and defines in the |
276 # The appearance of the initializer of individual variables and defines in the |
| 265 # documentation can be controlled using \showinitializer or \hideinitializer |
277 # documentation can be controlled using \showinitializer or \hideinitializer |
| 266 # command in the documentation regardless of this setting. |
278 # command in the documentation regardless of this setting. |
| 267 |
279 |
| 268 MAX_INITIALIZER_LINES = 30 |
280 MAX_INITIALIZER_LINES = 30 |
| 269 |
281 |
| 270 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources |
282 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources |
| 271 # only. Doxygen will then generate output that is more tailored for C. |
283 # only. Doxygen will then generate output that is more tailored for C. |
| 272 # For instance some of the names that are used will be different. The list |
284 # For instance, some of the names that are used will be different. The list |
| 273 # of all members will be omitted, etc. |
285 # of all members will be omitted, etc. |
| 274 |
286 |
| 275 OPTIMIZE_OUTPUT_FOR_C = YES |
287 OPTIMIZE_OUTPUT_FOR_C = YES |
| 276 |
288 |
| 277 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources |
289 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources |
| 278 # only. Doxygen will then generate output that is more tailored for Java. |
290 # only. Doxygen will then generate output that is more tailored for Java. |
| 279 # For instance namespaces will be presented as packages, qualified scopes |
291 # For instance, namespaces will be presented as packages, qualified scopes |
| 280 # will look different, etc. |
292 # will look different, etc. |
| 281 |
293 |
| 282 OPTIMIZE_OUTPUT_JAVA = NO |
294 OPTIMIZE_OUTPUT_JAVA = NO |
| 283 |
295 |
| 284 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated |
296 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated |
| 285 # at the bottom of the documentation of classes and structs. If set to YES the |
297 # at the bottom of the documentation of classes and structs. If set to YES the |
| 286 # list will mention the files that were used to generate the documentation. |
298 # list will mention the files that were used to generate the documentation. |
| 287 |
299 |
| 288 SHOW_USED_FILES = YES |
300 SHOW_USED_FILES = YES |
| 289 |
301 |
| |
302 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of |
| |
303 # the same type (for instance a group of public functions) to be put as a |
| |
304 # subgroup of that type (e.g. under the Public Functions section). Set it to |
| |
305 # NO to prevent subgrouping. Alternatively, this can be done per class using |
| |
306 # the \nosubgrouping command. |
| |
307 |
| |
308 SUBGROUPING = YES |
| |
309 |
| 290 #--------------------------------------------------------------------------- |
310 #--------------------------------------------------------------------------- |
| 291 # configuration options related to warning and progress messages |
311 # configuration options related to warning and progress messages |
| 292 #--------------------------------------------------------------------------- |
312 #--------------------------------------------------------------------------- |
| 293 |
313 |
| 294 # The QUIET tag can be used to turn on/off the messages that are generated |
314 # The QUIET tag can be used to turn on/off the messages that are generated |
| 305 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings |
325 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings |
| 306 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will |
326 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will |
| 307 # automatically be disabled. |
327 # automatically be disabled. |
| 308 |
328 |
| 309 WARN_IF_UNDOCUMENTED = NO |
329 WARN_IF_UNDOCUMENTED = NO |
| |
330 |
| |
331 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for |
| |
332 # potential errors in the documentation, such as not documenting some |
| |
333 # parameters in a documented function, or documenting parameters that |
| |
334 # don't exist or using markup commands wrongly. |
| |
335 |
| |
336 WARN_IF_DOC_ERROR = YES |
| 310 |
337 |
| 311 # The WARN_FORMAT tag determines the format of the warning messages that |
338 # The WARN_FORMAT tag determines the format of the warning messages that |
| 312 # doxygen can produce. The string should contain the $file, $line, and $text |
339 # doxygen can produce. The string should contain the $file, $line, and $text |
| 313 # tags, which will be replaced by the file and line number from which the |
340 # tags, which will be replaced by the file and line number from which the |
| 314 # warning originated and the warning text. |
341 # warning originated and the warning text. |
| 435 # then for each documented function all documented entities |
462 # then for each documented function all documented entities |
| 436 # called/used by that function will be listed. |
463 # called/used by that function will be listed. |
| 437 |
464 |
| 438 REFERENCES_RELATION = YES |
465 REFERENCES_RELATION = YES |
| 439 |
466 |
| |
467 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen |
| |
468 # will generate a verbatim copy of the header file for each class for |
| |
469 # which an include is specified. Set to NO to disable this. |
| |
470 |
| |
471 VERBATIM_HEADERS = YES |
| |
472 |
| 440 #--------------------------------------------------------------------------- |
473 #--------------------------------------------------------------------------- |
| 441 # configuration options related to the alphabetical class index |
474 # configuration options related to the alphabetical class index |
| 442 #--------------------------------------------------------------------------- |
475 #--------------------------------------------------------------------------- |
| 443 |
476 |
| 444 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index |
477 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index |
| 556 ENUM_VALUES_PER_LINE = 4 |
589 ENUM_VALUES_PER_LINE = 4 |
| 557 |
590 |
| 558 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be |
591 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be |
| 559 # generated containing a tree-like index structure (just like the one that |
592 # generated containing a tree-like index structure (just like the one that |
| 560 # is generated for HTML Help). For this to work a browser that supports |
593 # is generated for HTML Help). For this to work a browser that supports |
| 561 # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+, |
594 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, |
| 562 # or Internet explorer 4.0+). Note that for large projects the tree generation |
595 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are |
| 563 # can take a very long time. In such cases it is better to disable this feature. |
596 # probably better off using the HTML help feature. |
| 564 # Windows users are probably better off using the HTML help feature. |
|
| 565 |
597 |
| 566 GENERATE_TREEVIEW = NO |
598 GENERATE_TREEVIEW = NO |
| 567 |
599 |
| 568 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be |
600 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be |
| 569 # used to set the initial width (in pixels) of the frame in which the tree |
601 # used to set the initial width (in pixels) of the frame in which the tree |
| 570 # is shown. |
602 # is shown. |
| 571 |
603 |
| 572 TREEVIEW_WIDTH = 250 |
604 TREEVIEW_WIDTH = 250 |
| 573 |
605 |
| |
606 # If the GENERATE_DEVHELP tag is set to YES, an index file for the |
| |
607 # DevHelp documentation viewer will be generated. For more information, |
| |
608 # see http://www.imendio.com/projects/devhelp/ |
| |
609 |
| |
610 GENERATE_DEVHELP = YES |
| |
611 |
| |
612 # The DEVHELP_TITLE tag is used to specify the displayed name of the |
| |
613 # generated DevHelp book file. If left blank, the project name will |
| |
614 # be used. |
| |
615 |
| |
616 DEVHELP_TITLE = Gaim |
| |
617 |
| 574 #--------------------------------------------------------------------------- |
618 #--------------------------------------------------------------------------- |
| 575 # configuration options related to the LaTeX output |
619 # configuration options related to the LaTeX output |
| 576 #--------------------------------------------------------------------------- |
620 #--------------------------------------------------------------------------- |
| 577 |
621 |
| 578 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will |
622 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will |
| 756 # feature is still experimental and incomplete at the |
813 # feature is still experimental and incomplete at the |
| 757 # moment. |
814 # moment. |
| 758 |
815 |
| 759 GENERATE_PERLMOD = NO |
816 GENERATE_PERLMOD = NO |
| 760 |
817 |
| |
818 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate |
| |
819 # the necessary Makefile rules, Perl scripts and LaTeX code to be able |
| |
820 # to generate PDF and DVI output from the Perl module output. |
| |
821 |
| |
822 PERLMOD_LATEX = NO |
| |
823 |
| |
824 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be |
| |
825 # nicely formatted so it can be parsed by a human reader. This is useful |
| |
826 # if you want to understand what is going on. On the other hand, if this |
| |
827 # tag is set to NO the size of the Perl module output will be much smaller |
| |
828 # and Perl will parse it just the same. |
| |
829 |
| |
830 PERLMOD_PRETTY = YES |
| |
831 |
| |
832 # The names of the make variables in the generated doxyrules.make file |
| |
833 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. |
| |
834 # This is useful so different doxyrules.make files included by the same |
| |
835 # Makefile don't overwrite each other's variables. |
| |
836 |
| |
837 PERLMOD_MAKEVAR_PREFIX = |
| |
838 |
| 761 #--------------------------------------------------------------------------- |
839 #--------------------------------------------------------------------------- |
| 762 # Configuration options related to the preprocessor |
840 # Configuration options related to the preprocessor |
| 763 #--------------------------------------------------------------------------- |
841 #--------------------------------------------------------------------------- |
| 764 |
842 |
| 765 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will |
843 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will |
| 824 |
902 |
| 825 #--------------------------------------------------------------------------- |
903 #--------------------------------------------------------------------------- |
| 826 # Configuration::addtions related to external references |
904 # Configuration::addtions related to external references |
| 827 #--------------------------------------------------------------------------- |
905 #--------------------------------------------------------------------------- |
| 828 |
906 |
| 829 # The TAGFILES tag can be used to specify one or more tagfiles. |
907 # The TAGFILES option can be used to specify one or more tagfiles. |
| |
908 # Optionally an initial location of the external documentation |
| |
909 # can be added for each tagfile. The format of a tag file without |
| |
910 # this location is as follows: |
| |
911 # TAGFILES = file1 file2 ... |
| |
912 # Adding location for the tag files is done as follows: |
| |
913 # TAGFILES = file1=loc1 "file2 = loc2" ... |
| |
914 # where "loc1" and "loc2" can be relative or absolute paths or |
| |
915 # URLs. If a location is present for each tag, the installdox tool |
| |
916 # does not have to be run to correct the links. |
| |
917 # Note that each tag file must have a unique name |
| |
918 # (where the name does NOT include the path) |
| |
919 # If a tag file is not located in the directory in which doxygen |
| |
920 # is run, you must also specify the path to the tagfile here. |
| 830 |
921 |
| 831 TAGFILES = |
922 TAGFILES = |
| 832 |
923 |
| 833 # When a file name is specified after GENERATE_TAGFILE, doxygen will create |
924 # When a file name is specified after GENERATE_TAGFILE, doxygen will create |
| 834 # a tag file that is based on the input files it reads. |
925 # a tag file that is based on the input files it reads. |
| 855 #--------------------------------------------------------------------------- |
946 #--------------------------------------------------------------------------- |
| 856 # Configuration options related to the dot tool |
947 # Configuration options related to the dot tool |
| 857 #--------------------------------------------------------------------------- |
948 #--------------------------------------------------------------------------- |
| 858 |
949 |
| 859 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
950 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
| 860 # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or |
951 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or |
| 861 # super classes. Setting the tag to NO turns the diagrams off. Note that this |
952 # super classes. Setting the tag to NO turns the diagrams off. Note that this |
| 862 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is |
953 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is |
| 863 # recommended to install and use dot, since it yield more powerful graphs. |
954 # recommended to install and use dot, since it yields more powerful graphs. |
| 864 |
955 |
| 865 CLASS_DIAGRAMS = YES |
956 CLASS_DIAGRAMS = YES |
| 866 |
957 |
| 867 # If set to YES, the inheritance and collaboration graphs will hide |
958 # If set to YES, the inheritance and collaboration graphs will hide |
| 868 # inheritance and usage relations if the target is undocumented |
959 # inheritance and usage relations if the target is undocumented |
| 907 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each |
1004 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each |
| 908 # documented header file showing the documented files that directly or |
1005 # documented header file showing the documented files that directly or |
| 909 # indirectly include this file. |
1006 # indirectly include this file. |
| 910 |
1007 |
| 911 INCLUDED_BY_GRAPH = YES |
1008 INCLUDED_BY_GRAPH = YES |
| |
1009 |
| |
1010 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will |
| |
1011 # generate a call dependency graph for every global function or class method. |
| |
1012 # Note that enabling this option will significantly increase the time of a run. |
| |
1013 # So in most cases it will be better to enable call graphs for selected |
| |
1014 # functions only using the \callgraph command. |
| |
1015 |
| |
1016 CALL_GRAPH = NO |
| 912 |
1017 |
| 913 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
1018 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
| 914 # will graphical hierarchy of all classes instead of a textual one. |
1019 # will graphical hierarchy of all classes instead of a textual one. |
| 915 |
1020 |
| 916 GRAPHICAL_HIERARCHY = YES |
1021 GRAPHICAL_HIERARCHY = YES |
| 946 # the specified constraint. Beware that most browsers cannot cope with very |
1051 # the specified constraint. Beware that most browsers cannot cope with very |
| 947 # large images. |
1052 # large images. |
| 948 |
1053 |
| 949 MAX_DOT_GRAPH_HEIGHT = 1024 |
1054 MAX_DOT_GRAPH_HEIGHT = 1024 |
| 950 |
1055 |
| |
1056 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
| |
1057 # graphs generated by dot. A depth value of 3 means that only nodes reachable |
| |
1058 # from the root by following a path via at most 3 edges will be shown. Nodes that |
| |
1059 # lay further from the root node will be omitted. Note that setting this option to |
| |
1060 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also |
| |
1061 # note that a graph may be further truncated if the graph's image dimensions are |
| |
1062 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). |
| |
1063 # If 0 is used for the depth value (the default), the graph is not depth-constrained. |
| |
1064 |
| |
1065 MAX_DOT_GRAPH_DEPTH = 0 |
| |
1066 |
| 951 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
1067 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
| 952 # generate a legend page explaining the meaning of the various boxes and |
1068 # generate a legend page explaining the meaning of the various boxes and |
| 953 # arrows in the dot generated graphs. |
1069 # arrows in the dot generated graphs. |
| 954 |
1070 |
| 955 GENERATE_LEGEND = YES |
1071 GENERATE_LEGEND = YES |
| 956 |
1072 |
| 957 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will |
1073 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will |
| 958 # remove the intermedate dot files that are used to generate |
1074 # remove the intermediate dot files that are used to generate |
| 959 # the various graphs. |
1075 # the various graphs. |
| 960 |
1076 |
| 961 DOT_CLEANUP = YES |
1077 DOT_CLEANUP = YES |
| 962 |
1078 |
| 963 #--------------------------------------------------------------------------- |
1079 #--------------------------------------------------------------------------- |