Upgrade to latest Doxygen.
This commit is contained in:
		
							parent
							
								
									a532f2ad1b
								
							
						
					
					
						commit
						57ef7a79b4
					
				
					 79 changed files with 2686 additions and 2133 deletions
				
			
		| 
						 | 
				
			
			@ -1,4 +1,4 @@
 | 
			
		|||
# Doxyfile 1.8.6
 | 
			
		||||
# Doxyfile 1.8.7
 | 
			
		||||
 | 
			
		||||
# This file describes the settings to be used by the documentation system
 | 
			
		||||
# doxygen (www.doxygen.org) for a project.
 | 
			
		||||
| 
						 | 
				
			
			@ -70,6 +70,14 @@ OUTPUT_DIRECTORY       = ./Documentation/
 | 
			
		|||
 | 
			
		||||
CREATE_SUBDIRS         = NO
 | 
			
		||||
 | 
			
		||||
# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
 | 
			
		||||
# characters to appear in the names of generated files. If set to NO, non-ASCII
 | 
			
		||||
# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
 | 
			
		||||
# U+3044.
 | 
			
		||||
# The default value is: NO.
 | 
			
		||||
 | 
			
		||||
ALLOW_UNICODE_NAMES    = NO
 | 
			
		||||
 | 
			
		||||
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
 | 
			
		||||
# documentation generated by doxygen is written. Doxygen will use this
 | 
			
		||||
# information to generate all constant output in the proper language.
 | 
			
		||||
| 
						 | 
				
			
			@ -271,9 +279,12 @@ OPTIMIZE_OUTPUT_VHDL   = NO
 | 
			
		|||
# extension. Doxygen has a built-in mapping, but you can override or extend it
 | 
			
		||||
# using this tag. The format is ext=language, where ext is a file extension, and
 | 
			
		||||
# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
 | 
			
		||||
# C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
 | 
			
		||||
# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
 | 
			
		||||
# (default is Fortran), use: inc=Fortran f=C.
 | 
			
		||||
# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
 | 
			
		||||
# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
 | 
			
		||||
# Fortran. In the later case the parser tries to guess whether the code is fixed
 | 
			
		||||
# or free formatted code, this is the default for Fortran type files), VHDL. For
 | 
			
		||||
# instance to make doxygen treat .inc files as Fortran files (default is PHP),
 | 
			
		||||
# and .f files as C (default is Fortran), use: inc=Fortran f=C.
 | 
			
		||||
#
 | 
			
		||||
# Note For files without extension you can use no_extension as a placeholder.
 | 
			
		||||
#
 | 
			
		||||
| 
						 | 
				
			
			@ -981,7 +992,7 @@ USE_HTAGS              = NO
 | 
			
		|||
VERBATIM_HEADERS       = NO
 | 
			
		||||
 | 
			
		||||
# If the CLANG_ASSISTED_PARSING tag is set to YES, then doxygen will use the
 | 
			
		||||
# clang parser (see: http://clang.llvm.org/) for more acurate parsing at the
 | 
			
		||||
# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the
 | 
			
		||||
# cost of reduced performance. This can be particularly helpful with template
 | 
			
		||||
# rich C++ code for which doxygen's built-in parser lacks the necessary type
 | 
			
		||||
# information.
 | 
			
		||||
| 
						 | 
				
			
			@ -1262,7 +1273,8 @@ GENERATE_CHI           = NO
 | 
			
		|||
CHM_INDEX_ENCODING     =
 | 
			
		||||
 | 
			
		||||
# The BINARY_TOC flag controls whether a binary table of contents is generated (
 | 
			
		||||
# YES) or a normal table of contents ( NO) in the .chm file.
 | 
			
		||||
# YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
 | 
			
		||||
# enables the Previous and Next buttons.
 | 
			
		||||
# The default value is: NO.
 | 
			
		||||
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			@ -1502,11 +1514,11 @@ SEARCHENGINE           = NO
 | 
			
		|||
 | 
			
		||||
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
 | 
			
		||||
# implemented using a web server instead of a web client using Javascript. There
 | 
			
		||||
# are two flavours of web server based searching depending on the
 | 
			
		||||
# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
 | 
			
		||||
# searching and an index file used by the script. When EXTERNAL_SEARCH is
 | 
			
		||||
# enabled the indexing and searching needs to be provided by external tools. See
 | 
			
		||||
# the section "External Indexing and Searching" for details.
 | 
			
		||||
# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
 | 
			
		||||
# setting. When disabled, doxygen will generate a PHP script for searching and
 | 
			
		||||
# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
 | 
			
		||||
# and searching needs to be provided by external tools. See the section
 | 
			
		||||
# "External Indexing and Searching" for details.
 | 
			
		||||
# The default value is: NO.
 | 
			
		||||
# This tag requires that the tag SEARCHENGINE is set to YES.
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			@ -1794,6 +1806,13 @@ MAN_OUTPUT             = man
 | 
			
		|||
 | 
			
		||||
MAN_EXTENSION          = .3
 | 
			
		||||
 | 
			
		||||
# The MAN_SUBDIR tag determines the name of the directory created within
 | 
			
		||||
# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
 | 
			
		||||
# MAN_EXTENSION with the initial . removed.
 | 
			
		||||
# This tag requires that the tag GENERATE_MAN is set to YES.
 | 
			
		||||
 | 
			
		||||
MAN_SUBDIR             =
 | 
			
		||||
 | 
			
		||||
# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
 | 
			
		||||
# will generate one additional man file for each entity documented in the real
 | 
			
		||||
# man page(s). These additional files only source the real man page, but without
 | 
			
		||||
| 
						 | 
				
			
			@ -1821,18 +1840,6 @@ GENERATE_XML           = NO
 | 
			
		|||
 | 
			
		||||
XML_OUTPUT             = xml
 | 
			
		||||
 | 
			
		||||
# The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a
 | 
			
		||||
# validating XML parser to check the syntax of the XML files.
 | 
			
		||||
# This tag requires that the tag GENERATE_XML is set to YES.
 | 
			
		||||
 | 
			
		||||
XML_SCHEMA             =
 | 
			
		||||
 | 
			
		||||
# The XML_DTD tag can be used to specify a XML DTD, which can be used by a
 | 
			
		||||
# validating XML parser to check the syntax of the XML files.
 | 
			
		||||
# This tag requires that the tag GENERATE_XML is set to YES.
 | 
			
		||||
 | 
			
		||||
XML_DTD                =
 | 
			
		||||
 | 
			
		||||
# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
 | 
			
		||||
# listings (including syntax highlighting and cross-referencing information) to
 | 
			
		||||
# the XML output. Note that enabling this will significantly increase the size
 | 
			
		||||
| 
						 | 
				
			
			@ -1980,9 +1987,9 @@ PREDEFINED             = __DOXYGEN__ \
 | 
			
		|||
EXPAND_AS_DEFINED      =
 | 
			
		||||
 | 
			
		||||
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
 | 
			
		||||
# remove all refrences to function-like macros that are alone on a line, have an
 | 
			
		||||
# all uppercase name, and do not end with a semicolon. Such function macros are
 | 
			
		||||
# typically used for boiler-plate code, and will confuse the parser if not
 | 
			
		||||
# remove all references to function-like macros that are alone on a line, have
 | 
			
		||||
# an all uppercase name, and do not end with a semicolon. Such function macros
 | 
			
		||||
# are typically used for boiler-plate code, and will confuse the parser if not
 | 
			
		||||
# removed.
 | 
			
		||||
# The default value is: YES.
 | 
			
		||||
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 | 
			
		||||
| 
						 | 
				
			
			@ -2002,7 +2009,7 @@ SKIP_FUNCTION_MACROS   = YES
 | 
			
		|||
# where loc1 and loc2 can be relative or absolute paths or URLs. See the
 | 
			
		||||
# section "Linking to external documentation" for more information about the use
 | 
			
		||||
# of tag files.
 | 
			
		||||
# Note: Each tag file must have an unique name (where the name does NOT include
 | 
			
		||||
# Note: Each tag file must have a unique name (where the name does NOT include
 | 
			
		||||
# the path). If a tag file is not located in the directory in which doxygen is
 | 
			
		||||
# run, you must also specify the path to the tagfile here.
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue