mirror of
				https://github.com/mfulz/qmk_firmware.git
				synced 2025-10-31 05:12:33 +01:00 
			
		
		
		
	Upgrade Doxygen configuration files, custom style CSS and DOXYGEN build module for the latest Doxygen release.
This commit is contained in:
		
							parent
							
								
									63fb35f319
								
							
						
					
					
						commit
						94f5f31f10
					
				| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -908,13 +914,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -999,9 +1015,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -54,7 +54,7 @@ ERROR_IF_NONBOOL ?= $(if $(filter Y N, $($(strip $(1)))), , $(error Makefile $(s | ||||
| # Default values of optionally user-supplied variables
 | ||||
| DOXYGEN_CONF            ?= Doxygen.conf | ||||
| DOXYGEN_FAIL_ON_WARNING ?= Y | ||||
| DOXYGEN_OVERRIDE_PARAMS ?= QUIET=YES HTML_STYLESHEET=$(patsubst %/,%,$(LUFA_PATH))/DoxygenPages/Style/Style.css | ||||
| DOXYGEN_OVERRIDE_PARAMS ?= QUIET=YES HTML_EXTRA_STYLESHEET=$(patsubst %/,%,$(LUFA_PATH))/DoxygenPages/Style/Style.css | ||||
| 
 | ||||
| # Sanity check user supplied values
 | ||||
| $(foreach MANDATORY_VAR, $(LUFA_BUILD_MANDATORY_VARS), $(call ERROR_IF_UNSET, $(MANDATORY_VAR))) | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -908,12 +914,22 @@ HTML_FOOTER            = ./DoxygenPages/Style/Footer.htm | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = ./DoxygenPages/Style/Style.css | ||||
| HTML_STYLESHEET        =  | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = ./DoxygenPages/Style/Style.css | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| @ -999,9 +1015,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = com.lufa-lib.library.documentation | ||||
| 
 | ||||
|  | ||||
| @ -86,7 +86,7 @@ | ||||
|  *  \li Music Playing Alarm Clock (Tutorial): http://www.instructables.com/id/Music-Playing-Alarm-Clock/ | ||||
|  *  \li Nehebkau, Laptop Controlled Keyboard and Mouse: http://www.frank-zhao.com/cache/nehebkau.php | ||||
|  *  \li NeroJTAG, a JTAG dongle: https://github.com/makestuff/neroJtag | ||||
|  *  \li NES Controller USB modification: http://projects.peterpolidoro.net/video/NESUSB.htm | ||||
|  *  \li NES Controller USB modification: https://github.com/nfd/nes_adapter | ||||
|  *  \li Nikon wireless camera remote control (Norwegian): http://hekta.org/~hpe1119/ | ||||
|  *  \li Opendous-JTAG, an open source ARM JTAG debugger: http://code.google.com/p/opendous-jtag/ | ||||
|  *  \li Openkubus, an open source hardware-based authentication dongle: http://code.google.com/p/openkubus/ | ||||
|  | ||||
										
											
												File diff suppressed because it is too large
												Load Diff
											
										
									
								
							| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -910,13 +916,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -1001,9 +1017,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -908,13 +914,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -999,9 +1015,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -908,13 +914,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -999,9 +1015,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
| @ -1,4 +1,4 @@ | ||||
| # Doxyfile 1.8.1.2 | ||||
| # Doxyfile 1.8.2 | ||||
| 
 | ||||
| # This file describes the settings to be used by the documentation system | ||||
| # doxygen (www.doxygen.org) for a project. | ||||
| @ -136,7 +136,9 @@ FULL_PATH_NAMES        = YES | ||||
| # only done if one of the specified strings matches the left-hand part of | ||||
| # the path. The tag can be used to show relative paths in the file list. | ||||
| # If left blank the directory from which doxygen is run is used as the | ||||
| # path to strip. | ||||
| # path to strip. Note that you specify absolute paths here, but also | ||||
| # relative paths, which will be relative from the directory where doxygen is | ||||
| # started. | ||||
| 
 | ||||
| STRIP_FROM_PATH        = | ||||
| 
 | ||||
| @ -239,14 +241,15 @@ OPTIMIZE_FOR_FORTRAN   = NO | ||||
| OPTIMIZE_OUTPUT_VHDL   = NO | ||||
| 
 | ||||
| # Doxygen selects the parser to use depending on the extension of the files it | ||||
| # parses. With this tag you can assign which parser to use for a given 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, CSharp, C, | ||||
| # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions | ||||
| # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. | ||||
| # parses. With this tag you can assign which parser to use for a given | ||||
| # 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, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, | ||||
| # C++. 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 | ||||
| # that for custom extensions you also need to set FILE_PATTERNS otherwise the | ||||
| # files are not read by doxygen. | ||||
| 
 | ||||
| EXTENSION_MAPPING      = | ||||
| 
 | ||||
| @ -259,6 +262,13 @@ EXTENSION_MAPPING      = | ||||
| 
 | ||||
| MARKDOWN_SUPPORT       = NO | ||||
| 
 | ||||
| # When enabled doxygen tries to link words that correspond to documented classes, | ||||
| # or namespaces to their corresponding documentation. Such a link can be | ||||
| # prevented in individual cases by by putting a % sign in front of the word or | ||||
| # globally by setting AUTOLINK_SUPPORT to NO. | ||||
| 
 | ||||
| AUTOLINK_SUPPORT       = YES | ||||
| 
 | ||||
| # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want | ||||
| # to include (a tag file for) the STL sources as input, then you should | ||||
| # set this tag to YES in order to let doxygen match functions declarations and | ||||
| @ -279,12 +289,7 @@ CPP_CLI_SUPPORT        = NO | ||||
| 
 | ||||
| SIP_SUPPORT            = NO | ||||
| 
 | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter | ||||
| # and setter methods for a property. Setting this option to YES (the default) | ||||
| # will make doxygen replace the get and set methods by a property in the | ||||
| # documentation. This will only work if the methods are indeed getting or | ||||
| # setting a simple type. If this is not the case, or you want to show the | ||||
| # methods anyway, you should set this option to NO. | ||||
| # For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property. Setting this option to YES (the default) will make doxygen replace the get and set methods by a property in the documentation. This will only work if the methods are indeed getting or setting a simple type. If this is not the case, or you want to show the methods anyway, you should set this option to NO. | ||||
| 
 | ||||
| IDL_PROPERTY_SUPPORT   = YES | ||||
| 
 | ||||
| @ -372,7 +377,8 @@ EXTRACT_ALL            = YES | ||||
| 
 | ||||
| EXTRACT_PRIVATE        = YES | ||||
| 
 | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. | ||||
| # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal | ||||
| # scope will be included in the documentation. | ||||
| 
 | ||||
| EXTRACT_PACKAGE        = NO | ||||
| 
 | ||||
| @ -907,13 +913,23 @@ HTML_FOOTER            = | ||||
| 
 | ||||
| # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | ||||
| # style sheet that is used by each HTML page. It can be used to | ||||
| # fine-tune the look of the HTML output. If the tag is left blank doxygen | ||||
| # will generate a default style sheet. Note that doxygen will try to copy | ||||
| # the style sheet file to the HTML output directory, so don't put your own | ||||
| # style sheet in the HTML output directory as well, or it will be erased! | ||||
| # fine-tune the look of the HTML output. If left blank doxygen will | ||||
| # generate a default style sheet. Note that it is recommended to use | ||||
| # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this | ||||
| # tag will in the future become obsolete. | ||||
| 
 | ||||
| HTML_STYLESHEET        = | ||||
| 
 | ||||
| # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional | ||||
| # user-defined cascading style sheet that is included after the standard | ||||
| # style sheets created by doxygen. Using this option one can overrule | ||||
| # certain style aspects. This is preferred over using HTML_STYLESHEET | ||||
| # since it does not replace the standard style sheet and is therefor more | ||||
| # robust against future updates. Doxygen will copy the style sheet file to | ||||
| # the output directory. | ||||
| 
 | ||||
| HTML_EXTRA_STYLESHEET  = | ||||
| 
 | ||||
| # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or | ||||
| # other source files which should be copied to the HTML output directory. Note | ||||
| # that these files will be copied to the base HTML output directory. Use the | ||||
| @ -998,9 +1014,9 @@ DOCSET_FEEDNAME        = "Doxygen generated docs" | ||||
| 
 | ||||
| DOCSET_BUNDLE_ID       = org.doxygen.Project | ||||
| 
 | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify | ||||
| # the documentation publisher. This should be a reverse domain-name style | ||||
| # string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely | ||||
| # identify the documentation publisher. This should be a reverse domain-name | ||||
| # style string, e.g. com.mycompany.MyDocSet.documentation. | ||||
| 
 | ||||
| DOCSET_PUBLISHER_ID    = org.doxygen.Publisher | ||||
| 
 | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user
	 Dean Camera
						Dean Camera