aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-bsp/grub
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2013-12-16 10:57:49 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-18 11:14:40 +0000
commit0b76f034dd0320ec545229872be8095c44ddee73 (patch)
treee32d30deb0d0ba051b1c96b65d7f831fdeb6a97d /meta/recipes-bsp/grub
parent9976a860b495256d94ec44c5084b13f214351547 (diff)
downloadopenembedded-core-contrib-0b76f034dd0320ec545229872be8095c44ddee73.tar.gz
scripts/contrib: Add graph-tool
A simple script I put together for getting the paths from one node to another in a dot graph. This is useful for example in working out why a particular recipe is getting built in conjunction with dot graph files produced by bitbake -g. For example: $ bitbake -g core-image-minimal ... $ graph-tool find-paths pn-depends.dot core-image-minimal util-linux core-image-minimal -> packagegroup-core-boot -> udev -> glib-2.0 -> python-dbus -> dbus-glib -> dbus -> libsm -> e2fsprogs -> util-linux core-image-minimal -> packagegroup-core-boot -> udev -> glib-2.0 -> python-dbus -> dbus -> libsm -> e2fsprogs -> util-linux core-image-minimal -> packagegroup-core-boot -> udev -> util-linux Partially addresses [YOCTO #3362]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/recipes-bsp/grub')
0 files changed, 0 insertions, 0 deletions