[OE-core] [oe-core][RFC] nativesdk.bbclass: define empty PACKAGES/PACKAGES_DYNAMIC

[Richard Purdie]

On Tue, 2011-05-10 at 13:57 +0200, Martin Jansa wrote:
> * we had similar patch for native.bbclass
>   41d77ac37f606e54293826ba1e94a4254bddbfa6
>   I have no idea if the same could be used for nativesdk, because I'm
>   not using generated SDKs at all, that's why it's RFC and if there are
>   better ways to hide such errors, please let me know
> 
> * maybe PACKAGES just don't get extra prefix -nativesdk like
>   glib-2.0-utils-nativesdk
> 
> * those errors are shown like this:
>   ERROR: Trying to resolve runtime dependency glibc-charmap-utf-8 resulted
>   in conflicting PREFERRED_PROVIDER entries being found.
>   The providers found were: ['/OE/shr-core/openembedded-core/meta/recipes-core/eglibc/eglibc_2.12.bb', 'virtual:nativesdk:/OE/shr-core/openembedded-core/meta/recipes-core/eglibc/eglibc_2.12.bb']
>   The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/libc = eglibc', 'PREFERRED_PROVIDER_virtual/libc-nativesdk = eglibc-nativesdk']
> 
>   NOTE: multiple providers are available for runtime glibc-charmap-utf-8 (eglibc-nativesdk, eglibc, glibc, glibc-nativesdk)
>   NOTE: consider defining a PREFERRED_PROVIDER entry to match glibc-charmap-utf-8
>   NOTE: multiple providers are available for runtime glib-2.0-utils (glib-2.0-nativesdk, glib-2.0)
>   NOTE: consider defining a PREFERRED_PROVIDER entry to match glib-2.0-utils

This patch is certainly incorrect as we expect nativesdk to be packaged
and use the resulting packages. It sounds like some value in PACKAGES is
using a hardcoded reference to glibc instead of ${PN}.

Cheers,

Richard