Hi Gerry, The sound configure options were removed since the module has been changed to use sub-plugin. You choose which sound plugin to use when you run xfreerdp, not when you compile it. Whether a sound sub-plugin will be compiled depends on whether you have the development header, but it compiles does not mean it's will be used. You can read the man page on how to specify which sound sub-plugin you want to use when you run xfreerdp.
Of course one can argue to add configure option to disable some sound sub-plugin even when the header is presented in the system, but I really doubt there will be any use case for this. Vic On 04/15/2011 08:53 AM, Gerry Reno wrote: > Hi, > I cannot seem to find a configure option to control the buildtime > inclusion of sound plugin support. > > I'm looking for something like > --with-sound=alsa,pulse,esound,whatever. Or maybe > --with-plugin-sound=alsa,pulse,... > > I would like to be able to control precisely which sound plugins get > built, if any. > > For now, what would be the easiest way I could disable building a > sound plugin? > > > Regards, > Gerry ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
