Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: canadian-cross sdk?
Date: Tue, 13 Jul 2010 17:37:22 +0100	[thread overview]
Message-ID: <1279039042.28835.1133.camel@rex> (raw)
In-Reply-To: <4C3B5573.9010207@mentor.com>

On Mon, 2010-07-12 at 10:48 -0700, Tom Rini wrote:
> Richard Purdie wrote:
> > On Mon, 2010-07-12 at 11:05 +0600, Dmitry Vinokurov wrote:
> >> This question is important for me to. I'm running OE on linux-x86_64 
> >> machine and want to build ARM toolchain for linux-x86 machine. I've 
> >> asked about it on #irc and CruX| gave me config for building mingw32 
> >> toolchain, it's in attachment and maybe it'll be helpful for you. 
> >> Unfortunately, I couldn't adapt this config for my task, OE tries to 
> >> build mingw all the same.
> >>
> >> It would be great if someone explain how to build canadian cross SDK. I 
> >> haven't found nothing helpful about it neither in documentation nor in 
> >> ML archives but it is very important question I think.
> > 
> > The canadian toolchain bits in OE are still in need to some attention to
> > fully enable the case where the build machine is not the same as the
> > machine you want to run the SDK on.
> > 
> > In Poky this works already, you'd set SDKMACHINE=i586 and then
> > "MACHINE=qemuarm bitbake meta-toolchain".
> 
> So, if one wanted to update oe.dev again, is what's in poky's master 
> what works for you guys now?

Yes, absolutely. This is getting a lot of testing atm.

Cheers,

Richard





      reply	other threads:[~2010-07-13 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06  3:29 canadian-cross sdk? Angus Lees
2010-07-12  5:05 ` Dmitry Vinokurov
2010-07-12 14:57   ` Richard Purdie
2010-07-12 17:48     ` Tom Rini
2010-07-13 16:37       ` Richard Purdie [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=1279039042.28835.1133.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@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