Closed wouterdebie closed 1 year ago
I have no idea. :(
In theory, rust-analyzer should run the full build, but with that said, I've not used the custom components feature myself. Mr Obvious here, but you did restart VS Code (as in the Rust Analyzer language server) after applying the changes to Cargo.toml
(though that should not be necessary, I think)?
I've done some investigation and it seems an issue with the fact that wen using the esp
tool chain the component is not included in the bindings. I don't think it has something to do with the template, so I'll check with the esp-idf-sys
folks.
Hi,
I'm experiencing the following discrepancy between
rust-analyzer
builds and regularcargo
builds. I've added theesp-camera
component by adding acomponents/
directory in the root of my project with a checked out repo ofesp32-camera
, added abindings.h
and added the following to mycargo.toml
:When I run with
cargo build
, the component is included and I can use functions from it. However, when I userust-analyzer
(through vscode), the component doesn't seem to be included. I end up with a differentbindings.rs
in my target build directory that doesn't contain any reference to the camera component. Thebindings.rs
that is generated during thecargo build
does contain the camera code.Any idea why those two builds are different?