30 # If a relative path is entered, it will be relative to the location |
30 # If a relative path is entered, it will be relative to the location |
31 # where doxygen was started. If left blank the current directory will be used. |
31 # where doxygen was started. If left blank the current directory will be used. |
32 |
32 |
33 OUTPUT_DIRECTORY = |
33 OUTPUT_DIRECTORY = |
34 |
34 |
|
35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create |
|
36 # 4096 sub-directories (in 2 levels) under the output directory of each output |
|
37 # format and will distribute the generated files over these directories. |
|
38 # Enabling this option can be useful when feeding doxygen a huge amount of |
|
39 # source files, where putting all generated files in the same directory would |
|
40 # otherwise cause performance problems for the file system. |
|
41 |
|
42 CREATE_SUBDIRS = NO |
|
43 |
35 # The OUTPUT_LANGUAGE tag is used to specify the language in which all |
44 # The OUTPUT_LANGUAGE tag is used to specify the language in which all |
36 # documentation generated by doxygen is written. Doxygen will use this |
45 # documentation generated by doxygen is written. Doxygen will use this |
37 # information to generate all constant output in the proper language. |
46 # information to generate all constant output in the proper language. |
38 # The default language is English, other supported languages are: |
47 # The default language is English, other supported languages are: |
39 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, |
48 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, |
40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en |
49 # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese, |
41 # (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese, |
50 # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian, |
42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. |
51 # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, |
|
52 # Swedish, and Ukrainian. |
43 |
53 |
44 OUTPUT_LANGUAGE = English |
54 OUTPUT_LANGUAGE = English |
45 |
55 |
46 # This tag can be used to specify the encoding used in the generated output. |
56 # 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, |
57 # The encoding is not always determined by the language that is chosen, |
68 REPEAT_BRIEF = NO |
78 REPEAT_BRIEF = NO |
69 |
79 |
70 # This tag implements a quasi-intelligent brief description abbreviator |
80 # This tag implements a quasi-intelligent brief description abbreviator |
71 # that is used to form the text in various listings. Each string |
81 # that is used to form the text in various listings. Each string |
72 # in this list, if found as the leading text of the brief description, will be |
82 # in this list, if found as the leading text of the brief description, will be |
73 # stripped from the text and the result after processing the whole list, is used |
83 # stripped from the text and the result after processing the whole list, is |
74 # as the annotated text. Otherwise, the brief description is used as-is. If left |
84 # used as the annotated text. Otherwise, the brief description is used as-is. |
75 # blank, the following values are used ("$name" is automatically replaced with the |
85 # If left blank, the following values are used ("$name" is automatically |
76 # name of the entity): "The $name class" "The $name widget" "The $name file" |
86 # replaced with the name of the entity): "The $name class" "The $name widget" |
77 # "is" "provides" "specifies" "contains" "represents" "a" "an" "the" |
87 # "The $name file" "is" "provides" "specifies" "contains" |
|
88 # "represents" "a" "an" "the" |
78 |
89 |
79 ABBREVIATE_BRIEF = |
90 ABBREVIATE_BRIEF = |
80 |
91 |
81 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then |
92 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then |
82 # Doxygen will generate a detailed section even if there is only a brief |
93 # Doxygen will generate a detailed section even if there is only a brief |
83 # description. |
94 # description. |
84 |
95 |
85 ALWAYS_DETAILED_SEC = NO |
96 ALWAYS_DETAILED_SEC = NO |
86 |
97 |
87 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited |
98 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all |
88 # members of a class in the documentation of that class as if those members were |
99 # inherited members of a class in the documentation of that class as if those |
89 # ordinary class members. Constructors, destructors and assignment operators of |
100 # members were ordinary class members. Constructors, destructors and assignment |
90 # the base classes will not be shown. |
101 # operators of the base classes will not be shown. |
91 |
102 |
92 INLINE_INHERITED_MEMB = NO |
103 INLINE_INHERITED_MEMB = NO |
93 |
104 |
94 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full |
105 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full |
95 # path before files name in the file list and in the header files. If set |
106 # path before files name in the file list and in the header files. If set |
98 FULL_PATH_NAMES = NO |
109 FULL_PATH_NAMES = NO |
99 |
110 |
100 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag |
111 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag |
101 # can be used to strip a user-defined part of the path. Stripping is |
112 # can be used to strip a user-defined part of the path. Stripping is |
102 # only done if one of the specified strings matches the left-hand part of |
113 # only done if one of the specified strings matches the left-hand part of |
103 # the path. It is allowed to use relative paths in the argument list. |
114 # the path. The tag can be used to show relative paths in the file list. |
104 # If left blank the directory from which doxygen is run is used as the |
115 # If left blank the directory from which doxygen is run is used as the |
105 # path to strip. |
116 # path to strip. |
106 |
117 |
107 STRIP_FROM_PATH = |
118 STRIP_FROM_PATH = |
|
119 |
|
120 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of |
|
121 # the path mentioned in the documentation of a class, which tells |
|
122 # the reader which header file to include in order to use a class. |
|
123 # If left blank only the name of the header file containing the class |
|
124 # definition is used. Otherwise one should specify the include paths that |
|
125 # are normally passed to the compiler using the -I flag. |
|
126 |
|
127 STRIP_FROM_INC_PATH = |
108 |
128 |
109 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
129 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
110 # (but less readable) file names. This can be useful is your file systems |
130 # (but less readable) file names. This can be useful is your file systems |
111 # doesn't support long names like on DOS, Mac, or CD-ROM. |
131 # doesn't support long names like on DOS, Mac, or CD-ROM. |
112 |
132 |
160 # will result in a user-defined paragraph with heading "Side Effects:". |
180 # will result in a user-defined paragraph with heading "Side Effects:". |
161 # You can put \n's in the value part of an alias to insert newlines. |
181 # You can put \n's in the value part of an alias to insert newlines. |
162 |
182 |
163 ALIASES = |
183 ALIASES = |
164 |
184 |
165 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources |
185 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C |
166 # only. Doxygen will then generate output that is more tailored for C. |
186 # sources only. Doxygen will then generate output that is more tailored for C. |
167 # For instance, some of the names that are used will be different. The list |
187 # For instance, some of the names that are used will be different. The list |
168 # of all members will be omitted, etc. |
188 # of all members will be omitted, etc. |
169 |
189 |
170 OPTIMIZE_OUTPUT_FOR_C = NO |
190 OPTIMIZE_OUTPUT_FOR_C = NO |
171 |
191 |
209 # defined locally in source files will be included in the documentation. |
229 # defined locally in source files will be included in the documentation. |
210 # If set to NO only classes defined in header files are included. |
230 # If set to NO only classes defined in header files are included. |
211 |
231 |
212 EXTRACT_LOCAL_CLASSES = YES |
232 EXTRACT_LOCAL_CLASSES = YES |
213 |
233 |
|
234 # This flag is only useful for Objective-C code. When set to YES local |
|
235 # methods, which are defined in the implementation section but not in |
|
236 # the interface are included in the documentation. |
|
237 # If set to NO (the default) only methods in the interface are included. |
|
238 |
|
239 EXTRACT_LOCAL_METHODS = NO |
|
240 |
214 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all |
241 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all |
215 # undocumented members of documented classes, files or namespaces. |
242 # undocumented members of documented classes, files or namespaces. |
216 # If set to NO (the default) these members will be included in the |
243 # If set to NO (the default) these members will be included in the |
217 # various overviews, but no documentation section is generated. |
244 # various overviews, but no documentation section is generated. |
218 # This option has no effect if EXTRACT_ALL is enabled. |
245 # This option has no effect if EXTRACT_ALL is enabled. |
249 |
276 |
250 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
277 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
251 # file names in lower-case letters. If set to YES upper-case letters are also |
278 # file names in lower-case letters. If set to YES upper-case letters are also |
252 # allowed. This is useful if you have classes or files whose names only differ |
279 # allowed. This is useful if you have classes or files whose names only differ |
253 # in case and if your file system supports case sensitive file names. Windows |
280 # in case and if your file system supports case sensitive file names. Windows |
254 # users are advised to set this option to NO. |
281 # and Mac users are advised to set this option to NO. |
255 |
282 |
256 CASE_SENSE_NAMES = YES |
283 CASE_SENSE_NAMES = YES |
257 |
284 |
258 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen |
285 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen |
259 # will show members with their full class and namespace scopes in the |
286 # will show members with their full class and namespace scopes in the |
339 # at the bottom of the documentation of classes and structs. If set to YES the |
366 # at the bottom of the documentation of classes and structs. If set to YES the |
340 # list will mention the files that were used to generate the documentation. |
367 # list will mention the files that were used to generate the documentation. |
341 |
368 |
342 SHOW_USED_FILES = YES |
369 SHOW_USED_FILES = YES |
343 |
370 |
|
371 # If the sources in your project are distributed over multiple directories |
|
372 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy |
|
373 # in the documentation. |
|
374 |
|
375 SHOW_DIRECTORIES = YES |
|
376 |
|
377 # The FILE_VERSION_FILTER tag can be used to specify a program or script that |
|
378 # doxygen should invoke to get the current version for each file (typically from the |
|
379 # version control system). Doxygen will invoke the program by executing (via |
|
380 # popen()) the command <command> <input-file>, where <command> is the value of |
|
381 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file |
|
382 # provided by doxygen. Whatever the progam writes to standard output |
|
383 # is used as the file version. See the manual for examples. |
|
384 |
|
385 FILE_VERSION_FILTER = |
|
386 |
344 #--------------------------------------------------------------------------- |
387 #--------------------------------------------------------------------------- |
345 # configuration options related to warning and progress messages |
388 # configuration options related to warning and progress messages |
346 #--------------------------------------------------------------------------- |
389 #--------------------------------------------------------------------------- |
347 |
390 |
348 # The QUIET tag can be used to turn on/off the messages that are generated |
391 # The QUIET tag can be used to turn on/off the messages that are generated |
367 # parameters in a documented function, or documenting parameters that |
410 # parameters in a documented function, or documenting parameters that |
368 # don't exist or using markup commands wrongly. |
411 # don't exist or using markup commands wrongly. |
369 |
412 |
370 WARN_IF_DOC_ERROR = YES |
413 WARN_IF_DOC_ERROR = YES |
371 |
414 |
|
415 # This WARN_NO_PARAMDOC option can be abled to get warnings for |
|
416 # functions that are documented, but have no documentation for their parameters |
|
417 # or return value. If set to NO (the default) doxygen will only warn about |
|
418 # wrong or incomplete parameter documentation, but not about the absence of |
|
419 # documentation. |
|
420 |
|
421 WARN_NO_PARAMDOC = NO |
|
422 |
372 # The WARN_FORMAT tag determines the format of the warning messages that |
423 # The WARN_FORMAT tag determines the format of the warning messages that |
373 # doxygen can produce. The string should contain the $file, $line, and $text |
424 # doxygen can produce. The string should contain the $file, $line, and $text |
374 # tags, which will be replaced by the file and line number from which the |
425 # tags, which will be replaced by the file and line number from which the |
375 # warning originated and the warning text. |
426 # warning originated and the warning text. Optionally the format may contain |
|
427 # $version, which will be replaced by the version of the file (if it could |
|
428 # be obtained via FILE_VERSION_FILTER) |
376 |
429 |
377 WARN_FORMAT = "$file:$line: $text" |
430 WARN_FORMAT = "$file:$line: $text" |
378 |
431 |
379 # The WARN_LOGFILE tag can be used to specify a file to which warning |
432 # The WARN_LOGFILE tag can be used to specify a file to which warning |
380 # and error messages should be written. If left blank the output is written |
433 # and error messages should be written. If left blank the output is written |
390 # documented source files. You may enter file names like "myfile.cpp" or |
443 # documented source files. You may enter file names like "myfile.cpp" or |
391 # directories like "/usr/src/myproject". Separate the files or directories |
444 # directories like "/usr/src/myproject". Separate the files or directories |
392 # with spaces. |
445 # with spaces. |
393 |
446 |
394 INPUT = ../../doc/mainpage.dox \ |
447 INPUT = ../../doc/mainpage.dox \ |
395 ../../doc/graphs.dox \ |
448 ../../doc/graphs.dox \ |
396 ../../doc/maps.dox ../../doc/coding_style.dox \ |
449 ../../doc/maps.dox \ |
|
450 ../../doc/coding_style.dox \ |
397 ../../doc/groups.dox \ |
451 ../../doc/groups.dox \ |
398 ../lemon \ |
452 ../lemon \ |
399 ../lemon/concept \ |
453 ../lemon/concept \ |
400 ../test/test_tools.h \ |
454 ../test/test_tools.h \ |
401 klao/debug.h \ |
455 klao/debug.h \ |
402 jacint/max_flow.h \ |
456 jacint/max_flow.h \ |
403 jacint/max_matching.h \ |
457 jacint/max_matching.h \ |
404 marci/bfs_dfs.h \ |
458 marci/bfs_dfs.h \ |
405 marci/bfs_dfs_misc.h \ |
459 marci/bfs_dfs_misc.h \ |
406 marci/lp/lp_solver_wrapper.h \ |
460 marci/lp/lp_solver_wrapper.h \ |
407 jacint/graph_gen.h \ |
461 jacint/graph_gen.h \ |
408 marci/max_bipartite_matching.h \ |
462 marci/max_bipartite_matching.h \ |
409 marci/bipartite_graph_wrapper.h \ |
463 marci/bipartite_graph_wrapper.h \ |
410 alpar/graph_to_eps.cc \ |
464 alpar/graph_to_eps.cc \ |
411 deba \ |
465 deba |
412 |
|
413 |
466 |
414 # If the value of the INPUT tag contains directories, you can use the |
467 # If the value of the INPUT tag contains directories, you can use the |
415 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
468 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
416 # and *.h) to filter out the source-files in the directories. If left |
469 # and *.h) to filter out the source-files in the directories. If left |
417 # blank the following patterns are tested: |
470 # blank the following patterns are tested: |
418 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp |
471 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx |
419 # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc |
472 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm |
420 |
473 |
421 FILE_PATTERNS = |
474 FILE_PATTERNS = |
422 |
475 |
423 # The RECURSIVE tag can be used to turn specify whether or not subdirectories |
476 # The RECURSIVE tag can be used to turn specify whether or not subdirectories |
424 # should be searched for input files as well. Possible values are YES and NO. |
477 # should be searched for input files as well. Possible values are YES and NO. |
430 # excluded from the INPUT source files. This way you can easily exclude a |
483 # excluded from the INPUT source files. This way you can easily exclude a |
431 # subdirectory from a directory tree whose root is specified with the INPUT tag. |
484 # subdirectory from a directory tree whose root is specified with the INPUT tag. |
432 |
485 |
433 EXCLUDE = |
486 EXCLUDE = |
434 |
487 |
435 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories |
488 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or |
436 # that are symbolic links (a Unix filesystem feature) are excluded from the input. |
489 # directories that are symbolic links (a Unix filesystem feature) are excluded |
|
490 # from the input. |
437 |
491 |
438 EXCLUDE_SYMLINKS = NO |
492 EXCLUDE_SYMLINKS = NO |
439 |
493 |
440 # If the value of the INPUT tag contains directories, you can use the |
494 # If the value of the INPUT tag contains directories, you can use the |
441 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude |
495 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude |
472 # The INPUT_FILTER tag can be used to specify a program that doxygen should |
526 # The INPUT_FILTER tag can be used to specify a program that doxygen should |
473 # invoke to filter for each input file. Doxygen will invoke the filter program |
527 # invoke to filter for each input file. Doxygen will invoke the filter program |
474 # by executing (via popen()) the command <filter> <input-file>, where <filter> |
528 # by executing (via popen()) the command <filter> <input-file>, where <filter> |
475 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an |
529 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an |
476 # input file. Doxygen will then use the output that the filter program writes |
530 # input file. Doxygen will then use the output that the filter program writes |
477 # to standard output. |
531 # to standard output. If FILTER_PATTERNS is specified, this tag will be |
|
532 # ignored. |
478 |
533 |
479 INPUT_FILTER = |
534 INPUT_FILTER = |
|
535 |
|
536 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern |
|
537 # basis. Doxygen will compare the file name with each pattern and apply the |
|
538 # filter if there is a match. The filters are a list of the form: |
|
539 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further |
|
540 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER |
|
541 # is applied to all files. |
|
542 |
|
543 FILTER_PATTERNS = |
480 |
544 |
481 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using |
545 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using |
482 # INPUT_FILTER) will be used to filter the input files when producing source |
546 # INPUT_FILTER) will be used to filter the input files when producing source |
483 # files to browse (i.e. when SOURCE_BROWSER is set to YES). |
547 # files to browse (i.e. when SOURCE_BROWSER is set to YES). |
484 |
548 |
928 |
992 |
929 # The PREDEFINED tag can be used to specify one or more macro names that |
993 # The PREDEFINED tag can be used to specify one or more macro names that |
930 # are defined before the preprocessor is started (similar to the -D option of |
994 # are defined before the preprocessor is started (similar to the -D option of |
931 # gcc). The argument of the tag is a list of macros of the form: name |
995 # gcc). The argument of the tag is a list of macros of the form: name |
932 # or name=definition (no spaces). If the definition and the = are |
996 # or name=definition (no spaces). If the definition and the = are |
933 # omitted =1 is assumed. |
997 # omitted =1 is assumed. To prevent a macro definition from being |
|
998 # undefined via #undef or recursively expanded use the := operator |
|
999 # instead of the = operator. |
934 |
1000 |
935 PREDEFINED = DOXYGEN |
1001 PREDEFINED = DOXYGEN |
936 |
1002 |
937 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then |
1003 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then |
938 # this tag can be used to specify a list of macro names that should be expanded. |
1004 # this tag can be used to specify a list of macro names that should be expanded. |
942 EXPAND_AS_DEFINED = |
1008 EXPAND_AS_DEFINED = |
943 |
1009 |
944 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
1010 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
945 # doxygen's preprocessor will remove all function-like macros that are alone |
1011 # doxygen's preprocessor will remove all function-like macros that are alone |
946 # on a line, have an all uppercase name, and do not end with a semicolon. Such |
1012 # on a line, have an all uppercase name, and do not end with a semicolon. Such |
947 # function macros are typically used for boiler-plate code, and will confuse the |
1013 # function macros are typically used for boiler-plate code, and will confuse |
948 # parser if not removed. |
1014 # the parser if not removed. |
949 |
1015 |
950 SKIP_FUNCTION_MACROS = YES |
1016 SKIP_FUNCTION_MACROS = YES |
951 |
1017 |
952 #--------------------------------------------------------------------------- |
1018 #--------------------------------------------------------------------------- |
953 # Configuration::additions related to external references |
1019 # Configuration::additions related to external references |
995 #--------------------------------------------------------------------------- |
1061 #--------------------------------------------------------------------------- |
996 # Configuration options related to the dot tool |
1062 # Configuration options related to the dot tool |
997 #--------------------------------------------------------------------------- |
1063 #--------------------------------------------------------------------------- |
998 |
1064 |
999 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
1065 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
1000 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or |
1066 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base |
1001 # super classes. Setting the tag to NO turns the diagrams off. Note that this |
1067 # or super classes. Setting the tag to NO turns the diagrams off. Note that |
1002 # option is superseded by the HAVE_DOT option below. This is only a fallback. It is |
1068 # this option is superseded by the HAVE_DOT option below. This is only a |
1003 # recommended to install and use dot, since it yields more powerful graphs. |
1069 # fallback. It is recommended to install and use dot, since it yields more |
|
1070 # powerful graphs. |
1004 |
1071 |
1005 CLASS_DIAGRAMS = YES |
1072 CLASS_DIAGRAMS = YES |
1006 |
1073 |
1007 # If set to YES, the inheritance and collaboration graphs will hide |
1074 # If set to YES, the inheritance and collaboration graphs will hide |
1008 # inheritance and usage relations if the target is undocumented |
1075 # inheritance and usage relations if the target is undocumented |
1028 # will generate a graph for each documented class showing the direct and |
1095 # will generate a graph for each documented class showing the direct and |
1029 # indirect implementation dependencies (inheritance, containment, and |
1096 # indirect implementation dependencies (inheritance, containment, and |
1030 # class references variables) of the class with other documented classes. |
1097 # class references variables) of the class with other documented classes. |
1031 |
1098 |
1032 COLLABORATION_GRAPH = YES |
1099 COLLABORATION_GRAPH = YES |
|
1100 |
|
1101 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen |
|
1102 # will generate a graph for groups, showing the direct groups dependencies |
|
1103 |
|
1104 GROUP_GRAPHS = YES |
1033 |
1105 |
1034 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and |
1106 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and |
1035 # collaboration diagrams in a style similar to the OMG's Unified Modeling |
1107 # collaboration diagrams in a style similar to the OMG's Unified Modeling |
1036 # Language. |
1108 # Language. |
1037 |
1109 |
1067 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
1139 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
1068 # will graphical hierarchy of all classes instead of a textual one. |
1140 # will graphical hierarchy of all classes instead of a textual one. |
1069 |
1141 |
1070 GRAPHICAL_HIERARCHY = YES |
1142 GRAPHICAL_HIERARCHY = YES |
1071 |
1143 |
|
1144 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES |
|
1145 # then doxygen will show the dependencies a directory has on other directories |
|
1146 # in a graphical way. The dependency relations are determined by the #include |
|
1147 # relations between the files in the directories. |
|
1148 |
|
1149 DIRECTORY_GRAPH = YES |
|
1150 |
1072 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
1151 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
1073 # generated by dot. Possible values are png, jpg, or gif |
1152 # generated by dot. Possible values are png, jpg, or gif |
1074 # If left blank png will be used. |
1153 # If left blank png will be used. |
1075 |
1154 |
1076 DOT_IMAGE_FORMAT = png |
1155 DOT_IMAGE_FORMAT = png |
1102 |
1181 |
1103 MAX_DOT_GRAPH_HEIGHT = 1024 |
1182 MAX_DOT_GRAPH_HEIGHT = 1024 |
1104 |
1183 |
1105 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
1184 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
1106 # graphs generated by dot. A depth value of 3 means that only nodes reachable |
1185 # graphs generated by dot. A depth value of 3 means that only nodes reachable |
1107 # from the root by following a path via at most 3 edges will be shown. Nodes that |
1186 # from the root by following a path via at most 3 edges will be shown. Nodes |
1108 # lay further from the root node will be omitted. Note that setting this option to |
1187 # that lay further from the root node will be omitted. Note that setting this |
1109 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also |
1188 # option to 1 or 2 may greatly reduce the computation time needed for large |
1110 # note that a graph may be further truncated if the graph's image dimensions are |
1189 # code bases. Also note that a graph may be further truncated if the graph's |
1111 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). |
1190 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH |
1112 # If 0 is used for the depth value (the default), the graph is not depth-constrained. |
1191 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), |
|
1192 # the graph is not depth-constrained. |
1113 |
1193 |
1114 MAX_DOT_GRAPH_DEPTH = 0 |
1194 MAX_DOT_GRAPH_DEPTH = 0 |
|
1195 |
|
1196 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent |
|
1197 # background. This is disabled by default, which results in a white background. |
|
1198 # Warning: Depending on the platform used, enabling this option may lead to |
|
1199 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to |
|
1200 # read). |
|
1201 |
|
1202 DOT_TRANSPARENT = NO |
|
1203 |
|
1204 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output |
|
1205 # files in one run (i.e. multiple -o and -T options on the command line). This |
|
1206 # makes dot run faster, but since only newer versions of dot (>1.8.10) |
|
1207 # support this, this feature is disabled by default. |
|
1208 |
|
1209 DOT_MULTI_TARGETS = NO |
1115 |
1210 |
1116 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
1211 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
1117 # generate a legend page explaining the meaning of the various boxes and |
1212 # generate a legend page explaining the meaning of the various boxes and |
1118 # arrows in the dot generated graphs. |
1213 # arrows in the dot generated graphs. |
1119 |
1214 |