From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] scripts/oe-depends-dot: add it to handle dot files
Date: Sun, 21 Jan 2018 10:04:17 +0000 [thread overview]
Message-ID: <1516529057.24502.55.camel@linuxfoundation.org> (raw)
In-Reply-To: <c0f872f3412b16d7fcf126473d8fd7749cd44814.1516012306.git.liezhi.yang@windriver.com>
On Mon, 2018-01-15 at 18:34 +0800, Robert Yang wrote:
> Add it to handle recipe-depends.dot and task-depends.dot. E.g.:
>
> * Print why rpm is built
> $ oe-depends-dot -k rpm --why/-w recipe-depends.dot
> Because: core-image-sato libdnf libsolv dnf
>
> * Print bzip2-native's depends
> $ oe-depends-dot -k bzip2-native --depends/-d recipe-depends.dot
> Depends: automake-native gnu-config-native libtool-native quilt-
> native autoconf-native
>
> * Remove duplicated dependencies to reduce the size of the dot files.
> For example, A->B, B->C, A->C, then A->C can be removed. The dot
> files are too
> big, we nearly couldn't use 'dot -T' to generate pictcures for
> target recipes,
> remove the duplicated dependencies makes is it possible.
> $ bitbake core-image-sato -g
> $ oe-depends-dot -r recipe-depends.dot
> Saving reduced dot file to recipe-depends-reduced.dot
> $ du -sh recipe-depends*.dot
> 608K recipe-depends.dot
> 32K recipe-depends-reduced.dot
>
> It has been recuded from 608K to 32K, now we can generate a
> picture,
> otherwise, it is too big:
> $ dot -Tpng recipe-depends-reduced.dot -O
>
> It also can handle task-depends.dot.
I just wanted to mention that whilst I've not tried using it due to
time constraints, I like the idea of this approach a lot, thanks
Robert!
Cheers,
Richard
prev parent reply other threads:[~2018-01-21 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 10:34 [PATCH 0/1] scripts/oe-depends-dot: add it to handle dot files Robert Yang
2018-01-15 10:34 ` [PATCH 1/1] " Robert Yang
2018-01-21 10:04 ` Richard Purdie [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=1516529057.24502.55.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--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