From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Ezequiel Garcia <ezequiel@collabora.com>,
Shuah Khan <shuah@kernel.org>,
sean@mess.org
Subject: Re: [RFC] Create test script(s?) for regression testing
Date: Wed, 07 Nov 2018 22:04:03 +0200 [thread overview]
Message-ID: <15267027.MHiCTJmF4z@avalon> (raw)
In-Reply-To: <20181107175320.640a8c74@coco.lan>
Hi Mauro,
On Wednesday, 7 November 2018 21:53:20 EET Mauro Carvalho Chehab wrote:
> Em Wed, 07 Nov 2018 21:35:32 +0200 Laurent Pinchart escreveu:
> > On Wednesday, 7 November 2018 21:10:35 EET Mauro Carvalho Chehab wrote:
[snip]
> >> I'm with Hans on that matter: better to start with an absolute minimum
> >> of dependencies (like just: make, autotools, c, c++, bash),
> >
> > On a site note, for a new project, we might want to move away from
> > autotools. cmake and meson are possible alternatives that are way less
> > painful.
>
> Each toolset has advantages or disadvantages. We all know how
> autotools can be painful.
>
> One bad thing with cmake is that they deprecate stuff. A long-live project
> usually require several" backward" compat stuff at cmake files in order
> to cope with different behaviors that change as cmake evolves.
I don't know how much of a problem that would be. My experience with cmake is
good so far, but I haven't used it in a large scale project with 10+ years of
contributions :-)
> I never used mason myself.
It's the build system we picked for libcamera, I expect to provide feedback in
the not too distant future.
[snip]
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-11-08 5:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 8:37 [RFC] Create test script(s?) for regression testing Hans Verkuil
2018-11-06 11:36 ` Sakari Ailus
2018-11-06 13:12 ` Laurent Pinchart
2018-11-06 13:56 ` Hans Verkuil
2018-11-06 19:58 ` Laurent Pinchart
2018-11-07 8:05 ` Hans Verkuil
2018-11-07 10:06 ` Laurent Pinchart
2018-11-07 19:10 ` Mauro Carvalho Chehab
2018-11-07 19:35 ` Laurent Pinchart
2018-11-07 19:53 ` Mauro Carvalho Chehab
2018-11-07 20:04 ` Laurent Pinchart [this message]
2018-11-07 21:03 ` Shuah Khan
2018-11-07 19:36 ` Ezequiel Garcia
2018-11-06 13:39 ` Ezequiel Garcia
2018-12-10 13:44 ` Hans Verkuil
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=15267027.MHiCTJmF4z@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sean@mess.org \
--cc=shuah@kernel.org \
/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.