From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] meson: new package
Date: Sun, 8 Oct 2017 16:42:04 +0200 [thread overview]
Message-ID: <20171008144204.GA17840@itchy> (raw)
In-Reply-To: <20171008101754.GC2803@scaer>
Hi!
On 17-10-08 12:17:54, Yann E. MORIN wrote:
> J?rg, ?ric, All,
>
> On 2017-07-27 11:55 +0200, J?rg Krause spake thusly:
> > From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> >
> > This new package provides the host variant of the Meson Build System, an
> > open source build system meant to be both extremely fast, and as user
> > friendly as possible.
> >
> > More precisely, Meson creates configuration files for the Ninja build
> > system.
> >
> > Besides building Meson, it generates a configuration file
> > ("$(HOST_DIR)/etc/meson/cross-compilation.conf") to be used when
> > cross-compiling a Meson-based project.
> >
> > Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> > [J?rg Krause:
> > * bump to version 0.41.2
> > * use explicit tarball release instead of github helper
> > * use explicit sed
> > * pass BR2_GCC_TARGET_CPU to cross file]
> >
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > ---
> > v3:
> > * fix missing mkdir
> > ---
> > package/meson/cross-compilation.conf.in | 15 +++++++++++++++
> > package/meson/meson.hash | 2 ++
> > package/meson/meson.mk | 31 +++++++++++++++++++++++++++++++
> > 3 files changed, 48 insertions(+)
> > create mode 100644 package/meson/cross-compilation.conf.in
> > create mode 100644 package/meson/meson.hash
> > create mode 100644 package/meson/meson.mk
> >
> > diff --git a/package/meson/cross-compilation.conf.in b/package/meson/cross-compilation.conf.in
> > new file mode 100644
> > index 0000000000..d38fbb03cc
> > --- /dev/null
> > +++ b/package/meson/cross-compilation.conf.in
>
> And what about host packages that use meson?
Good question. I don't know about host packages that may switch to
Meson. But, out of curiosity, I'll try with a dummy package to see how
it would behave.
> > @@ -0,0 +1,15 @@
> > +# Note: in Meson terminology, what Buildroot calls the "host" system is the
> > +# "build" system and the "target" system is called the "host" system.
>
> Yeah, pretty confusing, isn't it? Buildroot is wrong here, but since
> we've been wrong for almost two decades now, we can't really change...
>
> I'd still suggest a little rephrasing:
>
> # Note: Buildroot's and Meson's terminologies differ about the meaning
> # of 'build', 'host' and 'target':
> # - Buildroot's 'host' is Meson's 'build'
> # - Buildroot's 'target' is Meson's 'host'
Looks sensible to me.
> Regards,
> Yann E. MORIN.
>
> > +[binaries]
> > +c = '@TARGET_CROSS at gcc'
> > +cpp = '@TARGET_CROSS at g++'
> > +ar = '@TARGET_CROSS at ar'
> > +strip = '@TARGET_CROSS at strip'
> > +pkgconfig = '@HOST_DIR@/usr/bin/pkg-config'
> > +
> > +[host_machine]
> > +system = 'linux'
> > +cpu_family ='@TARGET_ARCH@'
> > +cpu = '@TARGET_CPU@'
> > +endian = '@TARGET_ENDIAN@'
> > diff --git a/package/meson/meson.hash b/package/meson/meson.hash
> > new file mode 100644
> > index 0000000000..7f0de1d437
> > --- /dev/null
> > +++ b/package/meson/meson.hash
> > @@ -0,0 +1,2 @@
> > +# Locally generated
> > +sha256 074dd24fd068be0893e2e45bcc35c919d8e12777e9d6a7efdf72d4dc300867ca meson-0.41.2.tar.gz
> > diff --git a/package/meson/meson.mk b/package/meson/meson.mk
> > new file mode 100644
> > index 0000000000..e9f1ffe4d4
> > --- /dev/null
> > +++ b/package/meson/meson.mk
> > @@ -0,0 +1,31 @@
> > +################################################################################
> > +#
> > +# meson
> > +#
> > +################################################################################
> > +
> > +MESON_VERSION = 0.41.2
> > +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 = $(shell echo $(BR2_ENDIAN) | tr 'A-Z' 'a-z')
> > +
> > +define HOST_MESON_INSTALL_CROSS_CONF
> > + mkdir -p $(HOST_DIR)/etc/meson
> > + sed -e 's;@TARGET_CROSS@;$(TARGET_CROSS);g' \
> > + -e 's;@TARGET_ARCH@;$(ARCH);g' \
> > + -e 's;@TARGET_CPU@;$(BR2_GCC_TARGET_CPU);g' \
> > + -e 's;@TARGET_ENDIAN@;$(HOST_MESON_TARGET_ENDIAN);g' \
> > + -e 's;@HOST_DIR@;$(HOST_DIR);g' \
> > + $(HOST_MESON_PKGDIR)/cross-compilation.conf.in \
> > + > $(HOST_DIR)/etc/meson/cross-compilation.conf
> > +endef
> > +
> > +HOST_MESON_POST_INSTALL_HOOKS += HOST_MESON_INSTALL_CROSS_CONF
> > +
> > +$(eval $(host-python-package))
> > --
> > 2.13.3
> >
Regards,
--
ELB
next prev parent reply other threads:[~2017-10-08 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:55 [Buildroot] [PATCH v2 0/3] Add support for Meson build Jörg Krause
2017-07-27 9:55 ` [Buildroot] [PATCH v3 1/3] meson: new package Jörg Krause
2017-10-08 10:17 ` Yann E. MORIN
2017-10-08 14:42 ` Eric Le Bihan [this message]
2017-10-20 19:45 ` Peter Seiderer
2017-07-27 9:55 ` [Buildroot] [PATCH v3 2/3] docs/manual: document meson-based packages Jörg Krause
2017-10-08 10:03 ` Yann E. MORIN
2017-10-08 14:48 ` Eric Le Bihan
2017-10-08 16:48 ` Adrian Perez de Castro
2017-10-08 18:05 ` Yann E. MORIN
2017-07-27 9:55 ` [Buildroot] [PATCH v2 3/3] libmpdclient: bump to version 2.13 Jörg Krause
2017-10-21 12:26 ` 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=20171008144204.GA17840@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox