[oe] pkg-config confusion

[Gary Thomas]

I'm trying to update the gstreamer plugin recipes to use the
latest released packages.  This is causing some problems though
as with the newest code, the wrong version of ORCC is being used.

I've traced this down to the fact that previous releases just
inferred ORCC=orcc which worked correctly and picked up the
cross-tool compiler (in sysroots/i686-linux/... etc)

However, the new releases have a fancy M4 macro plus some command
line magic for using ORCC.  This falls apart because of these
lines:
       ORCC=`$PKG_CONFIG --variable=orcc orc-0.4`

Looking into this at configure time, I see that there is some confusion

ORCC=/usr/bin/orcc, PKG_CONFIG=/home/local/p69_poky/tmp/sysroots/i686-linux/usr/bin/pkg-config => /home/local/p69_poky/tmp/sysroots/i686-linux/usr/bin/pkg-config
PKG_CONFIG_DISABLE_UNINSTALLED=yes
PKG_CONFIG_SYSROOT_DIR=/home/local/p69_poky/tmp/sysroots/armv7a-poky-linux-gnueabi
PKG_CONFIG_DIR=/home/local/p69_poky/tmp/sysroots/armv7a-poky-linux-gnueabi/usr/lib/pkgconfig
PKG_CONFIG_LIBDIR=/home/local/p69_poky/tmp/sysroots/armv7a-poky-linux-gnueabi/usr/lib/pkgconfig
PKG_CONFIG_PATH=/home/local/p69_poky/tmp/sysroots/armv7a-poky-linux-gnueabi/usr/lib/pkgconfig:/home/local/p69_poky/tmp/sysroots/armv7a-poky-linux-gnueabi/usr/share/pkgconfig

So, it looks like bitbake is trying to run pkg-config using the
native version, but with the installed target databases.  This
in turn has it pick up the target version of ORCC, not the cross
version.

How can I convince it otherwise?

n.b. I think this same problem exists elsewhere as I've seen it
try to use the wrong version of the pygobject compiler which is
handled similarly.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------