Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: Bitbake inherit graph
Date: Thu, 29 Jan 2015 08:40:10 -0700	[thread overview]
Message-ID: <54CA545A.4060007@mlbassoc.com> (raw)
In-Reply-To: <1915662.1K5ZXqbggV@peggleto-mobl5.ger.corp.intel.com>

On 2015-01-29 07:51, Paul Eggleton wrote:
> On Thursday 29 January 2015 13:47:12 Roman Savchenko wrote:
>> How can I build inherit graph?
>
> Can you explain what you're looking for exactly? BitBake can produce (very
> large) task, PN and package graphs in .dot format with the -g option, but I'm
> not sure that that's what you're asking for.

Don't forget about the dependency explorer for a nice graphical
view of this data:
   $ bitbake <package> -g -u depexp

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2015-01-29 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 11:47 Bitbake inherit graph Roman Savchenko
2015-01-29 14:51 ` Paul Eggleton
2015-01-29 15:40   ` Gary Thomas [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=54CA545A.4060007@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=bitbake-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox