You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source code is documented ether via doxygen-like comments (this holds true for the c++ code) or via python docstrings. It might (!) be a good idea to include this documentation in an automatic fashion in the readthedocs documentation.
The text was updated successfully, but these errors were encountered:
While the offline build works fine, integration with readthedocs does not. That is, there is no documentation generated from the docstrings online accessible. One idea to get this going is to tell readthedocs to build khuri. However, this is not straightforward, for the building process requires cmake and external libraries.
Is there an easy way to have the api documenation online?
The source code is documented ether via doxygen-like comments (this holds true for the c++ code) or via python docstrings. It might (!) be a good idea to include this documentation in an automatic fashion in the readthedocs documentation.
The text was updated successfully, but these errors were encountered: