From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: Problems adding native support packages
Date: Fri, 11 Mar 2011 08:23:04 -0800 [thread overview]
Message-ID: <1299860584.2533.1.camel@scimitar> (raw)
In-Reply-To: <4D7A11EA.4050306@mlbassoc.com>
On Fri, 2011-03-11 at 05:13 -0700, Gary Thomas wrote:
> On 03/11/2011 04:19 AM, Gary Thomas wrote:
> > On 03/10/2011 09:57 PM, Tian, Kevin wrote:
> >>> From: Gary Thomas
> >>> Sent: Friday, March 11, 2011 11:29 AM
> >>>
> >>> I'm trying to import a native package from OE for which the
> >>> main package depends on libiconv. This seems to imply that
> >>> when I extend to the native package using BBCLASSEXTEND, the
> >>> native package depends on virtual/libiconv-native
> >>>
> >>> I can't figure out how to provide this. Any clues?
> >>
> >> I'm not sure about the problem here. do you want virtual/libiconv-native dependency
> >> or not? If target recipe already has a DEPENDS = "libiconv", then with BBCLASSEXTEND
> >> you have libiconv-native automatically.
> >>
> >> Or if you only want to add libiconv-native for native recipe exclusively, then:
> >>
> >> DEPENDS_virtclass-native = "virtual/libiconv-native"
> >
> > Actually, the problem is that such a dependency was added automatically by BBCLASSEXTEND.
> > virtual/libiconv is provided by eglibc package, but it's not clear if it can provide
> > virtual/libiconv-native
>
> It comes from this dependency which seems very hard to satisfy:
> meta/recipes-graphics/pango/pango.inc:DEPENDS = "glib-2.0 fontconfig freetype zlib virtual/libiconv virtual/libx11 libxft gtk-doc-native cairo"
virtual/libiconv is set in the *libc.conf included by the distro:
meta/conf/distro/include/poky-eglibc.inc:PREFERRED_PROVIDER_virtual/libiconv ?= "eglibc"
meta/conf/distro/include/poky-eglibc.inc:PREFERRED_PROVIDER_virtual/libiconv-nativesdk ?= "eglibc-nativesdk"
I guess we need a PREFERRED_PROVIDER_virtual/libiconv-natives ?=
"eglibc-native" entry in this file?
Cheers,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-11 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 3:28 Problems adding native support packages Gary Thomas
2011-03-11 4:57 ` Tian, Kevin
2011-03-11 5:09 ` Xu, Dongxiao
2011-03-11 5:15 ` Tian, Kevin
2011-03-11 5:18 ` Xu, Dongxiao
2011-03-11 5:52 ` Tian, Kevin
2011-03-11 22:25 ` Richard Purdie
2011-03-13 22:26 ` Gary Thomas
2011-03-11 11:29 ` Gary Thomas
2011-03-11 8:21 ` Khem Raj
2011-03-11 11:19 ` Gary Thomas
2011-03-11 12:13 ` Gary Thomas
2011-03-11 16:23 ` Joshua Lock [this message]
2011-03-12 0:09 ` Tian, Kevin
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=1299860584.2533.1.camel@scimitar \
--to=josh@openedhand.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox