When using conda the requirements in the main RTD yaml are ignored as it should be managed by conda. Conda docs indicate how to use pip in a conda environment, so migrate to that. Commit
|1 day ago|
|.github/workflows||2 weeks ago|
|breathe||2 weeks ago|
|documentation||1 day ago|
|examples||2 weeks ago|
|requirements||1 day ago|
|scripts||5 months ago|
|tests||5 months ago|
|.gitignore||4 months ago|
|.readthedocs.yaml||1 day ago|
|CHANGELOG.rst||2 weeks ago|
|CONTRIBUTING.rst||10 months ago|
|CONTRIBUTORS.rst||6 months ago|
|LICENSE||7 years ago|
|Makefile||5 months ago|
|README.rst||2 months ago|
|breathe-apidoc.py||9 months ago|
|mkrelease||1 year ago|
|mypy.ini||2 years ago|
|pyproject.toml||9 months ago|
|setup.cfg||9 months ago|
|setup.py||2 weeks ago|
Your technical docs, beautifully integrated
Sponsor: If you benefit from using Breathe as a company or an individual, you can financially support the Breathe project with recurring or one off contributions via Open Collective.
Breathe is a Sphinx plugin providing beautifully integrated Doxygen output in your user-facing documentation. It allows you to combine Doxygen's excellent technical understanding of your code base with the superb long form documentation output of the Sphinx system.
- Breathe packages on PyPI are PGP signed for Breathe >= v4.28.0.
- Breathe tarballs on GitHub are PGP signed for Breathe >= v4.29.0.
Breathe is available from github and PyPI, the Python Package Index. It can be installed with:
pip install breathe
The source for the documentation is in the
documentation folder if you want to built it and read it locally.
The testsuite can be run with:
The documentation also does a good effort of covering the available functionality with different examples. To build the documentation, run:
This will run doxygen over the example code and then run the Breathe documentation. View the results at:
Further to this if you want to compare the current documentation output against a previous state in order to check for regressions there is a
compare script in the
documentation folder. It takes two arguments which are two commit references that you'd like to compare. This means that all your changes have to be committed first. Also the script does not resolve state dependent references like
HEAD so provide concrete commit references like sha1s or branch names. A typical example is to compare your current branch output to master:
# Make sure all your changes are committed first cd documentation ./compare master my-branch
This will do a checkout and build at each commit and then run
meld against the resulting directories so you can see the differences introduced by your branch.
Breathe requires Python 3.6+, Sphinx 4.0+ and Doxygen 1.8+.
Mailing List Archives
The archive for the Google groups list can be found here.
Please post new questions as GitHub issues.
Projects Using Breathe
Examples of projects that use Breathe:
- Mozilla's DeepSpeech
- Microsoft's LightGBM
- Apache Arrow
- Espressif IoT Development Framework
- Zephyr Project
- Plaid ML
- Sony's Neural Network Libraries
mkrelease utility in the root of the repository.
Useful vim command for changelog conversion to the git tag format:
See CONTRIBUTORS for the full list.
- Dimitri van Heesch for Doxygen.
- Georg Brandl for Sphinx.
- David Goodger for Docutils and reStructuredText.
See the CHANGELOG.rst