-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
gh-95853: Add script to automate WASM build (GH-95828) #95828
Conversation
Automate WASM build with a new Python script. The script provides several build profiles with configure flags for Emscripten flavors and WASI. The script can detect and use Emscripten SDK and WASI SDK from default locations or env vars. ``configure`` now detects Node arguments and creates HOSTRUNNER arguments for Node 16. It also sets correct arguments for ``wasm64-emscripten``.
Getting failures on MacOS. Built with Testing with
Then that import failure repeats. |
$ ./Tools/wasm/wasm_builder.py emscripten-browser compile | ||
$ ./Tools/wasm/wasm_builder.py emscripten-node-dl test | ||
$ ./Tools/wasm/wasm_builder.py wasi test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the one compile example but the two test examples? I would just choose a single build target (e.g. wasi
), show the end-to-end, and start the example by saying you're using wasi
as an example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because emscripten-browser
target does not support test
verb. We do not have a test runner for browsers.
The test failure is caused by the fact that macOS does not have realpath command |
Co-authored-by: Brett Cannon <brett@python.org>
Co-authored-by: Brett Cannon <brett@python.org>
Happy type checker is happy
|
I have opened #95952 to track the test issue on macOS. |
Co-authored-by: Brett Cannon <brett@python.org>
Thanks @tiran for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Automate WASM build with a new Python script. The script provides several build profiles with configure flags for Emscripten flavors and WASI. The script can detect and use Emscripten SDK and WASI SDK from default locations or env vars. ``configure`` now detects Node arguments and creates HOSTRUNNER arguments for Node 16. It also sets correct arguments for ``wasm64-emscripten``. Co-authored-by: Brett Cannon <brett@python.org> (cherry picked from commit 32ac98e) Co-authored-by: Christian Heimes <christian@python.org>
GH-95968 is a backport of this pull request to the 3.11 branch. |
Automate WASM build with a new Python script. The script provides several build profiles with configure flags for Emscripten flavors and WASI. The script can detect and use Emscripten SDK and WASI SDK from default locations or env vars. ``configure`` now detects Node arguments and creates HOSTRUNNER arguments for Node 16. It also sets correct arguments for ``wasm64-emscripten``. Co-authored-by: Brett Cannon <brett@python.org>
GH-96045, GH-96389, GH-96744) (GH-96749) Automate WASM build with a new Python script. The script provides several build profiles with configure flags for Emscripten flavors and WASI. The script can detect and use Emscripten SDK and WASI SDK from default locations or env vars. ``configure`` now detects Node arguments and creates HOSTRUNNER arguments for Node 16. It also sets correct arguments for ``wasm64-emscripten``.
Automate WASM build with a new Python script. The script provides
several build profiles with configure flags for Emscripten flavors
and WASI. The script can detect and use Emscripten SDK and WASI SDK from
default locations or env vars.
configure
now detects Node arguments and creates HOSTRUNNERarguments for Node 16. It also sets correct arguments for
wasm64-emscripten
.