Linux Media Controller development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: kieran.bingham@ideasonboard.com,
	Ariel D'Alessandro <ariel@vanguardiasur.com.ar>,
	linux-media@vger.kernel.org, hverkuil@xs4all.nl, sean@mess.org,
	p.zabel@pengutronix.de, nicolas@ndufresne.ca,
	gjasny@googlemail.com,
	nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Xavier Claessens <xavier.claessens@collabora.com>
Subject: Re: [PATCH v1 1/1] Add support for meson building
Date: Fri, 19 Jun 2020 17:42:29 +0300	[thread overview]
Message-ID: <20200619144229.GD5823@pendragon.ideasonboard.com> (raw)
In-Reply-To: <f2bf8846e265024c20a77fa618d54455b3b7ca95.camel@collabora.com>

Hi Ezequiel,

On Fri, Jun 19, 2020 at 11:12:58AM -0300, Ezequiel Garcia wrote:
> +Xavier, Nicolas
> 
> On Thu, 2020-06-18 at 14:57 +0100, Kieran Bingham wrote:
> > Hi Ariel,
> > 
> > Wow there's a lot of work there! That must have taken quite some effort
> > between you and Ezequiel!
> > 
> 
> (: I don't remember having done much, so all kudos must go to Ariel.
>  
> > I've looked through, and about the only thing that stands out to me is
> > the way you're joining strings.
> > 
> > Meson provides a join_paths() function specifically for that.
> > Now we're "probably" not going to build this library on anything other
> > than linux, but I think the function still has merit over the arbitrary
> > strings which I mis-interpreted for 'divide' at first glance :S
> > 
> > Other than that, I expect we will have to run both build systems in
> > parallel for some time to allow packaging and other builders to adapt.
> > That might mean it's a bit more difficult to make sure both build
> > systems are updated when adding new files or changing the build in anyway.
> 
> Why?
> 
> Is it too naive to expect that's it's safe to just turn the flip on meson,
> and remove autotools?
> 
> Everyone doing packaging is already aware and used to meson.

If we add meson as an option and keep autotools supported in parallel,
there's a high change packagers won't notice, so it won't help much. I'd
recommend reaching out to known packagers (major distros, buildroot,
...) to let them know of the move. If any of them requests to have time
to adapt, then we could support both build systems in parallel.
Otherwise, I'd just flip the switch.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-06-19 16:44 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 [this message]
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
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=20200619144229.GD5823@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ariel@vanguardiasur.com.ar \
    --cc=ezequiel@collabora.com \
    --cc=gjasny@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kieran.bingham@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