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

(optionally) save logs of stdout and stderr #1331

Closed
nrc opened this issue Feb 21, 2015 · 2 comments
Closed

(optionally) save logs of stdout and stderr #1331

nrc opened this issue Feb 21, 2015 · 2 comments

Comments

@nrc
Copy link
Member

nrc commented Feb 21, 2015

Related to #985 and #1106.

It would be nice to save logs of the output of rustc and build scripts. Just dumping a log file in the target dir or have a new dir to put the logs in, either way would be fine. This could always happen or be specified with a flag to cargo build. I expect this to be useful for debugging and also (my use case) when replacing rustc with a tool and you want to see its output, even when it is successful.

@tivervac
Copy link

tivervac commented Apr 5, 2015

According to #985 output should be located in target/build/$crate-$hash/output. Saving them by default doesn't seem very user-friendly to me. Most of the time you can find the info you need in the printed logs thus users would actually be spammed by these log files they don't need. A special flag is a way better idea. If you are on a unix system you could ofcourse just use output redirection.

@alexcrichton
Copy link
Member

Ah yeah Cargo actually already does this for build scripts (in the places @FlashYoshi mentions) and otherwise Cargo no longer captures rustc/rustdoc output ever so it's always printed. As a result, I'm gonna close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants