[oe] How to extend SRC_URI_append?

[Maupin, Chase]

> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
> Jean-Christophe PLAGNIOL-VILLARD
> Sent: Friday, September 03, 2010 11:59 AM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] How to extend SRC_URI_append?
> 
> On 18:47 Fri 03 Sep     , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 07:44 Fri 03 Sep     , Chris Larson wrote:
> > > The append syntax you're referring to uses OVERRIDES.  FOO_somevalue
> > > replaces FOO if somevalue is in OVERRIDES.  FOO_append_somevalue is
> added to
> > > FOO if somevalue is in OVERRIDES.  I don't think SOC_FAMILY is in
> overrides
> > > at this time.
> > how can I extend it?
> is this ok?
> 
> diff --git a/conf/bitbake.conf b/conf/bitbake.conf
> index 677c76a..ecdf245 100644
> --- a/conf/bitbake.conf
> +++ b/conf/bitbake.conf
> @@ -677,9 +677,9 @@ BUILDCFG_NEEDEDVARS ?= "TARGET_ARCH TARGET_OS"
>  #
>  # This works for  functions as well, they are really just environment
> variables.
>  # Default OVERRIDES to make compilation fail fast in case of build system
> misconfiguration.
> -OVERRIDES =
> "local:${MACHINE}:${DISTRO}:${TARGET_OS}:${TARGET_ARCH}:build-
> ${BUILD_OS}:fail-fast:pn-${PN}"
> +OVERRIDES =
> "local:${MACHINE}:${DISTRO}:${TARGET_OS}:${TARGET_ARCH}:${SOC_FAMILY}:${TA
> RGET_ARCH}_${SOC_FAMILY}:build-${BUILD_OS}:fail-fast:pn-${PN}"
>  # Alternative OVERRIDES definition without "fail fast", usually only for
> native building and Scratchbox toolchains.
> -#OVERRIDES =
> "local:${MACHINE}:${DISTRO}:${TARGET_OS}:${TARGET_ARCH}:build-
> ${BUILD_OS}:pn-${PN}"
> +#OVERRIDES =
> "local:${MACHINE}:${DISTRO}:${TARGET_OS}:${TARGET_ARCH}:${SOC_FAMILY}:${TA
> RGET_ARCH}_${SOC_FAMILY}:build-${BUILD_OS}:pn-${PN}"
> 
>  ##################################################################
>  # Include the rest of the config files.
> 
> Best Regards,
> J.

Is there really a case for a ${TARGET_ARCH}_${SOC_FAMILY} override.  If these devices have different architectures are they really part of the same family?

As for adding this to bitbake.conf I guess I wouldn't object, but I don't know that this is something everyone would want.  Instead you could put this in your distro's conf file (like angstrom does) or in your local.conf file.

The distro/include/angstrom.inc file sets:

OVERRIDES .= ":${FEED_ARCH}:${SOC_FAMILY}"

I use SOC_FAMILY overrides in my work.

Just my two cents
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel