[Buildroot] [RFC v1 2/2] libdrm: change to meson build system
Thomas Petazzoni
thomas.petazzoni at bootlin.com
Sat Jul 14 20:27:29 UTC 2018
Hello,
On Fri, 13 Jul 2018 22:58:01 +0200, Peter Seiderer wrote:
> Signed-off-by: Peter Seiderer <ps.report at 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
More information about the buildroot
mailing list