cargo-component

cargo-component copied to clipboard

Building on https://github.com/bytecodealliance/cargo-component/issues/326, `cargo component serve` should be able to take a `--port` command similar to `wasmtime serve` to specify a port.

yoshuawuyts

this is more of a discussion point than a definite bug or feature request, but I figured it could help to share my anecdotal experience and a pain point, maybe...

dakom

cargo-component cannot find exported function in a world

5

I am following https://component-model.bytecodealliance.org/language-support/rust.html#importing-an-interface-into-a-command-component to create a command component with `cargo-component`. My adder WIT was: ``` package component:adder; world adder { export add: func(a: s32, b: s32) -> s32; }...

ifsheldon

When I walked through the tutorial in https://component-model.bytecodealliance.org/language-support/rust.html#importing-an-interface-into-a-command-component with my own adder example, after Step 3 adding `package.metadata.component.target.dependencies` and running `cargo build component`, I found `bindings.rs` was generated under `src`...

ifsheldon

Use wasm-wasip2 target as default build target

4

https://github.com/bytecodealliance/cargo-component/blob/1e58afa097e153797e4195cf3f2bc749a3654f31/README.md?plain=1#L184 Hi! I saw this today, but the referred issue has been closed as complete. The latest cargo-component 0.19 still uses wasm-wasip1 as the default build target. Rust in the...

ifsheldon

hi folks, playing with building wasm components and it seems the current approach requires one to run `cargo component bindings` to generate a `src/bindings.rs` file, which then has to be...

ryankurte