From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/7] json-glib: convert to meson build
Date: Thu, 24 Aug 2017 15:43:32 +0300 [thread overview]
Message-ID: <41875eb1-b054-edbf-02fb-dd145e6b363f@linux.intel.com> (raw)
In-Reply-To: <1503522842.2166.9.camel@linux.intel.com>
On 08/24/2017 12:14 AM, Leonardo Sandoval wrote:
>
>> -inherit gnomebase gettext lib_package gobject-introspection gtk-doc manpages
>> +inherit gnomebase-meson lib_package gobject-introspection gtk-doc manpages
>
> gettext is dropped, does it mean that it was not needed?
No. gettext.bbclass is specific to autotools, and meson has no
equivalent functionality. I'll amend the commit message.
Alex
next prev parent reply other threads:[~2017-08-24 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 17:06 [PATCH 0/7] Introduce meson build system Alexander Kanavin
2017-08-23 17:06 ` [PATCH 1/7] meson: add a recipe and class from meta-oe Alexander Kanavin
2017-08-23 19:25 ` Leonardo Sandoval
2017-08-23 17:06 ` [PATCH 2/7] gnomebase.bbclass: split into autotools and meson versions Alexander Kanavin
2017-08-23 17:06 ` [PATCH 3/7] gtk-doc.bbclass: add all directories where .so files are found to library search path Alexander Kanavin
2017-08-23 17:06 ` [PATCH 4/7] json-glib: convert to meson build Alexander Kanavin
2017-08-23 21:14 ` Leonardo Sandoval
2017-08-24 12:43 ` Alexander Kanavin [this message]
2017-08-23 17:06 ` [PATCH 5/7] libepoxy: " Alexander Kanavin
2017-08-23 17:06 ` [PATCH 6/7] libinput: " Alexander Kanavin
2017-08-23 17:06 ` [PATCH 7/7] sysprof: " Alexander Kanavin
2017-08-23 17:35 ` Andre McCurdy
2017-08-24 12:45 ` Alexander Kanavin
2017-08-24 19:41 ` Randy MacLeod
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=41875eb1-b054-edbf-02fb-dd145e6b363f@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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