Fixed V2 Protocol READ_FLASH_ISP and READ_EEPROM_ISP handler code in the AVRISP project.

[pub/lufa.git] / LUFA / Doxygen.conf

diff --git a/LUFA/Doxygen.conf b/LUFA/Doxygen.conf
index 6422c21..260340c 100644 (file)
--- a/LUFA/Doxygen.conf
+++ b/LUFA/Doxygen.conf
@@ -47,7 +47,7 @@ OUTPUT_DIRECTORY       = ./Documentation/
 # 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
@@ -269,7 +269,7 @@ SUBGROUPING            = YES
 # 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
@@ -640,7 +640,7 @@ EXAMPLE_RECURSIVE      = NO
 # 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
@@ -1227,7 +1227,7 @@ PREDEFINED             = __DOXYGEN__
 # 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      = \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
@@ -1388,7 +1388,7 @@ INCLUDED_BY_GRAPH      = YES
 # the time of a run. So in most cases it will be better to enable call graphs \r
 # for selected functions only using the \callgraph command.\r
 \r
-CALL_GRAPH             = YES\r
+CALL_GRAPH             = NO\r
 \r
 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then \r
 # doxygen will generate a caller dependency graph for every global function \r
@@ -1419,7 +1419,7 @@ DOT_IMAGE_FORMAT       = png
 # 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