cargo-component

cargo-component copied to clipboard

Confusion around component dependencies and target dependencies

4

For a second time, I've found myself in a debugging session ultimately due to me confusing component dependencies and target dependencies. I was confused why a local wit package would...

rylev

Implement support in `Cargo.toml` (i.e. `[package.metadata.component.bindings]`) for specifying how generated bindings should refer to already existing implementations. See https://github.com/bytecodealliance/wit-bindgen/issues/840.

peterhuene

How to describe dependencies on local packages with relative path

10

Hello developers, I'm trying to understand Component Model with cargo-component. To that end I have tried to create a simple example, but I have the following error and would like...

NewGyu

Implement same capability https://github.com/bytecodealliance/wit-bindgen/issues/825.

sehz

Preserve comments from wit file in the binary

2

Comments from the wit file are already copied to the bindings.rs file. These should also be contained in the final component, so that `wasm-tools component wit` can provide some useful...

lu4p

Confusing error if versions of local dependencies don't align

2

In a wit file I was referring to a dependency wit package but forgot to attach a version to it. Naturally, resolution failed as I don't have an unversioned package...

rylev

Build Failure with Inline WIT with `wit-bindgen`

6

## Description There's an inconsistency when building a project with inline WIT definitions using `cargo component build`. It fails under `cargo component` but succeeds when manually building with `cargo` and...

tqwewe

I had this .wit file: ``` package example:adder; interface add { add: func(a: u32, b: u32) -> u32; } /// An example world for the component to target. world adder...

lu4p

Document `package.metadata.component` configuration

4

I'm looking for documentation on `package.metadata.component` configurations that can be specified in `Cargo.toml`. Currently, [cargo-component-bindings](https://docs.rs/cargo-component-bindings/0.4.1/cargo_component_bindings/macro.generate.html#settings-1) only documents the `[package.metadata.component.bindings]` table. The default `Cargo.toml` added with `cargo component new --reactor foo`...

vwkd

Could cargo-component auto-compose components?

5

Currently if I add a `[package.metadata.component.dependencies]` section to a component with `path = '...'` the final output of `cargo component build` has an import of an instance. Could it be...

alexcrichton