Closed thegecko closed 10 months ago
Thanks for the PR! This is not using npmjs.com's registry but rather github's npm registry, right?
I think the CI problem is with -it
in docker run
.
Changing it to -i
should fix the failure.
This is not using npmjs.com's registry but rather github's npm registry, right?
that's right
I think the CI problem is with -it in docker run. Changing it to -i should fix the failure.
thanks, forgot to change that
LGTM
Although the action succeeded, it failed to find the output files, does this look right?
./build/llvm/bin/llvm-box.wasm
./build/llvm/bin/llvm-box.mjs
Nop, that doesn't look correct. Do you have bandwidth to take a look?
Ok, could you tell me where the output llvm wasm and mjs files end up? I don't have a set up I can look at
hm, I just checked, and the two files should be there: ./build/llvm/bin/llvm-box.{wasm,mjs}
OK, I'll build locally and see whats going on
This PR should add a GitHub action which builds the llvm WASM file (about 2 hours).
If triggered using a tag, a package should also be published onto the GitHub npm registry with emscripten types to allow the WASM file to be imported by another project e.g.:
This was developed to separate our usage of llvm-box from a consuming project. Feel free to use it as inspiration if something else is required in this project