Okay, I think I see the problem now. DEFAULTTUNES should not be set by
the machine config. So, removing it
and fixing the README accordingly takes care of that. People who for
example want hardfp then
set DEFAULTTUNE ?= "marvellpj4hf" in their local.conf . Is this correct?
On 2013-04-03 22:19, Koen Kooi wrote:
Local.conf
Fail. This means BSP providers are depending on users to do the right thing.
"The right thing"? Is forcing RPM package management "the right thing"? Is moving
DEPLOY_DIR "the right thing"?
The BSP should be able to say what it wants
For MACHINE settings yes, for DISTRO settings, no
and a distro layer needs to
override the BSP choice for distributions providing binaries for
multiple machines.
DISTRO settings in a BSP violates the Yocto Compatible rules as well as the
established OE rules, I don't see why that should get changed.
In this specific case, a BSP can set COMPATIBLE_HOST on the recipes that need
to be hardfloat.
In OE classic we had an ABI flag to set this globally, in OE-core the powers
that be force us to set a tune per machine in the DISTRO config. The price of
progress I guess.
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
