Everything was fine until I recently upgraded cargo-component-bindings to "0.6.0. Now, I get an error message saying
error: bindings file `/target/bindings/myproject/bindings.rs` does not exist
The file bindings.rs is generated, indeed, but it is placed to myproject/src.
The macro cargo_component_bindings::generate!(); does it allow to name a target folder?
Update:
My CI toolchain does not have a problem to build the same project.
It installs cargo install cargo-component@0.5.0 prior to the build where I have cargo-component v0.16.0 locally.
It seems that at a certain point, the output directory which seems to be determined by cargo-component changed. What I still do not understand is why the system still searches bindings.rs under the original path.
Last updated: Dec 06 2025 at 06:05 UTC