From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Felix01 Fischer <felix01.fischer@iav.de>,
Nitin A Kamble <nitin.a.kamble@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Confused which layers are needed for meta-intel/meta-crownbay
Date: Tue, 14 May 2013 10:22:53 +0100 [thread overview]
Message-ID: <5657638.Np3iF1lsb7@helios> (raw)
In-Reply-To: <OFF65EFDAC.F177D7D1-ONC1257B6B.002720EC-C1257B6B.00288BEC@retarus.de>
Hi Felix,
On Tuesday 14 May 2013 09:22:53 Felix01 Fischer wrote:
> I'm currently trying to build a booting core-image-sato image with MACHINE
> ?="crownbay". I'm using poky 9.0.0 and meta-intel (dylan branch).
>
> I've discovered something which confuses me:
>
> First meta-intel/meta-crownbay/README states that it is to be used with
> the openembedded.org bitbake and openembedded-core layer (both on branch
> master). Isn't this opposite in using yocto (as both provide bitbake) ?
It's not the opposite, it's the same. Poky is composed of openembedded-core,
bitbake, yocto-docs and a few other bits and pieces; so you can either use
poky here or openembedded-core + bitbake.
> Second meta-intel/meta-crownbay/README.sources points to yocto-1.3 (Line
> 10).
This is an oversight. Nitin, can you please correct this or avoid having the
fixed version URL in the document at all?
> Is it possible that these layers aren't ready for yocto 1.4 despite being
> packaged as "1.4-final", "1.4" and "danny-9.0.0"?
No, I think this is just a case where the URL hasn't been updated in the
README.sources file.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-14 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:22 Confused which layers are needed for meta-intel/meta-crownbay Felix01 Fischer
2013-05-14 9:22 ` Paul Eggleton [this message]
2013-05-14 9:34 ` Antwort: " Felix01 Fischer
2013-05-14 9:44 ` Paul Eggleton
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=5657638.Np3iF1lsb7@helios \
--to=paul.eggleton@linux.intel.com \
--cc=felix01.fischer@iav.de \
--cc=nitin.a.kamble@intel.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.