Mihai Renea

@chrysn

@chrysn thanks for the fast reply, this is valuable information. I will try out your suggestions and write down a log, perhaps that will help with building the documentation later....

Indeed, rust-analyzer is failing when building `build.rs` in riot-sys, because env variables are missing (` Please pass in RIOT_CC; see README.md for details.: NotPresent`). According to the rust-analyzer [documentation](https://rust-analyzer.github.io/manual.html#configuration), it...

I modified `settings.json` to the following, and it did the trick: ```json { "rust-analyzer.cargo.extraEnv": { "CC": "", "CFLAGS": "", "CPPFLAGS": "", "CXXFLAGS" : "", "RIOT_COMPILE_COMMANDS_JSON" : "/home/[email protected]/proj/lara_test_rust/bin/native/cargo-compile-commands.json", "RIOT_USEMODULE" : "at...

I understand. For the record, `cargo check` is already calling pretty much any `build.rs` it can find, so rust-analyzer too, indirectly. Quite alarming, tbh. What I had in mind is...

I looks good, my only suggestion would be that the contents of `$(USEMODULE)` be exported into a file, so I can `cat` it directly when setting the environment, and don't...

I think we're mixing up stuff here. `compile-commands.json` is not used by the IDE, but the language server. In this case, rust-analyzer is the language server, but it doesn't understand...

So, `RIOT_USEMODULE` must still be set, but is not printed by `info-rust`.

Oh, my bad! Yes, I pulled the last changes and now it works just fine!

Yes, I also think `riot-headers.h` is the next big hurdle. Solution ii is fine for the moment, but in the long run, it would be convenient to pull riot-sys from...