Inside Bitcoin
Opening the selected file…
Inside Bitcoin
Opening the selected file…
The code behind the network, with room to understand it.
Release published 2026-10-28 · Snapshot fetched 2026-11-01. Latest stable release at fetch time; development branches and Git history are excluded. Only the selected code window and visible folders load here.
2001# understand what is going on. On the other hand, if this tag is set to NO, the2002# size of the Perl module output will be much smaller and Perl will parse it2003# just the same.2004# The default value is: YES.2005# This tag requires that the tag GENERATE_PERLMOD is set to YES.2007PERLMOD_PRETTY = YES2009# The names of the make variables in the generated doxyrules.make file are2010# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful2011# so different doxyrules.make files included by the same Makefile don't2012# overwrite each other's variables.2013# This tag requires that the tag GENERATE_PERLMOD is set to YES.2015PERLMOD_MAKEVAR_PREFIX =2017#---------------------------------------------------------------------------2018# Configuration options related to the preprocessor2019#---------------------------------------------------------------------------2021# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all2022# C-preprocessor directives found in the sources and include files.2023# The default value is: YES.2025ENABLE_PREPROCESSING = YES2027# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names2028# in the source code. If set to NO, only conditional compilation will be2029# performed. Macro expansion can be done in a controlled way by setting2030# EXPAND_ONLY_PREDEF to YES.2031# The default value is: NO.2032# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2034MACRO_EXPANSION = NO2036# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then2037# the macro expansion is limited to the macros specified with the PREDEFINED and2038# EXPAND_AS_DEFINED tags.2039# The default value is: NO.2040# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2042EXPAND_ONLY_PREDEF = NO2044# If the SEARCH_INCLUDES tag is set to YES, the include files in the2045# INCLUDE_PATH will be searched if a #include is found.2046# The default value is: YES.2047# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2049SEARCH_INCLUDES = YES2051# The INCLUDE_PATH tag can be used to specify one or more directories that2052# contain include files that are not input files but should be processed by the2053# preprocessor.2054# This tag requires that the tag SEARCH_INCLUDES is set to YES.2056INCLUDE_PATH =2058# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard2059# patterns (like *.h and *.hpp) to filter out the header-files in the2060# directories. If left blank, the patterns specified with FILE_PATTERNS will be2061# used.2062# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2064INCLUDE_FILE_PATTERNS =2066# The PREDEFINED tag can be used to specify one or more macro names that are2067# defined before the preprocessor is started (similar to the -D option of e.g.2068# gcc). The argument of the tag is a list of macros of the form: name or2069# name=definition (no spaces). If the definition and the "=" are omitted, "=1"2070# is assumed. To prevent a macro definition from being undefined via #undef or2071# recursively expanded use the := operator instead of the = operator.2072# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2074PREDEFINED = ENABLE_EXTERNAL_SIGNER2076# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this2077# tag can be used to specify a list of macro names that should be expanded. The2078# macro definition that is found in the sources will be used. Use the PREDEFINED2079# tag if you want to use a different macro definition that overrules the2080# definition found in the source code.2081# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2083EXPAND_AS_DEFINED =2085# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will2086# remove all references to function-like macros that are alone on a line, have2087# an all uppercase name, and do not end with a semicolon. Such function macros2088# are typically used for boiler-plate code, and will confuse the parser if not2089# removed.2090# The default value is: YES.2091# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.2093SKIP_FUNCTION_MACROS = YES2095#---------------------------------------------------------------------------2096# Configuration options related to external references2097#---------------------------------------------------------------------------2099# The TAGFILES tag can be used to specify one or more tag files. For each tag2100# file the location of the external documentation should be added. The format of2101# a tag file without this location is as follows:2102# TAGFILES = file1 file2 ...2103# Adding location for the tag files is done as follows:2104# TAGFILES = file1=loc1 "file2 = loc2" ...2105# where loc1 and loc2 can be relative or absolute paths or URLs. See the2106# section "Linking to external documentation" for more information about the use2107# of tag files.2108# Note: Each tag file must have a unique name (where the name does NOT include2109# the path). If a tag file is not located in the directory in which doxygen is2110# run, you must also specify the path to the tagfile here.2112TAGFILES =2114# When a file name is specified after GENERATE_TAGFILE, doxygen will create a2115# tag file that is based on the input files it reads. See section "Linking to2116# external documentation" for more information about the usage of tag files.2118GENERATE_TAGFILE =2120# If the ALLEXTERNALS tag is set to YES, all external class will be listed in2121# the class index. If set to NO, only the inherited external classes will be2122# listed.2123# The default value is: NO.2125ALLEXTERNALS = NO2127# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed2128# in the modules index. If set to NO, only the current project's groups will be2129# listed.2130# The default value is: YES.2132EXTERNAL_GROUPS = YES2134# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in2135# the related pages index. If set to NO, only the current project's pages will2136# be listed.2137# The default value is: YES.2139EXTERNAL_PAGES = YES2141# The PERL_PATH should be the absolute path and name of the perl script2142# interpreter (i.e. the result of 'which perl').2143# The default file (with absolute path) is: /usr/bin/perl.2145PERL_PATH = /usr/bin/perl2147#---------------------------------------------------------------------------2148# Configuration options related to the dot tool2149#---------------------------------------------------------------------------2151# If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram2152# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to2153# NO turns the diagrams off. Note that this option also works with HAVE_DOT2154# disabled, but it is recommended to install and use dot, since it yields more2155# powerful graphs.2156# The default value is: YES.2158CLASS_DIAGRAMS = YES2160# You can define message sequence charts within doxygen comments using the \msc2161# command. Doxygen will then run the mscgen tool (see:2162# http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the2163# documentation. The MSCGEN_PATH tag allows you to specify the directory where2164# the mscgen tool resides. If left empty the tool is assumed to be found in the2165# default search path.2167MSCGEN_PATH =2169# You can include diagrams made with dia in doxygen documentation. Doxygen will2170# then run dia to produce the diagram and insert it in the documentation. The2171# DIA_PATH tag allows you to specify the directory where the dia binary resides.2172# If left empty dia is assumed to be found in the default search path.2174DIA_PATH =2176# If set to YES the inheritance and collaboration graphs will hide inheritance2177# and usage relations if the target is undocumented or is not a class.2178# The default value is: YES.2180HIDE_UNDOC_RELATIONS = YES2182# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is2183# available from the path. This tool is part of Graphviz (see:2184# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent2185# Bell Labs. The other options in this section have no effect if this option is2186# set to NO2187# The default value is: NO.2189HAVE_DOT = YES2191# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed2192# to run in parallel. When set to 0 doxygen will base this on the number of2193# processors available in the system. You can set it explicitly to a value2194# larger than 0 to get control over the balance between CPU load and processing2195# speed.2196# Minimum value: 0, maximum value: 32, default value: 0.2197# This tag requires that the tag HAVE_DOT is set to YES.2199DOT_NUM_THREADS = 02201# When you want a differently looking font in the dot files that doxygen2202# generates you can specify the font name using DOT_FONTNAME. You need to make2203# sure dot is able to find the font, which can be done by putting it in a2204# standard location or by setting the DOTFONTPATH environment variable or by2205# setting DOT_FONTPATH to the directory containing the font.2206# The default value is: Helvetica.2207# This tag requires that the tag HAVE_DOT is set to YES.2209DOT_FONTNAME = Helvetica2211# The DOT_FONTSIZE tag can be used to set the size (in points) of the font of2212# dot graphs.2213# Minimum value: 4, maximum value: 24, default value: 10.2214# This tag requires that the tag HAVE_DOT is set to YES.2216DOT_FONTSIZE = 102218# By default doxygen will tell dot to use the default font as specified with2219# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set2220# the path where dot can find it using this tag.2221# This tag requires that the tag HAVE_DOT is set to YES.2223DOT_FONTPATH =2225# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for2226# each documented class showing the direct and indirect inheritance relations.2227# Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.2228# The default value is: YES.2229# This tag requires that the tag HAVE_DOT is set to YES.2231CLASS_GRAPH = YES2233# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a2234# graph for each documented class showing the direct and indirect implementation2235# dependencies (inheritance, containment, and class references variables) of the2236# class with other documented classes.2237# The default value is: YES.2238# This tag requires that the tag HAVE_DOT is set to YES.2240COLLABORATION_GRAPH = YES2242# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for2243# groups, showing the direct groups dependencies.2244# The default value is: YES.2245# This tag requires that the tag HAVE_DOT is set to YES.2247GROUP_GRAPHS = YES2249# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and2250# collaboration diagrams in a style similar to the OMG's Unified Modeling
Independent explanations by MyBitcoinExplorer. Not affiliated with or endorsed by Bitcoin Core. Guides are educational and do not replace the source or its tests.
Bitcoin Core source © its contributors, distributed under the MIT license. Original notices and bundled third-party licenses are retained in the source tree.