All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Remove vala from oe-core
Date: Tue, 10 Nov 2015 17:19:00 +0200	[thread overview]
Message-ID: <56420AE4.1090500@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYdyoLGS6ws1nKzagF=osJ7d1hdc+FdTOh_bAoeD2sqSQ@mail.gmail.com>

On 11/10/2015 05:10 PM, Burton, Ross wrote:

>     I should clarify: there might be Vala software out there that
>     someone would want to run in an embedded context. And that software
>     might require Vala bindings for libraries that are in oe-core. If we
>     don't provide those bindings, then either the layer that adds vala
>     recipe also has to patch all of our oe-core recipes, or (worse!) the
>     person who needs something vala-based also has to ad-hoc-patch the
>     dependency recipes of that.
>
>
> One solution for no vala in oe-core would be for all vala-supporting
> recipes in oe-core to have a PACKAGECONFIG[vala], so if someone does
> want Vala then they just need to add meta-vala (for example) to their
> layers and enable the PACKAGECONFIGs where they want it enabled.
> There's plenty of prior art for this behaviour in oe-core already.


PACKAGECONFIG alone is not sufficient; to build the bindings properly, 
the package also needs to inherit vala.bbclass:

https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/tree/meta/classes/vala.bbclass?h=akanavin/gobject-introspection-experimental


Alex


  reply	other threads:[~2015-11-10 15:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 14:22 [RFC] Remove vala from oe-core Jussi Kukkonen
2015-11-10 14:22 ` Jussi Kukkonen
2015-11-10 14:30 ` Alexander Kanavin
2015-11-10 14:29   ` Carlos Rafael Giani
2015-11-10 14:32     ` Alexander Kanavin
2015-11-10 14:50   ` Paul Eggleton
2015-11-10 15:06     ` Alexander Kanavin
2015-11-10 15:09       ` Paul Eggleton
2015-11-10 15:10       ` Burton, Ross
2015-11-10 15:19         ` Alexander Kanavin [this message]
2015-11-10 15:29           ` Otavio Salvador
2015-11-10 15:37             ` Alexander Kanavin
2015-11-10 15:39               ` Otavio Salvador
2015-11-10 16:25                 ` Andreas Müller
2015-11-10 16:52                   ` Otavio Salvador
2015-11-11 17:17               ` Richard Purdie
2015-11-11 17:38                 ` Paul Eggleton
2015-11-12 11:18                 ` Alexander Kanavin
2015-11-10 16:02 ` [OE-core] " Martin Jansa
2015-11-10 16:02   ` Martin Jansa

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=56420AE4.1090500@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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.