You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should create a Wasm CM Rust project, so the template should be updated:
add WIT file
set Wasm CM metadata in Cargo.toml
Build project command
Start by calling the cargo_component to build the project and switch to use it as a library when our needs grow. We probably would like to avoid forking it but rather building on top of it.
EDIT(denys): I believe building on top of the cargo-component is no longer an option given that we are going to add plenty of customizations touching Cargo.toml (miden packaging), Wasm component building, etc. The only feasible solution I see is to copy the relevant parts of the cargo-component into cargo-miden.
The text was updated successfully, but these errors were encountered:
@bitwalker Do we want the extension to keep the support for building a non-Wasm CM projects as it does today along with Wasm CM? I mean, our whole toolchain will be Wasm CM oriented. Going Wasm CM only for the extension will simplify things a lot, but we would not be able to make a release until almost everything in the Beta1 milestone is implemented.
New project command
Should create a Wasm CM Rust project, so the template should be updated:
Build project command
Start by calling the
cargo_component
to build the project and switch to use it as a library when our needs grow. We probably would like to avoid forking it but rather building on top of it.EDIT(denys): I believe building on top of the
cargo-component
is no longer an option given that we are going to add plenty of customizations touching Cargo.toml (miden packaging), Wasm component building, etc. The only feasible solution I see is to copy the relevant parts of thecargo-component
intocargo-miden
.The text was updated successfully, but these errors were encountered: