09-04-2020, 12:07 PM
I've just pushed a new signal-desktop release, 1.35.1-2. That was quite horrible to build, so be aware that things might break when you use it:
This most recent signal release includes voice/video calling. I have not yet been able to test if those new features work as intended with my build, but at least the "base features" (ie. writing and receiving encrypted messages) seem to still work as intended.
Also, I've not yet been able to get the build process for it "PKGBUILDized" – basically there's no precompiled libringrtc.node provided (for aarch64) by signal-ringrtc-node, which means having to build ringrtc, which requires getting separate depot_tools, clang 11, ncurses5-compat-libs and quite some fiddling with build flags, variables and build pathes to build, as at no point has non-android-aarch64 seemed to have been considered a thing.
I'll still try to get this more streamlined in such a way that I can put it in the PKGBUILD, or at least provide usable build instructions so the required library can be built by others should it be desired to build from source :)
This most recent signal release includes voice/video calling. I have not yet been able to test if those new features work as intended with my build, but at least the "base features" (ie. writing and receiving encrypted messages) seem to still work as intended.
Also, I've not yet been able to get the build process for it "PKGBUILDized" – basically there's no precompiled libringrtc.node provided (for aarch64) by signal-ringrtc-node, which means having to build ringrtc, which requires getting separate depot_tools, clang 11, ncurses5-compat-libs and quite some fiddling with build flags, variables and build pathes to build, as at no point has non-android-aarch64 seemed to have been considered a thing.
I'll still try to get this more streamlined in such a way that I can put it in the PKGBUILD, or at least provide usable build instructions so the required library can be built by others should it be desired to build from source :)
