35eaed8d07
In the Config.in file of package foo, it often happens that there are other
symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense
when foo itself is enabled. There are two ways to express this: with
depends on BR2_PACKAGE_FOO
in each extra symbol, or with
if BR2_PACKAGE_FOO
...
endif
around the entire set of extra symbols.
The if/endif approach avoids the repetition of 'depends on' statements on
multiple symbols, so this is clearly preferred. But even when there is only
one extra symbol, if/endif is a more logical choice:
- it is future-proof for when extra symbols are added
- it allows to have just one strategy instead of two (less confusion)
This patch modifies the Config.in files accordingly.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
22 lines
553 B
Plaintext
22 lines
553 B
Plaintext
config BR2_PACKAGE_SCHIFRA
|
|
bool "schifra"
|
|
depends on BR2_INSTALL_LIBSTDCPP
|
|
help
|
|
Schifra is a very robust, highly optimized and extremely configurable
|
|
Reed-Solomon error correcting code library for both software and IP
|
|
core based applications with implementations in C++ and VHDL.
|
|
|
|
http://www.schifra.com/
|
|
|
|
if BR2_PACKAGE_SCHIFRA
|
|
|
|
config BR2_PACKAGE_SCHIFRA_EXAMPLES
|
|
bool "schifra examples"
|
|
help
|
|
Build and install the schifra example applications.
|
|
|
|
endif
|
|
|
|
comment "schifra needs a toolchain w/ C++"
|
|
depends on !BR2_INSTALL_LIBSTDCPP
|