Freeciv

# Doxyfile 1.9.8

# configuration file without replacing the environment variables or CMake type

# replacement variables:

# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to

# generate identifiers for the Markdown headings. Note: Every identifier is

# unique.

# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a

# sequence number starting at 0 and GITHUB use the lower case version of title

# with any whitespace replaced by '-' and punctuation characters removed.

# The default value is: DOXYGEN.

# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.

MARKDOWN_ID_STYLE = DOXYGEN

# If the TIMESTAMP tag is set different from NO then each generated page will

# contain the date or date and time when the page was generated. Setting this to

# NO can help when comparing the output of multiple runs.

# Possible values are: YES, NO, DATETIME and DATE.

# The default value is: NO.

TIMESTAMP = YES

# will also hide undocumented C++ concepts if enabled. This option has no effect

# if EXTRACT_ALL is enabled.

# Possible values are: SYSTEM, NO and YES.

# The default value is: SYSTEM.

# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about

# undocumented enumeration values. If set to NO, doxygen will accept

# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag

# will automatically be disabled.

# The default value is: NO.

WARN_IF_UNDOC_ENUM_VAL = NO

# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then doxygen behaves

# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined doxygen will not

# write the warning messages in between other messages but write them at the end

# of a run, in case a WARN_LOGFILE is defined the warning messages will be

# besides being in the defined file also be shown at the end of a run, unless

# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case

# the behavior will remain as with the setting FAIL_ON_WARNINGS.

# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.

# See also: INPUT_FILE_ENCODING

# This tag can be used to specify the character encoding of the source files

# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify

# character encoding on a per file pattern basis. Doxygen will compare the file

# name with each pattern and apply the encoding instead of the default

# INPUT_ENCODING) if there is a match. The character encodings are a list of the

# form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding

# "INPUT_ENCODING" for further information on supported encodings.

INPUT_FILE_ENCODING =

# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,

# *.cpp, *.cppm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl,

# *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d, *.php,

# *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be

# provided as doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,

# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.

# Note that doxygen will use the data processed and written to standard output

# for further processing, therefore nothing else, like debug statements or used

# commands (so in case of a Windows batch file always use @echo OFF), should be

# written to standard output.

#

# The Fortran standard specifies that for fixed formatted Fortran code all

# characters from position 72 are to be considered as comment. A common

# extension is to allow longer lines before the automatic comment starts. The

# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can

# be processed before the automatic comment starts.

# Minimum value: 7, maximum value: 10000, default value: 72.

FORTRAN_COMMENT_AFTER = 72

# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)

# that should be ignored while generating the index headers. The IGNORE_PREFIX

# tag works for classes, function and member names. The entity will be placed in

# the alphabetical list under the first letter of the entity name that remains

# after removing the prefix.

# list).

# Note: Since the styling of scrollbars can currently not be overruled in

# Webkit/Chromium, the styling will be left out of the default doxygen.css if

# one or more extra stylesheets have been specified. So if scrollbar

# customization is desired it has to be added explicitly. For an example see the

# documentation.

# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output

# should be rendered with a dark or light theme.

# Possible values are: LIGHT always generate light mode output, DARK always

# generate dark mode output, AUTO_LIGHT automatically set the mode according to

# the user preference, use light mode if no preference is set (the default),

# AUTO_DARK automatically set the mode according to the user preference, use

# dark mode if no preference is set and TOGGLE allow to user to switch between

# light and dark mode via a button.

# The default value is: AUTO_LIGHT.

# This tag requires that the tag GENERATE_HTML is set to YES.

HTML_COLORSTYLE = AUTO_LIGHT

# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be

# dynamically folded and expanded in the generated HTML source code.

# The default value is: YES.

# This tag requires that the tag GENERATE_HTML is set to YES.

HTML_CODE_FOLDING = YES

# The SITEMAP_URL tag is used to specify the full URL of the place where the

# generated documentation will be placed on the server by the user during the

# deployment of the documentation. The generated sitemap is called sitemap.xml

# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL

# is specified no sitemap is generated. For information about the sitemap

# protocol see https://www.sitemaps.org

# This tag requires that the tag GENERATE_HTML is set to YES.

SITEMAP_URL =

# The LATEX_BATCHMODE tag signals the behavior of LaTeX in case of an error.

# Possible values are: NO same as ERROR_STOP, YES same as BATCH, BATCH In batch

# mode nothing is printed on the terminal, errors are scrolled as if <return> is

# hit at every error; missing files that TeX tries to input or request from

# keyboard input (\read on a not open input stream) cause the job to abort,

# NON_STOP In nonstop mode the diagnostic message will appear on the terminal,

# but there is no possibility of user interaction just like in batch mode,

# SCROLL In scroll mode, TeX will stop only for missing files to input or if

# keyboard input is necessary and ERROR_STOP In errorstop mode, TeX will stop at

# each error, asking for user intervention.

# AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures

#---------------------------------------------------------------------------

# Configuration options related to Sqlite3 output

#---------------------------------------------------------------------------

# If the GENERATE_SQLITE3 tag is set to YES doxygen will generate a Sqlite3

# database with symbols found by doxygen stored in tables.

# The default value is: NO.

GENERATE_SQLITE3 = NO

# The SQLITE3_OUTPUT tag is used to specify where the Sqlite3 database will be

# put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put

# in front of it.

# The default directory is: sqlite3.

# This tag requires that the tag GENERATE_SQLITE3 is set to YES.

SQLITE3_OUTPUT = sqlite3

# The SQLITE3_OVERWRITE_DB tag is set to YES, the existing doxygen_sqlite3.db

# database file will be recreated with each doxygen run. If set to NO, doxygen

# will warn if an a database file is already found and not modify it.

# The default value is: YES.

# This tag requires that the tag GENERATE_SQLITE3 is set to YES.

SQLITE3_RECREATE_DB = YES

# If the ALLEXTERNALS tag is set to YES, all external classes and namespaces

# will be listed in the class and namespace index. If set to NO, only the

# inherited external classes will be listed.

# in the topic index. If set to NO, only the current project's groups will be

# Configuration options related to diagram generator tools

# https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent

# DOT_COMMON_ATTR is common attributes for nodes, edges and labels of

# subgraphs. When you want a differently looking font in the dot files that

# doxygen generates you can specify fontname, fontcolor and fontsize attributes.

# For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node,

# Edge and Graph Attributes specification</a> 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 setting DOT_FONTPATH to the

# directory containing the font. Default graphviz fontsize is 14.

# The default value is: fontname=Helvetica,fontsize=10.

DOT_COMMON_ATTR = "fontname=Helvetica,fontsize=10"

# DOT_EDGE_ATTR is concatenated with DOT_COMMON_ATTR. For elegant style you can

# add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a

# href=https://graphviz.org/doc/info/arrows.html>Complete documentation about

# arrows shapes.</a>

# The default value is: labelfontname=Helvetica,labelfontsize=10.

DOT_EDGE_ATTR = "labelfontname=Helvetica,labelfontsize=10"

# DOT_NODE_ATTR is concatenated with DOT_COMMON_ATTR. For view without boxes

# around nodes set 'shape=plain' or 'shape=plaintext' <a

# href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a>

# The default value is: shape=box,height=0.2,width=0.4.

# This tag requires that the tag HAVE_DOT is set to YES.

DOT_NODE_ATTR = "shape=box,height=0.2,width=0.4"

# You can set the path where dot can find font specified with fontname in

# DOT_COMMON_ATTR and others dot attributes.

# If the CLASS_GRAPH tag is set to YES or GRAPH or BUILTIN then doxygen will

# generate a graph for each documented class showing the direct and indirect

# inheritance relations. In case the CLASS_GRAPH tag is set to YES or GRAPH and

# HAVE_DOT is enabled as well, then dot will be used to draw the graph. In case

# the CLASS_GRAPH tag is set to YES and HAVE_DOT is disabled or if the

# CLASS_GRAPH tag is set to BUILTIN, then the built-in generator will be used.

# If the CLASS_GRAPH tag is set to TEXT the direct and indirect inheritance

# relations will be shown as texts / links.

# Possible values are: NO, YES, TEXT, GRAPH and BUILTIN.

# class with other documented classes. Explicit enabling a collaboration graph,

# when COLLABORATION_GRAPH is set to NO, can be accomplished by means of the

# command \collaborationgraph. Disabling a collaboration graph can be

# accomplished by means of the command \hidecollaborationgraph.

# groups, showing the direct groups dependencies. Explicit enabling a group

# dependency graph, when GROUP_GRAPHS is set to NO, can be accomplished by means

# of the command \groupgraph. Disabling a directory graph can be accomplished by

# means of the command \hidegroupgraph. See also the chapter Grouping in the

# manual.

# files. Explicit enabling an include graph, when INCLUDE_GRAPH is is set to NO,

# can be accomplished by means of the command \includegraph. Disabling an

# include graph can be accomplished by means of the command \hideincludegraph.

# files. Explicit enabling an included by graph, when INCLUDED_BY_GRAPH is set

# to NO, can be accomplished by means of the command \includedbygraph. Disabling

# an included by graph can be accomplished by means of the command

# \hideincludedbygraph.

# files in the directories. Explicit enabling a directory graph, when

# DIRECTORY_GRAPH is set to NO, can be accomplished by means of the command

# \directorygraph. Disabling a directory graph can be accomplished by means of

# the command \hidedirectorygraph.

# https://www.graphviz.org/)).

# You can include diagrams made with dia in doxygen documentation. Doxygen will

# then run dia to produce the diagram and insert it in the documentation. The

# DIA_PATH tag allows you to specify the directory where the dia binary resides.

# If left empty dia is assumed to be found in the default search path.

DIA_PATH =

# You can define message sequence charts within doxygen comments using the \msc

# command. If the MSCGEN_TOOL tag is left empty (the default), then doxygen will

# use a built-in version of mscgen tool to produce the charts. Alternatively,

# the MSCGEN_TOOL tag can also specify the name an external tool. For instance,

# specifying prog as the value, doxygen will call the tool as prog -T

# <outfile_format> -o <outputfile> <inputfile>. The external tool should support

# output file formats "png", "eps", "svg", and "ismap".

MSCGEN_TOOL =

# The MSCFILE_DIRS tag can be used to specify one or more directories that

# contain msc files that are included in the documentation (see the \mscfile

# command).

MSCFILE_DIRS =