From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Mardegan, Alberto" <AMardegan@luxoft.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Getting python-dbusmock into the SDK
Date: Thu, 25 Jan 2018 11:34:40 +0000 [thread overview]
Message-ID: <1516880080.24502.181.camel@linuxfoundation.org> (raw)
In-Reply-To: <8bf1b928-c37a-0590-5ead-e240b7d64eab@luxoft.com>
On Thu, 2018-01-25 at 10:36 +0000, Mardegan, Alberto wrote:
> On 24/01/2018 16:40, Burton, Ross wrote:
> >
> > Those are close matches on the assumption that maybe you did a
> > typo.
> Right, I had completely misread the error message :-)
>
> >
> > Yes, you need to add BBCLASSEXTEND as appropriate. Once you've
> > verified
> > that the recipes actually build correctly in nativesk please send
> > those
> > additions to oe-core.
> OK. FYI, there's another change that was needed: the dbus recipe has:
>
> OLDPKGNAME = "dbus-x11"
> OLDPKGNAME_class-nativesdk = ""
>
> I had to change the second line and set the value to "dbus-x11" there
> as
> well, or I would get an unsolved dependency (dbus-glib requires it).
Installing dbus in the sdk makes very little sense so you may want to
rethink that (or tell the sdk its a system provided dependency).
Cheers,
Richard
next prev parent reply other threads:[~2018-01-25 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 13:31 Getting python-dbusmock into the SDK Mardegan, Alberto
2018-01-24 13:40 ` Burton, Ross
2018-01-25 10:36 ` Mardegan, Alberto
2018-01-25 11:34 ` Richard Purdie [this message]
2018-01-25 15:05 ` Mardegan, Alberto
2018-01-26 10:59 ` Error building python-gobject for nativeSDK (was: Getting python-dbusmock into the SDK) Mardegan, Alberto
2018-01-26 16:13 ` Error building python-gobject for nativeSDK Alexander Kanavin
2018-01-26 16:38 ` Alexander Kanavin
2018-01-29 6:44 ` Mardegan, Alberto
2018-01-29 7:37 ` 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=1516880080.24502.181.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=AMardegan@luxoft.com \
--cc=poky@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.