From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Sean Young <sean@mess.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [RFC PATCH v4l-utils 0/1] Introduce the meson build system
Date: Mon, 16 Mar 2020 10:53:12 +0200 [thread overview]
Message-ID: <20200316085312.GN4732@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200315205421.28797-1-ezequiel@collabora.com>
Hi Ezequiel,
On Sun, Mar 15, 2020 at 05:54:20PM -0300, 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?), but otherwise tries to cover
> as much as possible.
>
> I'm sending this early patch, hoping to get some reviews
> and possibly some testing.
>
> Let me know what you think.
I like the concept :-) Is there a plan to drop autotools support ?
> Ezequiel Garcia (1):
> Add support for meson building
>
> gen-version.sh | 36 ++++++++++
> lib/libdvbv5/meson.build | 87 ++++++++++++++++++++++
> lib/libv4l2/meson.build | 43 +++++++++++
> lib/libv4lconvert/meson.build | 79 ++++++++++++++++++++
> lib/meson.build | 6 ++
> meson.build | 108 ++++++++++++++++++++++++++++
> meson_options.txt | 19 +++++
> utils/cec-compliance/meson.build | 39 ++++++++++
> utils/cec-ctl/meson.build | 33 +++++++++
> utils/cec-follower/meson.build | 35 +++++++++
> utils/gen_media_bus_format_codes.sh | 7 ++
> utils/gen_media_bus_format_names.sh | 7 ++
> utils/ir-ctl/meson.build | 30 ++++++++
> utils/libcecutil/meson.build | 46 ++++++++++++
> utils/media-ctl/meson.build | 35 +++++++++
> utils/meson.build | 32 +++++++++
> utils/v4l2-compliance/meson.build | 52 ++++++++++++++
> utils/v4l2-ctl/meson.build | 65 +++++++++++++++++
> version.h.in | 1 +
> 19 files changed, 760 insertions(+)
> create mode 100755 gen-version.sh
> create mode 100644 lib/libdvbv5/meson.build
> create mode 100644 lib/libv4l2/meson.build
> create mode 100644 lib/libv4lconvert/meson.build
> create mode 100644 lib/meson.build
> create mode 100644 meson.build
> create mode 100644 meson_options.txt
> create mode 100644 utils/cec-compliance/meson.build
> create mode 100644 utils/cec-ctl/meson.build
> create mode 100644 utils/cec-follower/meson.build
> create mode 100644 utils/gen_media_bus_format_codes.sh
> create mode 100644 utils/gen_media_bus_format_names.sh
> create mode 100644 utils/ir-ctl/meson.build
> create mode 100644 utils/libcecutil/meson.build
> create mode 100644 utils/media-ctl/meson.build
> create mode 100644 utils/meson.build
> create mode 100644 utils/v4l2-compliance/meson.build
> create mode 100644 utils/v4l2-ctl/meson.build
> create mode 100644 version.h.in
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-03-16 8:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 20:54 [RFC PATCH v4l-utils 0/1] Introduce the meson build system Ezequiel Garcia
2020-03-15 20:54 ` [RFC PATCH v4l-utils 1/1] Introduce support for meson building Ezequiel Garcia
2020-03-16 9:43 ` Laurent Pinchart
2020-03-16 18:44 ` Ezequiel Garcia
2020-03-16 18:07 ` Nicolas Dufresne
2020-03-21 13:11 ` Ezequiel Garcia
2020-03-25 10:26 ` Laurent Pinchart
2020-03-27 0:00 ` Nicolas Dufresne
2020-03-16 8:53 ` Laurent Pinchart [this message]
2020-03-16 9:25 ` [RFC PATCH v4l-utils 0/1] Introduce the meson build system Sean Young
2020-03-16 9:17 ` Hans Verkuil
2020-03-16 16:29 ` Ezequiel Garcia
2020-03-16 17:53 ` Nicolas Dufresne
2020-03-16 17:30 ` Mauro Carvalho Chehab
2020-03-16 17:32 ` Laurent Pinchart
2020-03-16 17:47 ` Nicolas Dufresne
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=20200316085312.GN4732@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sean@mess.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).