buildroot/package/alsa-utils, branch 2017.02

ncurses: remove BR2_PACKAGE_NCURSES_TARGET_{FORM, MENU, PANEL} options

2017-02-26T16:00:12+00:00

The ncurses sub-options BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL} are currently very badly broken: they only control whether the libform, libmenu and libpanel libraries are installed in $(TARGET_DIR), but do absolutely nothing about their installation in $(STAGING_DIR). This means that when one of those options is disabled, the corresponding library is indeed not installed in the target, but is available in staging. It can therefore be detected by the configure script of another package and used... even though the library will not be in the target, causing a runtime failure. Internally, ncurses.mk uses the "make install" logic of ncurses for the staging installation, but uses a completely hand-written logic for the target installation, which is the reason for this desynchronization between what's installed in staging and target. When BR2_PACKAGE_NCURSES_WCHAR=y, this also causes some build failures. Indeed, when BR2_PACKAGE_NCURSES_WCHAR=y, Buildroot creates some symbolic links lib.so -> libw.so in staging and target, but only for the lib that have been enabled by BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL}. Due to this, a package that for example needed the libmenu library but forgot to select BR2_PACKAGE_NCURSES_TARGET_MENU was: - Building fine with BR2_PACKAGE_NCURSES_WCHAR disabled (because libmenu.so exists in staging), but would fail to run at runtime because libmenu.so is not in the target. - Fail to build with BR2_PACKAGE_NCURSES_WCHAR=y because only libmenuw.so exists, and not the libmenu.so symbolic link. Since those libraries are small (43K for libform, 21K for libmenu and 8.2K for libpanel), this commit takes the very simple approach of removing those options, and installing the libraries unconditionally. It therefore uses the "make install" logic for both the staging *and* target installation. In detail, this commit: - Removes the NCURSES_PROGS variable, not needed since --without-progs already allows to disable the build and installation of programs. - Removes the NCURSES_LIBS-y variable, and replaces it with a single unconditional assignement to NCURSES_LIBS, only used to create the libw.so -> lib.so symbolic links when wchar support is enabled. - Removes NCURSES_INSTALL_TARGET_CMDS and the functions it was calling: NCURSES_INSTALL_TARGET_LIBS and NCURSES_INSTALL_TARGET_PROGS. - Adds a NCURSES_TARGET_SYMLINK_RESET hook to create the reset -> tset symbolic link, as was done before. - Adds a NCURSES_TARGET_CLEANUP_TERMINFO to cleanup the terminfo files in the target, so that we stay in the same situation in terms of installed terminfo files. - Removes the BR2_PACKAGE_NCURSES_TARGET_{FORM,MENU,PANEL} options from the Config.in files: both their definition and usage. - Simplifies all the symlink dance for lib -> libw, because as Yann E. Morin suggested, this dance is only needed in staging, not in the target. Once binaries have been built, they refer to the SONAME of the library, which is the libw variant (for shared linking). For static linking and .pc files, it's obvious that we don't care about them on the target. Therefore the NCURSES_LINK_LIBS_STATIC, NCURSES_LINK_LIBS_SHARED and NCURSES_LINK_PC functions no longer take any argument: they always apply to STAGING_DIR only. NCURSES_LINK_TARGET_LIBS is removed. It is worth mentioning that adding Config.in.legacy support is *NOT* necessary. Indeed: - If they were disabled before this patch, having them in Config.in.legacy would not trigger the legacy warning. - If they were enabled before this patch, then the behavior is unchanged: all libraries are now unconditionally installed. So there is no point in warning the user. We double-checked the installed size of a filesystem containing just ncurses before and after this patch, and the only folder that has its size changed is /usr/lib, growing from 852 KB to 932 KB in the wchar enabled case. That's a 80 KB system size increase. This commit fixes the sngrep build failure and potentially numerous runtime issues with ncurses. Fixes: http://autobuild.buildroot.net/results/7b5db21a6c568e6c6c8fe2b5d5a2f5ca24df510c/ Signed-off-by: Thomas Petazzoni

alsa-utils: disable manpages generation from reStructured text

2017-01-04T16:11:23+00:00

The alsaucm man page rst source file is missing in the tarball. When rst2man is detected on the host, build fails: make[2]: *** No rule to make target 'alsaucm.1', needed by 'all-am'. Stop. Upstream added[1] the missing file to the tarball to fix this issue. But since we don't need the manpage to begin with, just disable rst2man to shorten build time by a few milliseconds. [1] http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c6bdde171e1532f7b37333a5a746b6e662f12c53 Signed-off-by: Baruch Siach Acked-by: Bernd Kuhls Signed-off-by: Peter Korsgaard

alsa-utils: bump to version 1.1.3

2016-12-22T09:50:52+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

alsa-utils: bump version to 1.1.2

2016-08-03T18:47:15+00:00

Signed-off-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

alsa-utils: bump to version 1.1.1

2016-04-01T01:57:54+00:00

Patches upstream so drop them. The 'bat' binary utility was renamed to 'alsabat' probably to avoid some clash, keep the old .config symbol to avoid pointless legacy. Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

package/alsa-utils: use 'menuconfig' instead of 'config'+'menu'

2016-01-19T21:22:54+00:00

Drop the now useless comment. Signed-off-by: "Yann E. MORIN" Acked-by: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

package/alsa-utils: Add option for alsaloop util

2016-01-18T21:59:50+00:00

Add libsamplerate as optional dependency, see alsa-utils-1.1.0/alsaloop/Makefile.am [Peter: move libsamplerate dependency outside alsaloop conditional] Signed-off-by: Bernd Kuhls Signed-off-by: Peter Korsgaard

alsa-utils: allow installing the new alsatplg tool

2016-01-16T17:10:24+00:00

Since we now depend on !BR2_STATIC_LIBS to be able to build the alsatplg tool, it makes sense to provide an option to install it. Signed-off-by: Thomas Petazzoni

alsa-utils: re-order sub-options to use alphabetic ordering

2016-01-16T16:59:08+00:00

Signed-off-by: Thomas Petazzoni

alsa-utils: put 'select' after 'bool'

2016-01-16T16:57:07+00:00

In the definitions of the alsa-utils sub-options, the 'select' were before the 'bool', which is unusual and does not follow how we do things in general in Buildroot. This commit fixes that for all alsa-utils suboptions. Signed-off-by: Thomas Petazzoni