d95f260aee
We don't currently document the syntax of .hx files anywhere except in a few comments at the top of individual .hx files. We don't even have somewhere in the developer docs where we could do this. Add a new files docs/devel/docs.rst which can be a place to document how our docs build process works. For the moment, put in only a brief introductory paragraph and the documentation of the .hx files. We could later add to this file by for example describing how the QAPI-schema-to-docs process works, or anything else that developers might need to know about how to add documentation. Make the .hx files refer to this doc file, and clean up their header comments to be more accurate for the usage in each file and less cut-n-pasted. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Luc Michel <luc.michel@amd.com> Reviewed-by: David Woodhouse <dwmw@amazon.co.uk> Message-id: 20231212162313.1742462-1-peter.maydell@linaro.org
21 lines
417 B
ReStructuredText
21 lines
417 B
ReStructuredText
QEMU Build and Test System
|
|
--------------------------
|
|
|
|
Details about how QEMU's build system works and how it is integrated
|
|
into our testing infrastructure. You will need to understand some of
|
|
the basics if you are adding new files and targets to the build.
|
|
|
|
.. toctree::
|
|
:maxdepth: 3
|
|
|
|
build-system
|
|
kconfig
|
|
docs
|
|
testing
|
|
acpi-bits
|
|
qtest
|
|
ci
|
|
qapi-code-gen
|
|
fuzzing
|
|
control-flow-integrity
|