[oe] New meta-cubox layer
Koen Kooi
koen at dominion.thruhere.net
Wed Apr 3 20:19:10 UTC 2013
Op 3 apr. 2013, om 22:07 heeft Philip Balister <philip at balister.org> het volgende geschreven:
> On 04/03/2013 03:57 PM, Koen Kooi wrote:
>>
>>
>> Op 3 apr. 2013 om 21:34 heeft Philip Balister <philip at balister.org> het volgende geschreven:
>>
>>> On 04/03/2013 02:38 PM, Koen Kooi wrote:
>>>> Op 03-04-13 18:50, Carlos Rafael Giani schreef:
>>>>
>>>> Just like https://github.com/naguirre/meta-cubox you're mixing
>>>> DISTRO policy in the machine files by setting the tuning to
>>>> hardfloat. Don't do that. If you want hardfloat, set that in your
>>>> distro config, not in your machine config.
>>>
>>> This keeps coming up, but I do not see an answer that works for people
>>> creating BSP's that work with just oe-core and a BSP layer.
>>>
>>> How are we supposed to set TUNE parameters for this case? And yes,
>>> this case *must* produce useful output.
>>
>> 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.
>
> Philip
>
>
>>
>>
>>
>>>
>>> Philip
>>>
>>>
>>>>
>>>>
>>>> _______________________________________________ Openembedded-devel
>>>> mailing list Openembedded-devel at lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>>
>>>>
>>>>
>>
>>
More information about the Openembedded-devel
mailing list