# The PROJECT_NAME tag is a single word (or a sequence of words surrounded \r
# by quotes) that should identify the project.\r
\r
-PROJECT_NAME = "LUFA Library"\r
+PROJECT_NAME = "LUFA (Formerly MyUSB) Library"\r
\r
# The PROJECT_NUMBER tag can be used to enter a project or revision number. \r
# This could be handy for archiving the generated documentation or \r
# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90\r
\r
FILE_PATTERNS = *.h \\r
- *.c \\r
*.txt\r
\r
# The RECURSIVE tag can be used to turn specify whether or not subdirectories \r
# excluded from the INPUT source files. This way you can easily exclude a \r
# subdirectory from a directory tree whose root is specified with the INPUT tag.\r
\r
-EXCLUDE = \r
+EXCLUDE = Documentation/\r
\r
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or \r
# directories that are symbolic links (a Unix filesystem feature) are excluded \r
# wildcard * is used, a substring. Examples: ANamespace, AClass, \r
# AClass::ANamespace, ANamespace::*Test\r
\r
-EXCLUDE_SYMBOLS = __*\r
+EXCLUDE_SYMBOLS = __* INCLUDE_FROM_*\r
\r
# The EXAMPLE_PATH tag can be used to specify one or more files or \r
# directories that contain example code fragments that are included (see \r
# directories that contain image that are included in the documentation (see \r
# the \image command).\r
\r
-IMAGE_PATH = \r
+IMAGE_PATH = ./\r
\r
# The INPUT_FILTER tag can be used to specify a program that doxygen should \r
# invoke to filter for each input file. Doxygen will invoke the filter program \r
# The tag DOT_PATH can be used to specify the path where the dot tool can be \r
# found. If left blank, it is assumed the dot tool can be found in the path.\r
\r
-DOT_PATH = "C:/Program Files/Graphviz2.18/bin"\r
+DOT_PATH = \r
\r
# The DOTFILE_DIRS tag can be used to specify one or more directories that \r
# contain dot files that are included in the documentation (see the \r