The cirros image was rebuilt against the 3.13.0-83 kernel, drivers e1000e, igbvf...

[packages/trusty/cirros-testvm.git] / cirros-testvm / src-cirros / buildroot-2015.05 / package / bustle / Config.in

diff --git a/cirros-testvm/src-cirros/buildroot-2015.05/package/bustle/Config.in b/cirros-testvm/src-cirros/buildroot-2015.05/package/bustle/Config.in
new file mode 100644 (file)
index 0000000..f213da5
--- /dev/null
+++ b/cirros-testvm/src-cirros/buildroot-2015.05/package/bustle/Config.in
@@ -0,0 +1,26 @@
+config BR2_PACKAGE_BUSTLE
+       bool "bustle"
+       select BR2_PACKAGE_LIBPCAP
+       select BR2_PACKAGE_LIBGLIB2
+       depends on BR2_USE_WCHAR # libglib2
+       depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
+       depends on BR2_USE_MMU # libglib2
+       depends on BR2_PACKAGE_DBUS # runtime
+       help
+         Bustle is a better dbus-monitor! It records and draws
+         sequence diagrams of D-Bus activity, showing signal
+         emissions, method calls and their corresponding returns,
+         with timestamps for each individual event and the duration
+         of each method call. This can help you check for unwanted
+         D-Bus traffic, and pinpoint why your D-Bus-based application
+         isn't performing as well as you like.
+
+         This only installs the command line bustle-pcap tool, not
+         the graphical viewer.
+
+         http://www.willthompson.co.uk/bustle/
+
+comment "bustle needs a toolchain w/ wchar, threads"
+       depends on BR2_USE_MMU
+       depends on BR2_PACKAGE_DBUS
+       depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS