Use new kind= syntax for libs throughout Cargo
#1405
Conversation
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
| @@ -173,7 +173,7 @@ pub fn compile_targets<'a, 'b>(env: &str, | |||
|
|
|||
| for (&(ref pkg, _), output) in cx.build_state.outputs.lock().unwrap().iter() { | |||
| let any_dylib = output.library_links.iter().any(|l| { | |||
| !l.ends_with(":static") && !l.ends_with(":framework") | |||
| !l.ends_with("static=") && !l.ends_with("framework=") | |||
There was a problem hiding this comment.
Oh dear... that's only a little embarrasing
alexcrichton
force-pushed
the
issue-1401
branch
from
756f2f6 to
279c030
Compare
alexcrichton
force-pushed
the
issue-1401
branch
from
279c030 to
154efe4
Compare
|
☔ The latest upstream changes (presumably #1458) made this pull request unmergeable. Please resolve the merge conflicts. |
This should inadvertently fix rust-lang#1401
alexcrichton
force-pushed
the
issue-1401
branch
from
154efe4 to
7756fe6
Compare
This should inadvertently fix #1401
|
💔 Test failed - cargo-win-64 |
|
@bors: retry On Thu, Mar 26, 2015 at 2:53 PM, bors notifications@github.com wrote:
|
|
⚡ Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32 are reusable. Rebuilding only cargo-win-64... |
|
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64 |
This should inadvertently fix #1401