[OE-core] [RFH] Wrong behaviour regarding SDK native and target paths

[Richard Purdie]

On Sun, 2011-07-03 at 19:29 -0300, Otavio Salvador wrote:
> Hello,
> 
> I am looking for help to get our nativesdk working fine and I am quite
> confused how does it can work after all.
> 
> I have looked at meta/recipes-qt/meta/meta-toolchain-qte.bb and it has:
> 
> QT_TOOLS_PREFIX = "${SDKPATHNATIVE}${bindir_nativesdk}"
> 
> Running it is expanded to:
> 
> QT_TOOLS_PREFIX="/usr/local/oecore-i686-i586/sysroots/i686-oesdk-linux/usr/bin"
> 
> It seems right but in fact it is wrong since Qt binaries are installed into:
> 
> (devel)~/hacking/el% tar tjf
> tmp-eglibc-eglibc/deploy/sdk/oecore-i686-i586-toolchain-devel.tar.bz2|
> grep 'bin/moc4'
> ./usr/local/oecore-i686-i686/sysroots/i686-oesdk-linux/usr/bin/moc4
> 
> so, the generated information for the script won't work.
> 
> I am quite confused by all this is suppose to work. Someone help me?

It looks like in OE-Core we have:

conf/bitbake.conf:SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
conf/bitbake.conf:SDKPATH = "/usr/local/${SDK_NAME}"
conf/bitbake.conf:SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"

and in meta-yocto:

conf/distro/poky.conf:SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"

I suspect having TARGET_ARCH in the PATH might be a bad idea and we need
to rethink the defaults in OE-Core. Using something more like the
meta-yocto default above might help your problem.

Cheers,

Richard