Re: [PATCHv2] bitbake.conf: use TUNE_PKGARCH instead of TARGET_ARCH in SDK_NAME

[Saul Wold <sgw@linux.intel.com>]

On 03/15/2012 12:23 AM, Martin Jansa wrote:
> * also use weak assignment for SDK_NAME_PREFIX as suggested by khem
> * TUNE_PKGARCH is not 100% right too, because such SDK image usually has few
>    machine specific packages included (e.g. base-files, securetty, opkg configs)
>    but those are not important for SDK users so it's better to have one SDK for
>    whole e.g. armv7a-vfp-neon then 6 SDK for each machine which would work the
>    same.
>    You can see diff between crespo and om-gta04 SDK here:
>    http://build.shr-project.org/shr-core/sdk/oecore-i686-armv7a-vfp-neon-toolchain-efl-crespo-om-gta04.diff
>
> Signed-off-by: Martin Jansa<Martin.Jansa@gmail.com>
> ---
>   meta/conf/bitbake.conf |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 216da75..01fc52a 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -365,8 +365,8 @@ PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
>   # SDK variables,
>   ##################################################################
>
> -SDK_NAME_PREFIX = "oecore"
> -SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${TARGET_ARCH}"
> +SDK_NAME_PREFIX ?= "oecore"
> +SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_ARCH}-${TUNE_PKGARCH}"
>   SDKPATH = "/usr/local/${SDK_NAME_PREFIX}-${SDK_ARCH}"
>   SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
>

Merged into OE-Core

Thanks
	Sau!