Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yi Zhao <yi.zhao@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	ChenQi <Qi.Chen@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/9] json-glib: convert to meson build
Date: Fri, 12 Jan 2018 15:49:19 +0800	[thread overview]
Message-ID: <1d60e67e-cf3a-8a2c-e8bc-52e8060e8cae@windriver.com> (raw)
In-Reply-To: <991321f1-d190-3b20-c2c3-572bf6e5fcc5@linux.intel.com>

I also encountered this issue. For now, I found it only happened on 
ubuntu 14.04.

Looks like it invokes g-ir-scanner but not g-ir-scanner-wrapper when 
building gir.

In build.ninja:

COMMAND = 
'/buildarea/build/tmp/work/core2-64-poky-linux/json-glib/1.2.8-r0/recipe-sysroot-native/usr/bin/g-ir-scanner' 
...

On ubuntu 16.04, it uses g-ir-scanner-wrapper that could work:

COMMAND = 
/buildarea/build/tmp/work/core2-64-poky-linux/json-glib/1.2.8-r0/recipe-sysroot/usr/bin/g-ir-scanner-wrapper 
...


//Yi


在 2018年01月04日 17:27, Alexander Kanavin 写道:
> On 01/04/2018 10:51 AM, ChenQi wrote:
>>> file://0001-Do-not-disable-gobject-introspection-when-cross-comp.patch 
>>> \
>>> +           "
>>
>> I removed this patch and the compile succeeded.
>> Could you please check if this patch is really needed?
>> If it is, I think we'd better make build to succeed by default anyway.
>
> Yes, it is really needed. Without it, introspection files will not be 
> generated at all. I'll try to reproduce the failure.
>
> Alex



  reply	other threads:[~2018-01-12  7:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 13:04 [PATCH 1/9] meson: add a recipe and class from meta-oe Alexander Kanavin
2017-12-21 13:04 ` [PATCH 2/9] gnomebase.bbclass: split into autotools and meson versions Alexander Kanavin
2018-01-03 11:11   ` Richard Purdie
2018-01-04 13:13     ` Alexander Kanavin
2017-12-21 13:04 ` [PATCH 3/9] json-glib: convert to meson build Alexander Kanavin
2018-01-04  8:40   ` ChenQi
2018-01-04 12:35     ` Alexander Kanavin
2018-01-04  8:51   ` ChenQi
2018-01-04  9:27     ` Alexander Kanavin
2018-01-12  7:49       ` Yi Zhao [this message]
2017-12-21 13:04 ` [PATCH 4/9] libepoxy: " Alexander Kanavin
2017-12-21 13:04 ` [PATCH 5/9] libinput: " Alexander Kanavin
2017-12-21 13:04 ` [PATCH 6/9] sysprof: " Alexander Kanavin
2017-12-21 13:04 ` [PATCH 7/9] gst-player: Upgrade, rename to gst-examples Alexander Kanavin
2017-12-21 13:04 ` [PATCH 8/9] meson: export native env only for native build Alexander Kanavin
2017-12-21 13:04 ` [PATCH 9/9] meson: Port pkgconfig-native patch to 0.44.0 Alexander Kanavin
  -- strict thread matches above, loose matches on Subject: below --
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 3/9] json-glib: convert to meson build Alexander Kanavin
2018-01-04  9:31 Yang, Zhangle (Eric)
2017-11-17 12:02 [PATCH 0/9] Introduce meson build system Alexander Kanavin
2017-11-17 12:02 ` [PATCH 3/9] json-glib: convert to meson build 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=1d60e67e-cf3a-8a2c-e8bc-52e8060e8cae@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=Qi.Chen@windriver.com \
    --cc=alexander.kanavin@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