All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: Native/Cross/SDK rethink (Was: Re: RFC: "Virtual" native	and sdk recipes)
Date: Mon, 5 Jan 2009 08:42:10 -0700	[thread overview]
Message-ID: <20090105154209.GR400@smtp.west.cox.net> (raw)
In-Reply-To: <d2b9ea600901050631h5eda6de5yee190bf0841e5b15@mail.gmail.com>

On Mon, Jan 05, 2009 at 03:31:53PM +0100, Esben Haabendal wrote:
> On Fri, Jan 2, 2009 at 5:37 AM, Tom Rini <trini@kernel.crashing.org> wrote:
> > On Fri, Jan 02, 2009 at 01:11:53AM +0000, Richard Purdie wrote:
> >
> > [snip]
> >> Ideally I want to be able to generate a Linux 32 bit toolchain, a Linux
> >> 64 bit toolchain and a windows one. If I can do that using canadian-sdk,
> >> the current -sdk stuff can be removed.
> >
> > It's a theory, and not one I've tested (and I know it won't work _today_
> > as there's some hard-coded C:\ paths right now.  Those can die if we
> > build it properly relocatible like CodeSourcery does).
> 
> Sorry, but where would that be?
> 
> In class/canadian-sdk.bbclass:
> 
> SDK_PATH_sdk-mingw32 = "/OpenEmbedded/${SDK_NAME}"
> SDK_REALPATH = "${SDK_PATH}"
> SDK_REALPATH_sdk-mingw32 = "C:/OpenEmbedded/${SDK_NAME}"
> 
> Which should only hard-code C:/ into mingw32 toolchains.  I don't
> remember seing C:\

Just mis-remembered.  But the big point is we should be able to compile
everyone for /OpenEmbedded/${SDK_NAME} and it should just work.

-- 
Tom Rini



  reply	other threads:[~2009-01-05 15:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 16:25 RFC: "Virtual" native and sdk recipes Richard Purdie
2009-01-01 18:11 ` Koen Kooi
2009-01-01 20:07   ` Richard Purdie
2009-01-01 18:25 ` Tom Rini
2009-01-01 20:11   ` Richard Purdie
2009-01-01 22:02     ` Tom Rini
2009-01-02  1:11       ` Richard Purdie
2009-01-02  4:37         ` Native/Cross/SDK rethink (Was: Re: RFC: "Virtual" native and sdk recipes) Tom Rini
2009-01-05 14:31           ` Esben Haabendal
2009-01-05 15:42             ` Tom Rini [this message]
2009-01-05 17:29             ` Koen Kooi
2009-01-05 19:53               ` Tom Rini
2009-01-06 20:51               ` Esben Haabendal
2009-01-07  0:14                 ` Richard Purdie
2009-01-07  0:45                   ` Tom Rini
2009-01-08 22:59                   ` Leon Woestenberg
2009-01-09  0:54         ` RFC: "Virtual" native and sdk recipes Richard Purdie
2009-01-09  1:16           ` Tom Rini
2009-01-12 19:09             ` Tom Rini
2009-01-12 20:30             ` Esben Haabendal
2009-01-09 17:04           ` Tom Rini
2009-01-12 20:47             ` Tom Rini
2009-01-10 15:33           ` Tom Rini
2009-01-10 19:06             ` Tom Rini
2009-01-14  1:15           ` Tom Rini
2009-01-14 23:17             ` Tom Rini
2009-01-17  2:54               ` Tom Rini
2009-01-17  4:47           ` Tom Rini
2009-01-22 18:10             ` Tom Rini
2009-01-28 19:49               ` Tom Rini
2009-01-01 22:15 ` Tom Rini
2009-01-01 23:19 ` Richard Purdie
2009-01-03 11:17   ` Richard Purdie
2009-01-02 12:58 ` Koen Kooi
2009-01-14  0:03 ` Robert Schuster

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=20090105154209.GR400@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.