All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Gregor Jasny <gjasny@googlemail.com>,
	linux-media@vger.kernel.org, hverkuil@xs4all.nl, sean@mess.org,
	p.zabel@pengutronix.de, ezequiel@collabora.com,
	nicolas@ndufresne.ca, kieran.bingham@ideasonboard.com,
	xavier.claessens@collabora.com, nicolas.dufresne@collabora.com,
	user.vdr@gmail.com, sakari.ailus@iki.fi
Subject: Re: [v4l-utils v4 2/5] Add support for meson building
Date: Sat, 24 Apr 2021 01:34:07 +0300	[thread overview]
Message-ID: <YINLX5xd8/16gNYZ@pendragon.ideasonboard.com> (raw)
In-Reply-To: <5eb90b59-8896-ae22-690f-340f4ec9d8db@collabora.com>

Hi Ariel,

On Fri, Apr 23, 2021 at 07:31:01PM -0300, Ariel D'Alessandro wrote:
> Hi Mauro, Laurent,
> 
> I can see this thread didn't follow up.
> 
> Regarding Mauro's reasons about why not switching to meson, I totally 
> agree with this response from Laurent's. I don't see any of those 
> aspects being really an argument on why not supporting meson, but in any 
> case, discussion can follow up from there.
> 
> On 3/20/21 5:01 PM, Laurent Pinchart wrote:
> > Hi Mauro,
> > 
> > On Sat, Mar 20, 2021 at 08:32:09PM +0100, Mauro Carvalho Chehab wrote:
> [snip]
> >>
> >> I'm not a lover of autoconf tools. Yet, replacing from it on this
> >> project sounds a bad idea, for a couple of reasons.
> >>
> >> The main one is that nobody has yet provided any real reason about
> >> *why* auto-tools should be replaced.
> 
> IMHO, switching from autotools to meson has many advantages, like a 
> clear syntax, an active community and *faster* build speed than autotools.
> 
> On a cold cache:
> 
>    $ time (meson setup build/ -Ddefault_library=both ; ninja -j4 -C build/)
>    real 0m15.945s ; user 0m51.235s ; sys 0m6.914s
> 
>    $ time (./configure ; make -j4)
>    real 0m45.985s ; user 1m57.454s ; sys 0m9.404s
> 
> Although I haven't been involved in v4l-utils previously, I can see some 
> people interested on having meson build support, I'm not the only one 
> involved in this patchset.
> 
> I understand that every change comes with a cost, but I believe meson's 
> been adopted for some time now, other projects have already done the 
> move, and the advantages overcome the possible negative aspects 
> mentioned. Again, this is just my humble opinion, and to me that's the 
> *why* porting to meson is a good idea :-)
> 
> I'd like to hear for other reasons.

Gregor, you've provided feedback on the implementation (thanks about
that), but I don't think I've seen your opinion about the switch to
meson itself. Have I missed it, and if I haven't, could you share your
thoughts ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2021-04-23 22:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 17:22 [v4l-utils v4 0/5] Add support for meson building Ariel D'Alessandro
2021-03-17 17:22 ` [v4l-utils v4 1/5] Move README to markdown syntax Ariel D'Alessandro
2021-03-17 17:22 ` [v4l-utils v4 2/5] Add support for meson building Ariel D'Alessandro
2021-03-20 16:56   ` Gregor Jasny
2021-03-20 19:32     ` Mauro Carvalho Chehab
2021-03-20 20:01       ` Laurent Pinchart
2021-04-23 22:31         ` Ariel D'Alessandro
2021-04-23 22:34           ` Laurent Pinchart [this message]
2021-04-23 21:02     ` Ariel D'Alessandro
2021-04-29  2:11       ` Rosen Penev
2021-05-12 13:44         ` Ariel D'Alessandro
2021-03-21 11:16   ` Laurent Pinchart
2021-03-17 17:22 ` [v4l-utils v4 3/5] Copy Doxygen configuration file to doc/ Ariel D'Alessandro
2021-03-17 17:22 ` [v4l-utils v4 4/5] meson: Add support for doxygen documentation Ariel D'Alessandro
2021-03-17 17:22 ` [v4l-utils v4 5/5] Makefile.am: Distribute meson related files Ariel D'Alessandro

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=YINLX5xd8/16gNYZ@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ariel.dalessandro@collabora.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+huawei@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.