Feature Request: Allow cargo to specify the directory to run in

[strega-nil]

This would just be a nice feature for interfacing with other build systems, like Make. Currently, you have to

cd dir && cargo build

whereas, in this case you could just

cargo build --directory dir

This would be nice for integration with things like vim's make command, because cargo currently gives the wrong file: as if dir is the base directory, not dir/...

[alexcrichton]

This is actually already possible! If you do cargo build --manifest-path=dir/Cargo.toml it should do the trick.

[strega-nil]

Thanks! I'm sorry for wasting y'all's time 😝

[alexcrichton]

No worries, thanks for the issue regardless!

[1480c1]

Sorry for the necro, but a quick question, does the --manifest-path=dir/Cargo.toml thing also apply to commands other than build, like for example third-party cargo sub-commands? I personally am searching for something similar to make's, ninja's, and git's -C option that applies command wide and this was one of the first results that popped up

[bobbbay]

@1480c1 I would most recommend you test it out yourself! 😉

[mikhail-putilov]

It's such a pity that every tool has its own name for the same concept: maven requires '-f', git '-C' and cargo '--manifest-path' ☹️

[weihanglo]

This is already possible via an unstable flag -C. See #10098 for more.