Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mikko Ylinen <mikko.ylinen@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v3] mraa/upm: enable nodejs bindings by default
Date: Tue, 17 Oct 2017 15:12:06 +0300	[thread overview]
Message-ID: <25ca8a10-6ade-4852-c9e4-bb36b65e2fd6@linux.intel.com> (raw)
In-Reply-To: <20171017120705.GC4387@jama>

Hi,


On 17/10/17 15:07, Martin Jansa wrote:
> On Tue, Oct 17, 2017 at 02:55:39PM +0300, Mikko Ylinen wrote:
>> HAVE_NODEJS is a leftover from meta-refkit-core where the
>> layer had to adapt to different BBLAYER combinations (some
>> where nodejs wasn't available but mraa/upm were).
>>
>> Since that check is no longer needed and nodejs is in fact
>> part of meta-oe, nodejs bindings can be enabled by default
>> (with exceptions for armv4 and armv5 where nodejs isn't
>> available).
>>
>> Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
>> ---
>>   meta-oe/recipes-extended/mraa/mraa_git.bb | 6 +++++-
>>   meta-oe/recipes-extended/upm/upm_git.bb   | 6 +++++-
>>   2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta-oe/recipes-extended/mraa/mraa_git.bb b/meta-oe/recipes-extended/mraa/mraa_git.bb
>> index 616048fac..b93fd72c8 100644
>> --- a/meta-oe/recipes-extended/mraa/mraa_git.bb
>> +++ b/meta-oe/recipes-extended/mraa/mraa_git.bb
>> @@ -31,7 +31,11 @@ FILES_${PN}-utils = "${bindir}/"
>>   # override this in local.conf to get needed bindings.
>>   # BINDINGS_pn-mraa="python"
>>   # will result in only the python bindings being built/packaged.
>> -BINDINGS ??= "python ${@ 'nodejs' if oe.types.boolean(d.getVar('HAVE_NODEJS') or '0') else '' }"
>> +BINDINGS ??= "python nodejs"
>> +
>> +# nodejs isn't available for armv4/armv5 architectures
>> +BINDINGS_armv4 ??= "python"
>> +BINDINGS_armv5 ??= "python"
> Still missing one, aren't you?
>

With qemumips64 I got:

ERROR: Nothing PROVIDES 'mraa'
mraa was skipped: incompatible with host mips64-refkit-linux (not in 
COMPATIBLE_HOST)

So I left it out.

-- Mikko


  reply	other threads:[~2017-10-17 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  7:35 [meta-oe][PATCH] mraa/upm: enable nodejs bindings by default Mikko Ylinen
2017-10-15 23:14 ` Martin Jansa
2017-10-17 10:35   ` [meta-oe][PATCH v2] " Mikko Ylinen
2017-10-17 10:51     ` Martin Jansa
2017-10-17 11:55       ` [meta-oe][PATCH v3] " Mikko Ylinen
2017-10-17 12:07         ` Martin Jansa
2017-10-17 12:12           ` Mikko Ylinen [this message]
2017-10-20 22:53             ` Martin Jansa
2017-10-21 15:39               ` Khem Raj
2017-10-25  4:42                 ` Mikko Ylinen

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=25ca8a10-6ade-4852-c9e4-bb36b65e2fd6@linux.intel.com \
    --to=mikko.ylinen@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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