-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
No doxygen output generated with breathe #6795
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
Comments
@floriantschopp we don't execute the make file, we only execute the sphinx-build command as you can see in https://readthedocs.org/projects/maplab/builds/10637813/. |
I just tried to reproduce the exact same setup that is documented in the build log using the same |
@stsewd Anything else I can try? Thanks a lot for your assistance. |
@floriantschopp sorry, not sure what else to try. When you try locally, did you try in a clean directory? (removing all previous generated files, like |
Yea, I built it on a clean directory. |
FYI: I worked around this by using sphinx-multiversion and a self-hosted documentation. |
@floriantschopp from your build output, it seems that breathe is not well configured and it's not finding the source code of the API to document.
From the RTD's output it seems that you are not checking out the submodules and I guess the API you want to document using doxygen is there. |
Hi everyone,
I have a problem when trying to our local build of the maplab documentation to readthedocs.org
When using the Makefile locally, the build takes quite some time and results in successfully (with some warnings but I can fix them later) building the API documentation. On readthedocs, the build is also successful (very fast) but skips the API part. From the build logs, I cannot find a trace of why this could be happening.
I read #5144, #5145, #5076 and #2958 but without finding my issue.
Any help is highly appreciated.
Details
Expected Result
API documentation is generated using doxygen (with breathe/exhale)
Actual Result
Doxygen returns empty.
The text was updated successfully, but these errors were encountered: