2012-01-31 20:40:03 +01:00
|
|
|
config BR2_PACKAGE_LTTNG_TOOLS
|
|
|
|
bool "lttng-tools"
|
2012-12-17 02:32:02 +01:00
|
|
|
# liburcu only works on some architectures and requires thread support
|
2015-12-13 19:47:50 +01:00
|
|
|
depends on BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
|
2012-12-17 02:32:02 +01:00
|
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
2016-01-23 11:52:22 +01:00
|
|
|
depends on !BR2_STATIC_LIBS # uses dlfcn
|
2016-01-23 11:52:21 +01:00
|
|
|
select BR2_PACKAGE_LIBURCU
|
|
|
|
select BR2_PACKAGE_LIBXML2
|
|
|
|
select BR2_PACKAGE_POPT
|
|
|
|
select BR2_PACKAGE_UTIL_LINUX
|
|
|
|
select BR2_PACKAGE_UTIL_LINUX_LIBUUID
|
2012-01-31 20:40:03 +01:00
|
|
|
help
|
2015-03-06 18:35:52 +01:00
|
|
|
Userspace utilities for the LTTng 2.x tracing
|
2012-01-31 20:40:03 +01:00
|
|
|
infrastructure.
|
|
|
|
|
|
|
|
Those utilities are required on the target system to start
|
|
|
|
and stop tracing sessions. Analysis of the trace can be done
|
|
|
|
on the host machine using the babeltrace utility. This
|
|
|
|
utility is automatically built by Buildroot in
|
2017-07-05 13:14:34 +02:00
|
|
|
$(O)/host/bin/babeltrace, as a dependency of
|
2012-01-31 20:40:03 +01:00
|
|
|
lttng-tools. However, there is also a lttng-babeltrace
|
|
|
|
package for the target, if babeltrace on the target is
|
|
|
|
interesting.
|
|
|
|
|
2012-02-04 15:48:46 +01:00
|
|
|
If userspace tracing is desired, you need to enable
|
|
|
|
lttng-libust.
|
|
|
|
|
2012-01-31 20:40:03 +01:00
|
|
|
http://lttng.org
|
2012-12-17 02:32:02 +01:00
|
|
|
|
2017-06-28 15:10:00 +02:00
|
|
|
comment "lttng-tools needs a toolchain w/ threads, dynamic library"
|
2015-12-13 19:47:50 +01:00
|
|
|
depends on BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
|
2017-06-28 15:10:00 +02:00
|
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
|