All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Date: Sun, 15 Jul 2018 12:02:56 +0200	[thread overview]
Message-ID: <20180715100256.GA27498@itchy> (raw)
In-Reply-To: <20180714222729.00517695@windsurf>

Hi!
On 2018-07-14 22:27, Thomas Petazzoni 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 ?

Is it the technique used for cmake with $(BR2_CMAKE_HOST_DEPENDENCY), or
am I mistaken?

> Does Meson absolutely needs a Python 3 interpreter ?

Meson is strict about this. From setup.py:

```
if sys.version_info < (3, 5, 0):
    print('Tried to install with an unsupported version of Python. '
              'Meson requires Python 3.5.0 or greater')
	          sys.exit(1)
```

Regards,

--
ELB

  parent reply	other threads:[~2018-07-15 10:02 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 [this message]
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=20180715100256.GA27498@itchy \
    --to=eric.le.bihan.dev@free.fr \
    --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.