Remove documentation of deleted parameters from the RNDIS Host Class driver's device...

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

diff --git a/LUFA/Doxygen.conf b/LUFA/Doxygen.conf
index 136a723..3aafe6a 100644 (file)
--- a/LUFA/Doxygen.conf
+++ b/LUFA/Doxygen.conf
@@ -25,7 +25,7 @@ DOXYFILE_ENCODING      = UTF-8
 # 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
@@ -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
@@ -580,7 +580,6 @@ INPUT_ENCODING         = UTF-8
 # *.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
@@ -593,7 +592,7 @@ RECURSIVE              = YES
 # 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
@@ -615,7 +614,7 @@ EXCLUDE_PATTERNS       =
 # 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
@@ -641,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
@@ -1228,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
@@ -1389,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
@@ -1420,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
@@ -1482,4 +1481,4 @@ DOT_CLEANUP            = YES
 # The SEARCHENGINE tag specifies whether or not a search engine should be \r
 # used. If set to NO the values of all tags below this one will be ignored.\r
 \r
-SEARCHENGINE           = NO\r
+SEARCHENGINE           = YES\r