3d99b1e347
Also make a CPU only and GPU only build (although the latter still has a lot of CPU logic). Bug: skia: Change-Id: I857c2300021c2adb5344865c28e4ad3e8d332954 Reviewed-on: https://skia-review.googlesource.com/c/162022 Reviewed-by: Kevin Lubick <kjlubick@google.com> |
||
|---|---|---|
| .. | ||
| npm-asmjs | ||
| npm-wasm | ||
| perf | ||
| tests | ||
| .gitignore | ||
| chaining.js | ||
| 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