LD_LIBRARY_PATH has no effect as the plug-ins are loaded directly instead of by the system loader (which is why you need to set QT_PLUGIN_PATH instead of LD_LIBRARY_PATH for Qt's plug-ins).
I see various options to resolve this:
1. I modify the plug-in handler to check an environment variable like QPDFVIEW_PLUGIN_PATH during runtime in parallel to QT_PLUGIN_PATH. I did decide to against that in the past to reduce complexity as it isn't strictly necessary for a "portable" installation.
2. You can move the plug-ins into the same folder as the binary itself (since you are copying around the files anyway), as qpdfview will look for the plug-ins right next to the binary first.
3. You can use a build of qpdfview that statically includes the plugins which would give you a single binary.
In your case for an existing system, just moving the plug-in files as 2 is probably the easiest solution. However, since 0.4.14 is also quite old, you might want to consider building the current version from source using static plug-ins as in 3.
Hello mj162,
LD_LIBRARY_PATH has no effect as the plug-ins are loaded directly instead of by the system loader (which is why you need to set QT_PLUGIN_PATH instead of LD_LIBRARY_PATH for Qt's plug-ins).
I see various options to resolve this:
1. I modify the plug-in handler to check an environment variable like QPDFVIEW_ PLUGIN_ PATH during runtime in parallel to QT_PLUGIN_PATH. I did decide to against that in the past to reduce complexity as it isn't strictly necessary for a "portable" installation.
2. You can move the plug-ins into the same folder as the binary itself (since you are copying around the files anyway), as qpdfview will look for the plug-ins right next to the binary first.
3. You can use a build of qpdfview that statically includes the plugins which would give you a single binary.
In your case for an existing system, just moving the plug-in files as 2 is probably the easiest solution. However, since 0.4.14 is also quite old, you might want to consider building the current version from source using static plug-ins as in 3.
Best regards,
Adam