https://bugs.winehq.org/show_bug.cgi?id=50436
--- Comment #3 from j-r@online.de --- (In reply to Sveinar Søpler from comment #1)
Sorry for being dense here, but could you elaborate what issues this is causing? (Logs maybe where FAudio.pc is not found or something like that).
I was reluctant to post config.log, because it doesn't directly show the pkg-config result. I think I'll open an enhancement ticket for that (spamming config.log with failed pkg-config invocations).
I hope the information I posted above shows the problem more clearly.
You gather the pkg file should have something like: Requires: gstreamer-1.0
Yes, but I don't know whether that is the correct solution. Since the FAudio user doesn't care about the backend, FAudio should perhaps handle the dynamic loading of its backend internally.
If so, this might be better suited for https://github.com/FNA-XNA/FAudio/issues since it would not be a wine issue i guess. (Or perhaps a distro/packaging issue?)
Yes. The reasons why I was mentioning this were
a) using a gstreamer enabled FAudio build will currently give an unrelated error while configuring --with-faudio using the upstream generated pkg-config file
b) if FAudio should opt for the above solution, wine will need something like the cflags filtering currently used for gstreamer (because then FAudio cflags may contain -pthread)