From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Using meta-toolchain output as prebuilt toolchains
Date: Mon, 28 Mar 2011 11:58:18 -0700 [thread overview]
Message-ID: <4D90DA4A.3030605@mentor.com> (raw)
In-Reply-To: <600E597B-5D02-419E-A378-5EE511B848FA@dominion.thruhere.net>
On 03/27/2011 04:44 AM, Koen Kooi wrote:
> Hi,
>
> What is the preferred way of 'importing' prebuilt toolchains into OE-core? In oe.dev I can use this: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/meta/external-toolchain-angstrom.bb to 'import' an angstrom toolchain built with 'bitbake meta-toolchain', but I'm not sure how to do that in OE-core.
>
> My actual use case is actually 2 use-cases:
>
> 1) Hand people a prebuilt angstrom toolchain and migrate them to OE while keeping the toolchain
> 2) "Get started in 10 minutes" type of thing, I suspect an sstate mirror might be better.
>
> So any suggestions for #2 as well?
sstate is the best way to catch #2 and I know in general there's "look
at this URI for the file you want" bits. I haven't yet started kicking
the tires on sstate as hard as I have for packaged-staging however.
For #1, I believe external toolchains are to be supported still, but I
don't know off hand if the recipes still work (but there is both an old
CSL one as well as a poky toolchain one in meta/recipes-core/meta/).
Another area on my TODO list...
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-28 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 11:44 Using meta-toolchain output as prebuilt toolchains Koen Kooi
2011-03-27 19:34 ` Khem Raj
2011-03-27 20:26 ` Koen Kooi
2011-03-28 18:58 ` Tom Rini [this message]
2011-03-29 11:32 ` Gary Thomas
2011-03-29 15:32 ` Richard Purdie
2011-03-28 19:25 ` Richard Purdie
2011-03-31 19:36 ` Denys Dmytriyenko
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=4D90DA4A.3030605@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
/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