From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Date: Sat, 14 Jul 2018 22:27:29 +0200 [thread overview]
Message-ID: <20180714222729.00517695@windsurf> (raw)
In-Reply-To: <20180713205801.25976-2-ps.report@gmx.net>
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 ?
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.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-14 20:27 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 [this message]
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
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=20180714222729.00517695@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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.