The repository context of the repository rule calling this utility
function.

A list of URLs matching what is passed to repository_ctx.download and
repository_ctx.download_and_extract.

Name for the target.

List of source files to generate documentation for.
Can include any file that Doxygen can parse, as well as targets that return a DefaultInfo provider (usually genrules).
Since we are only considering the outputs files and not the sources, these targets will be built if necessary.

List of dependencies targets whose files present in the 'src', 'hdrs' and 'data' attributes will be collected to generate the documentation.
Transitive dependencies are also taken into account.
Since we are only considering the source files and not the outputs, these targets will not be built.

Label of the doxygen executable.

Label of the doxygen executable. Make sure it is also added to the srcs of the macro

List of additional configuration parameters to pass to Doxygen.

The template file to use to generate the Doxyfile.
The following substitutions are available:<br>

• # {{INPUT}}: Subpackage directory in the sandbox.<br>
• # {{ADDITIONAL PARAMETERS}}: Additional parameters given in the configurations attribute.<br>
• # {{OUTPUT DIRECTORY}}: The directory provided in the outs attribute.<br>
• {{OUTDIR}}: The output directory where the generated documentation will be placed.
  Can be used anywhere in the Doxyfile, usually to generate additional output files, like tag files.

Extra arguments to pass to the doxygen executable.

Whether to use the default shell environment when running doxygen.

Additional environment variables to set when running doxygen.

List of additional tools to include in the doxygen environment. Tools are executable inputs that may have their own runfiles which are automatically made available to the action.

Output folders bazel will keep. If only the html outputs is of interest, the default value will do.
otherwise, a list of folders to keep is expected (e.g. ["html", "latex"]).
Note that the rule will also generate an output group for each folder in the outs list having the same name.

This tag specifies the encoding used for all characters in the configuration file that follow.

The project_name tag is a single word (or a sequence of words surrounded by double-quotes, unless you are using Doxywizard) that should identify the project for which the documentation is generated.

The project_number tag can be used to enter a project or revision number.

Using the project_brief tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project.

With the project_logo tag one can specify a logo or an icon that is included in the documentation.

With the project_icon tag one can specify an icon that is included in the tabs when the HTML document is shown.

If the create_subdirs tag is set to True then Doxygen will create up to 4096 sub-directories (in 2 levels) under the output directory of each output format and will distribute the generated files over these directories.

Controls the number of sub-directories that will be created when create_subdirs tag is set to True.

If the allow_unicode_names tag is set to True, Doxygen will allow non-ASCII characters to appear in the names of generated files.

The output_language tag is used to specify the language in which all documentation generated by Doxygen is written.

If the brief_member_desc tag is set to True, Doxygen will include brief member descriptions after the members that are listed in the file and class documentation (similar to Javadoc).

If the repeat_brief tag is set to True, Doxygen will prepend the brief description of a member or function before the detailed description Note: If both hide_undoc_members and brief_member_desc are set to False, the brief descriptions will be completely suppressed.

This tag implements a quasi-intelligent brief description abbreviator that is used to form the text in various listings.

If the always_detailed_sec and repeat_brief tags are both set to True then Doxygen will generate a detailed section even if there is only a brief description.

If the inline_inherited_memb tag is set to True, Doxygen will show all inherited members of a class in the documentation of that class as if those members were ordinary class members.

If the full_path_names tag is set to True, Doxygen will prepend the full path before files name in the file list and in the header files.

The strip_from_path tag can be used to strip a user-defined part of the path.

The strip_from_inc_path tag can be used to strip a user-defined part of the path mentioned in the documentation of a class, which tells the reader which header file to include in order to use a class.

If the short_names tag is set to True, Doxygen will generate much shorter (but less readable) file names.

If the javadoc_autobrief tag is set to True then Doxygen will interpret the first line (until the first dot) of a Javadoc-style comment as the brief description.

If the javadoc_banner tag is set to True then Doxygen will interpret a line such as /*************** as being the beginning of a Javadoc-style comment "banner".

If the qt_autobrief tag is set to True then Doxygen will interpret the first line (until the first dot) of a Qt-style comment as the brief description.

The multiline_cpp_is_brief tag can be set to True to make Doxygen treat a multi-line C++ special comment block (i.e. a block of //! or /// comments) as a brief description.

By default Python docstrings are displayed as preformatted text and Doxygen's special commands cannot be used.

If the inherit_docs tag is set to True then an undocumented member inherits the documentation from any documented member that it re-implements.

If the separate_member_pages tag is set to True then Doxygen will produce a new page for each member.

The tab_size tag can be used to set the number of spaces in a tab.

This tag can be used to specify a number of aliases that act as commands in the documentation.

Set the optimize_output_for_c tag to True if your project consists of C sources only.

Set the optimize_output_java tag to True if your project consists of Java or Python sources only.

Set the optimize_for_fortran tag to True if your project consists of Fortran sources.

Set the optimize_output_vhdl tag to True if your project consists of VHDL sources.

Set the optimize_output_slice tag to True if your project consists of Slice sources only.

Doxygen selects the parser to use depending on the extension of the files it parses.

If the markdown_support tag is enabled then Doxygen pre-processes all comments according to the Markdown format, which allows for more readable documentation.

If the markdown_strict tag is enabled then Doxygen treats text in comments as Markdown formatted also in cases where Doxygen's native markup format conflicts with that of Markdown.

When the toc_include_headings tag is set to a non-zero value, all headings up to that level are automatically included in the table of contents, even if they do not have an id attribute.

The markdown_id_style tag can be used to specify the algorithm used to generate identifiers for the Markdown headings.

When enabled Doxygen tries to link words that correspond to documented classes, or namespaces to their corresponding documentation.

This tag specifies a list of words that, when matching the start of a word in the documentation, will suppress auto links generation, if it is enabled via autolink_support.

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 True in order to let Doxygen match functions declarations and definitions whose arguments contain STL classes (e.g. func(std::string); versus func(std::string) {}).

If you use Microsoft's C++/CLI language, you should set this option to True to enable parsing support.

Set the sip_support tag to True if your project consists of sip (see: https://www.riverbankcomputing.com/software) sources only.

For Microsoft's IDL there are propget and propput attributes to indicate getter and setter methods for a property.

If member grouping is used in the documentation and the distribute_group_doc tag is set to True then Doxygen will reuse the documentation of the first member in the group (if any) for the other members of the group.

If one adds a struct or class to a group and this option is enabled, then also any nested class or struct is added to the same group.

Set the subgrouping tag to True to allow class member groups of the same type (for instance a group of public functions) to be put as a subgroup of that type (e.g. under the Public Functions section).

When the inline_grouped_classes tag is set to True, classes, structs and unions are shown inside the group in which they are included (e.g. using \ingroup) instead of on a separate page (for HTML and Man pages) or section (for LaTeX and RTF).

When the inline_simple_structs tag is set to True, structs, classes, and unions with only public data fields or simple typedef fields will be shown inline in the documentation of the scope in which they are defined (i.e. file, namespace, or group documentation), provided this scope is documented.

When typedef_hides_struct tag is enabled, a typedef of a struct, union, or enum is documented as struct, union, or enum with the name of the typedef.

The size of the symbol lookup cache can be set using lookup_cache_size.

The num_proc_threads specifies the number of threads Doxygen is allowed to use during processing.

If the timestamp tag is set different from False then each generated page will contain the date or date and time when the page was generated.

If the extract_all tag is set to True, Doxygen will assume all entities in documentation are documented, even if no documentation was available.

If the extract_private tag is set to True, all private members of a class will be included in the documentation.

If the extract_priv_virtual tag is set to True, documented private virtual methods of a class will be included in the documentation.

If the extract_package tag is set to True, all members with package or internal scope will be included in the documentation.

If the extract_static tag is set to True, all static members of a file will be included in the documentation.

If the extract_local_classes tag is set to True, classes (and structs) defined locally in source files will be included in the documentation.

This flag is only useful for Objective-C code.

If this flag is set to True, the members of anonymous namespaces will be extracted and appear in the documentation as a namespace called 'anonymous_namespace{file}', where file will be replaced with the base name of the file that contains the anonymous namespace.

If this flag is set to True, the name of an unnamed parameter in a declaration will be determined by the corresponding definition.

If the hide_undoc_members tag is set to True, Doxygen will hide all undocumented members inside documented classes or files.

If the hide_undoc_classes tag is set to True, Doxygen will hide all undocumented classes that are normally visible in the class hierarchy.

If the hide_undoc_namespaces tag is set to YES, Doxygen will hide all undocumented namespaces that are normally visible in the namespace hierarchy.

If the hide_friend_compounds tag is set to True, Doxygen will hide all friend declarations.

If the hide_in_body_docs tag is set to True, Doxygen will hide any documentation blocks found inside the body of a function.

The internal_docs tag determines if documentation that is typed after a \internal command is included.

With the correct setting of option case_sense_names Doxygen will better be able to match the capabilities of the underlying filesystem.

If the hide_scope_names tag is set to False then Doxygen will show members with their full class and namespace scopes in the documentation.

If the hide_compound_reference tag is set to False (default) then Doxygen will append additional text to a page's title, such as Class Reference.

If the show_headerfile tag is set to True then the documentation for a class will show which file needs to be included to use the class.

If the show_include_files tag is set to True then Doxygen will put a list of the files that are included by a file in the documentation of that file.

If the show_grouped_memb_inc tag is set to True then Doxygen will add for each grouped member an include statement to the documentation, telling the reader which file to include in order to use the member.

If the force_local_includes tag is set to True then Doxygen will list include files with double quotes in the documentation rather than with sharp brackets.

If the inline_info tag is set to True then a tag [inline] is inserted in the documentation for inline members.

If the sort_member_docs tag is set to True then Doxygen will sort the (detailed) documentation of file and class members alphabetically by member name.

If the sort_brief_docs tag is set to True then Doxygen will sort the brief descriptions of file, namespace and class members alphabetically by member name.

If the sort_members_ctors_1st tag is set to True then Doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first.

If the sort_group_names tag is set to True then Doxygen will sort the hierarchy of group names into alphabetical order.

If the sort_by_scope_name tag is set to True, the class list will be sorted by fully-qualified names, including namespaces.

If the strict_proto_matching option is enabled and Doxygen fails to do proper type resolution of all parameters of a function it will reject a match between the prototype and the implementation of a member function even if there is only one candidate or it is obvious which candidate to choose by doing a simple string match.

The generate_todolist tag can be used to enable (YES) or disable (NO) the todo list.

The generate_testlist tag can be used to enable (YES) or disable (NO) the test list.

The generate_buglist tag can be used to enable (YES) or disable (NO) the bug list.

The generate_deprecatedlist tag can be used to enable (YES) or disable (NO) the deprecated list.

The enabled_sections tag can be used to enable conditional documentation sections, marked by \if <section_label> ... \endif and \cond <section_label> ... \endcond blocks.

The max_initializer_lines tag determines the maximum number of lines that the initial value of a variable or macro / define can have for it to appear in the documentation.

Set the show_used_files tag to False to disable the list of files generated at the bottom of the documentation of classes and structs.

Set the show_files tag to False to disable the generation of the Files page.

Set the show_namespaces tag to False to disable the generation of the Namespaces page.

The file_version_filter tag can be used to specify a program or script that Doxygen should invoke to get the current version for each file (typically from the version control system).

The layout_file tag can be used to specify a layout file which will be parsed by Doxygen.

The cite_bib_files tag can be used to specify one or more bib files containing the reference definitions.

The external_tool_path tag can be used to extend the search path (PATH environment variable) so that external tools such as latex and gs can be found.

The quiet tag can be used to turn on/off the messages that are generated to standard output by Doxygen.

The warnings tag can be used to turn on/off the warning messages that are generated to standard error (stderr) by Doxygen.

If the warn_if_undocumented tag is set to True then Doxygen will generate warnings for undocumented members.

If the warn_if_doc_error tag is set to True, Doxygen will generate warnings for potential errors in the documentation, such as documenting some parameters in a documented function twice, or documenting parameters that don't exist or using markup commands wrongly.

If warn_if_incomplete_doc is set to True, Doxygen will warn about incomplete function parameter documentation.

This warn_no_paramdoc option can be enabled to get warnings for functions that are documented, but have no documentation for their parameters or return value.

If warn_if_undoc_enum_val option is set to True, Doxygen will warn about undocumented enumeration values.

If warn_layout_file option is set to True, Doxygen will warn about issues found while parsing the user defined layout file, such as missing or wrong elements

If the warn_as_error tag is set to True then Doxygen will immediately stop when a warning is encountered.

The warn_format tag determines the format of the warning messages that Doxygen can produce.

In the $text part of the warn_format command it is possible that a reference to a more specific place is given.

The warn_logfile tag can be used to specify a file to which warning and error messages should be written.

The input tag is used to specify the files and/or directories that contain documented source files.

This tag can be used to specify the character encoding of the source files that Doxygen parses.

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.

If the value of the input tag contains directories, you can use the file_patterns tag to specify one or more wildcard patterns (like *.cpp and *.h) to filter out the source-files in the directories.

The recursive tag can be used to specify whether or not subdirectories should be searched for input files as well.

The exclude tag can be used to specify files and/or directories that should be excluded from the input source files.

The exclude_symlinks tag can be used to select whether or not files or directories that are symbolic links (a Unix file system feature) are excluded from the input.

If the value of the input tag contains directories, you can use the exclude_patterns tag to specify one or more wildcard patterns to exclude certain files from those directories.

The exclude_symbols tag can be used to specify one or more symbol names (namespaces, classes, functions, etc.) that should be excluded from the output.

The example_path tag can be used to specify one or more files or directories that contain example code fragments that are included (see the \include command).

If the value of the example_path tag contains directories, you can use the example_patterns tag to specify one or more wildcard pattern (like *.cpp and *.h) to filter out the source-files in the directories.

If the example_recursive tag is set to True then subdirectories will be searched for input files to be used with the \include or \dontinclude commands irrespective of the value of the recursive tag.

The image_path tag can be used to specify one or more files or directories that contain images that are to be included in the documentation (see the \image command).

The input_filter tag can be used to specify a program that Doxygen should invoke to filter for each input file.

The filter_patterns tag can be used to specify filters on a per file pattern basis.

If the filter_source_files tag is set to True, the input filter (if set using input_filter) will also be used to filter the input files that are used for producing the source files to browse (i.e. when source_browser is set to True).

The filter_source_patterns tag can be used to specify source filters per file pattern.

If the use_mdfile_as_mainpage tag refers to the name of a markdown file that is part of the input, its contents will be placed on the main page (index.html).

If the implicit_dir_docs tag is set to True, any README.md file found in subdirectories of the project's root, is used as the documentation for that subdirectory, except when the README.md starts with a \dir, \page or \mainpage command.

The Fortran standard specifies that for fixed formatted Fortran code all characters from position 72 are to be considered as comment.

If the source_browser tag is set to True then a list of source files will be generated.

Setting the inline_sources tag to True will include the body of functions, multi-line macros, enums or list initialized variables directly into the documentation.

Setting the strip_code_comments tag to True will instruct Doxygen to hide any special comment blocks from generated source code fragments.

If the referenced_by_relation tag is set to True then for each documented entity all documented functions referencing it will be listed.

If the references_relation tag is set to True then for each documented function all documented entities called/used by that function will be listed.

If the references_link_source tag is set to True and source_browser tag is set to True then the hyperlinks from functions in references_relation and referenced_by_relation lists will link to the source code.

If source_tooltips is enabled (the default) then hovering a hyperlink in the source code will show a tooltip with additional information such as prototype, brief description and links to the definition and documentation.

If the use_htags tag is set to True then the references to source code will point to the HTML generated by the htags(1) tool instead of Doxygen built-in source browser.

If the verbatim_headers tag is set the True then Doxygen will generate a verbatim copy of the header file for each class for which an include is specified.

If the clang_assisted_parsing tag is set to True then Doxygen will use the clang parser (see: http://clang.llvm.org/) for more accurate parsing at the cost of reduced performance.

If the clang_assisted_parsing tag is set to True and the clang_add_inc_paths tag is set to True then Doxygen will add the directory of each input to the include path.

If clang assisted parsing is enabled you can provide the compiler with command line options that you would normally use when invoking the compiler.

If clang assisted parsing is enabled you can provide the clang parser with the path to the directory containing a file called compile_commands.json.

If the alphabetical_index tag is set to True, an alphabetical index of all compounds will be generated.

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.

If the generate_html tag is set to True, Doxygen will generate HTML output The default value is: True.

The html_output tag is used to specify where the HTML docs will be put.

The html_file_extension tag can be used to specify the file extension for each generated HTML page (for example: .htm, .php, .asp).

The html_header tag can be used to specify a user-defined HTML header file for each generated HTML page.

The html_footer tag can be used to specify a user-defined HTML footer for each generated HTML page.

The html_stylesheet tag can be used to specify a user-defined cascading style sheet that is used by each HTML page.

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.

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.

The html_colorstyle tag can be used to specify if the generated HTML output should be rendered with a dark or light theme.

The html_colorstyle_hue tag controls the color of the HTML output.

The html_colorstyle_sat tag controls the purity (or saturation) of the colors in the HTML output.

The html_colorstyle_gamma tag controls the gamma correction applied to the luminance component of the colors in the HTML output.

If the html_dynamic_menus tag is set to True then the generated HTML documentation will contain a main index with vertical navigation menus that are dynamically created via JavaScript.

If the html_dynamic_sections tag is set to True then the generated HTML documentation will contain sections that can be hidden and shown after the page has loaded.

If the html_code_folding tag is set to True then classes and functions can be dynamically folded and expanded in the generated HTML source code.

If the html_copy_clipboard tag is set to True then Doxygen will show an icon in the top right corner of code and text fragments that allows the user to copy its content to the clipboard.

Doxygen stores a couple of settings persistently in the browser (via e.g. cookies).

With html_index_num_entries one can control the preferred number of entries shown in the various tree structured indices initially; the user can expand and collapse entries dynamically later on.

If the generate_docset tag is set to True, additional index files will be generated that can be used as input for Apple's Xcode 3 integrated development environment (see: https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard).

This tag determines the name of the docset feed.

This tag determines the URL of the docset feed.

This tag specifies a string that should uniquely identify the documentation set bundle.

The docset_publisher_id tag specifies a string that should uniquely identify the documentation publisher.

The docset_publisher_name tag identifies the documentation publisher.

If the generate_htmlhelp tag is set to True then Doxygen generates three additional HTML index files: index.hhp, index.hhc, and index.hhk.

The chm_file tag can be used to specify the file name of the resulting .chm file.

The hhc_location tag can be used to specify the location (absolute path including file name) of the HTML help compiler (hhc.exe).

The generate_chi flag controls if a separate .chi index file is generated (YES) or that it should be included in the main .chm file (NO).

The chm_index_encoding is used to encode HtmlHelp index (hhk), content (hhc) and project file content.

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.

The toc_expand flag can be set to True to add extra items for group members to the table of contents of the HTML help documentation and to the tree view.

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.

If the generate_qhp tag is set to True and both qhp_namespace and qhp_virtual_folder are set, an additional index file will be generated that can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated HTML documentation.

If the qhg_location tag is specified, the qch_file tag can be used to specify the file name of the resulting .qch file.

The qhp_namespace tag specifies the namespace to use when generating Qt Help Project output.

The qhp_virtual_folder tag specifies the namespace to use when generating Qt Help Project output.

If the qhp_cust_filter_name tag is set, it specifies the name of a custom filter to add.

The qhp_cust_filter_attrs tag specifies the list of the attributes of the custom filter to add.

The qhp_sect_filter_attrs tag specifies the list of the attributes this project's filter section matches.

The qhg_location tag can be used to specify the location (absolute path including file name) of Qt's qhelpgenerator.

If the generate_eclipsehelp tag is set to True, additional index files will be generated, together with the HTML files, they form an Eclipse help plugin.

A unique identifier for the Eclipse help plugin.

If you want full control over the layout of the generated HTML pages it might be necessary to disable the index and replace it with your own.

The generate_treeview tag is used to specify whether a tree-like index structure should be generated to display hierarchical information.

When generate_treeview is set to YES, the page_outline_panel option determines if an additional navigation panel is shown at the right hand side of the screen, displaying an outline of the contents of the main page, similar to e.g. https://developer.android.com/reference.

When generate_treeview is set to True, the full_sidebar option determines if the side bar is limited to only the treeview area (value False) or if it should extend to the full height of the window (value True).

The enum_values_per_line tag can be used to set the number of enum values that Doxygen will group on one line in the generated HTML documentation.

When the show_enum_values tag is set doxygen will show the specified enumeration values besides the enumeration mnemonics.

If the treeview is enabled (see generate_treeview) then this tag can be used to set the initial width (in pixels) of the frame in which the tree is shown.

If the ext_links_in_window option is set to True, Doxygen will open links to external symbols imported via tag files in a separate window.

If the obfuscate_emails tag is set to True, Doxygen will obfuscate email addresses.

If the html_formula_format option is set to svg, Doxygen will use the pdf2svg tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see https://inkscape.org) to generate formulas as SVG images instead of PNGs for the HTML output.

Use this tag to change the font size of LaTeX formulas included as images in the HTML documentation.

The formula_macrofile can contain LaTeX \newcommand and \renewcommand commands to create new LaTeX commands to be used in formulas as building blocks.

Enable the use_mathjax option to render LaTeX formulas using MathJax (see https://www.mathjax.org) which uses client side JavaScript for the rendering instead of using pre-rendered bitmaps.

With mathjax_version it is possible to specify the MathJax version to be used.

When MathJax is enabled you can set the default output format to be used for the MathJax output.

When MathJax is enabled you need to specify the location relative to the HTML output directory using the mathjax_relpath option.

The mathjax_extensions tag can be used to specify one or more MathJax extension names that should be enabled during MathJax rendering.

The mathjax_codefile tag can be used to specify a file with JavaScript pieces of code that will be used on startup of the MathJax code.

When the searchengine tag is enabled Doxygen will generate a search box for the HTML output.

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.

When external_search tag is enabled Doxygen will no longer generate the PHP script for searching.

The searchengine_url should point to a search engine hosted by a web server which will return the search results when external_search is enabled.

When server_based_search and external_search are both enabled the unindexed search data is written to a file for indexing by an external tool.

When server_based_search and external_search are both enabled the external_search_id tag can be used as an identifier for the project.

The extra_search_mappings tag can be used to enable searching through Doxygen projects other than the one defined by this configuration file, but that are all added to the same external search index.

If the generate_latex tag is set to True, Doxygen will generate LaTeX output.

The latex_output tag is used to specify where the LaTeX docs will be put.

The latex_cmd_name tag can be used to specify the LaTeX command name to be invoked.

The makeindex_cmd_name tag can be used to specify the command name to generate index for LaTeX.

The latex_makeindex_cmd tag can be used to specify the command name to generate index for LaTeX.

If the compact_latex tag is set to True, Doxygen generates more compact LaTeX documents.

The paper_type tag can be used to set the paper type that is used by the printer.

The extra_packages tag can be used to specify one or more LaTeX package names that should be included in the LaTeX output.

The latex_header tag can be used to specify a user-defined LaTeX header for the generated LaTeX document.

The latex_footer tag can be used to specify a user-defined LaTeX footer for the generated LaTeX document.

The latex_extra_stylesheet tag can be used to specify additional user-defined LaTeX style sheets that are included after the standard style sheets created by Doxygen.

The latex_extra_files tag can be used to specify one or more extra images or other source files which should be copied to the latex_output output directory.

If the pdf_hyperlinks tag is set to True, the LaTeX that is generated is prepared for conversion to PDF (using ps2pdf or pdflatex).

If the use_pdflatex tag is set to True, Doxygen will use the engine as specified with latex_cmd_name to generate the PDF file directly from the LaTeX files.

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

If the latex_hide_indices tag is set to True then Doxygen will not include the index chapters (such as File Index, Compound Index, etc.) in the output.

The latex_bib_style tag can be used to specify the style to use for the bibliography, e.g. plainnat, or ieeetr.

The latex_emoji_directory tag is used to specify the (relative or absolute) path from which the emoji images will be read.

If the generate_rtf tag is set to True, Doxygen will generate RTF output.

The rtf_output tag is used to specify where the RTF docs will be put.

If the compact_rtf tag is set to True, Doxygen generates more compact RTF documents.

If the rtf_hyperlinks tag is set to True, the RTF that is generated will contain hyperlink fields.

Load stylesheet definitions from file.

Set optional variables used in the generation of an RTF document.

The rtf_extra_files tag can be used to specify one or more extra images or other source files which should be copied to the rtf_output output directory.

If the generate_man tag is set to True, Doxygen will generate man pages for classes and files.

The man_output tag is used to specify where the man pages will be put.

The man_extension tag determines the extension that is added to the generated man pages.

The man_subdir tag determines the name of the directory created within man_output in which the man pages are placed.

If the man_links tag is set to True and Doxygen generates man output, then it will generate one additional man file for each entity documented in the real man page(s).

If the generate_xml tag is set to True, Doxygen will generate an XML file that captures the structure of the code including all documentation.

The xml_output tag is used to specify where the XML pages will be put.

If the xml_programlisting tag is set to True, Doxygen will dump the program listings (including syntax highlighting and cross-referencing information) to the XML output.

If the xml_ns_memb_file_scope tag is set to True, Doxygen will include namespace members in file scope as well, matching the HTML output.

If the generate_docbook tag is set to True, Doxygen will generate Docbook files that can be used to generate PDF.

The docbook_output tag is used to specify where the Docbook pages will be put.

If the generate_autogen_def tag is set to True, Doxygen will generate an AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures the structure of the code including all documentation.

If the generate_sqlite3 tag is set to True Doxygen will generate a Sqlite3 database with symbols found by Doxygen stored in tables.

The sqlite3_output tag is used to specify where the Sqlite3 database will be put.

The sqlite3_recreate_db tag is set to True, the existing doxygen_sqlite3.db database file will be recreated with each Doxygen run.

If the generate_perlmod tag is set to True, Doxygen will generate a Perl module file that captures the structure of the code including all documentation.

If the perlmod_latex tag is set to True, Doxygen will generate the necessary Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI output from the Perl module output.

If the perlmod_pretty tag is set to True, the Perl module output will be nicely formatted so it can be parsed by a human reader.

The names of the make variables in the generated doxyrules.make file are prefixed with the string contained in perlmod_makevar_prefix.

If the enable_preprocessing tag is set to True, Doxygen will evaluate all C-preprocessor directives found in the sources and include files.

If the macro_expansion tag is set to True, Doxygen will expand all macro names in the source code.

If the expand_only_predef and macro_expansion tags are both set to True then the macro expansion is limited to the macros specified with the predefined and expand_as_defined tags.

If the search_includes tag is set to True, the include files in the include_path will be searched if a #include is found.

The include_path tag can be used to specify one or more directories that contain include files that are not input files but should be processed by the preprocessor.

You can use the include_file_patterns tag to specify one or more wildcard patterns (like *.h and *.hpp) to filter out the header-files in the directories.

The predefined tag can be used to specify one or more macro names that are defined before the preprocessor is started (similar to the -D option of e.g. gcc).

If the macro_expansion and expand_only_predef tags are set to True then this tag can be used to specify a list of macro names that should be expanded.

If the skip_function_macros tag is set to True then Doxygen's preprocessor will 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.

The tagfiles tag can be used to specify one or more tag files.

When a file name is specified after generate_tagfile, Doxygen will create a tag file that is based on the input files it reads.

If the allexternals tag is set to True, all external classes and namespaces will be listed in the class and namespace index.

If the external_groups tag is set to True, all external groups will be listed in the topic index.

If the external_pages tag is set to True, all external pages will be listed in the related pages index.

If set to True the inheritance and collaboration graphs will hide inheritance and usage relations if the target is undocumented or is not a class.

If you set the have_dot tag to True then Doxygen will assume the dot tool is available from the path.

The dot_num_threads specifies the number of dot invocations Doxygen is allowed to run in parallel.

dot_common_attr is common attributes for nodes, edges and labels of subgraphs.

dot_edge_attr is concatenated with dot_common_attr.

dot_node_attr is concatenated with dot_common_attr.

You can set the path where dot can find font specified with fontname in dot_common_attr and others dot attributes.

If the dot_transparent tag is set to True, then the images generated by dot will have a transparent background.

If the class_graph tag is set to True or GRAPH or BUILTIN then Doxygen will generate a graph for each documented class showing the direct and indirect inheritance relations.

If the collaboration_graph tag is set to True then Doxygen will generate a graph for each documented class showing the direct and indirect implementation dependencies (inheritance, containment, and class references variables) of the class with other documented classes.

If the group_graphs tag is set to True then Doxygen will generate a graph for groups, showing the direct groups dependencies.

If the uml_look tag is set to True, Doxygen will generate inheritance and collaboration diagrams in a style similar to the OMG's Unified Modeling Language.

If the uml_look tag is enabled, the fields and methods are shown inside the class node.

If the uml_look tag is enabled, field labels are shown along the edge between two class nodes.

If the dot_uml_details tag is set to False, Doxygen will show attributes and methods without types and arguments in the UML graphs.

The dot_wrap_threshold tag can be used to set the maximum number of characters to display on a single line.

If the template_relations tag is set to True then the inheritance and collaboration graphs will show the relations between templates and their instances.

If the include_graph, enable_preprocessing and search_includes tags are set to True then Doxygen will generate a graph for each documented file showing the direct and indirect include dependencies of the file with other documented files.

If the included_by_graph, enable_preprocessing and search_includes tags are set to True then Doxygen will generate a graph for each documented file showing the direct and indirect include dependencies of the file with other documented files.

If the call_graph tag is set to True then Doxygen will generate a call dependency graph for every global function or class method.

If the caller_graph tag is set to True then Doxygen will generate a caller dependency graph for every global function or class method.

If the graphical_hierarchy tag is set to True then Doxygen will graphical hierarchy of all classes instead of a textual one.

If the directory_graph tag is set to True then Doxygen will show the dependencies a directory has on other directories in a graphical way.

The dir_graph_max_depth tag can be used to limit the maximum number of levels of child directories generated in directory dependency graphs by dot.

The dot_image_format tag can be used to set the image format of the images generated by dot.

If dot_image_format is set to svg, then this option can be set to True to enable generation of interactive SVG images that allow zooming and panning.

The dot_path tag can be used to specify the path where the dot tool can be found.

The dotfile_dirs tag can be used to specify one or more directories that contain dot files that are included in the documentation (see the \dotfile command).

You can include diagrams made with dia in Doxygen documentation.

The diafile_dirs tag can be used to specify one or more directories that contain dia files that are included in the documentation (see the \diafile command).

When using PlantUML, the plantuml_jar_path tag should be used to specify the path where java can find the plantuml.jar file or to the filename of jar file to be used.

When using PlantUML, the plantuml_cfg_file tag can be used to specify a configuration file for PlantUML.

When using PlantUML, the specified paths are searched for files specified by the !include statement in a PlantUML block.

The plantumlfile_dirs tag can be used to specify one or more directories that contain PlantUml files that are included in the documentation (see the \plantumlfile command).

The dot_graph_max_nodes tag can be used to set the maximum number of nodes that will be shown in the graph.

The max_dot_graph_depth tag can be used to set the maximum depth of the graphs generated by dot.

Set the dot_multi_targets tag to True to allow dot to generate multiple output files in one run (i.e. multiple -o and -T options on the command line).

If the generate_legend tag is set to True Doxygen will generate a legend page explaining the meaning of the various boxes and arrows in the dot generated graphs.

If the dot_cleanup tag is set to True, Doxygen will remove the intermediate files that are used to generate the various graphs.

You can define message sequence charts within Doxygen comments using the \msc command.

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).

Additional arguments to pass to the rule (e.g. visibility = ["//visibility:public"], tags = ["manual"])