[OE-core] multiple providers for gtk-icon-cache

[Burton, Ross]

On 7 March 2013 23:10, Andreas Müller <schnitzeltony at googlemail.com> wrote:
> ERROR: Multiple .bb files are due to be built which each provide
> virtual/gtk-update-icon-cache-native
> (/home/Superandy/data/oe-core/sources/openembedded-core/meta/recipes-gnome/gtk+/gtk-update-icon-cache-native_3.4.4.bb
> virtual:native:/home/Superandy/data/oe-core/sources/openembedded-core/meta/recipes-gnome/gtk+/gtk+_2.24.15.bb).
>  This usually means one provides something the other doesn't and should.
>
> Do both versions create same output?
>
> If yes: why not remove from gtk+?
> If no: ??

I wasn't expecting this to happen so quickly.

As can be seen from the recipes, gtk+-native is the full GTK+
platform, and gtk-update-icon-cache is just that single binary.  For
the purposes of generating a rootfs with a pre-populated icon cache,
gtk-update-icon-cache is all that is required.

So, why are you building gtk+-native?  It's probably one of:

1) you're building native applications that use GTK+.  In this case,
use PREFERRED_PROVIDER_virtual/gtk-update-icon-cache-native ?=
"gtk+-native".

2) you've recipes that use gtk-update-icon-cache on the host and so
depend on gtk+-native.  Change these to use the gtk-icon-cache class
instead.

Ross