-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Document expected workflow for WASI builds #105253
Labels
Comments
#105261 would probably simplify things if it were possible. |
23 tasks
We should probably consider creating a separate WASI dev container which does the actual build of WASI as part of the pre-build. That way the main dev container can be a bit faster and smaller to get up and going, while providing a pre-build that has WASI already built and ready to go. |
28 tasks
28 tasks
31 tasks
33 tasks
29 tasks
Part of #112473 . |
brettcannon
added a commit
that referenced
this issue
Nov 30, 2023
…t to simplify doing a WASI build (GH-112473)
39 tasks
67 tasks
aisk
pushed a commit
to aisk/cpython
that referenced
this issue
Feb 11, 2024
…asm/wasi.py` script to simplify doing a WASI build (pythonGH-112473)
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this issue
Sep 2, 2024
…asm/wasi.py` script to simplify doing a WASI build (pythonGH-112473)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With
Tools/wasm
, the tooling is there for building WASI, but the overall expected development flow could probably stand to be written out explicitly.The text was updated successfully, but these errors were encountered: