On Mon, 2011-08-01 at 00:36 -0700, Saul Wold wrote: > From: Mark Hatle <[email protected]> > > We need to add the tune-* override in order for more complicated tune > features to function properly. > > Signed-off-by: Mark Hatle <[email protected]> > --- > meta/conf/bitbake.conf | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf > index 9c80f11..11dfb6d 100644 > --- a/meta/conf/bitbake.conf > +++ b/meta/conf/bitbake.conf > @@ -637,9 +637,10 @@ AUTO_LIBNAME_PKGS = "${PACKAGES}" > # > # 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 = > "${TARGET_OS}:${TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:forcevariable" > +OVERRIDES = > "${TARGET_OS}:${TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${TUNEOVERRIDES}:${DISTROOVERRIDES}:forcevariable" > DISTROOVERRIDES ?= "${DISTRO}" > MACHINEOVERRIDES ?= "${MACHINE}" > +TUNEOVERRIDES ?= "tune-${DEFAULTTUNE}"
What exactly are the "more complicated tune features" that require this? It's not obvious to me that this is a good idea. p. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
