kumquat-buildroot/package/rt-tests/Config.in

28 lines
952 B
Plaintext
Raw Normal View History

config BR2_PACKAGE_RT_TESTS
bool "rt-tests"
depends on BR2_TOOLCHAIN_HAS_THREADS
# Too old uClibc, does not provide priority-inheritance
# mutexes
depends on !BR2_avr32
help
Set of utilities for testing the real-time behaviour of a
Linux system.
All tools are simple C programs with no dependencies, except
the hwlatdetect utility, which is a Python script and
therefore requires the Python interpreter. It will only be
installed if a Python interpreter has been selected in the
Buildroot configuration.
Note that this package requires a toolchain built with the
NPTL implementation of the pthread API (this is always the
case with glibc/eglibc toolchains, but may not necessarily
be the case with uClibc toolchains, since the thread
implementation is configurable).
http://rt.wiki.kernel.org
comment "rt-tests needs a toolchain w/ threads"
Config.in files: add missing dependencies to toolchain option comments When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> (untested) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-07 09:24:37 +01:00
depends on !BR2_avr32
depends on !BR2_TOOLCHAIN_HAS_THREADS