From: Gary Thomas <gary@mlbassoc.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Problems adding native support packages
Date: Fri, 11 Mar 2011 04:29:22 -0700 [thread overview]
Message-ID: <4D7A0792.2080903@mlbassoc.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A335C9B6F@shsmsx501.ccr.corp.intel.com>
On 03/10/2011 10:18 PM, Xu, Dongxiao wrote:
> Tian, Kevin wrote:
>>> From: Xu, Dongxiao
>>> Sent: Friday, March 11, 2011 1:09 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"
>>>>
>>>> Thanks
>>>> Kevin
>>>>
>>>>>
>>>>> n.b. the recipe from OE is librsvg and importing it seems to be
>>>>> pretty invasive. To build the native package, I needed to add
>>>>> native support for all of these packages:
>>>>>
>>>>> # modified: meta/recipes-gnome/gnome/libart-lgpl_2.3.21.bb
>>>>> # modified: meta/recipes-gnome/gtk+/gtk+.inc
>>>>> # modified: meta/recipes-graphics/cairo/cairo.inc
>>>>> # modified: meta/recipes-graphics/pango/pango.inc #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxcomposite_0.4.3.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxcursor_1.1.11.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxdamage_1.1.3.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxfixes_4.0.5.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxft_2.2.0.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxrandr_1.3.1.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/libxrender_0.9.6.bb #
>>>>> modified: meta/recipes-graphics/xorg-lib/pixman_0.20.2.bb #
>>>>> modified: meta/recipes-graphics/xorg-proto/compositeproto_0.4.2.bb
>>>>> # modified: meta/recipes-graphics/xorg-proto/damageproto_1.2.1.bb #
>>>>> modified: meta/recipes-graphics/xorg-proto/fixesproto_4.1.2.bb #
>>>>> modified: meta/recipes-graphics/xorg-proto/randrproto_1.3.2.bb #
>>>>> modified: meta/recipes-graphics/xorg-proto/renderproto_0.11.1.bb #
>>>>> modified: meta/recipes-graphics/xorg-proto/xineramaproto_1.2.1.bb #
>>>>> modified: meta/recipes-multimedia/alsa/alsa-tools_1.0.20.bb #
>>>>> modified: meta/recipes-support/atk/atk.inc # modified:
>>>>> meta/recipes-support/libcroco/libcroco_0.6.2.bb # modified:
>>>>> meta/recipes-support/libgcrypt/libgcrypt.inc # modified:
>>>>> meta/recipes-support/libgpg-error/libgpg-error_1.9.bb
>>>>>
>>>>> I also ran into a problem when I added native to atk, I get this
>>>>> error which makes no sense at all to me:
>>>>> NOTE: package atk-native-1.32.0-r0: task do_fetch: Started
>>>>> ERROR: Function 'Fetcher failure for URL:
>>>>> 'http://download.gnome.org/sources/atk/1.32/atk-native-1.32.0.tar.bz2'.
>>>>> Unable to fetch URL
>>>>> http://download.gnome.org/sources/atk/1.32/atk-native-1.32.0.tar.bz
>>>>> 2 from any source.' failed This seems to be the only package in
>>>>> the set above that wants to fetch a -native tarball (there are no
>>>>> such files in the sources repository as far as I can tell)
>>>
>>> atk's SRC_URI is assigned like:
>>>
>>> SRC_URI =
>>> "http://download.gnome.org/sources/atk/1.32/${PN}-${PV}.tar.bz2"
>>>
>>> After introducing native to atk, PN is changed to atk-native, thus
>>> no resouce is found in the repo.
>>>
>>> I will make a fix to that. But for your quick workaournd, you can
>>> change the atk's SRC_URI to:
>>>
>>> SRC_URI =
>>> "http://download.gnome.org/sources/atk/1.32/atk-${PV}.tar.bz2"
>>>
>>
>> use ${BPN}-${PV} instead.
>
> Yes. This is the right approach.
>
> I checked in current poky meta recipes, there are about 67 recipes which directly uses ${PN} in the SRC_URI line.
>
> Do we need to change all of them to ${BPN}?
This worked fine, thanks. Now to figure out how to get virtual/libiconv-native built.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-11 11:29 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 [this message]
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
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=4D7A0792.2080903@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dongxiao.xu@intel.com \
--cc=poky@lists.pokylinux.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.