public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, ezequiel@collabora.com,
	gjasny@googlemail.com, hverkuil@xs4all.nl,
	kieran.bingham@ideasonboard.com, nicolas@ndufresne.ca,
	p.zabel@pengutronix.de, rosenp@gmail.com, sakari.ailus@iki.fi,
	sean@mess.org, user.vdr@gmail.com,
	xavier.claessens@collabora.com
Subject: Re: [PATCH v7 0/5] Switch build system to meson
Date: Tue, 13 Sep 2022 01:26:31 +0300	[thread overview]
Message-ID: <Yx+yF3/9Q+cICUdD@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220912180454.1b956a3d@coco.lan>

Hi Mauro,

On Mon, Sep 12, 2022 at 06:04:54PM +0200, Mauro Carvalho Chehab wrote:
> Em Fri,  9 Sep 2022 16:44:07 +0300 Laurent Pinchart escreveu:
> 
> > Hello everybody,
> > 
> > This series is the latest (and greatest) attempt to switch v4l-utils
> > from autotools to meson.
> > 
> > Compared to v6, the first noticeable change is that fixups have been
> > squashed into their corresponding commit. Detailed changelogs are now
> > included in individual patches.
> > 
> > The second big change is that the last patch from v6 ("Makefile.am:
> > Distribute meson related files") got replaced by 5/5 which drops
> > autotools support, completing the switch from autotools to meson.
> > 
> > A branch that includes this series can be found at
> > 
> >         git://linuxtv.org/pinchartl/v4l-utils.git meson
> > 
> > Ariel D'Alessandro (4):
> >   Move README to markdown syntax
> >   Add support for meson building
> >   Copy Doxygen configuration file to doc/
> >   meson: Add support for doxygen documentation
> > 
> > Laurent Pinchart (1):
> >   Drop autoconf/automake support
> 
> With the risk or repeating myself a couple of times, I have no
> idea what was built with meson, when using the version from
> your repository:
> 
> 	git://linuxtv.org/pinchartl/v4l-utils.git meson
> 
> (which btw seems to have some patches that are different
> from the 5 ones you submitted) 

I think I've already pushed some fixes on that branch. There will be a
v8 on the list, I'll push a tag with the version number to avoid
confusion.

> as it doesn't provide anything similar to what current 
> autotools-based support provides:

Sorry for missing your comment before. Meson has a summary() function
that can generate similar output, I'll enable it in the next version.

> $ ./configure
> ...
> compile time options summary
> ============================
> 
>     Host OS                    : linux-gnu
>     X11                        : yes
>     GL                         : yes
>     glu                        : yes
>     libelf		       : yes
>     libjpeg                    : yes
>     libudev                    : yes
>     pthread                    : yes
>     QT version                 : v5.4 with QtGL
>     ALSA support               : yes
>     SDL support		       : yes
> 
>     build dynamic libs         : yes
>     build static libs          : yes
> 
>     gconv                      : no
> 
>     dynamic libv4l             : yes
>     v4l_plugins                : yes
>     v4l_wrappers               : yes
>     libdvbv5                   : yes
>     dvbv5-daemon               : yes
>     v4lutils                   : yes
>     qv4l2                      : yes
>     qvidcap                    : yes
>     v4l2-ctl uses libv4l       : yes
>     v4l2-ctl-32                : no
>     v4l2-compliance            : yes
>     v4l2-compliance uses libv4l: yes
>     v4l2-compliance-32         : no
>     BPF IR Decoders:           : no

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-09-12 22:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 13:44 [PATCH v7 0/5] Switch build system to meson Laurent Pinchart
2022-09-09 13:44 ` [PATCH v7 1/5] Move README to markdown syntax Laurent Pinchart
2022-09-09 13:44 ` [PATCH v7 2/5] Add support for meson building Laurent Pinchart
2022-09-09 13:44 ` [PATCH v7 3/5] Copy Doxygen configuration file to doc/ Laurent Pinchart
2022-09-09 13:44 ` [PATCH v7 4/5] meson: Add support for doxygen documentation Laurent Pinchart
2022-09-09 13:44 ` [PATCH v7 5/5] Drop autoconf/automake support Laurent Pinchart
2022-09-11  0:33 ` [PATCH v7 0/5] Switch build system to meson Laurent Pinchart
2022-09-11  2:17 ` Rosen Penev
2022-09-12 10:06   ` Laurent Pinchart
2023-02-11 17:12     ` Laurent Pinchart
2022-09-12 14:41 ` Gregor Jasny
2022-09-12 22:29   ` Laurent Pinchart
2022-09-13  6:54     ` Hans Verkuil
2022-09-13  7:04       ` Mauro Carvalho Chehab
2022-09-13  7:14         ` Mauro Carvalho Chehab
2022-09-13  7:15     ` Hans Verkuil
2022-09-13  8:51       ` Laurent Pinchart
2023-02-12  0:10         ` Laurent Pinchart
2022-09-13  8:52       ` Hans Verkuil
2022-09-12 16:04 ` Mauro Carvalho Chehab
2022-09-12 22:26   ` Laurent Pinchart [this message]
2022-09-23 10:54 ` Hans Verkuil
2023-02-11 20:41   ` Laurent Pinchart

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=Yx+yF3/9Q+cICUdD@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ezequiel@collabora.com \
    --cc=gjasny@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=rosenp@gmail.com \
    --cc=sakari.ailus@iki.fi \
    --cc=sean@mess.org \
    --cc=user.vdr@gmail.com \
    --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