From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Gregor Jasny <gjasny@googlemail.com>,
linux-media@vger.kernel.org, ezequiel@collabora.com,
kieran.bingham@ideasonboard.com, mchehab@kernel.org,
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: Sun, 12 Feb 2023 02:10:35 +0200 [thread overview]
Message-ID: <Y+gue3R+x6GWPORv@pendragon.ideasonboard.com> (raw)
In-Reply-To: <YyBEdPGpsVMIP9dq@pendragon.ideasonboard.com>
Hi Hans,
On Tue, Sep 13, 2022 at 11:51:01AM +0300, Laurent Pinchart wrote:
> On Tue, Sep 13, 2022 at 08:15:43AM +0100, Hans Verkuil wrote:
> > On 9/12/22 23:29, Laurent Pinchart wrote:
> > > On Mon, Sep 12, 2022 at 04:41:33PM +0200, Gregor Jasny wrote:
> > >> Hello Laurent and all the other helping hands,
> > >>
> > >> On 9/9/22 3:44 PM, Laurent Pinchart wrote:
> > >>> 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.
> > >>
> > >> Tested-by: Gregor Jasny <gjasny@googlemail.com>
> > >>
> > >> v7 is still working as expected with my Debian and Ubuntu packaging scripts.
> > >
> > > Thanks for testing. I'll post a v8 with the improvements suggested in
> > > the review comments. I will also include updates to the
> > > v4l-utils.spec.in file, and would appreciate help testing it.
> > >
> > >> What would you think would be a good time to release these changes?
> > >> Should I do a release shortly after the this change has landed?
> > >
> > > I think that would be a good idea. Once v8 is out, if there are no more
> > > issues, I think it could be merged.
> >
> > Two questions: for meson, what is the equivalent to 'make distclean'?
> > Just rm -rf build?
>
> That's correct. Meson doesn't make *any* change to the source directory.
>
> > And another: if I enable building for v4l2-ctl-32 and
> > v4l2-compliance-32, then those targets aren't build AFAICS.
>
> I'll check that (a bit busy this week with ELC and LPC).
They get built for me. I've rebased meson support on top of the latest
master branch and fixed lots of small issues, so I may have fixed this
at the same time. I'll post v8 soon, if you still experience the
problem, I'll debug it with you.
> > It's needed for testing 32-bit compat code.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-02-12 0:10 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 [this message]
2022-09-13 8:52 ` Hans Verkuil
2022-09-12 16:04 ` Mauro Carvalho Chehab
2022-09-12 22:26 ` Laurent Pinchart
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=Y+gue3R+x6GWPORv@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