Skip to content
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

Wasm CM support in cargo extension #90

Closed
Tracked by #80
greenhat opened this issue Jan 11, 2024 · 1 comment · Fixed by #329
Closed
Tracked by #80

Wasm CM support in cargo extension #90

greenhat opened this issue Jan 11, 2024 · 1 comment · Fixed by #329
Assignees
Labels
cargo-miden Pertaining to the Cargo extension frontend frontend wasm WebAssembly frontend

Comments

@greenhat
Copy link
Contributor

greenhat commented Jan 11, 2024

New project command

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.

@greenhat greenhat self-assigned this Jan 11, 2024
@greenhat greenhat added frontend wasm WebAssembly frontend labels Jan 11, 2024
@bitwalker bitwalker added this to the Builder's Testnet milestone Feb 7, 2024
@greenhat greenhat modified the milestones: Alpha, Beta 1 Apr 2, 2024
@bitwalker bitwalker modified the milestones: Beta 1, Beta 2 May 6, 2024
@bitwalker bitwalker modified the milestones: Beta 2, Beta 1 Sep 3, 2024
@greenhat
Copy link
Contributor Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cargo-miden Pertaining to the Cargo extension frontend frontend wasm WebAssembly frontend
Projects
None yet
2 participants