SCM

SCM Repository

[matrix] Diff of /pkg/Doxyfile
ViewVC logotype

Diff of /pkg/Doxyfile

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 188, Mon May 31 18:50:01 2004 UTC revision 189, Mon May 31 19:03:51 2004 UTC
# Line 17  Line 17 
17  # The PROJECT_NAME tag is a single word (or a sequence of words surrounded  # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
18  # by quotes) that should identify the project.  # by quotes) that should identify the project.
19    
20  PROJECT_NAME           = lme4  PROJECT_NAME           = Matrix
21    
22  # The PROJECT_NUMBER tag can be used to enter a project or revision number.  # The PROJECT_NUMBER tag can be used to enter a project or revision number.
23  # This could be handy for archiving the generated documentation or  # This could be handy for archiving the generated documentation or
24  # if some version control system is used.  # if some version control system is used.
25    
26  PROJECT_NUMBER         = 0.1-7  PROJECT_NUMBER         = 0.8-7
27    
28  # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)  # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
29  # base path where the generated documentation will be put.  # base path where the generated documentation will be put.
30  # If a relative path is entered, it will be relative to the location  # 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.  # where doxygen was started. If left blank the current directory will be used.
32    
33  OUTPUT_DIRECTORY       = doc  OUTPUT_DIRECTORY       = ./inst/doc
34    
35  # The OUTPUT_LANGUAGE tag is used to specify the language in which all  # The OUTPUT_LANGUAGE tag is used to specify the language in which all
36  # documentation generated by doxygen is written. Doxygen will use this  # documentation generated by doxygen is written. Doxygen will use this
# Line 101  Line 101 
101    
102  ALWAYS_DETAILED_SEC    = NO  ALWAYS_DETAILED_SEC    = NO
103    
104  # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited  # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show
105  # members of a class in the documentation of that class as if those members were  # all inherited members of a class in the documentation of that class
106  # ordinary class members. Constructors, destructors and assignment operators of  # as if those members were ordinary class members. Constructors,
107  # the base classes will not be shown.  # destructors and assignment operators of the base classes will not be
108    # shown.
109    
110  INLINE_INHERITED_MEMB  = NO  INLINE_INHERITED_MEMB  = NO
111    
# Line 244  Line 245 
245  ENABLED_SECTIONS       =  ENABLED_SECTIONS       =
246    
247  # The MAX_INITIALIZER_LINES tag determines the maximum number of lines  # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
248  # the initial value of a variable or define consist of for it to appear in  # the initial value of a variable or define consist of for it to
249  # the documentation. If the initializer consists of more lines than specified  # appear in the documentation. If the initializer consists of more
250  # here it will be hidden. Use a value of 0 to hide initializers completely.  # lines than specified here it will be hidden. Use a value of 0 to
251  # The appearance of the initializer of individual variables and defines in the  # hide initializers completely.  The appearance of the initializer of
252  # documentation can be controlled using \showinitializer or \hideinitializer  # individual variables and defines in the documentation can be
253  # command in the documentation regardless of this setting.  # controlled using \showinitializer or \hideinitializer command in the
254    # documentation regardless of this setting.
255    
256  MAX_INITIALIZER_LINES  = 30  MAX_INITIALIZER_LINES  = 30
257    
258  # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources  # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of
259  # only. Doxygen will then generate output that is more tailored for C.  # C sources only. Doxygen will then generate output that is more
260  # For instance some of the names that are used will be different. The list  # tailored for C.  For instance some of the names that are used will
261  # of all members will be omitted, etc.  # be different. The list of all members will be omitted, etc.
262    
263  OPTIMIZE_OUTPUT_FOR_C  = YES  OPTIMIZE_OUTPUT_FOR_C  = YES
264    
265  # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources  # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of
266  # only. Doxygen will then generate output that is more tailored for Java.  # Java sources only. Doxygen will then generate output that is more
267  # For instance namespaces will be presented as packages, qualified scopes  # tailored for Java.  For instance namespaces will be presented as
268  # will look different, etc.  # packages, qualified scopes will look different, etc.
269    
270  OPTIMIZE_OUTPUT_JAVA   = NO  OPTIMIZE_OUTPUT_JAVA   = NO
271    
272  # Set the SHOW_USED_FILES tag to NO to disable the list of files generated  # Set the SHOW_USED_FILES tag to NO to disable the list of files
273  # at the bottom of the documentation of classes and structs. If set to YES the  # generated at the bottom of the documentation of classes and
274  # list will mention the files that were used to generate the documentation.  # structs. If set to YES the list will mention the files that were
275    # used to generate the documentation.
276    
277  SHOW_USED_FILES        = YES  SHOW_USED_FILES        = YES
278    
# Line 277  Line 280 
280  # configuration options related to warning and progress messages  # configuration options related to warning and progress messages
281  #---------------------------------------------------------------------------  #---------------------------------------------------------------------------
282    
283  # The QUIET tag can be used to turn on/off the messages that are generated  # The QUIET tag can be used to turn on/off the messages that are
284  # by doxygen. Possible values are YES and NO. If left blank NO is used.  # generated by doxygen. Possible values are YES and NO. If left blank
285    # NO is used.
286    
287  QUIET                  = NO  QUIET                  = NO
288    
289  # The WARNINGS tag can be used to turn on/off the warning messages that are  # The WARNINGS tag can be used to turn on/off the warning messages
290  # generated by doxygen. Possible values are YES and NO. If left blank  # that are generated by doxygen. Possible values are YES and NO. If
291  # NO is used.  # left blank NO is used.
292    
293  WARNINGS               = YES  WARNINGS               = YES
294    
295  # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings  # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate
296  # for undocumented members. If EXTRACT_ALL is set to YES then this flag will  # warnings for undocumented members. If EXTRACT_ALL is set to YES then
297  # automatically be disabled.  # this flag will automatically be disabled.
298    
299  WARN_IF_UNDOCUMENTED   = YES  WARN_IF_UNDOCUMENTED   = YES
300    
301  # The WARN_FORMAT tag determines the format of the warning messages that  # The WARN_FORMAT tag determines the format of the warning messages
302  # doxygen can produce. The string should contain the $file, $line, and $text  # that doxygen can produce. The string should contain the $file,
303  # tags, which will be replaced by the file and line number from which the  # $line, and $text tags, which will be replaced by the file and line
304  # warning originated and the warning text.  # number from which the warning originated and the warning text.
305    
306  WARN_FORMAT            = "$file:$line: $text"  WARN_FORMAT            = "$file:$line: $text"
307    
308  # The WARN_LOGFILE tag can be used to specify a file to which warning  # The WARN_LOGFILE tag can be used to specify a file to which warning
309  # and error messages should be written. If left blank the output is written  # and error messages should be written. If left blank the output is
310  # to stderr.  # written to stderr.
311    
312  WARN_LOGFILE           =  WARN_LOGFILE           =
313    
# Line 311  Line 315 
315  # configuration options related to the input files  # configuration options related to the input files
316  #---------------------------------------------------------------------------  #---------------------------------------------------------------------------
317    
318  # The INPUT tag can be used to specify the files and/or directories that contain  # The INPUT tag can be used to specify the files and/or directories
319  # documented source files. You may enter file names like "myfile.cpp" or  # that contain documented source files. You may enter file names like
320  # directories like "/usr/src/myproject". Separate the files or directories  # "myfile.cpp" or directories like "/usr/src/myproject". Separate the
321  # with spaces.  # files or directories with spaces.
322    
323  INPUT                  = src  INPUT                  = src
324    
325  # If the value of the INPUT tag contains directories, you can use the  # If the value of the INPUT tag contains directories, you can use the
326  # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp  # FILE_PATTERNS tag to specify one or more wildcard pattern (like
327  # and *.h) to filter out the source-files in the directories. If left  # *.cpp and *.h) to filter out the source-files in the directories. If
328  # blank the following patterns are tested:  # left blank the following patterns are tested: *.c *.cc *.cxx *.cpp
329  # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp  # *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp *.h++
330  # *.h++ *.idl *.odl  # *.idl *.odl
331    
332  FILE_PATTERNS          = *.c *.h  FILE_PATTERNS          = *.c *.h
333    
334  # The RECURSIVE tag can be used to turn specify whether or not subdirectories  # The RECURSIVE tag can be used to turn specify whether or not
335  # should be searched for input files as well. Possible values are YES and NO.  # subdirectories should be searched for input files as well. Possible
336  # If left blank NO is used.  # values are YES and NO.  If left blank NO is used.
337    
338  RECURSIVE              = NO  RECURSIVE              = NO
339    
340  # The EXCLUDE tag can be used to specify files and/or directories that should  # The EXCLUDE tag can be used to specify files and/or directories that
341  # excluded from the INPUT source files. This way you can easily exclude a  # should excluded from the INPUT source files. This way you can easily
342  # subdirectory from a directory tree whose root is specified with the INPUT tag.  # exclude a subdirectory from a directory tree whose root is specified
343    # with the INPUT tag.
344    
345  EXCLUDE                =  EXCLUDE                =
346    
347  # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories  # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
348  # that are symbolic links (a Unix filesystem feature) are excluded from the input.  # directories that are symbolic links (a Unix filesystem feature) are
349    # excluded from the input.
350    
351  EXCLUDE_SYMLINKS       = NO  EXCLUDE_SYMLINKS       = NO
352    
353  # If the value of the INPUT tag contains directories, you can use the  # If the value of the INPUT tag contains directories, you can use the
354  # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude  # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to
355  # certain files from those directories.  # exclude certain files from those directories.
356    
357  EXCLUDE_PATTERNS       =  EXCLUDE_PATTERNS       =
358    
359  # The EXAMPLE_PATH tag can be used to specify one or more files or  # The EXAMPLE_PATH tag can be used to specify one or more files or
360  # directories that contain example code fragments that are included (see  # directories that contain example code fragments that are included
361  # the \include command).  # (see the \include command).
362    
363  EXAMPLE_PATH           =  EXAMPLE_PATH           =
364    
365  # If the value of the EXAMPLE_PATH tag contains directories, you can use the  # If the value of the EXAMPLE_PATH tag contains directories, you can
366  # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp  # use the EXAMPLE_PATTERNS tag to specify one or more wildcard pattern
367  # and *.h) to filter out the source-files in the directories. If left  # (like *.cpp and *.h) to filter out the source-files in the
368  # blank all files are included.  # directories. If left blank all files are included.
369    
370  EXAMPLE_PATTERNS       =  EXAMPLE_PATTERNS       =
371    
372  # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be  # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will
373  # searched for input files to be used with the \include or \dontinclude  # be searched for input files to be used with the \include or
374  # commands irrespective of the value of the RECURSIVE tag.  # \dontinclude commands irrespective of the value of the RECURSIVE
375  # Possible values are YES and NO. If left blank NO is used.  # tag.  Possible values are YES and NO. If left blank NO is used.
376    
377  EXAMPLE_RECURSIVE      = NO  EXAMPLE_RECURSIVE      = NO
378    
379  # The IMAGE_PATH tag can be used to specify one or more files or  # The IMAGE_PATH tag can be used to specify one or more files or
380  # directories that contain image that are included in the documentation (see  # directories that contain image that are included in the
381  # the \image command).  # documentation (see the \image command).
382    
383  IMAGE_PATH             =  IMAGE_PATH             =
384    
385  # The INPUT_FILTER tag can be used to specify a program that doxygen should  # The INPUT_FILTER tag can be used to specify a program that doxygen
386  # invoke to filter for each input file. Doxygen will invoke the filter program  # should invoke to filter for each input file. Doxygen will invoke the
387  # by executing (via popen()) the command <filter> <input-file>, where <filter>  # filter program by executing (via popen()) the command <filter>
388  # is the value of the INPUT_FILTER tag, and <input-file> is the name of an  # <input-file>, where <filter> is the value of the INPUT_FILTER tag,
389  # input file. Doxygen will then use the output that the filter program writes  # and <input-file> is the name of an input file. Doxygen will then use
390  # to standard output.  # the output that the filter program writes to standard output.
391    
392  INPUT_FILTER           =  INPUT_FILTER           =
393    
394  # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using  # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if
395  # INPUT_FILTER) will be used to filter the input files when producing source  # set using INPUT_FILTER) will be used to filter the input files when
396  # files to browse.  # producing source files to browse.
397    
398  FILTER_SOURCE_FILES    = NO  FILTER_SOURCE_FILES    = NO
399    
# Line 395  Line 401 
401  # configuration options related to source browsing  # configuration options related to source browsing
402  #---------------------------------------------------------------------------  #---------------------------------------------------------------------------
403    
404  # If the SOURCE_BROWSER tag is set to YES then a list of source files will  # If the SOURCE_BROWSER tag is set to YES then a list of source files
405  # be generated. Documented entities will be cross-referenced with these sources.  # will be generated. Documented entities will be cross-referenced with
406    # these sources.
407    
408  SOURCE_BROWSER         = NO  SOURCE_BROWSER         = NO
409    
410  # Setting the INLINE_SOURCES tag to YES will include the body  # Setting the INLINE_SOURCES tag to YES will include the body of
411  # of functions and classes directly in the documentation.  # functions and classes directly in the documentation.
412    
413  INLINE_SOURCES         = NO  INLINE_SOURCES         = NO
414    
415  # If the REFERENCED_BY_RELATION tag is set to YES (the default)  # If the REFERENCED_BY_RELATION tag is set to YES (the default) then
416  # then for each documented function all documented  # for each documented function all documented functions referencing it
417  # functions referencing it will be listed.  # will be listed.
418    
419  REFERENCED_BY_RELATION = YES  REFERENCED_BY_RELATION = YES
420    
421  # If the REFERENCES_RELATION tag is set to YES (the default)  # If the REFERENCES_RELATION tag is set to YES (the default) then for
422  # then for each documented function all documented entities  # each documented function all documented entities called/used by that
423  # called/used by that function will be listed.  # function will be listed.
424    
425  REFERENCES_RELATION    = YES  REFERENCES_RELATION    = YES
426    
# Line 435  Line 442 
442    
443  # In case all classes in a project start with a common prefix, all  # In case all classes in a project start with a common prefix, all
444  # classes will be put under the same header in the alphabetical index.  # classes will be put under the same header in the alphabetical index.
445  # The IGNORE_PREFIX tag can be used to specify one or more prefixes that  # The IGNORE_PREFIX tag can be used to specify one or more prefixes
446  # should be ignored while generating the index headers.  # that should be ignored while generating the index headers.
447    
448  IGNORE_PREFIX          =  IGNORE_PREFIX          =
449    
# Line 522  Line 529 
529  ENUM_VALUES_PER_LINE   = 4  ENUM_VALUES_PER_LINE   = 4
530    
531  # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be  # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
532  # generated containing a tree-like index structure (just like the one that  # generated containing a tree-like index structure (just like the one
533  # is generated for HTML Help). For this to work a browser that supports  # that is generated for HTML Help). For this to work a browser that
534  # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+,  # supports JavaScript and frames is required (for instance Mozilla,
535  # or Internet explorer 4.0+). Note that for large projects the tree generation  # Netscape 4.0+, or Internet explorer 4.0+). Note that for large
536  # can take a very long time. In such cases it is better to disable this feature.  # projects the tree generation can take a very long time. In such
537  # Windows users are probably better off using the HTML help feature.  # cases it is better to disable this feature.  Windows users are
538    # probably better off using the HTML help feature.
539    
540  GENERATE_TREEVIEW      = NO  GENERATE_TREEVIEW      = NO
541    
# Line 749  Line 757 
757    
758  PREDEFINED             =  PREDEFINED             =
759    
760  # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then  # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES
761  # this tag can be used to specify a list of macro names that should be expanded.  # then this tag can be used to specify a list of macro names that
762  # The macro definition that is found in the sources will be used.  # should be expanded.  The macro definition that is found in the
763  # Use the PREDEFINED tag if you want to use a different macro definition.  # sources will be used.  Use the PREDEFINED tag if you want to use a
764    # different macro definition.
765    
766  EXPAND_AS_DEFINED      = F77_NAME F77_CALL  EXPAND_AS_DEFINED      = F77_NAME F77_CALL
767    
768  # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then  # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
769  # doxygen's preprocessor will remove all function-like macros that are alone  # doxygen's preprocessor will remove all function-like macros that are
770  # on a line and do not end with a semicolon. Such function macros are typically  # alone on a line and do not end with a semicolon. Such function
771  # used for boiler-plate code, and will confuse the parser if not removed.  # macros are typically used for boiler-plate code, and will confuse
772    # the parser if not removed.
773    
774  SKIP_FUNCTION_MACROS   = YES  SKIP_FUNCTION_MACROS   = YES
775    
# Line 771  Line 781 
781    
782  TAGFILES               =  TAGFILES               =
783    
784  # When a file name is specified after GENERATE_TAGFILE, doxygen will create  # When a file name is specified after GENERATE_TAGFILE, doxygen will
785  # a tag file that is based on the input files it reads.  # create a tag file that is based on the input files it reads.
786    
787  GENERATE_TAGFILE       =  GENERATE_TAGFILE       =
788    
789  # If the ALLEXTERNALS tag is set to YES all external classes will be listed  # If the ALLEXTERNALS tag is set to YES all external classes will be
790  # in the class index. If set to NO only the inherited external classes  # listed in the class index. If set to NO only the inherited external
791  # will be listed.  # classes will be listed.
792    
793  ALLEXTERNALS           = NO  ALLEXTERNALS           = NO
794    
795  # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed  # If the EXTERNAL_GROUPS tag is set to YES all external groups will be
796  # in the modules index. If set to NO, only the current project's groups will  # listed in the modules index. If set to NO, only the current
797  # be listed.  # project's groups will be listed.
798    
799  EXTERNAL_GROUPS        = YES  EXTERNAL_GROUPS        = YES
800    
# Line 798  Line 808 
808  #---------------------------------------------------------------------------  #---------------------------------------------------------------------------
809    
810  # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will  # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
811  # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or  # generate a inheritance diagram (in Html, RTF and LaTeX) for classes
812  # super classes. Setting the tag to NO turns the diagrams off. Note that this  # with base or super classes. Setting the tag to NO turns the diagrams
813  # option is superceded by the HAVE_DOT option below. This is only a fallback. It is  # off. Note that this option is superceded by the HAVE_DOT option
814  # recommended to install and use dot, since it yield more powerful graphs.  # below. This is only a fallback. It is recommended to install and use
815    # dot, since it yield more powerful graphs.
816    
817  CLASS_DIAGRAMS         = YES  CLASS_DIAGRAMS         = YES
818    
# Line 811  Line 822 
822    
823  HIDE_UNDOC_RELATIONS   = YES  HIDE_UNDOC_RELATIONS   = YES
824    
825  # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is  # If you set the HAVE_DOT tag to YES then doxygen will assume the dot
826  # available from the path. This tool is part of Graphviz, a graph visualization  # tool is available from the path. This tool is part of Graphviz, a
827  # toolkit from AT&T and Lucent Bell Labs. The other options in this section  # graph visualization toolkit from AT&T and Lucent Bell Labs. The
828  # have no effect if this option is set to NO (the default)  # other options in this section have no effect if this option is set
829    # to NO (the default)
830    
831  HAVE_DOT               = NO  HAVE_DOT               = NO
832    
# Line 825  Line 837 
837    
838  CLASS_GRAPH            = YES  CLASS_GRAPH            = YES
839    
840  # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen  # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then
841  # will generate a graph for each documented class showing the direct and  # doxygen will generate a graph for each documented class showing the
842  # indirect implementation dependencies (inheritance, containment, and  # direct and indirect implementation dependencies (inheritance,
843  # class references variables) of the class with other documented classes.  # containment, and class references variables) of the class with other
844    # documented classes.
845    
846  COLLABORATION_GRAPH    = YES  COLLABORATION_GRAPH    = YES
847    
# Line 873  Line 886 
886    
887  DOTFILE_DIRS           =  DOTFILE_DIRS           =
888    
889  # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width  # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed
890  # (in pixels) of the graphs generated by dot. If a graph becomes larger than  # width (in pixels) of the graphs generated by dot. If a graph becomes
891  # this value, doxygen will try to truncate the graph, so that it fits within  # larger than this value, doxygen will try to truncate the graph, so
892  # the specified constraint. Beware that most browsers cannot cope with very  # that it fits within the specified constraint. Beware that most
893  # large images.  # browsers cannot cope with very large images.
894    
895  MAX_DOT_GRAPH_WIDTH    = 1024  MAX_DOT_GRAPH_WIDTH    = 1024
896    
897  # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height  # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows
898  # (in pixels) of the graphs generated by dot. If a graph becomes larger than  # height (in pixels) of the graphs generated by dot. If a graph
899  # this value, doxygen will try to truncate the graph, so that it fits within  # becomes larger than this value, doxygen will try to truncate the
900  # the specified constraint. Beware that most browsers cannot cope with very  # graph, so that it fits within the specified constraint. Beware that
901  # large images.  # most browsers cannot cope with very large images.
902    
903  MAX_DOT_GRAPH_HEIGHT   = 1024  MAX_DOT_GRAPH_HEIGHT   = 1024
904    
905  # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will  # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
906  # generate a legend page explaining the meaning of the various boxes and  # generate a legend page explaining the meaning of the various boxes
907  # arrows in the dot generated graphs.  # and arrows in the dot generated graphs.
908    
909  GENERATE_LEGEND        = YES  GENERATE_LEGEND        = YES
910    
911  # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will  # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
912  # remove the intermedate dot files that are used to generate  # remove the intermedate dot files that are used to generate the
913  # the various graphs.  # various graphs.
914    
915  DOT_CLEANUP            = YES  DOT_CLEANUP            = YES
916    

Legend:
Removed from v.188  
changed lines
  Added in v.189

root@r-forge.r-project.org
ViewVC Help
Powered by ViewVC 1.0.0  
Thanks to:
Vienna University of Economics and Business Powered By FusionForge