From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFC: external toolchain recipes in OE-Core
Date: Mon, 2 Dec 2013 17:28:04 +0100 [thread overview]
Message-ID: <20131202162804.GB3714@jama> (raw)
In-Reply-To: <1471026.rDxeBhQvgN@helios>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
On Mon, Dec 02, 2013 at 04:18:52PM +0000, Paul Eggleton wrote:
> 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
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.
> 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.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-12-02 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 16:18 RFC: external toolchain recipes in OE-Core Paul Eggleton
2013-12-02 16:28 ` Martin Jansa [this message]
2013-12-02 16:28 ` Burton, Ross
2013-12-02 19:29 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131202162804.GB3714@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox