From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][meta-oe][meta-toolchain][PATCH] meta-toolchain: populate with gcc and binutils from meta-oe
Date: Thu, 22 Mar 2012 13:32:01 +0100 [thread overview]
Message-ID: <jkf63s$8hf$1@dough.gmane.org> (raw)
In-Reply-To: <CAMKF1sqXOfFU+qG-8xzP0TqGTYVADxf44rHW112eLiVHzJH=NQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 22-03-12 13:23, Khem Raj schreef:
> On Thu, Mar 22, 2012 at 3:27 AM, Koen Kooi <koen@dominion.thruhere.net>
> wrote: Op 22-03-12 11:15, Koen Kooi schreef:
>>>>
>>>> Op 22 mrt. 2012, om 11:07 heeft Martin Jansa het volgende
>>>> geschreven:
>>>>
>>>>> On Thu, Mar 22, 2012 at 11:01:39AM +0100, Koen Kooi wrote:
>>>>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>>>>>
>>>>> Why not move them?
>>>>
>>>> This was done to have people test it in the oe-core +
>>>> meta-toolchain setup. And to avoid bblayers.conf conflicts
>>>>
>>>>> Or create stub of meta-toolchain in 1st patch for people to add
>>>>> it to bblayers and then move it in 2nd.
>>>>
>>>> That sounds like a better way to do it. Maybe Eric will do that in
>>>> his patchset :)
>
> I don't have a strong opinion on this and if Eric wants me to respin the
> RFC I'll gladly do that. But I would prefer that I can be lazy and just
> merge other peoples patches :)
>
>> yes git move should be better since then we can do git log --follow I
>> dont know if that works with copied files too or not.
>
>> meta-toolchain may not be the best name since we already have
>> meta-toolchain as a target for sdk generation. that should actually
>> have been called sdk but here we will create a confusion. but may be
>> target in OE-Core should ve renamed too
I'm fine with calling it 'toolchain-layer' and not using the 'meta' prefix.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPaxu+AAoJEHZqAkdh1vT6GL8P/3ctciJfWKTgKaOLlSdtTvCD
M1f6p06mm81ZRy2jvrxiB0Ui/TVI7QBRnRZ7Cq+FaCe9vOFXLmINL1ljIYSB3Fkz
CxZBc+wj6BDuPGk6SHN13lhYJgZmKcTY/mfYT2sp4R+VEC/Zv4M8o2SB7qUuLxuY
wWtP8O1/ydJTvdk/IcPMDSoRtNRM+pHBd/grt20N2l7c8/80SYM2xFQAG/ACDNmt
oHFFzNfg46c9YaB9aAey02OLaC/sh0r9NrZ6vQcRZp1bDf0RlIprTpBBDANfp2ss
hEQhZTZmYN44JtmrJBK7fnpxxjNvRK1E24+rWFQSR+0rFzFNBsOtOGypegxN5VAs
ypcOjUBvNF4TivxZUAcxLOTEN4YgW93pbp/lDVhGgiGIAPYMclHPP8By8dhI6ErE
JLbWrQGAV87wux+KKAkYzXzO25NeMGo0TZc35wnTsT+P+/q4aqZyK9eV9b+p73lF
O1GqN5MyGHWOGM8Xbfjx6ycaeArrUxBqdk5omcxlmM/ieeDwAQWrGKWNxChmXbN9
Mu7dMqSLCnCV4d8xSX8HCZuIhhdqDGVmL5MSTAW5930+6Sdaa8OfdRd6m9Y26Mpf
SYAparX2d6YBdvTCDrO8O1Bukx+6LXXN5PThP975euhdL5pasOwjl3M77J87LGJh
oznZSDS/uXbq9lRFSx6+
=nkR0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-22 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 10:01 [RFC][meta-oe][meta-toolchain][PATCH] meta-toolchain: populate with gcc and binutils from meta-oe Koen Kooi
2012-03-22 10:07 ` Martin Jansa
2012-03-22 10:12 ` Eric Bénard
2012-03-22 10:20 ` Martin Jansa
2012-03-22 10:15 ` Koen Kooi
2012-03-22 10:27 ` Koen Kooi
2012-03-22 12:23 ` Khem Raj
2012-03-22 12:32 ` Koen Kooi [this message]
2012-03-22 10:09 ` Eric Bénard
2012-03-22 14:33 ` Paul Eggleton
2012-03-22 14:36 ` Paul Eggleton
2012-03-22 16:08 ` Khem Raj
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='jkf63s$8hf$1@dough.gmane.org' \
--to=koen@dominion.thruhere.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