From: Denys Dmytriyenko <denis@denix.org>
To: Anjandeep Sahni <x0212391@ti.com>
Cc: "poky, mailing-list" <poky@yoctoproject.org>
Subject: Re: External Toolchain
Date: Fri, 28 Mar 2014 12:42:19 -0400 [thread overview]
Message-ID: <20140328164219.GG3370@denix.org> (raw)
In-Reply-To: <53354CED.4090700@ti.com>
On Fri, Mar 28, 2014 at 03:50:29PM +0530, Anjandeep Sahni wrote:
> Hi all,
>
> I am fairly new to poky. Just had a few queries.
>
> I wanted to know where exactly in the build directory does poky
> build the default toolchain.
> And also if I have to use an external linaro toolchain, how would I
> go about it? Should I just include the meta-linaro layer, and add
> the TCMODE variable to local.conf?
> I downloaded and extracted the prebuilt binaries for linaro
> toolchain. How do I point my build system to use these instead of
> the default toolchain?
Anjandeep,
Please take a look at the presentation I gave at the last year ELC:
http://elinux.org/images/c/c8/ExternalToolchainsInYocto.pdf
Also, feel free to ping me directly at denys@ti.com if you are working on a
project for TI - there's a lot of re-use potential...
--
Denys
next prev parent reply other threads:[~2014-03-28 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 10:20 External Toolchain Anjandeep Sahni
2014-03-28 16:42 ` Denys Dmytriyenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 9:26 external toolchain Virgilia Eigner
2015-11-19 7:01 ` Khem Raj
2015-11-20 9:18 ` Virgilia Eigner
2015-10-28 18:37 External toolchain Virgilia Eigner
2015-10-28 18:46 ` Khem Raj
2012-07-12 19:20 external toolchain Dallas Clement
2012-07-12 19:23 ` Chris Larson
2011-02-24 9:13 External toolchain Luca Bolognini
2011-02-23 11:49 Luca Bolognini
2011-02-23 19:28 ` Khem Raj
2011-02-24 4:07 ` Denys Dmytriyenko
2011-02-22 9:16 Luca Bolognini
2011-02-22 9:47 ` Ahsan, Noor
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=20140328164219.GG3370@denix.org \
--to=denis@denix.org \
--cc=poky@yoctoproject.org \
--cc=x0212391@ti.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 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.