All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Thornburg, Christopher A" <christopher.a.thornburg@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: How to use pre-built external Yocto toolchain
Date: Thu, 28 Nov 2013 13:17:17 +0000	[thread overview]
Message-ID: <16697287.VBkEKFbcaF@helios> (raw)
In-Reply-To: <752F65977A748344A01D69BF22DCDBAE4FDDDA9B@FMSMSX105.amr.corp.intel.com>

Hi Christopher,

On Wednesday 27 November 2013 23:02:43 Thornburg, Christopher A wrote:
> I must be missing something obvious. It's easy for me to build and install a
> toolchain package using bitbake meta-toolchain
> The resulting toolchain package shows up at...
> ./tmp/deploy/sdk/poky-eglibc-i686-meta-toolchain-core2-toolchain-1.5.sh
> ...which is easy to install.
> 
> It seems the proper way to use such an external toolchain would be to set
> TCMODE, but TCMODE only seems to support 'default' (i.e. build an internal
> toolchain) and 'external-sourcery' (i.e. use an external sourcery
> toolchain). :S
> 
> How do I use an external toolchain built as above?

We don't support this; if you're going to use our toolchain it's expected that 
you let the build system take care of building it. If what you want is to 
accelerate repeat builds or builds of the same source on different machines, 
the solution for that is to use shared state (using SSTATE_MIRRORS to share 
between different build machines, if needed).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-11-28 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 23:02 How to use pre-built external Yocto toolchain Thornburg, Christopher A
2013-11-28 13:17 ` Paul Eggleton [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=16697287.VBkEKFbcaF@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=christopher.a.thornburg@intel.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.