You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
suricata/doc/devguide
Jason Ish b9a429e6ce devguide: move image generation into sphinx setup
While ReadTheDocs can't execute arbitrary scripts, we can install
mscgen in the container that builds the docs (see .readthedocs.yaml).

Then instead of calling generate-images.sh from the Makefile, move this
into the setup function defined on conf.yaml, which will generate the
scripts as part of a normal Sphinx workflow.

This should give us an image generation solution that works on
ReadTheDocs, and locally within anyones build system provided they have
mscgen installed.
4 years ago
..
_static
codebase devguide: add page about rust unittests 4 years ago
extending doc/devguide: add few more explanations & details 4 years ago
internals
tools devguide: move image generation into sphinx setup 4 years ago
.gitignore devguide/app-layer: rename /img dir to /diagrams 4 years ago
Makefile.am devguide: move image generation into sphinx setup 4 years ago
Makefile.sphinx doc/devguide: add Transactions documentation page 4 years ago
README.md
conf.py devguide: move image generation into sphinx setup 4 years ago
index.rst

README.md

Suricata Developer Guide

This directory contains the Suricata Developer Guide. The Sphinx Document Generator is used to build the documentation. For a primer os reStructuredText see the reStructuredText Primer.

Verifying Changes

There are a number of output formats to choose from when making the source documentation locally (e.g. html, pdf, man).

The documentation source can be built with make -f Makefile.sphinx html. Substitute the 'html' word for desired output format.

There are different application dependencies based on the output desired.