-
Notifications
You must be signed in to change notification settings - Fork 3
Compilation instruction is somewhat unclear. #2
Comments
The steps in detail:
To install, you can create links or copy the binaries (assumes a standard pidgin directory location):
|
Ahh, there isn't a repository for Here is the full log:
|
Whoops. This is the first time I actually used submodules in production. Obviously, I did something wrong. It should be |
Compilation failed. Here is the log:
I am eager to get this version working. Hopefully it works better than |
I, too, have only few contacts on Signal. This plug-in is not well-tested at all. I expect it to work worse than purple-signald. However, I think this one has more potential to get better. ;) It looks like I still got something wrong with the submodule. I want to look into it tonight or maybe next week. |
Thanks, I am looking forward to your fixes. I myself wanted to write a pidgin plugin at one point, but the libpurple API looked really messy, and that put me off. Good luck! Please do reply to this issue when you have a fix, so I know when I can try compilation again. :) |
It looks like you downloaded signal-cli 0.6.12. I was not even aware this new version exists (please bear with me – it is only nine days old). There was an incompatible change in the API. So as of today, this plug-in must be built against signal-cli 0.6.11 exactly. I improved the CMakeLists.txt so it checks the version.
Please be aware that this plug-in may actually be worse, as this line indicates. ;) Is is text-message only, for now. Also, especially noticeable in case of linking, the contacts are not downloaded. You need to receive a message, then select "add buddy" from the conversation window to add the contact to Pidgin's local buddy list. In theory, you can also add a buddy using Pidgin's main window menu and then send them a message, but I never actually tried that.
I would not say "messy", but rather "very C". That is why I chose to implement the larger part of the C ↔ Java glue logic of this plug-in in C++. I never did anything like that before. It certainly is a learning experience. :) |
That shouldn't stop the compilation, right? I thought you specify signal-cli version after launching the plugin. ;) |
In this case, it does. I am building on top of signal-cli, re-defining two of it's classes |
Okay, I got it compiled, and installed. The signal-cli jar's location should be set to Also, I can't see anyone of my contacts, is that to be expected? |
Yes. I did not implement download of contacts, yet. |
I had this problem; INSTALL.md's compilation instructions aren't just unclear but are incomplete, almost nonexistent. If one never used cmake nor with make may be days/weeks/months/years before figuring this out. When projects used cmake I used to just change my mind and not use them (until years later more used & wrote about it.) |
I added a link to the build instructions to the main readme. This should make things more clear. As for the use of cmake: This project targets Linux and win32 while using a mix of C, C++ and Java. cmake handles this situation incredibly well. If you happen to know any tool which does the job better and/or being more concise, I am open for suggestions. @dchmelik |
Closing due to lack of response. |
Yes: they're very unclear/incomplete: please update INSTALL.md |
At the moment, is not possible to build this plug-in for win32 since recent versions of some dependencies are unavailable (and reportedly incompatible). Since I cannot even build the library, I can neither update the build instructions nor the installation instructions. I am sorry. For Linux, there is libpurple-signald, which also is not in a good shape, but it works for me™. |
Hi,
I find it difficult to follow you compilation instruction under Linux (https://github.com/hoehermann/purple-signal/blob/master/INSTALL.md). Could you provide step-by-step command please?
The text was updated successfully, but these errors were encountered: