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.
251# instance, some of the names that are used will be different. The list of all252# members will be omitted, etc.253# The default value is: NO.255OPTIMIZE_OUTPUT_FOR_C = NO257# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or258# Python sources only. Doxygen will then generate output that is more tailored259# for that language. For instance, namespaces will be presented as packages,260# qualified scopes will look different, etc.261# The default value is: NO.263OPTIMIZE_OUTPUT_JAVA = NO265# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran266# sources. Doxygen will then generate output that is tailored for Fortran.267# The default value is: NO.269OPTIMIZE_FOR_FORTRAN = NO271# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL272# sources. Doxygen will then generate output that is tailored for VHDL.273# The default value is: NO.275OPTIMIZE_OUTPUT_VHDL = NO277# Doxygen selects the parser to use depending on the extension of the files it278# parses. With this tag you can assign which parser to use for a given279# extension. Doxygen has a built-in mapping, but you can override or extend it280# using this tag. The format is ext=language, where ext is a file extension, and281# language is one of the parsers supported by doxygen: IDL, Java, Javascript,282# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:283# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:284# Fortran. In the later case the parser tries to guess whether the code is fixed285# or free formatted code, this is the default for Fortran type files), VHDL. For286# instance to make doxygen treat .inc files as Fortran files (default is PHP),287# and .f files as C (default is Fortran), use: inc=Fortran f=C.288#289# Note: For files without extension you can use no_extension as a placeholder.290#291# Note that for custom extensions you also need to set FILE_PATTERNS otherwise292# the files are not read by doxygen.294EXTENSION_MAPPING =296# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments297# according to the Markdown format, which allows for more readable298# documentation. See http://daringfireball.net/projects/markdown/ for details.299# The output of markdown processing is further processed by doxygen, so you can300# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in301# case of backward compatibilities issues.302# The default value is: YES.304MARKDOWN_SUPPORT = YES306# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up307# to that level are automatically included in the table of contents, even if308# they do not have an id attribute.309# Note: This feature currently applies only to Markdown headings.310# Minimum value: 0, maximum value: 99, default value: 0.311# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.313TOC_INCLUDE_HEADINGS = 0315# When enabled doxygen tries to link words that correspond to documented316# classes, or namespaces to their corresponding documentation. Such a link can317# be prevented in individual cases by putting a % sign in front of the word or318# globally by setting AUTOLINK_SUPPORT to NO.319# The default value is: YES.321AUTOLINK_SUPPORT = YES323# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want324# to include (a tag file for) the STL sources as input, then you should set this325# tag to YES in order to let doxygen match functions declarations and326# definitions whose arguments contain STL classes (e.g. func(std::string);327# versus func(std::string) {}). This also make the inheritance and collaboration328# diagrams that involve STL classes more complete and accurate.329# The default value is: NO.331BUILTIN_STL_SUPPORT = NO333# If you use Microsoft's C++/CLI language, you should set this option to YES to334# enable parsing support.335# The default value is: NO.337CPP_CLI_SUPPORT = NO339# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:340# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen341# will parse them like normal C++ but will assume all classes use public instead342# of private inheritance when no explicit protection keyword is present.343# The default value is: NO.345SIP_SUPPORT = NO347# For Microsoft's IDL there are propget and propput attributes to indicate348# getter and setter methods for a property. Setting this option to YES will make349# doxygen to replace the get and set methods by a property in the documentation.350# This will only work if the methods are indeed getting or setting a simple351# type. If this is not the case, or you want to show the methods anyway, you352# should set this option to NO.353# The default value is: YES.355IDL_PROPERTY_SUPPORT = YES357# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC358# tag is set to YES then doxygen will reuse the documentation of the first359# member in the group (if any) for the other members of the group. By default360# all members of a group must be documented explicitly.361# The default value is: NO.363DISTRIBUTE_GROUP_DOC = NO365# If one adds a struct or class to a group and this option is enabled, then also366# any nested class or struct is added to the same group. By default this option367# is disabled and one has to add nested compounds explicitly via \ingroup.368# The default value is: NO.370GROUP_NESTED_COMPOUNDS = NO372# Set the SUBGROUPING tag to YES to allow class member groups of the same type373# (for instance a group of public functions) to be put as a subgroup of that374# type (e.g. under the Public Functions section). Set it to NO to prevent375# subgrouping. Alternatively, this can be done per class using the376# \nosubgrouping command.377# The default value is: YES.379SUBGROUPING = YES381# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions382# are shown inside the group in which they are included (e.g. using \ingroup)383# instead of on a separate page (for HTML and Man pages) or section (for LaTeX384# and RTF).385#386# Note that this feature does not work in combination with387# SEPARATE_MEMBER_PAGES.388# The default value is: NO.390INLINE_GROUPED_CLASSES = NO392# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions393# with only public data fields or simple typedef fields will be shown inline in394# the documentation of the scope in which they are defined (i.e. file,395# namespace, or group documentation), provided this scope is documented. If set396# to NO, structs, classes, and unions are shown on a separate page (for HTML and397# Man pages) or section (for LaTeX and RTF).398# The default value is: NO.400INLINE_SIMPLE_STRUCTS = NO402# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or403# enum is documented as struct, union, or enum with the name of the typedef. So404# typedef struct TypeS {} TypeT, will appear in the documentation as a struct405# with name TypeT. When disabled the typedef will appear as a member of a file,406# namespace, or class. And the struct will be named TypeS. This can typically be407# useful for C code in case the coding convention dictates that all compound408# types are typedef'ed and only the typedef is referenced, never the tag name.409# The default value is: NO.411TYPEDEF_HIDES_STRUCT = NO413# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This414# cache is used to resolve symbols given their name and scope. Since this can be415# an expensive process and often the same symbol appears multiple times in the416# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small417# doxygen will become slower. If the cache is too large, memory is wasted. The418# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range419# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536420# symbols. At the end of a run doxygen will report the cache usage and suggest421# the optimal cache size from a speed point of view.422# Minimum value: 0, maximum value: 9, default value: 0.424LOOKUP_CACHE_SIZE = 0426#---------------------------------------------------------------------------427# Build related configuration options428#---------------------------------------------------------------------------430# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in431# documentation are documented, even if no documentation was available. Private432# class members and static file members will be hidden unless the433# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.434# Note: This will also disable the warnings about undocumented members that are435# normally produced when WARNINGS is set to YES.436# The default value is: NO.438EXTRACT_ALL = YES440# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will441# be included in the documentation.442# The default value is: NO.444EXTRACT_PRIVATE = YES446# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal447# scope will be included in the documentation.448# The default value is: NO.450EXTRACT_PACKAGE = NO452# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be453# included in the documentation.454# The default value is: NO.456EXTRACT_STATIC = YES458# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined459# locally in source files will be included in the documentation. If set to NO,460# only classes defined in header files are included. Does not have any effect461# for Java sources.462# The default value is: YES.464EXTRACT_LOCAL_CLASSES = YES466# This flag is only useful for Objective-C code. If set to YES, local methods,467# which are defined in the implementation section but not in the interface are468# included in the documentation. If set to NO, only methods in the interface are469# included.470# The default value is: NO.472EXTRACT_LOCAL_METHODS = NO474# If this flag is set to YES, the members of anonymous namespaces will be475# extracted and appear in the documentation as a namespace called476# 'anonymous_namespace{file}', where file will be replaced with the base name of477# the file that contains the anonymous namespace. By default anonymous namespace478# are hidden.479# The default value is: NO.481EXTRACT_ANON_NSPACES = NO483# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all484# undocumented members inside documented classes or files. If set to NO these485# members will be included in the various overviews, but no documentation486# section is generated. This option has no effect if EXTRACT_ALL is enabled.487# The default value is: NO.489HIDE_UNDOC_MEMBERS = NO491# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all492# undocumented classes that are normally visible in the class hierarchy. If set493# to NO, these classes will be included in the various overviews. This option494# has no effect if EXTRACT_ALL is enabled.495# The default value is: NO.497HIDE_UNDOC_CLASSES = NO499# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend500# (class|struct|union) declarations. If set to NO, these declarations will be
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.