I have two rust-analyzer.linkedProjects because I've currently split my projects due to a common dependency version incompatability. I did this to avoid having another git repository for a temporary situation. The primary one is in the root of the vscode workspace folder, and the other is in a subdirectory. The Rust Analyzer works fine with this setup. However I cannot set up a launch configuration for the inner workspace since this extension seems to support only cargo workspaces at the root of a vscode workspace. I searched for any configuration option, tried relativePathBase, e.g., ${workspaceFolder:internal}/sub_project but that did not work. It only finds crates registered in the parent (root) directory.
Is there a way to specify the relevant "Rust Analyzer Linked Project" (path) for an lldb launch config? Whether or not there may be a better way to configure dependencies in a single workspace, shouldn't launch configs match the project specification ability of the rust-analyzer?
I have two
rust-analyzer.linkedProjectsbecause I've currently split my projects due to a common dependency version incompatability. I did this to avoid having another git repository for a temporary situation. The primary one is in the root of the vscode workspace folder, and the other is in a subdirectory. The Rust Analyzer works fine with this setup. However I cannot set up a launch configuration for the inner workspace since this extension seems to support only cargo workspaces at the root of a vscode workspace. I searched for any configuration option, triedrelativePathBase, e.g.,${workspaceFolder:internal}/sub_projectbut that did not work. It only finds crates registered in the parent (root) directory.Is there a way to specify the relevant "Rust Analyzer Linked Project" (path) for an
lldblaunch config? Whether or not there may be a better way to configure dependencies in a single workspace, shouldn't launch configs match the project specification ability of therust-analyzer?