Re: [RFC PATCH v4l-utils 0/1] Introduce the meson build system

[Nicolas Dufresne <nicolas@ndufresne.ca>]

Le lundi 16 mars 2020 à 13:29 -0300, Ezequiel Garcia a écrit :
> Hi Hans,
> 
> On Mon, 2020-03-16 at 10:17 +0100, Hans Verkuil wrote:
> > On 3/15/20 9:54 PM, Ezequiel Garcia wrote:
> > > Here's a first step towards using meson:
> > > 
> > >     https://mesonbuild.com/
> > > 
> > > As you can see, this doesn't include all tools and libraries
> > > (are there any libv4l1 users?),
> > 
> > Probably yes.
> > 
> >  but otherwise tries to cover
> > > as much as possible.
> > 
> > Last week I added options to build 32 bit variants of v4l2-ctl and v4l2-compliance,
> > it will be interesting to see how meson does that.
> > 
> > I'm not opposed to changing over to meson, but then the old system has to be removed
> > either at the same time or in a second patch.
> > 
> 
> I think some projects kept autotools for a while until the
> transition to meson is complete.
> 
> Any reason why we'd have to do the transition atomically?

Having two (or more) build systems is usually of great pain. In
GStreamer we went that route as we had to develop some extra features
into Meson to support our much more complex use case. Today, meson is
mature enough to allow a quick transition. Of course, having patches
merged with few days of delay helps if you have CI and other Bot to
update. An atomic transition would cause downtime in that context.

> 
> Thanks,
> Ezequiel
>