-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to make ALSA relocatable in the filesystem? #34
Comments
It appears that https://github.com/flatpak/freedesktop-sdk-images/blob/1.6/alsa-lib-plugin-path.patch might be addressing this? |
In commit b906db1, the snd_dlopen() implements the automatic lookup to the ALSA_PLUGIN_DIR directory. It is not necessary to add the absolute paths in callers now. The plugin names are also searched in ld.so.conf paths as the fallback now, but it should not be a big problem. BugLink: #34 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
BugLink: #34 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Commited to master. |
This patch breaks building alsa-lib with uClibc:
RTLD_DL_LINKMAP & RTLD_DI_ORIGIN, are unsupported on uClibc: |
Why uclibc build defines Line 72 in 6eb78d4
If you have a better way to check non-glibc build, we can change it. |
We want to bundle a private copy of ALSA with our application, so that the ALSA from the Linux distribution is not used at all. Yet it seems ALSA is relying on some absolute paths compiled in with no clear way to pass in a different location for ALSA at runtime.
How to do this?
Use case:
As an application developer, I want to ship my application together with all dependencies. This bundle is using musl libc, ships its own musl libc and runtime, and it is intended to also run on glibc-based systems.
Reference:
mumble-voip/mumble#3959 (comment)
The text was updated successfully, but these errors were encountered: