From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Best practice to resolve dependency loops ?
Date: Fri, 09 Jul 2010 10:48:32 +0100 [thread overview]
Message-ID: <1278668912.2706.3.camel@scimitar> (raw)
In-Reply-To: <201007091049.09034.schnitzeltony@gmx.de>
On Fri, 2010-07-09 at 10:49 +0200, Andreas Mueller wrote:
> On Friday 09 July 2010 10:05:56 am Hauser, Wolfgang (external) wrote:
> > What is the best practice to examine and solve such problems ?
>
> I would like to add an additional question:
>
> bitbake supports -g for dependency trees in dot syntax. What is the best tool to browse these files. I checked graphviz but this just paints complete unviewable posters. Is there e.g something like
> a dot to html converter aavialable?
You can use the dependency explorer UI built into Bitbake:
bitbake -g -u depexp some-task
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
prev parent reply other threads:[~2010-07-09 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 8:05 Best practice to resolve dependency loops ? Hauser, Wolfgang (external)
2010-07-09 8:49 ` Andreas Mueller
2010-07-09 9:03 ` Hauser, Wolfgang (external)
2010-07-09 9:06 ` Graham Gower
2010-07-09 9:48 ` Joshua Lock [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=1278668912.2706.3.camel@scimitar \
--to=josh@linux.intel.com \
--cc=openembedded-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 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.