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

Crate level rust-analyzer.cargo.target? Perhaps just use .cargo/config.toml? #11900

Open
Zageron opened this issue Apr 5, 2022 · 4 comments
Open
Labels
C-support Category: support questions

Comments

@Zageron
Copy link

Zageron commented Apr 5, 2022

Is there any way to do this?
I believe I recall seeing some older posts mentioning that there isn't currently support for multi-target.

I think this is asking the same thing? #10021

@trevyn
Copy link

trevyn commented Jun 4, 2022

If you’re using vscode, you can make a .vscode/settings.json file with project-level settings overrides, if that’s what you’re looking for.

see also: #11268

@Veykril Veykril added the C-support Category: support questions label Jun 4, 2022
@dacut
Copy link

dacut commented Jun 26, 2022

Does this actually work? VSCode shows it as an unsupported attribute at the folder level (assuming that's what you meant by project). Neither rust-analyzer.cargo.target nor rust-analyzer.cargo.features seem to have any effect at the folder level.

@trevyn
Copy link

trevyn commented Jun 26, 2022

It looks like setting up a "multi-root workspace" may let you customize settings at the "folder level":

https://code.visualstudio.com/docs/editor/workspaces#_multiroot-workspace-settings:

When you open a .code-workspace as workspace, all workspace settings will be added into the .code-workspace file.

You can still configure settings per root folder and the Settings editor will present a third setting scope called Folder Settings:

@dacut
Copy link

dacut commented Jun 26, 2022

I'm using exactly that, but rust-analyzer doesn't appear to honor folder-level settings. This seems to be something that the extension needs to support directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-support Category: support questions
Projects
None yet
Development

No branches or pull requests

4 participants