Open echoesofastolenlife opened 3 years ago
The plug-in does not appear in the list if the purple_signal.dll
cannot be loaded due to missing dependencies. The only hard "early" dependency is jvm.dll
from a 32 bit Java 11 (or newer) installation. You can open the purple_signal.dll
with http://www.dependencywalker.com/ (there are more recent variants of this tool, this just happens to what I am using). Launch it in the same environment as you launch Pidgin. If it shows you jvm.dll
as a missing dependency, then PATH probably not includes the location of the jvm.dll
.
I could write the plug-in in such a way that it shows an error message rather than it not appearing, but it is tedious and error-prone. That is why I left it the way it currently is.
Please note: There are additional "late, dynamic" dependencies, such as zkgroup.dll
and libsignal_jni.dll
. The latter is not available for Windows. :( As long as this is the case, the latest release cannot be used on Windows. For this reason, I am currently not working on this project. I hope someday someone will provide releases of all dependencies.
@EionRobb Nice idea, but that is a 64bit dll. The win32 build of Pidgin is 32bit and cannot load 64bit dlls. :(
Do you happen to know if Pidgin 3 will be 64bit?
Update: According to Pidgin developer Gary Kramlich, Pidgin3 for Windows will be 64bit.
Signal is not among the options on the "Add New Account" list on a Windows 7 install
I don't imagine it's with any other dependencies than the signal .dll and .jar themselves that could cause this, so I haven't investigated too far on those
I did have pidgin installed on the default "Program Files (x86)" folder previous to discovering this plugin. I tried both the program folder and the user folder, and as you had indicated the user folder didn't fix it either.
If this is the problem, is there a workaround? A way to specify another plugin folder for pidgin to draw from, etc? Is there another issue that could be causing pidgin not to detect the plugin?