https://bugs.winehq.org/show_bug.cgi?id=37555
--- Comment #4 from Todd Chester ToddAndMargo@zoho.com --- (In reply to Henri Verbeet from comment #3)
(In reply to Rosanne DiMesio from comment #1)
However, I do agree the message "No sound system was found" is confusing to inexperienced users. Most of the time, only the 32 bit files are missing. Something like "No supported 32 bit sound system found" might be better. .
I suppose it might help to specifically mention "${notice_platform}development files", like most of the other messages for missing libraries and the like, instead of referring to "sound system" in general, although I'd also argue that that's implied by the message coming from configure.
The harder problem is of course that we can't know if the user wants to use Alsa, OSS, CoreAudio, or perhaps in the future PulseAudio, which makes it hard to talk about a specific package.
Hi Henri,
I think it is all in the wording. "If you wish to enable a sound system on [insert OS], please add [insert applicable package]..." Or something like that.
Basically, ./configure has to know what specific OS's sound package to look for or it could never load the appropriate package, so it does have to have knowledge of what it needs. And relaying that to the user is what I am after.
-T