Confused which layers are needed for meta-intel/meta-crownbay

Confused which layers are needed for meta-intel/meta-crownbay

[Felix01 Fischer]

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hello,

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) ?

Second meta-intel/meta-crownbay/README.sources points to yocto-1.3 (Line 
10).

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"?


Viele Grüße

Felix Fischer

Studentischer Mitarbeiter (VC-D1)
Vehicle Cockpit Electronics Devices

IAV GmbH
Carnotstr. 1
10587 BERLIN
GERMANY

Phone: +49 30 39978-9540
Fax:      +49 30 39978-9411
E-Mail:  <mailto:felix01.fischer@iav.de>
Internet: http://www.iav.com

Sitz/Registered Office: Berlin, 
Registergericht/Registration Court: Amtsgericht Charlottenburg, 
Registernummer/Company Registration Number: HRB 21 280, 
Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert, 
Dr. Rüdiger Goyk
 

[-- Attachment #2: Type: text/html, Size: 1684 bytes --]

Re: Confused which layers are needed for meta-intel/meta-crownbay

[Paul Eggleton]

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

Antwort: Re: Confused which layers are needed for meta-intel/meta-crownbay

[Felix01 Fischer]

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]

> 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.
> 

First, thank you for your quick reply :-)

So I guess, it's fine only to add meta-intel and meta-intel/meta-crownbay 
to BBLayers and not openembedded-core and bitbake, too?

If so, why not remove this confusing reference to open-embedded?

> > 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



Viele Grüße

Felix Fischer

Studentischer Mitarbeiter (VC-D1)
Vehicle Cockpit Electronics Devices

IAV GmbH
Carnotstr. 1
10587 BERLIN
GERMANY

Phone: +49 30 39978-9540
Fax:      +49 30 39978-9411
E-Mail:  <mailto:felix01.fischer@iav.de>
Internet: http://www.iav.com

Sitz/Registered Office: Berlin, 
Registergericht/Registration Court: Amtsgericht Charlottenburg, 
Registernummer/Company Registration Number: HRB 21 280, 
Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert, 
Dr. Rüdiger Goyk

[-- Attachment #2: Type: text/html, Size: 2911 bytes --]

Re: Confused which layers are needed for meta-intel/meta-crownbay

[Paul Eggleton]

On Tuesday 14 May 2013 11:34:38 Felix01 Fischer wrote:
> > 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.
> 
> First, thank you for your quick reply :-)
> 
> So I guess, it's fine only to add meta-intel and meta-intel/meta-crownbay
> to BBLayers and not openembedded-core and bitbake, too?

No, if you are already using poky, you wouldn't add openembedded-core to 
bblayers.conf and you would never add bitbake there (bitbake is the build 
tool, it's not a layer).
 
> If so, why not remove this confusing reference to open-embedded?

Most layers declare these dependencies because some users prefer to use 
separate openembedded-core and bitbake rather than the combined poky, and it 
is the established convention within the layer documentation to declare the 
separate dependencies. Perhaps we could be clearer in our documentation that 
poky can take place of those however.
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre