# 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
# if some version control system is used.\r
\r
-PROJECT_NUMBER = 090401\r
+PROJECT_NUMBER = 000000\r
\r
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) \r
# base path where the generated documentation will be put. \r
# source files, where putting all generated files in the same directory would \r
# otherwise cause performance problems for the file system.\r
\r
-CREATE_SUBDIRS = YES\r
+CREATE_SUBDIRS = NO\r
\r
# The OUTPUT_LANGUAGE tag is used to specify the language in which all \r
# documentation generated by doxygen is written. Doxygen will use this \r
# be useful for C code in case the coding convention dictates that all compound \r
# types are typedef'ed and only the typedef is referenced, never the tag name.\r
\r
-TYPEDEF_HIDES_STRUCT = NO\r
+TYPEDEF_HIDES_STRUCT = YES\r
\r
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to \r
# determine which symbols to keep in memory and which to flush to disk.\r
# hierarchy of group names into alphabetical order. If set to NO (the default) \r
# the group names will appear in their defined order.\r
\r
-SORT_GROUP_NAMES = NO\r
+SORT_GROUP_NAMES = YES\r
\r
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be \r
# sorted by fully-qualified names, including namespaces. If set to \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
# against the file with absolute path, so to exclude all test directories \r
# for example use the pattern */test/*\r
\r
-EXCLUDE_PATTERNS = */LowLevel/USBMode.h\r
+EXCLUDE_PATTERNS = \r
\r
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names \r
# (namespaces, classes, functions, etc.) that should be excluded from the \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
# used to set the initial width (in pixels) of the frame in which the tree \r
# is shown.\r
\r
-TREEVIEW_WIDTH = 250\r
+TREEVIEW_WIDTH = 300\r
\r
# Use this tag to change the font size of Latex formulas included \r
# as images in the HTML documentation. The default is 10. Note that \r
# The macro definition that is found in the sources will be used. \r
# Use the PREDEFINED tag if you want to use a different macro definition.\r
\r
-EXPAND_AS_DEFINED = BUTTLOADTAG\r
+EXPAND_AS_DEFINED = _CALLBACK_PARAM\r
\r
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then \r
# doxygen's preprocessor will remove all function-like macros that are alone \r
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen \r
# will generate a graph for groups, showing the direct groups dependencies\r
\r
-GROUP_GRAPHS = NO\r
+GROUP_GRAPHS = YES\r
\r
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and \r
# collaboration diagrams in a style similar to the OMG's Unified Modeling \r
# file showing the direct and indirect include dependencies of the file with \r
# other documented files.\r
\r
-INCLUDE_GRAPH = NO\r
+INCLUDE_GRAPH = YES\r
\r
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and \r
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each \r
# documented header file showing the documented files that directly or \r
# indirectly include this file.\r
\r
-INCLUDED_BY_GRAPH = NO\r
+INCLUDED_BY_GRAPH = YES\r
\r
# If the CALL_GRAPH and HAVE_DOT options are set to YES then \r
# doxygen will generate a call dependency graph for every global function \r
# in a graphical way. The dependency relations are determined by the #include\r
# relations between the files in the directories.\r
\r
-DIRECTORY_GRAPH = NO\r
+DIRECTORY_GRAPH = YES\r
\r
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images \r
# generated by dot. Possible values are png, jpg, or gif\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
projects / pub / lufa.git / blobdiff