-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Provide a separate build argument to set plugin search path #1307
Comments
Setting the environment variable |
This feels like a breaking change for any existing packaging that sets |
Yes, we would have to set |
@bbhtt Does that patch work for you? (Set the install path explicitly with |
Thank you! It seems to work, I set it like this:
Mine was a quick hack to get something working. |
@bbhtt Thanks for reporting this and testing the fix. |
At the moment both the install and search path are tied to the same build argument
PLUGIN_DIRECTORY
. It'd be useful to have a separate build argument for the search path for sandboxed applications.Something like this potentially:
The use case is that when building Flatpak runtimes, libheif is built with the plugin path
/usr/lib/x86_64-linux-gnu/extension/libheif
as we want the plugins to be installed in/usr/lib/x86_64-linux-gnu/extension/libheif
. It cannot be set to/app/...
as that is a special prefix not used outside Flatpak.Then the contents of
/usr/lib/x86_64-linux-gnu/extension/
is copied into the Flatpak extension and mounted at/app/lib/extension/libheif
.But
libheif.so
now wants the plugins to be in/usr/lib/x86_64-linux-gnu/extension/libheif
while they are actually mounted at/app/lib/extension/libheif
.The text was updated successfully, but these errors were encountered: