Problem with custom target-dir

[Stargateur]

I changed the target-dir of cargo to .target but despite rls have something that should use cargo config, this seem to not working. Is this because atom-ide-rust overwrite target_dir ? Or this is a bug of rls ?

Maybe this is link to this, rust-lang/vscode-rust#322

I also try to put a rls.toml and add:

[rust]
target_dir = ".target"
target-dir = ".target"

or

target_dir = ".target"
target-dir = ".target"

Both not working, I expected that it should only change the default directory where rls is build but both just do nothing. Also, I like that fact they didn't follow the same rule target_dir != target-dir, I tried both just in case.

That a big problem for me because I use rust in a unity project in Unity only way to avoid there create .meta file is to use hidden file, sometime these .meta file block cargo because somehow cargo doesn't like .lock.meta (but I already fixed this with cargo config). Also, this make unity editor slow because it check for every new file I don't know if this could stop rls to work cause of lock file as cargo but I want to avoid the problem.

Is there something, I do wrong ?

[alexheretic]

Try a rls.toml in the project root with

target_dir = ".target/rls"

This works when I use it. Using ".target/rls" makes sense if you plan to use ".target" for manual cargo invocations, normally rls will use "target/rls".

And yes it's not great that rls is picky about snake-case/kebab-case particularly as .cargo config uses kebab here. This is something that must be improved upstream: https://github.com/rust-lang/rls

[Stargateur]

That indeed work, thank.

That strange because the pull request that I linked clearly say, that RLS should use cargo setting and the code let target_dir = target_dir.join("rls"); look like it was the indented behavior.

Should I open an issue in RLS to ask about clarify the behavior ?

And somehow target_dir = ".target" look to works now. I don't understand. AH I think I understand RLS and cargo was using the same debug folder so I didn't see the difference. That explain a lot about the lock file ;)

[alexheretic]

Yes I agree, setting .cargo/config to

[build]
target-dir = ".target"

is the main way to set target for cargo. As you say the RLS code looks like it should use this, but it isn't working for me either.

Using the RLS config via rls.toml is a full override, it'll ignore cargo config. So it makes sense that the rls config is working.

[alexheretic]

I've raised an issue to improve the config parses, ie kebab-case: rust-lang/rls#1153

I'll leave the target-dir should be cargo-target-dir + "rls" issue to you.