From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Date: Mon, 16 Jul 2018 10:35:27 +0200 [thread overview]
Message-ID: <20180716103527.2e139eb4@windsurf> (raw)
In-Reply-To: <fqht1fxpqg.ln2@ID-313208.user.individual.net>
Hello,
On Mon, 16 Jul 2018 05:59:43 +0200, Bernd Kuhls wrote:
> > I agree that there needs to be an explanation for the switch. Is
> > upstream moving to CMake, and getting rid of autotools support in the
> > future ? Other reason ?
>
> From the current discussion of your RFC I am unable to see the
> "*compelling* reason" for using meson.
I think it all depends on upstream's strategy. Are they adding meson
just as an alternate build system and intend to keep autotools, or are
they adding meson with the plan of phasing out and removing autotools
based build ?
In the latter case, then switching to meson definitely makes sense.
> Instead the mess around python2/python3 imho does not justify the
> few seconds libdrm itself will build faster, so NACK.
The python2/python3 mess has nothing to do with libdrm, it's an
existing and separate meson support issue, which we already have for
other packages using the meson build system.
However, I agree that the need to build host-python3 to build meson
packages is really annoying :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-16 8:35 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
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 [this message]
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=20180716103527.2e139eb4@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.