On Mon Sep 23 20:32:47 2024 +0000, Alexandre Julliard wrote:
Like normal dlls, a load failure is not necessarily an error. This should be printed in the higher level modules in the cases where it's actually a problem.
Thanks for looking into it.
I tried to identify the higher levels.
* [dlls/ntdll/unix/virtual.c](https://gitlab.winehq.org/wine/wine/-/blob/42af68b8b7cf066a1738c483e8ea1b5bf...) * [dlls/winealsa.drv/mmdevdrv.c](https://gitlab.winehq.org/wine/wine/-/blob/42af68b8b7cf066a1738c483e8ea1b5bf...): * [dlls/mmdevapi/main.c](https://gitlab.winehq.org/wine/wine/-/blob/42af68b8b7cf066a1738c483e8ea1b5bf...)
What about adding the ERR in mmdevapi when no driver succeeds, and changing the ERR in `get_builtin_unix_funcs` to a WARN_(module), and adding an additional WARN_(module) to winealsa (and pulse, oss, and coredrive)?
That way the default output should just get the additional line if no audio driver is loaded, and the user could proceed by WINEDEBUG=warn+module?