Change the default output location to target/debug #1373
Conversation
|
r? @wycats (rust_highfive has picked a reviewer for you, use r? to override) |
|
cc @huonw |
|
Should we try to make progress on #785 (comment) too? (Though, I suspect changing from |
|
Hm that's a good point, I had forgotten about that. You can already get that behavior with a specified |
|
@bors: r=wycats 6881fbc23d1d60452ca96d6ec1cb62c6dded548c |
|
⌛ Testing commit 6881fbc with merge 496579a... |
|
💔 Test failed - cargo-win-32 |
This commit now funnels all output of Cargo by default to be in `target/debug` instead of the bare `target` directory. This change is targeted at raising awareness of whether a debug build is being used (as opposed to a release build). It is also aimed at remedying a common scenario where `cargo build` is followed by `cargo build --release` and then the debug binaries are run by accident. This does not yet explore the option of providing symlinks to the most recent build, hence this commit is a breaking change due to the restructuring of the layout of the output. Note that this commit does **not** change the output location for documentation. All output of `cargo doc` continues to be funneled into the `target/doc` directory. Closes rust-lang#785
This commit now funnels all output of Cargo by default to be in `target/debug` instead of the bare `target` directory. This change is targeted at raising awareness of whether a debug build is being used (as opposed to a release build). It is also aimed at remedying a common scenario where `cargo build` is followed by `cargo build --release` and then the debug binaries are run by accident. This does not yet explore the option of providing symlinks to the most recent build, hence this commit is a breaking change due to the restructuring of the layout of the output. Note that this commit does **not** change the output location for documentation. All output of `cargo doc` continues to be funneled into the `target/doc` directory. Closes #785
|
💔 Test failed - cargo-win-32 |
|
@bors: retry On Fri, Mar 6, 2015 at 11:35 AM, bors notifications@github.com wrote:
|
|
⚡ Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-64 are reusable. Rebuilding only cargo-win-32... |
|
💔 Test failed - cargo-win-32 |
|
@bors: retry
|
|
⚡ Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-64 are reusable. Rebuilding only cargo-win-32... |
|
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64 |
5 participants
This commit now funnels all output of Cargo by default to be in
target/debuginstead of the bare
targetdirectory. This change is targeted at raisingawareness of whether a debug build is being used (as opposed to a release
build). It is also aimed at remedying a common scenario where
cargo buildisfollowed by
cargo build --releaseand then the debug binaries are run byaccident.
This does not yet explore the option of providing symlinks to the most recent
build, hence this commit is a breaking change due to the restructuring of the
layout of the output.
Note that this commit does not change the output location for documentation.
All output of
cargo doccontinues to be funneled into thetarget/docdirectory.
Closes #785