view Resources/CodeGeneration/testWasmIntegrated/build-web.sh @ 1327:4f8db2d202c8 broker

OrthancSeriesProgressiveLoader now has two modes that can be selected at object creation : - progressive (will first load jpeg50, then jpeg90 then PAM) - non-progressive (will directly load PAM (uncompressed)) Please note that the slice loading order remains dynamic and depending upon the slice that the client code wishes to extract from the volume.
author Benjamin Golinvaux <bgo@osimis.io>
date Wed, 25 Mar 2020 14:34:27 +0100
parents f185cfcb72a0
children
line wrap: on
line source

#!/bin/bash
set -e

mkdir -p build-final

# compile TS to JS
tsc --module commonjs --sourceMap -t ES2015 --outDir "build-tsc/" build-wasm/TestStoneCodeGen_generated.ts testWasmIntegrated.ts 

# bundle JS files to final build dir 
browserify "build-tsc/build-wasm/testWasmIntegratedCpp_generated.js" "build-tsc/testWasmIntegrated.js" -o "build-final/testWasmIntegratedApp.js"

# copy WASM loader JS file to final build dir 
cp build-wasm/testWasmIntegratedCpp.js build-final/

# copy HTML start page to output dir
cp testWasmIntegrated.html build-final/


# copy styles to output dir
cp styles.css build-final/

# copy WASM binary to output dir
cp build-wasm/testWasmIntegratedCpp.wasm  build-final/

cp ../test_data/testTestStoneCodeGen.yaml build-final/
cp ../testCppHandler/test_data/test_Message2.json build-final/cppHandler_test_Message2.json

echo "...Serving files at http://127.0.0.1:8080/build-final/testWasmIntegrated.html"

sudo python3 serve.py