157577b866
There was a break that was solved by adding -lGL to our link steps. I discovered a few extra flags to aid in debugging builds and I've left those in (they aren't too noisy IMO). This changes the base dockerfile to use the official emscripten one. Code size delta for full build is +5 kb For future reference, emsdk decides which "library JS" files to pull in using |
||
---|---|---|
.. | ||
npm-asmjs | ||
npm-wasm | ||
perf | ||
tests | ||
.gitignore | ||
chaining.js | ||
CHANGELOG.md | ||
compile.sh | ||
externs.js | ||
helper.js | ||
karma.bench.conf.js | ||
karma.conf.js | ||
Makefile | ||
package.json | ||
pathkit_wasm_bindings.cpp | ||
README.md | ||
serve.py |
PathKit WASM API
This library lets you use Skia's feature-rich PathOps API in the browser.
Compiling the source
Download the Enscriptem SDK.
Set the EMSDK environment variable to the directory you installed it to.
Run ./compile.sh
to compile a production, WASM build to $SKIA_HOME/out/pathkit
.
Add "--help" for more options.
Deploying to npm
# Build all 3 versions (release, test, debug) for both asmjs and WASM
# These binaries will be placed in the proper places of npm-*/bin
# This takes 5-10 minutes.
make npm
# Update the package.json files of both npm-asmjs and npm-wasm
make update-patch # or update-minor or update-major
# Publish both repos
make publish