be084204eb
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>
34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
config BR2_PACKAGE_LTTNG_TOOLS
|
|
bool "lttng-tools"
|
|
select BR2_PACKAGE_LIBURCU
|
|
select BR2_PACKAGE_POPT
|
|
select BR2_PACKAGE_UTIL_LINUX
|
|
select BR2_PACKAGE_UTIL_LINUX_LIBUUID
|
|
# liburcu only works on some architectures and requires thread support
|
|
depends on BR2_arm || BR2_armeb || BR2_i386 || BR2_powerpc || BR2_x86_64
|
|
depends on BR2_LARGEFILE
|
|
depends on BR2_USE_WCHAR # util-linux
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
|
help
|
|
Userspace utilities for the LTTng 2.0 tracing
|
|
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
|
|
$(O)/host/usr/bin/babeltrace, as a dependency of
|
|
lttng-tools. However, there is also a lttng-babeltrace
|
|
package for the target, if babeltrace on the target is
|
|
interesting.
|
|
|
|
If userspace tracing is desired, you need to enable
|
|
lttng-libust.
|
|
|
|
http://lttng.org
|
|
|
|
comment "lttng-tools needs a toolchain w/ largefile, threads, wchar"
|
|
depends on BR2_arm || BR2_armeb || BR2_i386 || BR2_powerpc || BR2_x86_64
|
|
depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS || \
|
|
!BR2_USE_WCHAR
|