All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Felix01 Fischer <felix01.fischer@iav.de>
Cc: yocto@yoctoproject.org
Subject: Re: Confused which layers are needed for meta-intel/meta-crownbay
Date: Tue, 14 May 2013 10:44:45 +0100	[thread overview]
Message-ID: <9312274.8dCqzJR46U@helios> (raw)
In-Reply-To: <OFE5D984C5.AA62713E-ONC1257B6B.00342B6A-C1257B6B.00349BEB@retarus.de>

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


      reply	other threads:[~2013-05-14  9:45 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
2013-05-14  9:34   ` Antwort: " Felix01 Fischer
2013-05-14  9:44     ` Paul Eggleton [this message]

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=9312274.8dCqzJR46U@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=felix01.fischer@iav.de \
    --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.