[ViewVC] Diff of: svn/ircd-hybrid/branches/8.2.x/doc/Doxyfile

Comparing ircd-hybrid/branches/8.2.x/doc/Doxyfile (file contents):
Revision 7667 by michael, Wed Jul 20 17:09:36 2016 UTC vs.
Revision 7670 by michael, Wed Jul 20 18:22:12 2016 UTC

-<
+# Doxyfile 1.8.6
->
+# Doxyfile 1.8.8
->
+# $Id$
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project.
+CREATE_SUBDIRS         = NO
-+
+# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
-+
+# characters to appear in the names of generated files. If set to NO, non-ASCII
-+
+# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
-+
+# U+3044.
-+
+# The default value is: NO.
-+
-+
+ALLOW_UNICODE_NAMES    = NO
-+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
+# documentation generated by doxygen is written. Doxygen will use this
+# information to generate all constant output in the proper language.
+# extension. Doxygen has a built-in mapping, but you can override or extend it
+# using this tag. The format is ext=language, where ext is a file extension, and
+# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
-<
+# C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
-<
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
-<
+# (default is Fortran), use: inc=Fortran f=C.
->
+# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
->
+# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
->
+# Fortran. In the later case the parser tries to guess whether the code is fixed
->
+# or free formatted code, this is the default for Fortran type files), VHDL. For
->
+# instance to make doxygen treat .inc files as Fortran files (default is PHP),
->
+# and .f files as C (default is Fortran), use: inc=Fortran f=C.
+# Note For files without extension you can use no_extension as a placeholder.
+# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
+# For LaTeX the style of the bibliography can be controlled using
+# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
-<
+# search path. Do not use file names with spaces, bibtex cannot handle them. See
-<
+# also \cite for info how to create references.
->
+# search path. See also \cite for info how to create references.
+CITE_BIB_FILES         =
+VERBATIM_HEADERS       = YES
-+
+# If the CLANG_ASSISTED_PARSING tag is set to YES, then doxygen will use the
-+
+# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the
-+
+# cost of reduced performance. This can be particularly helpful with template
-+
+# rich C++ code for which doxygen's built-in parser lacks the necessary type
-+
+# information.
-+
+# Note: The availability of this option depends on whether or not doxygen was
-+
+# compiled with the --with-libclang option.
-+
+# The default value is: NO.
-+
-+
+CLANG_ASSISTED_PARSING = NO
-+
-+
+# If clang assisted parsing is enabled you can provide the compiler with command
-+
+# line options that you would normally use when invoking the compiler. Note that
-+
+# the include paths will already be set by doxygen for the files and directories
-+
+# specified with INPUT and INCLUDE_PATH.
-+
+# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
-+
-+
+CLANG_OPTIONS          =
-+
+#---------------------------------------------------------------------------
+# Configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+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
->
+# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
->
+# cascading style sheets that are 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. For an example
-<
+# see the documentation.
->
+# Doxygen will copy the style sheet files to the output directory.
->
+# Note: The order of the extra stylesheet files is of importance (e.g. the last
->
+# stylesheet in the list overrules the setting of the previous ones in the
->
+# list). For an example see the documentation.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+HTML_EXTRA_STYLESHEET  =
+CHM_INDEX_ENCODING     =
+# The BINARY_TOC flag controls whether a binary table of contents is generated (
-<
+# YES) or a normal table of contents ( NO) in the .chm file.
->
+# YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
->
+# enables the Previous and Next buttons.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
+# implemented using a web server instead of a web client using Javascript. There
-<
+# are two flavours of web server based searching depending on the
-<
+# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
-<
+# searching and an index file used by the script. When EXTERNAL_SEARCH is
-<
+# enabled the indexing and searching needs to be provided by external tools. See
-<
+# the section "External Indexing and Searching" for details.
->
+# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
->
+# setting. When disabled, doxygen will generate a PHP script for searching and
->
+# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
->
+# and searching needs to be provided by external tools. See the section
->
+# "External Indexing and Searching" for details.
+# The default value is: NO.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+# Note: Only use a user-defined header if you know what you are doing! The
+# following commands have a special meaning inside the header: $title,
-<
+# $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
-<
+# replace them by respectively the title of the page, the current date and time,
-<
+# only the current date, the version number of doxygen, the project name (see
-<
+# PROJECT_NAME), or the project number (see PROJECT_NUMBER).
->
+# $datetime, $date, $doxygenversion, $projectname, $projectnumber,
->
+# $projectbrief, $projectlogo. Doxygen will replace $title with the empy string,
->
+# for the replacement values of the other commands the user is refered to
->
+# HTML_HEADER.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+LATEX_HEADER           =
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
+# generated LaTeX document. The footer should contain everything after the last
-<
+# chapter. If it is left blank doxygen will generate a standard footer.
->
+# chapter. If it is left blank doxygen will generate a standard footer. See
->
+# LATEX_HEADER for more information on how to generate a default footer and what
->
+# special commands can be used inside the footer.
+# Note: Only use a user-defined footer if you know what you are doing!
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+PDF_HYPERLINKS         = YES
-<
+# If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
->
+# If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
+# the PDF file directly from the LaTeX files. Set this option to YES to get a
+# higher quality PDF documentation.
+# The default value is: YES.
+MAN_EXTENSION          = .3
-+
+# The MAN_SUBDIR tag determines the name of the directory created within
-+
+# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
-+
+# MAN_EXTENSION with the initial . removed.
-+
+# This tag requires that the tag GENERATE_MAN is set to YES.
-+
-+
+MAN_SUBDIR             =
-+
+# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
+# will generate one additional man file for each entity documented in the real
+# man page(s). These additional files only source the real man page, but without
+XML_OUTPUT             = xml
-–
+# The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a
-–
+# validating XML parser to check the syntax of the XML files.
-–
+# This tag requires that the tag GENERATE_XML is set to YES.
-–
-–
+XML_SCHEMA             =
-–
-–
+# The XML_DTD tag can be used to specify a XML DTD, which can be used by a
-–
+# validating XML parser to check the syntax of the XML files.
-–
+# This tag requires that the tag GENERATE_XML is set to YES.
-–
-–
+XML_DTD                =
-–
+# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
+# listings (including syntax highlighting and cross-referencing information) to
+# the XML output. Note that enabling this will significantly increase the size
+DOCBOOK_OUTPUT         = docbook
-+
+# If the DOCBOOK_PROGRAMLISTING tag is set to YES doxygen will include the
-+
+# program listings (including syntax highlighting and cross-referencing
-+
+# information) to the DOCBOOK output. Note that enabling this will significantly
-+
+# increase the size of the DOCBOOK output.
-+
+# The default value is: NO.
-+
+# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
-+
-+
+DOCBOOK_PROGRAMLISTING = NO
-+
+#---------------------------------------------------------------------------
+# Configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+EXPAND_AS_DEFINED      =
+# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
-<
+# remove all refrences to function-like macros that are alone on a line, have an
-<
+# all uppercase name, and do not end with a semicolon. Such function macros are
-<
+# typically used for boiler-plate code, and will confuse the parser if not
->
+# remove all references to function-like macros that are alone on a line, have
->
+# an all uppercase name, and do not end with a semicolon. Such function macros
->
+# are typically used for boiler-plate code, and will confuse the parser if not
+# removed.
+# The default value is: YES.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+# where loc1 and loc2 can be relative or absolute paths or URLs. See the
+# section "Linking to external documentation" for more information about the use
+# of tag files.
-<
+# Note: Each tag file must have an unique name (where the name does NOT include
->
+# Note: Each tag file must have a unique name (where the name does NOT include
+# the path). If a tag file is not located in the directory in which doxygen is
+# run, you must also specify the path to the tagfile here.
+# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
+# Bell Labs. The other options in this section have no effect if this option is
+# set to NO
-<
+# The default value is: NO.
->
+# The default value is: YES.
+HAVE_DOT               = YES
+DOT_NUM_THREADS        = 0
-<
+# When you want a differently looking font n the dot files that doxygen
->
+# When you want a differently looking font in the dot files that doxygen
+# generates you can specify the font name using DOT_FONTNAME. You need to make
+# sure dot is able to find the font, which can be done by putting it in a
+# standard location or by setting the DOTFONTPATH environment variable or by
+# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
+# to make the SVG files visible in IE 9+ (other browsers do not have this
+# requirement).
-<
+# Possible values are: png, jpg, gif and svg.
->
+# Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
->
+# png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
->
+# gif:cairo:gd, gif:gd, gif:gd:gd and svg.
+# The default value is: png.
+# This tag requires that the tag HAVE_DOT is set to YES.
+DIAFILE_DIRS           =
-+
+# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
-+
+# path where java can find the plantuml.jar file. If left blank, it is assumed
-+
+# PlantUML is not used or called during a preprocessing step. Doxygen will
-+
+# generate a warning when it encounters a \startuml command in this case and
-+
+# will not generate output for the diagram.
-+
+# This tag requires that the tag HAVE_DOT is set to YES.
-+
-+
+PLANTUML_JAR_PATH      =
-+
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
+# that will be shown in the graph. If the number of nodes in a graph becomes
+# larger than this value, doxygen will truncate the graph, which is visualized

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines (old)
->
+Changed lines (new)

Comparing ircd-hybrid/branches/8.2.x/doc/Doxyfile (file contents): Revision 7667 by michael, Wed Jul 20 17:09:36 2016 UTC vs. Revision 7670 by michael, Wed Jul 20 18:22:12 2016 UTC

Diff Legend

Comparing ircd-hybrid/branches/8.2.x/doc/Doxyfile (file contents):
Revision 7667 by michael, Wed Jul 20 17:09:36 2016 UTC vs.
Revision 7670 by michael, Wed Jul 20 18:22:12 2016 UTC