diff options
authorJuergen Borleis <>2016-06-21 15:24:46 +0200
committerMichael Olbrich <>2016-06-21 17:07:10 +0200
commit8630be655dd89d20a6de10fd8eb25475d17f2b30 (patch)
parent5ce7a1877f3b0dcc9deb565562434295adceac66 (diff)
Doc: add a section how to generate the documentation
This also includes some hints how to extend and/or adapt the existing documentation. It defines the external dependencies to be able to build the documentation as well. Signed-off-by: Juergen Borleis <>
2 files changed, 74 insertions, 0 deletions
diff --git a/doc/daily_work_section.rst b/doc/daily_work_section.rst
index c5c963e4e..daec36dca 100644
--- a/doc/daily_work_section.rst
+++ b/doc/daily_work_section.rst
@@ -4,4 +4,5 @@ Various Aspects of Daily Work
.. include::
.. include::
.. include::
+.. include::
.. include::
diff --git a/doc/ b/doc/
new file mode 100644
index 000000000..59b69c01d
--- /dev/null
+++ b/doc/
@@ -0,0 +1,73 @@
+Integrate project specific Documentaion into the Manual
+PTXdist supports the ability to integrate project specific documentation
+into the final PTXdist manual. To do so, PTXdist handles file replacements and
+additions, while generating the documentation.
+File replacement is working in the same manner like for all other files in
+a PTXdist based project: a local file with the same name superseds a global file
+from PTXdist.
+With this mechanism we can replace existing PTXdist documentation or add new one.
+If we want to add a new global section to the manual we can copy the global
+PTXdist ``doc/index.rst`` file into our local ``doc/`` directory and adapt it
+To change or add things less intrusive we can do it on the various ``*.inc``
+files in the PTXdist's ``doc/`` directory which define the content of the
+For example to change the image createn section's content, we can copy the
+global PTXdist ``doc/`` into our local ``doc/`` directory and
+adapt it to the behaviour of our project.
+In the generic documentation source many text uses variables instead of fixed
+content. These variables are filled with values extracted from the current PTXdist
+project prior building the final documentation. Since PTXdist projects are bound
+to a defined PTXdist version and toolchain version, this kind of information is
+extracted from the current settings and substituted in the documentation. This
+behaviour ensures the documentaiton includes the project's exact definition to
+external dependencies.
+Refer the PTXdist file ``doc/`` for more information on variable
+substitution. This PTXdist global file can be superseded by a local copy as well.
+Requirements to build the Documentation
+ - *Liberation Sans/Liberation Sans Bold* or *DejaVu Sans/DejaVu Sans Bold*
+ (for the "Portable Document Format", e.g. PDF)
+ - *Inconsolata*, *DejaVu Sans Mono* or *Liberation Sans Mono*
+ (for the "Portable Document Format", e.g. PDF)
+ - *Sphinx* version 1.3.4, better 1.4.2 (for all kind of document formats)
+ - *TeX Live 2016* (for the "Portable Document Format", e.g. PDF)
+Building the Documentation
+PTXdist comes with support to generate *HTML* or *Portable Document Format* based
+documentation from the sources.
+The command:
+ $ ptxdist docs-html
+will build the HTML based documentation into ``Documentation/html`` and the entry
+file for this kind of documentation is ``Documentation/html/index.html``.
+The command:
+ $ ptxdist docs-latex
+will build the Latex based documentation which results into the final
+*Portable Document Format* document. This result can be found in