Skip to contentSkip to conversation

RFC: external toolchain recipes in OE-Core

DISCUSSION Paul Eggleton 4 participants 4 messages Dec 2, 2013

lore
Share & tools
lore
#0 lore raw

Hi all,

Currently we have an external-sourcery-toolchain recipe in OE-Core; one of the main reasons we have it there is as an example of how to create a working external toolchain recipe for those that need to create their own. Since the creation of the meta-sourcery layer however, this recipe has been left largely unmaintained. Even assuming nobody tries to use it as-is with the CodeSourcery toolchain, without testing and maintenance the recipe can bitrot (and has broken as a result of changes elsewhere in OE-Core), and thus any external toolchain recipe created based upon it may end up not working either. We need to come up with a plan for what to do with this recipe - here are some possibilities:

A) Keep it in OE-Core and ensure it is tested and maintained

B) Remove it and just point to meta-sourcery as a maintained and working example of how to write an external toolchain recipe

C) Replace it with a less concrete example recipe in meta-skeleton that we maintain going forward

What do people think?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#1 lore raw
Quoted 13 lines · Paul Eggleton

Hi all,

Currently we have an external-sourcery-toolchain recipe in OE-Core; one of the main reasons we have it there is as an example of how to create a working external toolchain recipe for those that need to create their own. Since the creation of the meta-sourcery layer however, this recipe has been left largely unmaintained. Even assuming nobody tries to use it as-is with the CodeSourcery toolchain, without testing and maintenance the recipe can bitrot (and has broken as a result of changes elsewhere in OE-Core), and thus any external toolchain recipe created based upon it may end up not working either. We need to come up with a plan for what to do with this recipe - here are some possibilities:

Quoted 4 lines

A) Keep it in OE-Core and ensure it is tested and maintained

B) Remove it and just point to meta-sourcery as a maintained and working example of how to write an external toolchain recipe

This looks best to me. Maybe with another link to external linaro toochain which is probably used by many people and to show that it's just an example and recipes for external toolchain + tcmode need to be adjusted to specific toolchain.

Quoted 2 lines

C) Replace it with a less concrete example recipe in meta-skeleton that we maintain going forward

I fear that less concrete example will bitrot even faster and won't be easy to test and fix without creating concrete recipe from it.

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
In reply to Paul Eggleton
Quoted 2 lines · Paul Eggleton

B) Remove it and just point to meta-sourcery as a maintained and working example of how to write an external toolchain recipe

This seems like the easiest option that will continue to work in the long-term. As toolchains are all different a less concrete example doesn't seem very useful as it will be too abstract to be tested.

Ross

#3 lore raw
Quoted 7 lines · Ross
Quoted 2 lines · Paul Eggleton

B) Remove it and just point to meta-sourcery as a maintained and working example of how to write an external toolchain recipe

This seems like the easiest option that will continue to work in the long-term. As toolchains are all different a less concrete example doesn't seem very useful as it will be too abstract to be tested.

Agreed; this allow us to reduce the amount of QA work for Yocto fellows as well.

Signature · 3 lines
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750