4a17c682e9
The MIPS-specific source for vector scaling operations fails to build on Debian's mips64el: [97/303] Compiling C object webrtc/common_audio/libcommon_audio.a.p/signal_processing_vector_scaling_operations_mips.c.o FAILED: webrtc/common_audio/libcommon_audio.a.p/signal_processing_vector_scaling_operations_mips.c.o cc [...] webrtc/common_audio/libcommon_audio.a.p/signal_processing_vector_scaling_operations_mips.c.o.d -o webrtc/common_audio/libcommon_audio.a.p/signal_processing_vector_scaling_operations_mips.c.o -c ../webrtc/common_audio/signal_processing/vector_scaling_operations_mips.c /tmp/cc7UGPkY.s: Assembler messages: /tmp/cc7UGPkY.s:57: Error: opcode not supported on this processor: mips64r2 (mips64r2) `extrv_r.w $3,$ac0,$8' ninja: build stopped: subcommand failed. The EXTRV_R.W instruction it uses is part of DSP extensions for this architecture. In signal_processing_library.h, this function's prototype is guarded with #if defined(MIPS_DSP_R1_LE). Guard the implementation like that as well to fix the error. 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.