Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Rust launch config when root not workspaceFolder #1105

Open
kriswuollett opened this issue May 27, 2024 · 0 comments
Open

Support Rust launch config when root not workspaceFolder #1105

kriswuollett opened this issue May 27, 2024 · 0 comments
Labels
enhancement Enchancement request

Comments

@kriswuollett
Copy link

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?

@kriswuollett kriswuollett added the enhancement Enchancement request label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enchancement request
Projects
None yet
Development

No branches or pull requests

1 participant