[oe] New meta-cubox layer

[Martin Jansa]

Yes that looks correct, you can also find this thread
http://patches.openembedded.org/patch/37055/ interesting (better on other
archive, but linuxtogo is down now).

Unfortunately that RFC was rejected, so DISTROs have to hardcode list of
supported MACHINEs and their defaulttunes, SHR does the same in:
https://github.com/shr-distribution/meta-smartphone/blob/shr/meta-shr/conf/distro/include/defaulttunes.inc


On Thu, Apr 4, 2013 at 12:29 AM, Carlos Rafael Giani
<dv at pseudoterminal.org>wrote:

> On 2013-04-04 00:21, Khem Raj wrote:
>
>> On Apr 3, 2013, at 2:45 PM, Otavio Salvador <otavio at ossystems.com.br>
>> wrote:
>>
>>  On Wed, Apr 3, 2013 at 5:49 PM, Carlos Rafael Giani
>>> <dv at pseudoterminal.org> wrote:
>>>
>>>> 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?
>>>>
>>> You may provide a machine variant with has this set; so it will build
>>> a machine with this enabled.
>>>
>> I would say no. Weather to choose Hard float or not is more of a
>> capability that machine exposes
>> but distro decided the policy see how its done in angstrom for beagle
>> board and beagle bone
>>
>>
> You mean this file? https://github.com/Angstrom-**
> distribution/meta-angstrom/**blob/master/conf/distro/**
> include/arm-defaults.inc<https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/arm-defaults.inc>
>
> ______________________________**_________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.**openembedded.org<Openembedded-devel at lists.openembedded.org>
> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**openembedded-devel<http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel>
>