You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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, triedrelativePathBase
, 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 therust-analyzer
?The text was updated successfully, but these errors were encountered: