Re: [PATCH] SDK_NAME: Change to include image name and machine.

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2013-08-19 at 16:10 -0700, Flanagan, Elizabeth wrote:
> There apparently are differences caused by each machines tunings (for
> example, meta-fsl-arm's imx53qsb is armv7a-vfp-neon, whereas qemuarm
> is armv5te). With SDK_NAME as it is, you'd end up with two files that
> have the exact same name and toolchains builds that are different.
> Example. qemuarm's toolchain env setup should be named
> 'environment-setup-armv5te-poky-linux-gnueabi' but the toolchain I
> just downloaded from the last master build is
> 'environment-setup-armv7a-vfp-neon-poky-linux-gnueabi' because it's
> the toolchain from the meta-fsl-arm build. I'm not sure how deep the
> issues go outside of these relatively small naming issues. ccing: Yi
> Zhao as I'm sure he can tell us more.
> 
> I agree that TUNE_PKGARCH is probably a better solution than
> TARGET_ARCH but with how I'm generating toolchains now (bitbake
> core-image-sato  -c populate_sdk) I can see a day when having the
> IMAGE_BASENAME included would be a very useful thing.
> 
> So, would anyone be opposed to:
> 
> SDK_NAME = "${DISTRO}-${TCLIBC}-${SDK_ARCH}-${IMAGE_BASENAME}-${TUNE_PKGARCH}"

Looks good to me, it was ${MACHINE} which worried me, TUNE_PKGARCH is
the right thing.

We should also remove [nostamp] from any SDK/ADT bits where it remains.

Cheers,

Richard