From d4b34404d3d142bccac53aba41730e2e6cad4300 Mon Sep 17 00:00:00 2001
From: exquo <62397152+exquo@users.noreply.github.com>
Date: Sun, 18 Jul 2021 17:27:36 +0000
Subject: [PATCH] Add build native libs repo link

---
 Provide-native-lib-for-libsignal.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Provide-native-lib-for-libsignal.md b/Provide-native-lib-for-libsignal.md
index 68e3a35..a58e7a3 100644
--- a/Provide-native-lib-for-libsignal.md
+++ b/Provide-native-lib-for-libsignal.md
@@ -3,6 +3,8 @@ You need to use the library files that are compiled for your CPU architecture an
 
 Do note that signal-cli already comes pre-bundled with the linux (with a recent enough gnu libc, see [#643](https://github.com/AsamK/signal-cli/issues/643)) x86_64 version of zkgroup and libsignal-service, so if you are on that platform then you should be able to use signal-cli with no issues.
 
+**Update:** pre-compiled libraries for most popular platforms are now available in a [GitHub actions repo](https://github.com/exquo/signal-libs-build) (see [#662](https://github.com/AsamK/signal-cli/discussions/662)).
+
 # libsignal-client
 ### Building libsignal-client yourself
 Go to the [releases page](https://github.com/signalapp/libsignal-client/releases) and download the source for the libsignal-client version used by signal-cli (**Check the version of signal-client....jar in the signal-cli lib folder** - as of 1st May 2021 its v0.8.1 release).