From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Date: Sun, 15 Jul 2018 16:31:30 +0200 [thread overview]
Message-ID: <20180715163130.1cb50643@windsurf> (raw)
In-Reply-To: <20180715100256.GA27498@itchy>
Hello Eric,
On Sun, 15 Jul 2018 12:02:56 +0200, Eric Le Bihan wrote:
> > 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 ?
>
> Is it the technique used for cmake with $(BR2_CMAKE_HOST_DEPENDENCY), or
> am I mistaken?
No, it's not the same thing. BR2_CMAKE_HOST_DEPENDENCY is to avoid
building CMake if a suitable CMake version is already provided on the
host.
What I'm suggesting as a first step is to avoid building both
host-python3 and host-python. Once this first step is done, and only
host-python3 gets built, then maybe we can think of avoiding the
host-python3 build by using the system-provided version, with something
similar to BR2_CMAKE_HOST_DEPENDENCY.
> > Does Meson absolutely needs a Python 3 interpreter ?
>
> Meson is strict about this. From setup.py:
Meh, OK :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-15 14:31 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 [this message]
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=20180715163130.1cb50643@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox