docs: Add --generate-md to the gdbus-codegen documentation

Add it to the documentation the same way it is done for reStructured and docbook.
This commit is contained in:
Corentin Noël 2024-12-12 11:51:49 +00:00 committed by Philip Withnall
parent 67b5a37f2b
commit 2021e20a8a

View File

@ -39,6 +39,7 @@ SYNOPSIS
| [--c-generate-autocleanup none|objects|all]
| [--output-directory *OUTDIR* | --output *OUTFILE*]
| [--generate-docbook *OUTFILES*]
| [--generate-md *OUTFILES*]
| [--generate-rst *OUTFILES*]
| [--pragma-once]
| [--xml-files *FILE*]
@ -120,6 +121,12 @@ Each generated DocBook XML file (see the ``--generate-docbook`` option for
details) is a ``RefEntry`` article describing the D-Bus interface. (See the
`DocBook documentation <https://tdg.docbook.org/tdg/4.5/refentry.html>`_.)
GENERATING MARKDOWN DOCUMENTATION
-----------------------------------------
Each generated Markdown file (see the ``--generate-md`` option for
details) is a plain text Markdown document describing the D-Bus interface.
GENERATING RESTRUCTUREDTEXT DOCUMENTATION
-----------------------------------------
@ -157,6 +164,15 @@ The following options are supported:
Pass ``--output-directory`` to specify the directory to put the output files
in. By default the current directory will be used.
``--generate-md`` *OUTFILES*
Generate Markdown Documentation for each D-Bus interface and put it in
``OUTFILES-NAME.md`` where ``NAME`` is a placeholder for the interface
name, e.g. ``net.Corp.FooBar`` and so on.
Pass ``--output-directory`` to specify the directory to put the output files
in. By default the current directory will be used.
``--generate-rst`` *OUTFILES*
Generate reStructuredText Documentation for each D-Bus interface and put it in