Building xrdp PulseAudio modules for great remote desktop experience

Dominik George nik at
Thu Oct 6 12:57:47 UTC 2016

Hi Felipe,

> The situation has changed a bit: pulseaudio upstream is receptive to
> shipping such headers provided they have a define that users
> explicitly need to be set (so that people do not unsuspectingly use
> it), because the module api is not easily stabilized at the moment. I
> believe that this is just lacking someone that implement this at the
> moment. So maybe the bug should be untagged wontfix.

How would I go about that? Would I find out what APIs the module needs
to build, then ask upstream to add them to their shipped header files,
then wait for them to find their way into the Debian pulseaudio-dev


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <>

More information about the pkg-pulseaudio-devel mailing list