1e167a4aad
This patch makes the `make docs` directive incremental avoiding re-running the siphon when the source hasn't changed, and leveraging sphinx internal cache. It adds a `make rebuild-docs` directive for cases where this caching logic might break, e.g. in CI. The virtualenv doesn't also get recreated on each build, which might be enough when writing docs, provided automated process leverage its rebuild counterpart. Type: improvement Change-Id: Ie90de3adebeed017b249cad81c6c160719f71e8d Signed-off-by: Nathan Skrzypczak <nathan.skrzypczak@gmail.com> Signed-off-by: Dave Wallace <dwallacelf@gmail.com>
Building VPP Documents These instructions show how the VPP documentation sources are built. To build your files, you can either Create a Virtual Environment using virtualenv, which installs all the required applications for you. Create a Virtual Environment using virtualenv ============================ For more information on how to use the Python virtual environment check out https://packaging.python.org/guides/installing-using-pip-and-virtualenv Get the Documents ------------------------------ For example start with a clone of the vpp. $ git clone https://gerrit.fd.io/r/vpp $ cd vpp Install the virtual environment ---------------------------------------------- $ python -m pip install --user virtualenv $ python -m virtualenv env $ source env/bin/activate $ pip install -r docs/etc/requirements.txt $ cd docs Which installs all the required applications into it's own, isolated, virtual environment, so as to not interfere with other builds that may use different versions of software. Build the html files ---------------------------- Be sure you are in your vpp/docs directory, since that is where Sphinx will look for your conf.py file, and build the documents into an index.html file $ make html View the results ------------------------ If there are no errors during the build process, you should now have an index.html file in your vpp/docs/_build/html directory, which you can then view in your browser.