On 04/15/2011 03:59 AM, Vic Lee wrote:
> 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
>
>
Hi Vic,
The use case is cross-compile. Even though the header files are
available on the build system that does not mean that the functionality
will be present on the target system. And this is why an explicit
configure switch is necessary to control the building of the plugin. I
would like not to disturb the build system if possible. Devel header
files may be there for other purposes so I would like to not be removing
them.
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
