From: Sean Young <sean@mess.org>
To: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
p.zabel@pengutronix.de, laurent.pinchart@ideasonboard.com,
ezequiel@collabora.com, nicolas@ndufresne.ca,
kieran.bingham@ideasonboard.com, gjasny@googlemail.com
Subject: Re: [PATCH v1 0/1] Add support for meson building
Date: Fri, 19 Jun 2020 13:10:13 +0100 [thread overview]
Message-ID: <20200619121013.GA14721@gofer.mess.org> (raw)
In-Reply-To: <20200618133303.28676-1-ariel@vanguardiasur.com.ar>
On Thu, Jun 18, 2020 at 10:33:02AM -0300, Ariel D'Alessandro wrote:
> Hi all,
>
> After a couple of RFCs, here's the final patchset adding support for the
> meson build system.
>
> All functionality provided by the autotools based build was ported to
> meson, except sync-with-kernel. I guess we can add it at some later
> point and have this merged anyway.
sync-with-kernel is a few fragments of shell that live in various parts
of the tree (Makefiles). It's just static shell, the build system doesn't
need to do any substitions.
I think sync-with-kernel doesn't really belong in the build system; This
can be moved into its own shell script.
> Native and cross compilation has been tested with several options. Any
> feedback, testing or suggestions are welcome. Looking forward to see
> this merged in the next release hopefully :-)
>
> Here's a simple comparison between meson and autotools performance for a
> native build:
>
> $ time meson build/
> [...]
> real 0m3.172s
> user 0m2.698s
> sys 0m0.577s
> $ time ninja -C build/ -j4
> [...]
> real 0m19.533s
> user 1m11.860s
> sys 0m7.956s
>
> $ time (./bootstrap.sh && ./configure)
> [...]
> real 0m19.289s
> user 0m16.448s
> sys 0m2.756s
> $ time make -j4
> [...]
> real 0m55.250s
> user 2m29.425s
> sys 0m10.829s
Nice! This will really help when I'm testing on the rpi.
Sean
next prev parent reply other threads:[~2020-06-19 12:10 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
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 ` Sean Young [this message]
2020-06-19 14:09 ` [PATCH v1 0/1] " 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=20200619121013.GA14721@gofer.mess.org \
--to=sean@mess.org \
--cc=ariel@vanguardiasur.com.ar \
--cc=ezequiel@collabora.com \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
/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