From: William Mills <wmills@ti.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
Koen Kooi <koen@beagleboard.org>
Subject: Re: proper recipe for building for beagle xM? meta-ti?
Date: Fri, 2 Mar 2012 17:50:48 -0500 [thread overview]
Message-ID: <4F514EC8.8000606@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1203021729040.31351@oneiric>
On 03/02/2012 05:33 PM, Robert P. J. Day wrote:
> On Fri, 2 Mar 2012, William Mills wrote:
>
> ... snip ...
>
>> Congratulations you are the first beta tester for the new README.txt
>> language :) (patched two days ago).
>>
>> Denys: I suggest
>>
>> change:
>>
>> "Due to the above, it is now recommended to follow the instructions
>> at http://www.angstrom-distribution.org/building-angstrom"
>>
>> to:
>>
>> "When the other layer combinations are supported instructions will
>> be supplied here. Until that time please see the Angstrom setup
>> instructions below.
>>
>> *** Angstrom w/ meta-ti Layer Stack setup: ***
>> Please follow the instructions at
>> http://www.angstrom-distribution.org/building-angstrom"
>
> i might try something a bit different. given that angstrom is the
> tested way to go, by all means, point that out and *strongly*
> recommend that approach.
>
> on the other hand, what is the current issue with the yocto/meta-ti
> combo? is it *known* to be broken? or is it simply not sufficiently
> tested? in cases like that, i see no problem in cautioning people
> about it, but telling them that if they're feeling adventurous,
> they're welcome to give it a shot but if it breaks, as they say, they
> get to keep all the pieces.
>
> don't discourage people from trying it, but make sure you give
> proper instructions for how to use it, that's all. unless, as i said,
> it's really and truly unusable.
We will update the README when it is merely in need of testing.
Today, we know there is code that does not work with GCC 4.6.
Today, we know there are features in the recipes that do not work w/o
Angstrom.
As soon as we remove the above for even one platform we will update the
README to reflect an Alpha state for oc-core &| poky layer stack for
that platform(s).
next prev parent reply other threads:[~2012-03-02 22:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:51 proper recipe for building for beagle xM? meta-ti? Robert P. J. Day
2012-02-28 21:22 ` Bruce Ashfield
2012-02-28 21:55 ` Robert P. J. Day
2012-02-28 22:09 ` Koen Kooi
2012-02-28 22:28 ` Robert P. J. Day
2012-03-02 10:06 ` Koen Kooi
2012-03-02 16:45 ` Stewart, David C
2012-03-02 16:51 ` Robert P. J. Day
2012-03-02 17:15 ` Koen Kooi
2012-03-02 22:22 ` William Mills
2012-03-02 22:33 ` Robert P. J. Day
2012-03-02 22:50 ` William Mills [this message]
2012-03-02 23:18 ` Gary Thomas
2012-03-03 0:07 ` William Mills
2012-03-04 6:18 ` Denys Dmytriyenko
2012-03-04 12:19 ` Robert P. J. Day
2012-03-04 12:36 ` Gary Thomas
2012-03-04 12:54 ` Robert P. J. Day
2012-03-04 17:01 ` Koen Kooi
2012-03-04 18:14 ` Robert P. J. Day
2012-03-04 19:27 ` Denys Dmytriyenko
2012-03-04 19:43 ` Robert P. J. Day
2012-03-04 19:45 ` Gary Thomas
2012-03-04 20:01 ` Brian Hutchinson
2012-03-04 20:04 ` Denys Dmytriyenko
2012-03-04 21:18 ` Robert P. J. Day
2012-03-05 5:12 ` [yocto] " Denys Dmytriyenko
2012-03-05 11:00 ` Robert P. J. Day
2012-03-04 21:38 ` Robert P. J. Day
2012-03-05 4:26 ` Denys Dmytriyenko
2012-03-05 9:52 ` Jack Mitchell
2012-03-04 6:08 ` Denys Dmytriyenko
2012-02-28 22:12 ` Bruce Ashfield
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=4F514EC8.8000606@ti.com \
--to=wmills@ti.com \
--cc=koen@beagleboard.org \
--cc=rpjday@crashcourse.ca \
--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.