A roundup of my current issues with the alsa-lib repository:
1. No apparent .so (dynamic link) file output.
The configure and make instructions were followed, and no apparent .so resulted:
samiam@samiam-home-pc:~/projects/alsa/alsa-lib-1.1.9$ find . -name *.so samiam@samiam-home-pc:~/projects/alsa/alsa-lib-1.1.9$ find . -name *.a ./src/timer/.libs/libtimer.a ./src/rawmidi/.libs/librawmidi.a ./src/ucm/.libs/libucm.a ./src/topology/.libs/libtopology.a ./src/.libs/libasound.a ./src/hwdep/.libs/libhwdep.a ./src/seq/.libs/libseq.a ./src/mixer/.libs/libmixer.a ./src/control/.libs/libcontrol.a ./src/pcm/.libs/libpcm.a samiam@samiam-home-pc:~/projects/alsa/alsa-lib-1.1.9$ This has made it difficult to debug issues with the library. Using the configure flags does not seem to have an effect on this, IE: ./configure --enable-shared=yes --enable-static=no Linux distributions have libasound.so files in them, so clearly it was possible at some time in the past.
2. Build instructions are conflicting. ./configure make Does work on this version. This is the standard GNU build method, and I have seen these build instructions around the internet for building alsa. The INSTALL file recommends: ./gitcompile Which also (appears) to work, but no reason appears for why this special file is needed or what it does that is different. I can't get a .so (dynamic library from the build, so I can't check the function of the resulting build. Is there a reason the instructions from ./gitcompile cannot be merged back into the make?
3. make install brings the system down. Executing: make install Brought my ubuntu 18.04 sound system down. I had to reinstall Ubuntu to get it to work again.
In summary, ALSA is not a development project anymore. It is the "official sound system of Linux" and is part of the kernel. There is a lot of activity on the ALSA list. Cannot some effort be put into professionalizing the repository?
Thank you for your attention, Scott A. Franco San Jose, CA