51788521b7
This commit adds a dependency of the libglib2 package on thread support in the toolchain, since upstream libglib2 doesn't build without thread support. The commit is rather large as it involves propagating the dependency on thread support to all reverse dependencies of the libglib2 package. [Thomas: squash all patches into one, make a few minor fixes, the most important one being to not add comments about MMU requirement when a package doesn't work on !MMU platforms.] Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
25 lines
983 B
Plaintext
25 lines
983 B
Plaintext
config BR2_PACKAGE_LATENCYTOP
|
|
bool "latencytop"
|
|
depends on BR2_USE_WCHAR # libglib2
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
|
|
select BR2_PACKAGE_NCURSES
|
|
select BR2_PACKAGE_LIBGLIB2
|
|
help
|
|
There are many types and causes of latency. LatencyTOP
|
|
focuses on the type of latency that causes skips in audio,
|
|
stutters in your desktop experience or that overloads your
|
|
server (while you have plenty of CPU power left).
|
|
|
|
LatencyTOP focuses on the cases where the applications want
|
|
to run and execute useful code, but there's some resource
|
|
that's not currently available (and the kernel then blocks
|
|
the process). This is done both on a system level and on a
|
|
per process level, so that you can see what's happening to
|
|
the system, and which process is suffering and/or causing
|
|
the delays.
|
|
|
|
http://www.latencytop.org
|
|
|
|
comment "latencytop requires a toolchain with WCHAR and threading support"
|
|
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
|