Prepare for ARM/FreeBSD/NetBSD nightlies #2510
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
|
Some of the makefile/script changes here as well were also done to support out-of-tree build directories (when I was playing around inside docker). The updates of crates were just done largely to add r? @brson |
alexcrichton
force-pushed
the
xcompile
branch
2 times, most recently
from
b11e724
to
005de35
Compare
|
cc @japaric |
alexcrichton
force-pushed
the
xcompile
branch
2 times, most recently
from
f87379a
to
d363095
Compare
|
@bors r+ fuck makefiles |
|
📌 Commit d363095 has been approved by |
This commit beefs up Cargo's makefiles to support nightly builds of Cargo for multiple platforms. This primarily involves vendoring the logic of how to build OpenSSL for statically linking against Cargo into the Makefiles directly. We'll have to update the version of OpenSSL as releases are made, but we essentially already do that with the normal docker container. The Linux nightlies will still run in the normal dist docker container (a really old CentOS build) and builds for new platforms will happen in the standard linux-cross container we use for other cross builds. The nightly versions of these will produce Cargo tarballs for a whole bunch of platforms to get uploaded. This has been tested in the `alexcrichton/rust-slave-linux-cross:2016-03-17b` docker container for the 3 ARM targets and FreeBSD target. NetBSD will come once rust-lang/rust#32407 lands.
bors
added a commit
that referenced
this pull request
Mar 23, 2016
Prepare for ARM/FreeBSD/NetBSD nightlies This commit beefs up Cargo's makefiles to support nightly builds of Cargo for multiple platforms. This primarily involves vendoring the logic of how to build OpenSSL for statically linking against Cargo into the Makefiles directly. We'll have to update the version of OpenSSL as releases are made, but we essentially already do that with the normal docker container. The Linux nightlies will still run in the normal dist docker container (a really old CentOS build) and builds for new platforms will happen in the standard linux-cross container we use for other cross builds. The nightly versions of these will produce Cargo tarballs for a whole bunch of platforms to get uploaded. This has been tested in the `alexcrichton/rust-slave-linux-cross:2016-03-17b` docker container for the 3 ARM targets and FreeBSD target. NetBSD will come once rust-lang/rust#32407 lands.
|
☀️ Test successful - 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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit beefs up Cargo's makefiles to support nightly builds of Cargo for
multiple platforms. This primarily involves vendoring the logic of how to build
OpenSSL for statically linking against Cargo into the Makefiles directly. We'll
have to update the version of OpenSSL as releases are made, but we essentially
already do that with the normal docker container.
The Linux nightlies will still run in the normal dist docker container (a really
old CentOS build) and builds for new platforms will happen in the standard
linux-cross container we use for other cross builds. The nightly versions of
these will produce Cargo tarballs for a whole bunch of platforms to get
uploaded.
This has been tested in the
alexcrichton/rust-slave-linux-cross:2016-03-17bdocker container for the 3 ARM targets and FreeBSD target. NetBSD will come once
rust-lang/rust#32407 lands.