From: Mark Hatle <mark.hatle@windriver.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: What is GMAE?
Date: Fri, 14 Dec 2012 18:53:14 -0600 [thread overview]
Message-ID: <50CBC9FA.7090605@windriver.com> (raw)
In-Reply-To: <CAFZh4h-nVqnzFVH8SsmKyJL+=8DPa6ew-YQG1=dy2j13kxCtSA@mail.gmail.com>
On 12/14/12 3:57 PM, Brian Hutchinson wrote:
> On Fri, Dec 14, 2012 at 4:09 PM, Zhang, Jessica <jessica.zhang@intel.com> wrote:
>> Actually I talked with Richard regarding retiring the toolchain targets (meta-toolchain and meta-toolchain-gmae) as Mark mentioned that now we can build a toolchain matching the >image. Also, we're continue improving adt-installer which also allows you to setup sysroot using the target image as well. Richard's concern is there maybe some legacy user that >preferred the toolchain target. With the latest changes in toolchain generation which really maps to target images, probably we should unplug to legacy ones to make the toolchain generation more streamline. Thoughts or concerns?
>
> I'm one of the users that is stuck using Edison 6.0. I'm desperate
> for the ability to generate a toolchain and sysroot that matches our
> target. Right now I have to build meta-toolchain and then manually
> look in the tmp for sysroot-destdir related stuff from our build and
> copy it to the sysroot in /opt/poky and hand that out to developers.
> When our sister group overseas makes a change that effects the sysroot
> it breaks our build and I have to figure out what happened and
> manually adjust our sysroot to fix the problem. I sure would like to
> be able to just do an update and then bitbake the toolchain to pick up
> the changes. I figure we are stuck with Edison for a while ... can I
> back port these toolchain features you all are talking about to
> Edison?
There are changes to both bitbake and oe-core required. You'll have to look
back at the oe-core mailing list to find the right set to backport.
We have backported the items to our 1.2 (7.0 Denzil) based system, but I'm not
aware of anyone who is using it in 1.1 (6.0 Edison).
--Mark
> Regards,
>
> Brian
>
next prev parent reply other threads:[~2012-12-15 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 19:43 What is GMAE? Tim Bird
2012-12-14 19:46 ` Burton, Ross
2012-12-14 19:50 ` Robert P. J. Day
2012-12-14 20:45 ` Mark Hatle
2012-12-14 21:09 ` Zhang, Jessica
2012-12-14 21:57 ` Brian Hutchinson
2012-12-14 22:58 ` Zhang, Jessica
2012-12-15 0:53 ` Mark Hatle [this message]
2012-12-15 17:44 ` Jack Mitchell
2012-12-14 22:12 ` Tim Bird
2012-12-15 0:50 ` Mark Hatle
2012-12-15 11:04 ` Robert P. J. Day
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=50CBC9FA.7090605@windriver.com \
--to=mark.hatle@windriver.com \
--cc=b.hutchman@gmail.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.