Skip to content
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

Windows binary builds are missing #1

Open
Neustradamus opened this issue Feb 28, 2019 · 8 comments
Open

Windows binary builds are missing #1

Neustradamus opened this issue Feb 28, 2019 · 8 comments
Labels
wontfix This will not be worked on

Comments

@Neustradamus
Copy link

@hoehermann: Can you add Windows binary files for all versions?

@hoehermann
Copy link
Owner

hoehermann commented Feb 28, 2019

Update: I created the purple-signal project. Check its readme to see the current state.

No, I won't. Sorry.

In case anyone wants to look into this, they are welcome.

@hoehermann hoehermann added the wontfix This will not be worked on label Feb 28, 2019
@EionRobb
Copy link

I took a stab at this, but signald is hard-wired to use Unix sockets. It should be fairly straight-forward to switch it to use TCP sockets, but that would need a larger rewrite of the plugin than what I have spare time for at the moment

(Also, I added this plugin to the list of Pidgin's third party plugins)

@rasa
Copy link

rasa commented Feb 18, 2020

I took a stab at this, but signald is hard-wired to use Unix sockets.

Windows supposedly now has support for Unix sockets. See
https://unwcf.com/posts/unix-sockets/ as well as:
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/

@EionRobb
Copy link

That's pretty neat. It'll be a little tricky to write support for that with mingw but not terrible.

Unfortunately that doesn't help on the Java side of the fence. Java needs to add support for unix sockets before the signald jar will work.

@hoehermann
Copy link
Owner

I tried to tackle this problem by eliminating the need for sockets completely by embedding the Java implementation in the C library over here: https://github.com/hoehermann/purple-signal It works on Linux, but crashes on Windows. So far, I gained nothing but experience. In case someone is masochistic enough to debug the JVM internals, he or she is welcome to look into it.

@hoehermann
Copy link
Owner

Okay, apparently I am the masochist. Turned out, it was a type error in untyped code. Fairly easy to catch if you know what to look for, but it took me an awful amount of time. Now hoehermann/purple-signal@0967a40 exists and https://stackoverflow.com/questions/60688140/ exists, too. There might be hope for Windows-users after all. :)

@Neustradamus
Copy link
Author

@hoehermann: Thanks, can you look for other softs/libs?

  • purple-signal
  • purple-gowhatsapp

Can you add builds in /releases sections too?

@hoehermann
Copy link
Owner

hoehermann commented Mar 24, 2020

@Neustradamus

Signal (Updated in 2024)

  • purple-presage: Uses a different back-end. Due to the ongoing problems with signald, purple-presage is my current daily driver. There is a native windows version.
  • purple-signald: No Windows build since signald does not run on Windows. Using Unix sockets through WSL has not been successful as of yet.
  • purple-signal: It looked promising, but the API is unstable and upstream has stopped providing Windows binaries.

WhatsApp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants