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>
25 lines
835 B
Plaintext
25 lines
835 B
Plaintext
config BR2_PACKAGE_BCUSDK
|
|
bool "bcusdk"
|
|
depends on BR2_USE_MMU # libpthsem
|
|
depends on BR2_INSTALL_LIBSTDCPP
|
|
select BR2_PACKAGE_LIBPTHSEM
|
|
help
|
|
A free development environment for the Bus Coupling Units of
|
|
the European Installation Bus.
|
|
|
|
The European Installation Bus EIB is a home and building
|
|
automation bus system. It is optimized for low-speed control
|
|
applications like lighting and blinds control.
|
|
|
|
BCUs (Bus Coupling Units) are standardized, generic
|
|
platforms for embedded EIB devices. They include the entire
|
|
physical layer network interface, power supply and a
|
|
microcontroller with an implementation of the EIB protocol
|
|
stack stored in the ROM.
|
|
|
|
http://www.auto.tuwien.ac.at/~mkoegler/eib/
|
|
|
|
comment "bcusdk needs a toolchain w/ C++"
|
|
depends on BR2_USE_MMU
|
|
depends on !BR2_INSTALL_LIBSTDCPP
|