From: Gregor Jasny <gjasny@googlemail.com>
To: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>,
Xavier Claessens <xavier.claessens@collabora.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Ezequiel Garcia <ezequiel@collabora.com>
Cc: kieran.bingham@ideasonboard.com, linux-media@vger.kernel.org,
hverkuil@xs4all.nl, sean@mess.org, p.zabel@pengutronix.de,
nicolas@ndufresne.ca,
nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [PATCH v1 1/1] Add support for meson building
Date: Mon, 29 Jun 2020 20:56:54 +0200 [thread overview]
Message-ID: <6f598f9e-cb1b-2dd4-6a95-efe0895da0dc@googlemail.com> (raw)
In-Reply-To: <f4c5552e-c639-8e71-968e-1cd8fe5152cb@vanguardiasur.com.ar>
Hello,
On 6/25/20 8:52 PM, Ariel D'Alessandro wrote:
> The Doxygen m4 script provides several features, like:
>
> $ git grep 'DX_ARG_ABLE(' m4/ax_prog_doxygen.m4
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(doc, [generate any doxygen documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(dot, [generate graphics for doxygen
> documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(man, [generate doxygen manual pages],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(rtf, [generate doxygen RTF documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(xml, [generate doxygen XML documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(chm, [generate doxygen compressed HTML
> help documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(chi, [generate doxygen seperate
> compressed HTML help index file],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(html, [generate doxygen plain HTML
> documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(ps, [generate doxygen PostScript
> documentation],
> m4/ax_prog_doxygen.m4:DX_ARG_ABLE(pdf, [generate doxygen PDF documentation],
>
> I could port them all to meson and have options for each one. But, do we really
> need all of them or just a subset?
>
> For instance, from [0]:
>
> $ git grep CONFIGURE_FLAGS.*doxygen
> rules:CONFIGURE_FLAGS += --enable-doxygen-man --disable-doxygen-ps
> --disable-doxygen-pdf
I think we need html (Debian) and man (Fedora).
Thanks for looking into it!
-Gregor
next prev parent reply other threads:[~2020-06-29 21:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 13:33 [PATCH v1 0/1] Add support for meson building Ariel D'Alessandro
2020-06-18 13:33 ` [PATCH v1 1/1] " Ariel D'Alessandro
2020-06-18 13:57 ` Kieran Bingham
2020-06-18 14:06 ` Laurent Pinchart
2020-06-18 14:11 ` Kieran Bingham
2020-06-19 14:12 ` Ezequiel Garcia
2020-06-19 14:42 ` Laurent Pinchart
2020-06-19 18:40 ` Xavier Claessens
2020-06-20 4:45 ` VDRU VDRU
2020-06-22 18:07 ` Gregor Jasny
2020-06-22 19:09 ` Gregor Jasny
2020-06-23 17:26 ` Ariel D'Alessandro
2020-06-24 19:46 ` Gregor Jasny
2020-06-25 18:32 ` Ariel D'Alessandro
2020-06-29 18:44 ` Gregor Jasny
2020-07-03 2:15 ` Ariel D'Alessandro
2020-06-25 18:52 ` Ariel D'Alessandro
2020-06-29 18:56 ` Gregor Jasny [this message]
2020-07-08 5:48 ` Ariel D'Alessandro
2020-07-16 19:48 ` Gregor Jasny
2020-06-19 19:04 ` Xavier Claessens
2020-06-22 19:19 ` Ariel D'Alessandro
2020-06-19 12:10 ` [PATCH v1 0/1] " Sean Young
2020-06-19 14:09 ` Ezequiel Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f598f9e-cb1b-2dd4-6a95-efe0895da0dc@googlemail.com \
--to=gjasny@googlemail.com \
--cc=ariel@vanguardiasur.com.ar \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=sean@mess.org \
--cc=xavier.claessens@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox