-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Custom location for output directory (target
path)
#1156
Comments
+1 This pains me. |
+1. My use case also stems from integrating with another build system. My current workaround is just to symlink I'd also like it if this sort of thing picked up config from the env, to avoid passing flags all over the show. |
+1 |
+1 I use SublimeLinter to automatically run cargo in the background and display any errors in Sublime Text. This however means that there is still a cargo process running in the background when I switch back to the terminal and run |
Closing as a dupe of #482 |
It should be possible to change the location of Cargo's output from the default
target
subdirectory. I'm not sure whether it's not possible or I just don't know how to read the Cargo doc.Use case: I have project
foo
with several sub-directoriesarnold
,bethany
,chris
, etc. I use CMake to build the main project which builds each sub-project in paths likebuild/arnold
. One of these sub-projects now uses Rust and Cargo (because Cargo has awesome dependency management), so from the point of view of the project Cargo should place its output inbuild/bethany
notbethany/target
.This is not currently a significant issue, but it could be with larger projects.
A related issue is that rustc warning/error messages should now give either absolute paths or paths relative to the root of the project, i.e.
bethany/src/lib.rs:36
instead ofsrc/lib.rs:36
.The text was updated successfully, but these errors were encountered: