On Tue, Mar 9, 2010 at 10:24 AM, Phil Blundell <[email protected]> wrote:
> On Tue, 2010-03-09 at 13:16 -0500, Denys Dmytriyenko wrote:
>> So, what would be the proper fix? I'm blocked at the moment with this
>> gtk+/apple-red.png issue, where gtk+ is being pulled by gstreamer...
>> Thanks in advance for any help or suggestions.
>
> I think the patch that Graeme posted, or a subset of it, is at least
> part of the proper fix.  I'll check that in this evening.  With that,
> using gtk+ as the provider for gdk-pixbuf-csource-native ought to do
> what you need.

Prior to the above patch, gtk+ would build for me with no problems.
Afterwards I get:

| Making all in demos
| make[2]: Entering directory
`/home/sakoman/source/omap3-oe/tmp/work/armv7a-angstrom-linux-gnueabi/gtk+-2.18.6-r8.3/gtk+-2.18.6/demos'
| 
/home/sakoman/source/omap3-oe/tmp/staging/i686-linux/usr/bin/gdk-pixbuf-csource
--raw --build-list              \
|               apple_red  ./apple-red.png      \
|                 gnome_foot ./gnome-foot.png   \
|         > test-inline-pixbufs.h                               \
|       || (rm -f test-inline-pixbufs.h && false)
|
| (process:4835): GdkPixbuf-WARNING **: Cannot open pixbuf loader
module file 
'/home/sakoman/source/omap3-oe/tmp/staging/i686-linux/etc/gtk-2.0/gdk-pixbuf.loaders':
No such file or directory
| failed to load "./apple-red.png": Couldn't recognize the image file
format for file './apple-red.png'
| make[2]: *** [test-inline-pixbufs.h] Error 1

So for me it seems to have triggered the problem it was trying to fix!

Steve

> Getting the standalone g-p-c-n to DTRT will require a bit more fiddling
> but I don't think it should be very hard.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> [email protected]
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to