Changelog History
Page 3
-
v0.3.5 Changes
January 21, 2017🛠 Fixed
- Relative paths in
dependencies.{}.path
were not being correctly handled.
- Relative paths in
-
v0.3.4 Changes
January 18, 2017➕ Added
- A
[dependencies.{}.stage]
(or[target.{}.dependencies.{}.stage]
) entry in Xargo.toml. This lets you build a sysroot in "stages". This is required, for instance, to build thetest
crate whose dependency on thestd
crate is not explicitly listed in its Cargo.toml. Example:
✅ To make
xargo test
work - A
-
v0.3.3 Changes
January 09, 2017➕ Added
- 👌 Support for building a custom sysroot when compiling natively.
- 👌 Support for specifying dependencies as
[dependencies]
in Xargo.toml.
-
v0.3.2 Changes
January 03, 2017🔄 Changed
XARGO_RUST_SRC
is now used when working with nightly Rust and it has precedence over therust-src
component.
-
v0.3.1 Changes
December 30, 2016➕ Added
- You can now specify the location where Xargo stores the sysroots via the
XARGO_HOME
environment variable. If unspecified, the sysroots will be stored in$HOME/.xargo
- You can now specify the location where Xargo stores the sysroots via the
-
v0.3.0 Changes
December 28, 2016🔄 Changed
0️⃣ [breaking-change] By default, Xargo now only compiles the
core
crate. To build more crates, use aXargo.toml
file🏗 [breaking-change] Xargo will now build a sysroot for any target that's not the host.
🖨 The verbose flag,
-v
, makes Xargo print all the shell commands it invokes to stderr.
-
v0.2.3 Changes
December 19, 2016➕ Added
- 👌 Support for the 'dev' channel. When using the dev channel, you must specify the path to the Rust source directory via the XARGO_RUST_SRC environment variable.
🔄 Changed
- The rust-src search logic to account for recent changes in the Rust distribution.
-
v0.2.2 Changes
December 12, 2016🔄 Changed
🏗 Xargo will now try to build every crate "below"
std
, i.e. all its dependencies, in topological order. This makes Xargo robust against changes in thestd
facade as it no longer depends on hard coded crate names likerustc_unicode
.Xargo won't rebuild the sysroot if the only thing that changed in Cargo.toml is profile.*.lto. Enabling/disabling LTO doesn't change how dependencies are compiled.
Xargo won't rebuild the sysroot if the linker flags (
-C link-arg
) have changed. Those don't affect how the dependencies are compiled.
-
v0.2.1 Changes
October 22, 2016🔄 Changed
- No weird
()
output inxargo -V
if Xargo was built viacargo install
- 👍 Better formatted error messages. Mention the RUST_BACKTRACE env variable which is used to get backtraces on errors.
- No weird
-
v0.2.0 Changes
October 16, 2016➕ Added
- 🚀 Statically linked binary releases for Linux (x86 musl targets)
xargo -V
output now includes the commit hash and date
🔄 Changed
- Xargo now depends on the
rust-src
component being installed. Install it withrustup component add rust-src
. - Xargo no longer depends on libcurl, libssh or libssl and, therefore, it's now much easier to build.
- Xargo now respects the existing rustdocflags (RUSTDOCFLAGS env var, build.rustdocflags, etc) when passing --sysroot to rustdoc.
- 🔒 File locking logic has been revised/simplied and now lock periods are shorter