73aed233b2
Using the have_neon boolean to enable NEON code means we have to either fully enable it or fully disable it. When using -Dneon=runtime, ideally only the parts that support runtime checks would be built for NEON, and those that don't would be built without NEON. Though, there are no longer any runtime checks for NEON anywhere, so it's equivalent to 'no' with a warning. In general, we should use have_* variables to indicate compiler support, and *_opt options to choose if and how we want to utilize that. Use neon_opt to control NEON compilation and avoid modifying have_neon which now would fully refer to compiler support. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
About
This is meant to be a more Linux packaging friendly copy of the AudioProcessing module from the WebRTC project. The ideal case is that we make no changes to the code to make tracking upstream code easy.
This package currently only includes the AudioProcessing bits, but I am very open to collaborating with other projects that wish to distribute other bits of the code and hopefully eventually have a single point of packaging all the WebRTC code to help people reuse the code and avoid keeping private copies in several different projects.
Building
This project uses the Meson build system. The quickest way to build is:
# Initialise into the build/ directory, for a prefixed install into the
# install/ directory
meson . build -Dprefix=$PWD/install
# Run the actual build
ninja -C build
# Install locally
ninja -C build install
# The libraries, headers, and pkg-config files are now in the install/
# directory
Feedback
Patches, suggestions welcome. You can file an issue on our Gitlab repository.
Notes
- It might be nice to try LTO on the library. We build a lot of code as part of the main AudioProcessing module deps, and it's possible that this could provide significant space savings.