Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: any way to simply list the layers that contributed to final image?
Date: Mon, 31 Oct 2016 02:41:28 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1610310237330.8165@localhost.localdomain> (raw)


  in order to drag in a bunch of python modules to my
core-image-minimal, i added various layers just to play it safe:

BBLAYERS ?= " \
  /home/rpjday/oe/dist/layers/poky/meta \
  /home/rpjday/oe/dist/layers/poky/meta-poky \
  /home/rpjday/oe/dist/layers/poky/meta-yocto-bsp \
  /home/rpjday/oe/dist/layers/meta-openembedded/meta-oe \
  /home/rpjday/oe/dist/layers/meta-openembedded/meta-webserver \
  /home/rpjday/oe/dist/layers/meta-openembedded/meta-networking \
  /home/rpjday/oe/dist/layers/meta-openembedded/meta-python \
  /home/rpjday/oe/dist/layers/meta-cloud-services \
  /home/rpjday/oe/dist/layers/meta-cloud-services/meta-openstack \
  /home/rpjday/oe/dist/layers/meta-virtualization \
  "

in the end, is there a way to list just those layers that actually
contributed recipes?

  i know i can run:

  $ bitbake-layers show-recipes

to see where *all* recipes would come from, but that's overly verbose.
is there a shortcut?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



                 reply	other threads:[~2016-10-31  6:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1610310237330.8165@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox