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

Switch to output release/debug after compile #2909

Merged
merged 1 commit into from
Jul 26, 2016

Conversation

sophiajt
Copy link

This is similar to #2896 but instead of inline, it puts an indicator at the bottom showing if it was a release or debug build.

jturner-23759:cargo jturner$ ./target/release/cargo build
Finished debug (unoptimized + debuginfo) build.
jturner-23759:cargo jturner$ ./target/release/cargo build --release
Finished release (optimized) build.

@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@sophiajt
Copy link
Author

Image to see a better example:

screen shot 2016-07-22 at 9 03 25 pm

@jonas-schievink
Copy link
Contributor

I feel like "Finished" should be the same color as "Compiling" (and aligned to it)

@@ -76,7 +78,7 @@ impl<'a> JobState<'a> {
}

impl<'a> JobQueue<'a> {
pub fn new<'cfg>(cx: &Context<'a, 'cfg>) -> JobQueue<'a> {
pub fn new<'cfg>(cx: &Context<'a, 'cfg>, is_release: bool, is_doc_all: bool) -> JobQueue<'a> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these booleans are actually accessible through cx.build_config, so perhaps they don't need to be passed in?

@alexcrichton
Copy link
Member

I personally like this being set apart a bit so you know it's not just another crate being compiled, but I could go both ways.

@sophiajt
Copy link
Author

I can go either way re: styling. Shouldn't be too hard to fix up the tests now that they're updated.

@sophiajt
Copy link
Author

Now:

screen shot 2016-07-25 at 11 29 23 am

@alexcrichton
Copy link
Member

Looks good to me, thanks @jonathandturner! Could you also squash the commits down?

@alexcrichton
Copy link
Member

@bors: r+ cd955f1

Thanks @jonathandturner!

@bors
Copy link
Contributor

bors commented Jul 25, 2016

⌛ Testing commit cd955f1 with merge dc46aba...

bors added a commit that referenced this pull request Jul 25, 2016
…crichton

Switch to output release/debug after compile

This is similar to #2896 but instead of inline, it puts an indicator at the bottom showing if it was a release or debug build.

```
jturner-23759:cargo jturner$ ./target/release/cargo build
Finished debug (unoptimized + debuginfo) build.
jturner-23759:cargo jturner$ ./target/release/cargo build --release
Finished release (optimized) build.
```
@bors
Copy link
Contributor

bors commented Jul 26, 2016

☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing dc46aba to master...

@bors bors merged commit cd955f1 into rust-lang:master Jul 26, 2016
@sophiajt sophiajt deleted the debug_release_at_bottom branch July 26, 2016 15:41
@alexcrichton alexcrichton added the relnotes Release-note worthy label Jul 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relnotes Release-note worthy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants