[meta-ti] building Yocto for Pandaboard

[William Mills]

On 02/08/2012 05:51 PM, James Abernathy wrote:
>
> On Feb 8, 2012, at 5:34 PM, Gary Thomas wrote:
>
>> On 2012-02-08 15:27, Koen Kooi wrote:
>>>
>>> Op 8 feb. 2012, om 23:22 heeft Gary Thomas het volgende geschreven:
>>>
>>>> On 2012-02-08 15:18, Koen Kooi wrote:
>>>>>
>>>>> Op 8 feb. 2012, om 23:11 heeft jfabernathy het volgende geschreven:
>>>>>
>>>>>> On 02/08/2012 05:05 PM, Gary Thomas wrote:
>>>>>>> On 2012-02-08 14:58, jfabernathy wrote:
>>>>>>>> I'm trying to build the pandaboard BSP for Yocto. I cloned the meta-ti repository in the poky directory and tried to build core-image-sato for both machine pandaboard and
>>>>>>>> omap4430-panda. However, I immediately get an error because bitbake is looking for recipes-images/angstrom/systemd-image.bb, which is required in the ti-hw-bringup-image.bb image
>>>>>>>> recipe.
>>>>>>>>
>>>>>>>> All I really included was the machine name change in local.conf and added the meta-ti layer in bblayers.conf.
>>>>>>>>
>>>>>>>> Did I miss a step?
>>>>>>>
>>>>>>> This was discussed last week.  Add this line to your local.conf
>>>>>>>   BBMASK = ".*/meta-ti/recipes-misc/"
>>>>>>> This will skip some BeagleBoard/BeagleBone recipes that are not
>>>>>>> currently working in a Yocto tree.
>>>>>>>
>>>>>> Thanks a bunch. That got it going.  The README said nothing
>>>>>
>>>>> Stop spreading such lies!
>>>>
>>>> It's not a lie, just a perspective.
>>>
>>> It *is* a lie, since the README is non-empty. Regardless of what you want to do, the README does contain content.

I for one read that as Gary intended, that the README did not say 
anything about how to get it to work with Yocto.  Can we word things is 
a less confrontational way please?

>>
>> Sorry, I thought you were referring to my work-around to get this
>> going in Yocto.  Obviously, he was looking for more info in the
>> README than just how to use this layer with Angstrom and I agree
>> that this "trick" probably does not belong in the README.
>>
>> --
>
> Wow!  Sorry I jumped into a mailing list I obviously don't understand or belong in.

There was nothing wrong with your question.

As Gary said there has not been too many end user questions on meta-ti 
yet.  Of course someone has to be first.

meta-ti is still in early development.  It started life working only in 
an Angstrom context.  We are making changes that will make most of it 
work with just oe-core or yocto/poky but that is not ready yet.  Gary's 
work around is an interesting approximation of what we are shooting for.

> I apologize if I offended.  I did read the README, but it didn't make a bit of sense to me because it talked about angstrom, which I don't know anything about and wondered what that had to do with yocto.  My current Yocto knowledge is based on the meta-intel layer, which doesn't mention angstrom.  It sounds like the hint/trick that Gary mentioned will make bitbake build with just yocto, which is what I want.  My goal is more of a proof of concept.  I'd like to prove if you could take the same image recipe and move it from Pandaboard to Atom and vice versa.  That way a developer could pick the hardware platform based on the performance, features, and cost.  The software effort should be minimal to move if the Yocto concept works as advertised.
>
> Jim A
>
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti
>
> _______________________________________________
> meta-ti mailing list
> meta-ti at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti