How to setup rust-analyzer to use cross for all the building?

[becothas]

Hi.
I am trying to setup cross to use together with rust-analyzer.

To get cross to work, I had to create a modified Dockerfile, that only copies my libs and *.h files into the image. After that cross worked as expected, but rust-analyzer cannot expand procMacros and searches the target directory in my os-root.

My current rust-analyzer configuration.

    "rust-analyzer": {
        "check":{
            "features":"all",
            "overrideCommand": ["cross", "check", "--message-format=json","--target=armv7-unknown-linux-gnueabihf"],
            "targets": "armv7-unknown-linux-gnueabihf"
        },
        "cargo":{
            "buildScripts": {
                "overrideCommand": ["cross", "check", "--message-format=json","--target=armv7-unknown-linux-gnueabihf"]
            },
            "target": "armv7-unknown-linux-gnueabihf"
        }
    }
}

Dockerfile

FROM ghcr.io/cross-rs/armv7-unknown-linux-gnueabihf:edge


COPY sysroot/lib /lib
COPY sysroot/usr /usr

Cross.toml

[build]

default-target = "armv7-unknown-linux-gnueabihf"

[target.armv7-unknown-linux-gnueabihf]
image = "cross-env:latest"

Rust analyzer version rust-analyzer 1.76.0
Host Arch is x86_64 with Linux

Is there a guide to setup Rust-analyzer with cross to have all the building happen with cross, because of dependencies that are precompiled for the target platform ?
Or can somebody give me some support to get it working?

[Emilgardis]

This is more a rust-analyzer problem. We shouldnt do anything to make this not work.

[becothas]

Thanks for your reply.
I discussed the issue in the rust forum Discussion

The solution was, to just start rust-analyzer in a cross container with
cross-util run -i --target <target> -- rust-analyzer