3 @INCLUDE = Doxyfile-common
5 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
6 # base path where the generated documentation will be put.
7 # If a relative path is entered, it will be relative to the location
8 # where doxygen was started. If left blank the current directory will be used.
10 OUTPUT_DIRECTORY = doc/reference
12 # If the value of the INPUT tag contains directories, you can use the
13 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
14 # and *.h) to filter out the source-files in the directories. If left
15 # blank the following patterns are tested:
16 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
17 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
23 # The HTML_HEADER tag can be used to specify a personal HTML header for
24 # each generated HTML page. If it is left blank doxygen will generate a
27 HTML_HEADER = doc/TracHeader.html
29 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
30 # will be generated that can be used as input for tools like the
31 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
32 # of the generated HTML documentation.
34 GENERATE_HTMLHELP = NO
36 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
37 # be used to specify the file name of the resulting .chm file. You
38 # can add a path in front of the file if the result should not be
39 # written to the html output directory.