Hi, On Tue, 4 Jan 2022, at 3:51 AM, tangmeng@xxxxxxxxxxxxx wrote: > I am currently doing push webrtc to the debian repository, which can [...] > I noticed the webrtc-audio-processing project in > https://salsa.debian.org/pulseaudio-team/webrtc-audio-processing > is part of webrtc. > > Now, I want to confirm whether this module has the same function as > the audio-processing module in > https://webrtc.googlesource.com/src > > If yes! If the webrtc-audio-processing module is integrated in the > libwebrtc library, is that will be OK? > > In other words, do I need to bring the library prov ided through the > webrtc-audio-processing source package in the libwebrtc project? > > If yes, do I need to perform any necessary tests, and whether there are > existing reverse dependencies that need to be changed? The webrc-audio-processing library is the AudioProcessing and AudioCoding module, copied over from libwebrtc, packaged with a more distribution-friendly build system. I think your effort to package libwebrtc should be independent of this: these modules (which are internal to the library, in a sense) often break API, and we try to manage that in the distribution process so that downstream consumers of the library (PulseAudio, PipeWire, GStreamer) are able to have sensible dependency management. Cheers, Arun
