From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Graphing package dependencies
Date: Thu, 6 May 2010 10:14:37 +0200 [thread overview]
Message-ID: <20100506101437.5e35c795@surf> (raw)
Hello,
Following the question asked by Will yesterday, I just went ahead and
implement a small tool that generates a graph of dependencies for a
given package.
The result of this tool for the libgtk2 package can be seen at
http://free-electrons.com/~thomas/libgtk2-package-dependencies.pdf
This is the kind of funny things we can do with a generic package
infrastructure :-)
The implementation of this tool is available in my graph-dependencies
branch at
http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=graph-dependencies.
There are three commits in this branch:
* package: Add new <pkg>-show-depends to list dependencies
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=graph-dependencies&id=27ad37038055e5af12546a5941099264f37feecc
* package: optimize the implementation of UPPERCASE
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=graph-dependencies&id=b6a46aaed9e497503b66789d1b212473d7c78b58
* New graph-depends script
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=graph-dependencies&id=99c53bd52389c003707335d454d1bd1cace9ebfb
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2010-05-06 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 8:14 Thomas Petazzoni [this message]
2010-05-06 9:46 ` [Buildroot] Graphing package dependencies Peter Korsgaard
2010-05-13 18:21 ` Thomas Petazzoni
2010-05-14 10:40 ` Lionel Landwerlin
2010-05-17 6:46 ` Peter Korsgaard
2010-05-17 7:03 ` Thomas Petazzoni
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=20100506101437.5e35c795@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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