commit | 5327421044bd9be21a105096ec791c5407876820 | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Tue Feb 16 23:34:49 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Feb 16 23:34:49 2021 +0000 |
tree | 881aedde53563be2a63fc1832aaadc108dca4831 | |
parent | cab44e6267cae89ea7fc55c73ba98e9811b33b51 [diff] | |
parent | 882dbb1a2cf5e1cbccad294a5624444bdcf8ce4c [diff] |
[LSC] Add LOCAL_LICENSE_KINDS to external/tinyalsa_new am: 535e6ea3ed am: 59ec086f3b am: 2901cc5713 am: 882dbb1a2c Original change: https://android-review.googlesource.com/c/platform/external/tinyalsa_new/+/1588897 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I3627122e76eadf0c8e148484526d20cd0f85ffce
TinyALSA is a small library to interface with ALSA in the Linux kernel.
The aims are:
TinyALSA supports these build systems:
To build and install with Make, run the commands:
make sudo make install sudo ldconfig
TinyALSA is now available as a set of the following Debian packages from launchpad:
Package Name: | Description: |
---|---|
tinyalsa | Contains tinyplay, tinycap, tinymix and tinypcminfo |
libtinyalsa | Contains the shared library |
libtinyalsa-dev | Contains the static library and header files |
To install these packages, run the commands:
sudo apt-add-repository ppa:taylorcholberton/tinyalsa sudo apt-get update sudo apt-get install tinyalsa sudo apt-get install libtinyalsa-dev
Once installed, the man pages are available via:
man tinyplay man tinycap man tinymix man tinypcminfo man libtinyalsa-pcm man libtinyalsa-mixer
To test libtinyalsa, please follow the instructions,
Visit here to get more info to setup Bazel environment.
The test program does pcm_* operations on loopback devices. You have to insert loopback devices after your system boots up.
sudo modprobe snd-aloop sudo chmod 777 /dev/snd/*
bazel test //:tinyalsa_tests --test_output=all
The default playback device is hw:2,0 and the default capture device is hw:2,1. If your loopback devices are not hw:2,0 and hw:2,1, you can specify the loopback device.
bazel test //:tinyalsa_tests --test_output=all \ --copt=-DTEST_LOOPBACK_CARD=[loopback card] \ --copt=-DTEST_LOOPBACK_PLAYBACK_DEVICE=[loopback playback device] \ --copt=-DTEST_LOOPBACK_CAPTURE_DEVICE=[loopback capture device]
bazel coverage //:tinyalsa_tests --combined_report=lcov --test_output=all genhtml bazel-out/_coverage/_coverage_report.dat -o tinyalsa_tests_coverage