For my optional sage package [1], the last time I spent time building its documentation using Sage, I ended up with these command in my makefile, which calls a sphinx makefile:
cd docs && sage -sh -c "make html" cd docs && sage -sh -c "make latexpdf" For now, I am not using sage_autodoc extension. So *.rst files are not generated automatically as they are in Sage doc tree. [1] https://github.com/seblabbe/slabbe On Saturday, August 27, 2016 at 2:40:26 PM UTC+2, Simon King wrote: > > Hi! > > It has been a long time since I was considering Sage's doc builder. So, > please allow me to ask, since it is conceivable that I missed recent > developments: > > - Assume you have bunch of cython and python files sitting in a folder > that is not part of the SageMath src tree. Think of a pip-installable > package. Its docstrings are complient with what we do in the src tree. > It used to be the case that SageMath packages could provide > documentation in SAGE_ROOT/local/share/doc. How can I use Sage's > doc-builder to that aim? My old solution of using a modified copy > of a very outdated version of Sage's doc-builder shipped with my spkg > certainly isn't a good solution. > - Is it possible to have links from the package's documentation to > SageMath's documentation? IIRC, it used to be a problem, but perhaps > it works now. > > Best regards, > Simon > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
