-
Couldn't load subscription status.
- Fork 700
Add example for building executor_runner in Wasm #12303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12303
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New Failures, 4 Cancelled Jobs, 1 Unrelated FailureAs of commit a21942d with merge base 6669637 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Thanks for adding the CI test, and all the debugging to get it working! Great job. |
### Summary Added the license header to the bash scripts added in #12303. ### Test plan N/A
Summary
Since we want to have ExecuTorch on web builds, we first need to be able to compile it to Wasm. An example was added that gives instructions on how to build executor_runner with Emscripten, along with some modifications to CMakeLists.txt while Emscripten is used while building.
Test plan
The test script can be run with
bash examples/wasm/test_build_wasm.shfrom the root directory. This attempts to build executor_runner and run it on the add_mul and mv2 models.Added a CI test-build-wasm-linux to run this script.