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: Thu, 16 Jul 2020 21:48:47 +0200 [thread overview]
Message-ID: <d7f4925b-07ee-fe6a-e865-ca5985145dc3@googlemail.com> (raw)
In-Reply-To: <0d9bd469-d23d-cef0-9e69-ea0b57e3f3b8@vanguardiasur.com.ar>
Hello,
On 7/8/20 7:48 AM, Ariel D'Alessandro wrote:
> I've pushed meson Doxygen support to:
> https://gitlab.com/adalessandro/v4l-utils/-/tree/v4l-utils-1.20.0-meson-v1
>
> The following options were added, supporting html and man.
>
> # Doxygen options
> option('doxygen-doc', type : 'feature', value : 'auto',
> description : 'Generate doxygen project documentation')
> option('doxygen-html', type : 'boolean',
> description : 'Generate doxygen plain HTML documentation')
> option('doxygen-man', type : 'boolean', value : false,
> description : 'Generate doxygen manual pages')
>
> So, you should get html and man documentation using:
>
> CONFIGURE_FLAGS += -Ddoxygen-doc=enabled -Ddoxygen-man=enabled
>
> Note that documentation will be installed to:
>
> doxygen_install_dir = join_paths(get_option('datadir'), 'doc',
> '@0@-@1@'.format(meson.project_name(),
> as_version))
>
> Using default values, that'd be: /usr/local/share/doc/v4l-utils-1.20.0/
I changed the code above to omit the version and now I have working
Debian packages. I need to test the packages on a real Linux Desktop but
that will have to wait until I can re-enter our offices.
Acked-by: Gregor Jasny <gjasny@googlemail.com>
Thanks,
Gregor
next prev parent reply other threads:[~2020-07-16 19:48 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
2020-07-08 5:48 ` Ariel D'Alessandro
2020-07-16 19:48 ` Gregor Jasny [this message]
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=d7f4925b-07ee-fe6a-e865-ca5985145dc3@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