From: Rich Pixley <rich.pixley@palm.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake versions
Date: Thu, 09 Feb 2012 12:06:35 -0800 [thread overview]
Message-ID: <4F34274B.60502@palm.com> (raw)
In-Reply-To: <CAMKF1so61ndkzii_qK-sLiX6czvHXvaMFvBsxzm78z87zRTQkA@mail.gmail.com>
Er... wasn't doing so intentionally. Was just following the "getting
started" page on the wiki.
I think that page needs to be adjusted to at least warn folks that it's
stale. That probably isn't the right way to "get started" today.
I'll start over from 'core.
--rich
On 2/8/12 17:47 , Khem Raj wrote:
> On Wed, Feb 8, 2012 at 3:26 PM, Rich Pixley<rich.pixley@palm.com> wrote:
>> I'm having trouble even parsing using bitbake> 1.12.
>>
>> Am I right in thinking that the openembedded tree isn't ready to be built
>> with bitbake> 1.12?
> I have used 1.10.x successfully with old oe classic but that was sometime ago
> if you want to use oe classic please use the
> 2011.03-maintenance branch you stand a better chance with that branch
>
>
>> If so, then the getting started document should probably include this info.
> yes getting started should reflect how to get started with layered oe.
>
>> --rich
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-02-09 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 23:26 bitbake versions Rich Pixley
2012-02-09 1:47 ` Khem Raj
2012-02-09 20:06 ` Rich Pixley [this message]
2012-02-09 21:14 ` Khem Raj
2012-02-09 9:01 ` Andrei Gherzan
2012-02-09 9:42 ` Frans Meulenbroeks
2012-02-09 14:49 ` 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=4F34274B.60502@palm.com \
--to=rich.pixley@palm.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 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.