Summary: | xine_artsplugin/configure.in.in doesn't disable plugin even if --without-arts is specified | ||
---|---|---|---|
Product: | [Unmaintained] arts | Reporter: | Laurence Withers <l> |
Component: | xine_artsplugin | Assignee: | Multimedia Developers <kde-multimedia> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | disable xine_artsplugin if arts is unwanted |
Description
Laurence Withers
2004-06-20 22:32:10 UTC
Created attachment 6423 [details]
disable xine_artsplugin if arts is unwanted
simply copied from audiofile_artsplugin. As I use arts I didn't test the patch
That works fine... let's see Microsoft beat the turnaround time on this one :-) (On a Sunday evening as well!). Thanks very much, Stefan. Any chance this could be added to CVS in time for 3.3.0 beta 2? It's the last bug I'm aware of that's stopping us from providing KDE on a Gentoo system without arts. Many thanks! guess why arts is part of kde, certainly not to disable it. Sure, sure, but arts isn't for everyone :-) Consider systems without soundcards, or with hardware mixers, etc. Combined with high CPU usage (one of the Gentoo devs reports 20% CPU usage from arts on his Apple laptop, dropping to 5% for sound without arts), there is some motivation for achieving this. Whilst I appreciate that fixing bugs in this vein isn't going to be high priority, the "--disable-arts" configure machinery is already in place and you've already written a working patch, so we might as well allow users like me to live without arts. In fact, other than a couple of tricky bits, I have a KDE 3.3 beta system running without arts right now, and it rocks! ---------------------------- revision 1.13 date: 2004/06/23 15:32:36; author: mlaurent; state: Exp; lines: +4 -0 Don't try to compile it when we use "--without-arts" Well, he could have been so kind and closed this bug back then... :) |