Show More
@@ -16,7 +16,7 b' Requirements' | |||
|
16 | 16 | |
|
17 | 17 | The documentation must be built using Python 3. |
|
18 | 18 | |
|
19 |
In addition |
|
|
19 | In addition to :ref:``devinstall``, | |
|
20 | 20 | the following tools are needed to build the documentation: |
|
21 | 21 | |
|
22 | 22 | - sphinx |
@@ -40,7 +40,7 b' html``.' | |||
|
40 | 40 | |
|
41 | 41 | ``make html_noapi`` - same as above, but without running the auto-generated API |
|
42 | 42 | docs. When you are working on the narrative documentation, the most time |
|
43 | consuming portion of the build process is the processing and rending of the | |
|
43 | consuming portion of the build process is the processing and rendering of the | |
|
44 | 44 | API documentation. This build target skips that. |
|
45 | 45 | |
|
46 | 46 | ``make pdf`` will compile a pdf from the documentation. |
@@ -53,7 +53,7 b' previous docs build.' | |||
|
53 | 53 | To remove the previous docs build you can use ``make clean``. |
|
54 | 54 | You can also combine ``clean`` with other `make` commands; |
|
55 | 55 | for example, |
|
56 | ``make clean html`` will do a complete rebuild of the docs or `make clean pdf` will do a complete build of the pdf. | |
|
56 | ``make clean html`` will do a complete rebuild of the docs or ``make clean pdf`` will do a complete build of the pdf. | |
|
57 | 57 | |
|
58 | 58 | |
|
59 | 59 | Continuous Integration |
General Comments 0
You need to be logged in to leave comments.
Login now