From: Esben Haabendal <EsbenHaabendal@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: sdk.bbclass and gcc-cross-sdk
Date: Fri, 07 Mar 2008 23:32:37 +0100 [thread overview]
Message-ID: <47D1C285.2000703@gmail.com> (raw)
In-Reply-To: <1204748655.8110.174.camel@dax.rpnet.com>
Richard Purdie skrev:
> On Wed, 2008-03-05 at 20:06 +0100, Leon Woestenberg wrote:
>
>> On Wed, Mar 5, 2008 at 7:11 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
>>
>>> What do I propose as a solution? I think the simplest thing is to would
>>> be to do some/all of:
>>>
>>> a) revert my sdk.bbclass changes
>>> b) continue with our build == host assumption for gcc-cross-sdk for now
>>> c) rename sdk.bbclass cross-sdk.bbclass
>>> d) add a "real" sdk.bbclass
>>>
>>>
>> Before a), I would like to see a description of what we expect the
>> different classes to do, simply because I have lost track. I
>> understood we never supported building Canadian cross-compilers, BTW.
>>
>
> The 'normal' situation for OE is:
>
> build = "build system"
> host = target = "set by machine config"
>
> cross.bbclass:
>
> build = host = "build system"
> target = "set by machine config"
>
> native.bbclass:
>
> build = host = target = "build system"
>
> sdk.bbclass (previously)
>
> build = host = "build system"
> target = "set by machine config"
>
> sdk.bbclass (previously)
>
> build = "build system"
> host = "build system with modified vendor"
> target = "set by machine config"
>
>
>> There are other projects that focus on the correctness of building
>> cross toolchains*, canadian or non-canadian, and if we have clear
>> requirements for each of our classes, I would like to see if I can
>> understand what we do (correctly or not).
>>
>
> So sdk.bbclass did become a kind of Canadian cross but only with a
> different vendor part of the triplet. I'd not realised this had changed
> what gcc-cross-sdk was doing so drastically since it still worked!
>
> "gcc" is a normal package, "gcc-initial" and "gcc-cross" are cross
> packages, gcc-cross-sdk is an sdk package.
>
> We could support building canadian cross if we wanted, Id propose a new
> class for it though (sdk-canadian?). Does that cover what you wanted?
>
I would love to see canadian cross support in OE. It would save me the
effort maintaining an OE hacked up to build a standard meta-toolchain
target.
If there is interest in it, I wouldn't mind working on this issue. And
if I am the only one interested in it, I might want to do it anyway.
Just for fun :-)
/Esben
next prev parent reply other threads:[~2008-03-07 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 18:11 sdk.bbclass and gcc-cross-sdk Richard Purdie
2008-03-05 19:06 ` Leon Woestenberg
2008-03-05 20:24 ` Richard Purdie
2008-03-06 22:58 ` Leon Woestenberg
2008-03-07 10:12 ` Richard Purdie
2008-03-07 22:32 ` Esben Haabendal [this message]
2008-03-08 15:47 ` Florian Boor
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=47D1C285.2000703@gmail.com \
--to=esbenhaabendal@gmail.com \
--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