# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1605723993 -3600
# Node ID 18384efed33df024bba0bf10c05fa14f511fdeac
# Parent  66e5fcdf5597fca694452ce760c48b2da1cbc03e
debian unstable instructions

diff -r 66e5fcdf5597 -r 18384efed33d Applications/StoneWebViewer/WebAssembly/NOTES.txt
--- a/Applications/StoneWebViewer/WebAssembly/NOTES.txt	Wed Nov 18 11:19:09 2020 +0100
+++ b/Applications/StoneWebViewer/WebAssembly/NOTES.txt	Wed Nov 18 19:26:33 2020 +0100
@@ -30,7 +30,38 @@
 Then, if the installation path is "~/Downloads/emsdk/":
 
 # source ~/Downloads/emsdk/emsdk_env.sh
-# cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=${EMSDK}/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake -DALLOW_DOWNLOADS=ON -G Ninja
+# mkdir Build && cd Build
+# cmake .. -DCMAKE_BUILD_TYPE=Release \
+  -DCMAKE_TOOLCHAIN_FILE=${EMSDK}/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake \
+  -DALLOW_DOWNLOADS=ON -G Ninja
 # ninja install
 
 => The binaries will be put in "../../../wasm-binaries/StoneWebViewer/"
+
+
+Debian unstable
+===============
+
+Last update: 2020-11-18
+
+IMPORTANT - Currently broken: The linker fails on Debian Sid with the
+default package. A workaround is available using "experimental"
+packages:
+https://github.com/emscripten-core/emscripten/issues/11895#issuecomment-729840497
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975069
+
+
+# sudo apt-get install emscripten python3-clang python3-pystache ninja-build
+# mkdir Build && cd Build
+# EMSCRIPTEN=/usr/bin/ cmake .. -DCMAKE_BUILD_TYPE=Release \
+  -DCMAKE_TOOLCHAIN_FILE=/usr/share/emscripten/cmake/Modules/Platform/Emscripten.cmake \
+  -DLIBCLANG=/usr/lib/x86_64-linux-gnu/libclang-9.so \
+  -DALLOW_DOWNLOADS=ON -G Ninja
+# ninja install
+
+=> The binaries will be put in "../../../wasm-binaries/StoneWebViewer/"
+
+The invokation of CMake will give the following warning, that can be safely ignored:
+
+"System is unknown to cmake, create:
+Platform/Emscripten to use this system, please post your config file on discourse.cmake.org so it can be added to cmake"