From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Kelly <mkelly@xevo.com>,
Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/9] gnomebase-meson.bbclass: add a meson-specific version
Date: Wed, 10 Jan 2018 18:48:51 +0000 [thread overview]
Message-ID: <1515610131.29722.112.camel@linuxfoundation.org> (raw)
In-Reply-To: <64c07649-f0df-9acc-fbf3-e8f6a52db9f1@xevo.com>
On Wed, 2018-01-10 at 09:55 -0800, Martin Kelly wrote:
> On 01/05/2018 06:57 AM, Alexander Kanavin wrote:
> >
> > On 01/05/2018 01:47 PM, Burton, Ross wrote:
> > >
> > > Do we even need gnomebase-meson with this? I can see a future
> > > where
> > > GNOME is entirely Meson and then we could just switch the
> > > default
> > > GNOMEBASEBUILDCLASS from autotools to meson.
> > >
> > > (prior art being the tarball compression type)
> >
> > I'm fine with this. Just so everyone else knows: RP has actually
> > made
> > the change already, and merged everything to master, so the YP
> > supports
> > meson as a first class citizen now.
> >
> > Alex
> Technically I'd call it a 0.9-class citizen, as the SDK doesn't work
> yet
> :), but still a whole lot better than 0.
We'll get there and patches are very welcome.
Also *very* welcome would be some SDK tests which illustrate the
problem so we can a) fix it and b) ensure it doesn't regress again!
Cheers,
Richard
next prev parent reply other threads:[~2018-01-10 18:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 13:12 [PATCH 1/9] meson: add a recipe and class from meta-oe Alexander Kanavin
2018-01-04 13:12 ` [PATCH 2/9] gnomebase-meson.bbclass: add a meson-specific version Alexander Kanavin
2018-01-05 11:47 ` Burton, Ross
2018-01-05 14:57 ` Alexander Kanavin
2018-01-10 17:55 ` Martin Kelly
2018-01-10 18:48 ` Richard Purdie [this message]
2018-01-10 19:11 ` Martin Kelly
2018-01-11 11:35 ` Alexander Kanavin
2018-01-11 17:49 ` Richard Purdie
2018-01-11 19:26 ` Martin Kelly
2018-01-04 13:12 ` [PATCH 3/9] json-glib: convert to meson build Alexander Kanavin
2018-01-04 13:12 ` [PATCH 4/9] libepoxy: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 5/9] libinput: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 6/9] sysprof: " Alexander Kanavin
2018-01-04 13:12 ` [PATCH 7/9] gst-player: Upgrade, rename to gst-examples Alexander Kanavin
2018-01-04 13:12 ` [PATCH 8/9] meson: export native env only for native build Alexander Kanavin
2018-01-04 13:12 ` [PATCH 9/9] meson: Port pkgconfig-native patch to 0.44.0 Alexander Kanavin
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=1515610131.29722.112.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=mkelly@xevo.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.