Documentation generator for C++ based on Doxygen and mosra/m.css.

• Overview
• Example
• Installation
• Usage
• Config file options
• Migrating from Doxygen
• Why the name "Poxy"?
• License and Attribution

mosra/m.css is a Doxygen-based documentation generator that significantly improves on Doxygen's default output by controlling some of Doxygen's more unruly options, supplying it's own slick HTML+CSS generation and adding a fantastic live search feature. Poxy builds upon both by:

• Moving the configuration out into a TOML file
• Preprocessing the Doxygen XML to fix a bunch of Doxygen bugs quirks
• Postprocessing the generated HTML to improve syntax highlighting and add a few other improvements
• Allowing source, image and example directories to be recursive or shallow on a per-directory basis
• Automatically defining C++ language feature macros based on your project's target C++ version
• Automatically integrating the cppreference.com doxygen tagfile
• Providing a number of additional built-in doxygen @alias commands
• Giving more control over the HTML inline using square-bracket [tags][/tags]
• Adding a switchable light theme
• Adding support for C++20 concepts
• Self-hosting fonts to reduce external HTTP requests
• Inlining SVGs so they can take advantage of currentColor
• Quite a bit more!

The homepage + documentation for toml++ is built using poxy:

• homepage: marzer.github.io/tomlplusplus
• config file: poxy.toml

• Python 3.7+
• Doxygen 1.8.20+ (must be visible on system path)

pip install poxy

Poxy is a command-line application.

usage: poxy [-h] [-v] [--html | --no-html] [--ppinclude <regex>] [--ppexclude <regex>]
            [--theme {light,dark,custom}] [--threads N] [--version] [--xml | --no-xml]
            [--werror | --no-werror] [--bug-report]
            [config]

  _ __   _____  ___   _
 | '_ \ / _ \ \/ / | | |
 | |_) | (_) >  <| |_| |
 | .__/ \___/_/\_\\__, |
 | |               __/ |
 |_|              |___/  v0.12.0 - github.com/marzer/poxy

Generate fancy C++ documentation.

positional arguments:
  config                path to poxy.toml or a directory containing it (default: .)

options:
  -h, --help            show this help message and exit
  -v, --verbose         enable very noisy diagnostic output
  --html, --no-html     specify whether HTML output is required (default: True)
  --ppinclude <regex>   pattern matching HTML file names to post-process (default: all)
  --ppexclude <regex>   pattern matching HTML file names to exclude from post-processing (default: none)
  --theme {light,dark,custom}
                        override the default visual theme (default: read from config)
  --threads N           set the number of threads to use (default: automatic)
  --version             print the version and exit
  --xml, --no-xml       specify whether XML output is required (default: False)
  --werror, --no-werror
                        override the treating of warnings as errors (default: read from config)
  --bug-report          captures all output in a zip file for easier bug reporting.

The basic three-step to using Poxy is similar to Doxygen:

1. Create your poxy.toml (Poxy's answer to the Doxyfile)
2. Invoke Poxy on it: poxy path/to/poxy.toml (or simply poxy if the cwd contains the config file)
3. See your HTML documentation <cwd>/html

For a self-contained poxy.toml example to copy and paste from, see the one used by toml++.

For a full list of options, with full descriptions, schemas and usage examples, see the Configuration options wiki page.

Generally the relevant Doxyfile options will have a corresponding poxy.toml option (or be replaced by something more specific) so migration is largely a transcription and box-ticking exercise, though there are a few gotchas:

Many of Doxygen's various knobs and switches are manually overridden by Poxy, and are not configurable. This is intentional! Doxygen tends to break in hilarious and fantastic ways from one release to the next; reducing it to a very 'locked-down' back-end minimizes the damage future regressions can do, allowing me to keep most debugging python-side.

If there is some Doxygen feature you would like exposed in Poxy, please create a feature request.

This is in contrast to Doxygen, which has all paths be relative to the Doxygen process' current working directory regardless of where the Doxyfile was. I've always personally found that to be nothing but a source of error, so Poxy does away with it.

Poxy always emits HTML to <cwd>/html and XML to <cwd>/xml. You cannot use your config file to specify where any output will be placed - use your command-line environment for this purpose instead by changing the CWD. This is to eliminate nasty surprises brought on by goofy config file decisions and help with portability.

There is no equivalent to Doxygen's @INCLUDE. If your project is structured in such a way that a multi-level Doxyfile hierarchy is necessary, Poxy isn't for you.

Originally it was simply called "dox", but there's already a C++ documentation project with that name, so I smashed "python" and "dox" together and this is what I came up with.

Also "poxy" can be slang for cheap, inferior, poor quality, etc., which I thought was funny.

This project is published under the terms of the MIT license.

Significant credit must go to Vladimír Vondruš (mosra) and his amazing m.css Doxygen theme. Poxy bundles a fork of m.css, used per the MIT/Expat license (which can also be found in the installed python package).