gitolite/buildrootschalter
gitolite/buildrootschalter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
fc093d61ce
buildrootschalter/package/madplay/Config.in

23 lines
629 B
Plaintext
Raw Normal View History

madplay package
2007-05-10 11:20:20 +02:00
config BR2_PACKAGE_MADPLAY
bool "madplay"
select BR2_PACKAGE_LIBMAD
select BR2_PACKAGE_LIBID3TAG
madplay: fixes build when toolchain has locale support Otherwise build fails in intl/relocatable.c with: ./relocatable.c: In function 'libintl_relocate': ./relocatable.c:402:40: error: 'INSTALLPREFIX' undeclared (first use in this function) ./relocatable.c:402:40: note: each undeclared identifier is reported only once for each function it appears in [Peter: drop redundant 'else' part] Signed-off-by: Julien Boibessot <julien.boibessot@armadeus.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-10 11:17:48 +01:00
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALE
madplay package
2007-05-10 11:20:20 +02:00
help
Cleanup + ALSA support for madplay
2007-07-28 17:57:09 +02:00
Command-line front-end to libmad, a high-quality MPEG audio decoder.
It currently supports MPEG-1 and the MPEG-2 extension to lower
sampling frequencies, as well as the de facto MPEG 2.5 format. All
three audio layers — Layer I, Layer II, and Layer III (i.e. MP3) —
are fully implemented.
madplay package
2007-05-10 11:20:20 +02:00
http://www.underbit.com/products/mad/
Cleanup + ALSA support for madplay
2007-07-28 17:57:09 +02:00
Config.in files: use if/endif instead of 'depends on' for main symbol 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>
2013-12-20 22:31:30 +01:00
if BR2_PACKAGE_MADPLAY
Cleanup + ALSA support for madplay
2007-07-28 17:57:09 +02:00
config BR2_PACKAGE_MADPLAY_ALSA
bool
default y
Config.in files: use if/endif instead of 'depends on' for main symbol 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>
2013-12-20 22:31:30 +01:00
depends on BR2_PACKAGE_ALSA_LIB
endif
Reference in New Issue Copy Permalink