2017-10-29 14:10:51 +01:00
|
|
|
################################################################################
|
|
|
|
#
|
|
|
|
# meson
|
|
|
|
#
|
|
|
|
################################################################################
|
|
|
|
|
2019-06-17 17:17:20 +02:00
|
|
|
MESON_VERSION = 0.51.0
|
2017-10-29 14:10:51 +01:00
|
|
|
MESON_SITE = https://github.com/mesonbuild/meson/releases/download/$(MESON_VERSION)
|
|
|
|
MESON_LICENSE = Apache-2.0
|
|
|
|
MESON_LICENSE_FILES = COPYING
|
|
|
|
MESON_SETUP_TYPE = setuptools
|
|
|
|
|
|
|
|
HOST_MESON_DEPENDENCIES = host-ninja
|
|
|
|
HOST_MESON_NEEDS_HOST_PYTHON = python3
|
|
|
|
|
|
|
|
HOST_MESON_TARGET_ENDIAN = $(call LOWERCASE,$(BR2_ENDIAN))
|
2018-09-12 12:22:53 +02:00
|
|
|
HOST_MESON_TARGET_CPU = $(GCC_TARGET_CPU)
|
2017-10-29 14:10:51 +01:00
|
|
|
|
2018-12-26 09:52:27 +01:00
|
|
|
# https://mesonbuild.com/Reference-tables.html#cpu-families
|
|
|
|
ifeq ($(BR2_arcle)$(BR2_arceb),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = arc
|
|
|
|
else ifeq ($(BR2_arm)$(BR2_armeb),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = arm
|
|
|
|
else ifeq ($(BR2_aarch64)$(BR2_aarch64_be),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = aarch64
|
|
|
|
else ifeq ($(BR2_i386),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = x86
|
|
|
|
else ifeq ($(BR2_mips)$(BR2_mipsel),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = mips
|
|
|
|
else ifeq ($(BR2_mips64)$(BR2_mips64el),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = mips64
|
|
|
|
else ifeq ($(BR2_powerpc),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = ppc
|
|
|
|
else ifeq ($(BR2_powerpc64)$(BR2_powerpc64le),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = ppc64
|
|
|
|
else ifeq ($(BR2_riscv),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = riscv64
|
|
|
|
else ifeq ($(BR2_sparc),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = sparc
|
|
|
|
else ifeq ($(BR2_sparc64),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = sparc64
|
|
|
|
else ifeq ($(BR2_x86_64),y)
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = x86_64
|
|
|
|
else
|
|
|
|
HOST_MESON_TARGET_CPU_FAMILY = $(ARCH)
|
|
|
|
endif
|
|
|
|
|
package/meson: fix empty arguments in cross-compilation.conf
When TARGET_CFLAGS (or _LDFLAGS or _CXXFLAGS) are empty, but were
constructed by appending other variables, like:
TARGET_CFLAGS = $(SOMETHING) $(SOMETHING_ELSE)
and both variables are empty, then $(TARGET_CFLAGS) is _not_ the
null-string; it's value is a string made of a single space.
This means that the construct:
$(if $(TARGET_CFLAGS),true,false)
will in fact return 'true'.
In our case, it means that we will call:
`printf '"%s", ' `
which expands to just:
"",
which we are then happy to insert as-is in the generated
cross-compilation.conf.
Then meson, will happily call the compiler with an empty argument.
The compiler is less happy, though:
arm-none-linux-gnueabi-gcc: error: : No such file or directory
And this is not even trivial to debug either... The only clue being that
there seems to be something missing between ': :'
We fix that testing the $(strip)ed value. We can still pass the
non-$(strip) expansion, because the shell will just do it for us, and we
are then sure there is at least one non-blank word in there.
Thanks a lot to Adam for his invaluable help debugging this!
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Adam Duskett <aduskett@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-06-24 22:25:47 +02:00
|
|
|
HOST_MESON_SED_CFLAGS = $(if $(strip $(TARGET_CFLAGS)),`printf '"%s"$(comma) ' $(TARGET_CFLAGS)`)
|
|
|
|
HOST_MESON_SED_LDFLAGS = $(if $(strip $(TARGET_LDFLAGS)),`printf '"%s"$(comma) ' $(TARGET_LDFLAGS)`)
|
|
|
|
HOST_MESON_SED_CXXFLAGS = $(if $(strip $(TARGET_CXXFLAGS)),`printf '"%s"$(comma) ' $(TARGET_CXXFLAGS)`)
|
2017-12-30 10:56:35 +01:00
|
|
|
|
package/pkg-meson: support per-package directories
Currently, package/meson/meson.mk generates a single global
cross-compilation.conf file, with the path to the compiler, cflags,
ldflags, and various other details. This file is then used when
building all meson-based packages.
This causes two problems:
- It is not compatible with per-package directories, because with
per-package folders, we need to use a different compiler, and
possibly CFLAGS/LDFLAGS for each package.
- It is not possible to define per package CFLAGS. Indeed, when
cross-compiling, meson doesn't support passing CFLAGS through the
environment, only the CFLAGS from cross-compilation.conf are taken
into account.
For this reason, this commit:
- Introduces a per-package cross-compilation.conf, which is generated
by the pkg-meson infrastructure in the "configure" step right
before calling meson. The file is generated in $(@D)/build/, and
because it is generated within a given package "configure" step,
the compiler path is the one of this package.
- Keeps the global cross-compilation.conf in $(HOST_DIR)/etc/meson/,
for the SDK use-case of Buildroot. Since we want the final and
global values of the compiler path, CFLAGS and LDFLAGS, generating
this global cross-compilation.conf is moved to a
TARGET_FINALIZE_HOOKS. If we were keeping this as a
HOST_MESON_POST_INSTALL_HOOKS, it would contain values specific to
the host-meson package.
For now, we don't yet support per-package CFLAGS/LDFLAGS, but having
such per-package cross-compilation.conf is a necessary preparation to
achieve this goal.
This commit has been tested by building all Buildroot packages that
use meson: json-glib, systemd, enlightenment, at-spi2-core, ncmpc,
libmpdclient and ncmpc.
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
[Thomas:
- add extended commit log
- in pkg-meson.mk, re-use variables defined in meson.mk to do the
replacement of CFLAGS/LDFLAGS/CXXFLAGS
- move the generation of the global cross-compilation.conf to a
TARGET_FINALIZE_HOOKS
- testing with per-package folders]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Tested-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-11-30 11:40:03 +01:00
|
|
|
# Generate a Meson cross-compilation.conf suitable for use with the
|
|
|
|
# SDK
|
2017-10-29 14:10:51 +01:00
|
|
|
define HOST_MESON_INSTALL_CROSS_CONF
|
|
|
|
mkdir -p $(HOST_DIR)/etc/meson
|
|
|
|
sed -e "s%@TARGET_CROSS@%$(TARGET_CROSS)%g" \
|
2018-12-26 09:52:27 +01:00
|
|
|
-e "s%@TARGET_ARCH@%$(HOST_MESON_TARGET_CPU_FAMILY)%g" \
|
2017-10-29 14:10:51 +01:00
|
|
|
-e "s%@TARGET_CPU@%$(HOST_MESON_TARGET_CPU)%g" \
|
|
|
|
-e "s%@TARGET_ENDIAN@%$(HOST_MESON_TARGET_ENDIAN)%g" \
|
2017-12-30 10:56:35 +01:00
|
|
|
-e "s%@TARGET_CFLAGS@%$(HOST_MESON_SED_CFLAGS)%g" \
|
|
|
|
-e "s%@TARGET_LDFLAGS@%$(HOST_MESON_SED_LDFLAGS)%g" \
|
|
|
|
-e "s%@TARGET_CXXFLAGS@%$(HOST_MESON_SED_CXXFLAGS)%g" \
|
2017-10-29 14:10:51 +01:00
|
|
|
-e "s%@HOST_DIR@%$(HOST_DIR)%g" \
|
|
|
|
$(HOST_MESON_PKGDIR)/cross-compilation.conf.in \
|
|
|
|
> $(HOST_DIR)/etc/meson/cross-compilation.conf
|
|
|
|
endef
|
|
|
|
|
package/pkg-meson: support per-package directories
Currently, package/meson/meson.mk generates a single global
cross-compilation.conf file, with the path to the compiler, cflags,
ldflags, and various other details. This file is then used when
building all meson-based packages.
This causes two problems:
- It is not compatible with per-package directories, because with
per-package folders, we need to use a different compiler, and
possibly CFLAGS/LDFLAGS for each package.
- It is not possible to define per package CFLAGS. Indeed, when
cross-compiling, meson doesn't support passing CFLAGS through the
environment, only the CFLAGS from cross-compilation.conf are taken
into account.
For this reason, this commit:
- Introduces a per-package cross-compilation.conf, which is generated
by the pkg-meson infrastructure in the "configure" step right
before calling meson. The file is generated in $(@D)/build/, and
because it is generated within a given package "configure" step,
the compiler path is the one of this package.
- Keeps the global cross-compilation.conf in $(HOST_DIR)/etc/meson/,
for the SDK use-case of Buildroot. Since we want the final and
global values of the compiler path, CFLAGS and LDFLAGS, generating
this global cross-compilation.conf is moved to a
TARGET_FINALIZE_HOOKS. If we were keeping this as a
HOST_MESON_POST_INSTALL_HOOKS, it would contain values specific to
the host-meson package.
For now, we don't yet support per-package CFLAGS/LDFLAGS, but having
such per-package cross-compilation.conf is a necessary preparation to
achieve this goal.
This commit has been tested by building all Buildroot packages that
use meson: json-glib, systemd, enlightenment, at-spi2-core, ncmpc,
libmpdclient and ncmpc.
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
[Thomas:
- add extended commit log
- in pkg-meson.mk, re-use variables defined in meson.mk to do the
replacement of CFLAGS/LDFLAGS/CXXFLAGS
- move the generation of the global cross-compilation.conf to a
TARGET_FINALIZE_HOOKS
- testing with per-package folders]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Tested-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-11-30 11:40:03 +01:00
|
|
|
TARGET_FINALIZE_HOOKS += HOST_MESON_INSTALL_CROSS_CONF
|
2017-10-29 14:10:51 +01:00
|
|
|
|
|
|
|
$(eval $(host-python-package))
|