All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Ashish Shrivastava" <ashish.shrivastava@axis.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Not able to disable introspection in gstreamer
Date: Wed, 16 Mar 2016 18:41:24 +0200 (EET)	[thread overview]
Message-ID: <56868.10.252.1.171.1458146484.squirrel@linux.intel.com> (raw)
In-Reply-To: <1458140066928.8568@axis.com>

> I am trying to build latest poky version from upstream but it was failing
> in "gobject-introspection-data?".
>
> I disabled it with comments mentioned in:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?id=8c14c746da1784c4bdaa621dde6fccd99e72ef1b
>
>
> by adding folloing line in config:
>
> MACHINE_FEATURES_BACKFILL_CONSIDERED = "gobject-introspection-data"
>
>
> Now gstreamer is throwing error for introspection.

Your log seems to say that gstreamer is at 1.6.0, and therefore is coming
from some other layer than oe-core (which has 1.6.3). Disabling
introspection in recipes by using MACHINE_FEATURES_BACKFILL_CONSIDERED
only works if those recipes inherit gobject-introspection class, and so
this is what you should do. Or migrate from your custom gstreamer recipes
to ones provided by oe-core, and then you don't have to disable anything
at all most likely, and you will gain ability to use gstreamer from Python
scripts, Vala or other runtimes.

Alex


      parent reply	other threads:[~2016-03-16 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 14:54 Not able to disable introspection in gstreamer Ashish Shrivastava
2016-03-16 15:12 ` Burton, Ross
2016-03-16 15:32   ` Ashish Shrivastava
2016-03-16 16:13 ` Martin Jansa
2016-03-16 16:13   ` Burton, Ross
2016-03-16 16:41 ` alexander.kanavin [this message]

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=56868.10.252.1.171.1458146484.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=ashish.shrivastava@axis.com \
    --cc=yocto@yoctoproject.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 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.