From 60795a8d002c7fdb850e7a2f35f674057fe346b0 Mon Sep 17 00:00:00 2001
From: exquo <62397152+exquo@users.noreply.github.com>
Date: Sun, 21 Nov 2021 10:17:11 +0000
Subject: [PATCH] Add a comment about bundling .so on windows

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

diff --git a/Provide-native-lib-for-libsignal.md b/Provide-native-lib-for-libsignal.md
index d55f33a..8f0d2ff 100644
--- a/Provide-native-lib-for-libsignal.md
+++ b/Provide-native-lib-for-libsignal.md
@@ -65,7 +65,7 @@ For signal-cli to be able to use the newly compiled library file, it can either
 
 or be placed on the Java library path (see below). Only if there is no bundled file will libsignal search the library path (`java.library.path`) for the `.dylib`/`.so`/`.dll` file.
 
-Note: on Windows, bundling the compiled `signal_jni.dll` file does not seem to work: see [#517](https://github.com/AsamK/signal-cli/issues/517).
+Note: on Windows, bundling the compiled `signal_jni.dll` file does not seem to work: see [#517](https://github.com/AsamK/signal-cli/issues/517). (According a [comment](https://github.com/AsamK/signal-cli/issues/517#issuecomment-894677266) in that thread, bundling does work if the files are renamed).
 
 
 #### Java library path