From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Using Pre Built Toolchain in Yocto Tree
Date: Fri, 13 Mar 2015 09:03:39 -0600 [thread overview]
Message-ID: <5502FC4B.6010802@mlbassoc.com> (raw)
In-Reply-To: <5502F87A.90208@windriver.com>
On 2015-03-13 08:47, Mark Hatle wrote:
> On 3/13/15 6:43 AM, Darshan Patel wrote:
>> Is there a way to configure Yocto to use Pre Built toolchain (like downloaded
>> from CodeSourcery, etc.). I want to avoid building toolchain because it takes
>> too much time and using new toolchain is not of my concern.
>
> If you wish to use the Mentor Sourcery toolchain, they have a layer available
> that allows you to incorporate it.
>
> https://github.com/MentorEmbedded/meta-sourcery
>
> I have not used this layer in a while (and I don't work for Mentor), so if you
> have questions you may need to find someone who is more familiar with the layer.
>
>
> There is another alternative though. Build the toolchain once, store the
> sstate-cache files that were generated and use those on subsequent builds.
> There is a mechanism called the locked sstate-cache where you can feed into your
> configuration the hashes for the sstate-cache item you are interested in. This
> will tell the system to simply re-use the components, and ignore any system
> changes that may have occurred.
Could you elaborate on this (locked sstate-cache)? I don't see any
mention of it in the documentation.
>
> --Mark
>
>> I was using this feature in buildroot.
>>
>> Thanks in Advance!!!
>>
>> --
>> Regards
>> Darshan
>>
>>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-03-13 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 11:43 Using Pre Built Toolchain in Yocto Tree Darshan Patel
2015-03-13 13:50 ` Maxin John
2015-03-13 14:02 ` Maxin John
2015-03-13 14:47 ` Mark Hatle
2015-03-13 15:03 ` Gary Thomas [this message]
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=5502FC4B.6010802@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.