Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dominik Holland <dominik.holland@pelagicore.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: nativesdk-dbus depends on nativesdk-dbus-ptest-ptest
Date: Wed, 13 Nov 2013 17:29:32 +0100	[thread overview]
Message-ID: <5283A8EC.4010300@pelagicore.com> (raw)
In-Reply-To: <5283A080.1050702@pelagicore.com>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Hi,

sorry my fault it needs to be RDEPENDS_dbus_class-nativesdk = ""

but shouldn't than the RDEPENDS_class-native = "" also be changed to 
RDEPENDS_dbus_class-native = ""


Dominik

On 11/13/2013 04:53 PM, Dominik Holland wrote:
> Hi,
>
> i'm trying to port a application which has a dependency to dbus. This 
> tool is host tool and should be included in the sdk.
>
> Because of that i added a dependency to nativesdk-dbus. But it doesn't 
> build for because nativesdk-dbus depends on nativesdk-dbus-ptest-ptest 
> which is not available.
>
> There are 2 options i can see to solve this:
>
> Solution 1: Change the dbus-ptest recipe to also use the nativesdk class.
>
> Solution 2: Change the dbus recipe to not depend on ptest on nativesdks.
>
> I'm favoring Solution 2 and i tried to add RDEPENDS_class-nativesdk = 
> "" to the dbus.inc but that doesn't help.
>
> Is there anything that i'm missing or do i really need to install 
> ptest into my SDK ?
>
> Best Regards
>  Dominik


[-- Attachment #2: Type: text/html, Size: 2113 bytes --]

      parent reply	other threads:[~2013-11-13 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5283A080.1050702@pelagicore.com>
2013-11-13 15:56 ` nativesdk-dbus depends on nativesdk-dbus-ptest-ptest Dominik Holland
2013-11-13 16:29 ` Dominik Holland [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=5283A8EC.4010300@pelagicore.com \
    --to=dominik.holland@pelagicore.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