-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Doxygen developer documentation available via readthedocs #1844
Comments
Hi Considering the changes to how the docs will be built after #1843 , I was wondering if it made sense to do the following
I wanted to try out the process (in a very rough fashion) so I created a branch based off of @jougs' branch for #1843. I then modified the normaldoc file, so running Of course the other problem mentioned is not getting output on ReadtheDocs So that's what I have so far. @jougs @steffengraber what do you think? |
Please see #1905 for a proposal related to this
Also see #1905. And I like your proposal regarding XML as the intermediate format |
Issue automatically marked stale! |
This issue should wait until #2560 is merged becaue it makes huge changes to the conf.py file and affects the build of the docs. |
Issue automatically marked stale! |
Before #1843, NEST used the Breathe extension for Sphinx to extract the Doxygen code comments from the source base. However, the extracted information was not (and still isn't) shown on Read the Docs.
The main task for solving this issue is to decide how and where in the documentation to display the developer level information and making the necessary changes to the configuration and build system. Activating the Breathe extension itself involves the following steps:
Doxyfile
to thedoc
directory. See here for the version that was removed in Fix doc buildsystem #1843."breathe"
to theextensions
list defined indoc/conf.py:L117
doc/conf.py
:This issue might or might not have a connection to some of the action items in #1659.
The text was updated successfully, but these errors were encountered: