From: Gary Thomas <gary@mlbassoc.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Analyzing dependencies
Date: Wed, 13 Apr 2016 08:20:38 +0200 [thread overview]
Message-ID: <570DE536.9020701@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1soC0Yy13GyVVoe3KY3SjP26MvrHSbr3WS6x=dRW0uy=0Q@mail.gmail.com>
On 2016-04-13 08:08, Khem Raj wrote:
> Use any program that reads dotty files
>
Know of any interactive ones that let you explore like the 'depexp'?
> On Apr 12, 2016 11:05 PM, "Gary Thomas" <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
> If I generate the dependency files (-g => *.dot files) for
> my target recipe, is there a way to view/analyze them "off line"
> much the same way as using "bitbake -u depexp"?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-04-13 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 6:05 Analyzing dependencies Gary Thomas
2016-04-13 6:08 ` Khem Raj
2016-04-13 6:13 ` Robert Yang
2016-04-13 6:20 ` Gary Thomas [this message]
2016-07-13 22:43 ` Paul Eggleton
2016-07-14 2:39 ` Peter Kjellerstedt
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=570DE536.9020701@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.