From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Date: Sun, 15 Jul 2018 21:19:34 +0200 [thread overview]
Message-ID: <20180715211934.0cccdb2b@gmx.net> (raw)
In-Reply-To: <20180714222729.00517695@windsurf>
Hello Thomas,
On Sat, 14 Jul 2018 22:27:29 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Fri, 13 Jul 2018 22:58:01 +0200, Peter Seiderer wrote:
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Notes:
> > - convertion from "LIBDRM_CONF_ENV = ac_cv_prog_cc_c99='-std=gnu99'"
> > is missing (maybe meson gets it right (?) or use LIBDRM_MESON_CFLAGS
> > to force it)
>
> With all those packages migrating to meson, would it be possible to
> look at removing some dependencies from host-ninja/host-meson ? Right
> now, host-ninja forces to build a Python interpreter, either
> host-python or host-python3, and then host-meson forces to build
> host-python3.
>
> If Ninja is compatible with both Python 2 and Python 3, why can't we
> use the system-provided Python interpreter rather than building our
> own ?
>
> Does Meson absolutely needs a Python 3 interpreter ?
Yes, the dependency on two different Phython versions is ridiculous
for two tools working togehter...
For ninja the FAQ [1] states:
Does Ninja support Python 3?
Using Ninja for your project is language-agnostic. Internally Ninja uses
Python 2 to build itself. It is my belief that systems where /usr/bin/python
is not Python 2 are broken (given that we can't go back in time and add a
/usr/bin/python2 on existing systems; see also this discussion).
However, I've grudgingly accepted patches to make the code run under
Python 3 when they're not horrifically ugly.
The other way round for meson to downgrade to Python 2 there is a
mesa patch 'meson: Build with Python 3' stating:
Now that all the build scripts are compatible with both Python 2 and 3,
we can flip the switch and tell Meson to use the latter.
Since Meson already depends on Python 3 anyway, this means we don't need
two different Python stacks to build Mesa.
>
> Meson allows faster builds than autoconf/automake, but in practice, for
> a simple build with just a few packages, if one of them uses Meson,
> then the build is actually slower due to the need to build
> host-python3, and maybe even host-python, as that's what host-ninja
> defaults to.
My speedup for libdrm only was from 20 seconds down to 7 seconds...
Regards,
Peter
[1] https://github.com/ninja-build/ninja/wiki/FAQ
[2] https://gitlab.freedesktop.org/bochecha/mesa/commit/f024258066e310757b37c2fc31376300c72a4805
>
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2018-07-15 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 20:58 [Buildroot] [RFC v1 1/2] meson: change from global to per package cross-compilation.conf Peter Seiderer
2018-07-13 20:58 ` [Buildroot] [RFC v1 2/2] libdrm: change to meson build system Peter Seiderer
2018-07-14 20:27 ` Thomas Petazzoni
2018-07-14 20:31 ` Thomas Petazzoni
2018-07-15 10:02 ` Eric Le Bihan
2018-07-15 14:31 ` Thomas Petazzoni
2018-07-15 19:19 ` Peter Seiderer [this message]
2018-07-15 19:02 ` Peter Seiderer
2018-07-15 20:55 ` Peter Seiderer
2018-07-16 3:59 ` Bernd Kuhls
2018-07-16 8:35 ` Thomas Petazzoni
2018-07-17 19:14 ` Peter Seiderer
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=20180715211934.0cccdb2b@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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.