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