Support configuration of what compiler to run #1629
Conversation
Not having a lifetime parameter on the ubiquitous Config structure allows a great deal of other lifetime annotations to be removed and should make dealing with storage of Config in a structure much easier (only one lifetime to deal with, not two).
|
r? @brson |
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
|
@bors r+ |
|
📌 Commit 9afa4c1 has been approved by |
|
⌛ Testing commit 9afa4c1 with merge 7395317... |
|
💔 Test failed - cargo-linux-32 |
|
@bors: retry On Mon, May 18, 2015 at 5:15 PM, bors [email protected] wrote:
|
|
⚡ Previous build results for cargo-linux-64, cargo-mac-32, cargo-mac-64 are reusable. Rebuilding only cargo-linux-32, cargo-win-32, cargo-win-64... |
|
💔 Test failed - cargo-win-32 |
|
@bors: r=brson |
|
📌 Commit 97f9b51 has been approved by |
|
@bors: r+ |
|
📌 Commit 3144125 has been approved by |
|
⌛ Testing commit 3144125 with merge 61a59f8... |
|
💔 Test failed - cargo-linux-64 |
In addition to global RUSTC/RUSTDOC env vars, this commit recognizes `build.rustc` and `build.rustdoc` as configuration keys for Cargo to instruct what tools should be used instead of the default. Closes rust-lang#967
These commits add two vectors through which the compiler run can be configured: * A `RUSTC` environment variable * A `build.rustc` configuration variable in a `.cargo/config` file
|
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64 |
These commits add two vectors through which the compiler run can be configured:
RUSTCenvironment variablebuild.rustcconfiguration variable in a.cargo/configfile