Skip to content

Commit

Permalink
js: don't regenerate wrappers and wasm constants when building
Browse files Browse the repository at this point in the history
The wasm build should build what is in tree like the other wrappers do,
and not silently update the generated code before compiling.
  • Loading branch information
jgriffiths committed Jan 29, 2024
1 parent 8327cf5 commit 57cc3ce
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
6 changes: 0 additions & 6 deletions src/wasm_package/build.sh
Original file line number Diff line number Diff line change
@@ -1,12 +1,6 @@
#! /usr/bin/env bash
set -xeo pipefail

# Update function list in wasm_exports.sh and run codegen for the public API in functions.js
(cd ../.. && ./tools/build_wrappers.py)

# Update WASM package constants and version to match libwally
(cd ../.. && ./tools/update_wasm_package.sh)

# Build WASM (Note Elements is always enabled)
(cd ../.. && ./tools/build_wasm.sh)
mkdir -p libwally_wasm && cp ../../dist/wallycore.{js,wasm} libwally_wasm/
Expand Down
2 changes: 1 addition & 1 deletion tools/update_wasm_package.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,4 @@ current_version=$(grep -oP 'AC_INIT\(\[libwallycore\],\[\K[^\]]+' configure.ac)


# Calling build_wrappers.py is also necessary to update the wasm functions.js file.
# This is handled by update_generated.sh and by the wasm package build script.
# This is handled by update_generated.sh which calls this script.

0 comments on commit 57cc3ce

Please sign in to comment.