| commit | f1c0d44ff0150591e7cedf37ef3d550c3872d408 | [log] [tgz] |
|---|---|---|
| author | Zack M. Davis <code@zackmdavis.net> | Tue Jan 31 20:51:24 2017 -0800 |
| committer | Alex Crichton <alex@alexcrichton.com> | Fri Mar 03 11:21:09 2017 -0800 |
| tree | a2fd03b9c59d0cbacc2bbe247d345a7666f0c1ea | |
| parent | d8fe364e535c48cd3327156d70fa7ada2f781163 [diff] |
make build tests not depend on minutiæ of rustc output This little patch arises from the maelstrom of my purity born of pain. It's the pain of seeing rust-lang/rust#38103 in its perfect crystalline beauty waste away on page four of https://github.com/rust-lang/rust/pulls, waiting, ready, itching to land, dying with anticipation to bring the light of clearer lint group error messages to Rust users of all creeds and nations, only for its promise to be cruelly blocked by the fateful, hateful hand of circular dependency. For it is written in src/tools/cargotest/main.rs that the Cargo tests must pass before the PR can receive Appveyor's blessing, but the Cargo tests could not pass (because they depend on fine details of the output that the PR is meant to change), and the Cargo tests could not be changed (because updating the test expectation to match the proposed new compiler output, would fail with the current compiler). The Gordian knot is cut in the bowels of cargotest's very notion of comparison (of JSON objects) itself, by means of introducing a magic string literal `"{...}"`, which can server as a wildcard for any JSON sub-object. And so it will be for the children, and the children's children, and unto the 1.17.0 and 1.18.0 releases, that Cargo's build test expectations will faithfully expect the exact JSON output by Cargo itself, but the string literal `"{...}"` shall be a token upon the JSON output by rustc, and when I see `"{...}"`, I will pass over you, and the failure shall not be upon you. And this day shall be unto you for a memorial.
Cargo downloads your Rust project’s dependencies and compiles your project.
Learn more at http://doc.crates.io/
Cargo is distributed by default with Rust, so if you've got rustc installed locally you probably also have cargo installed locally.
Cargo requires the following tools and packages to build:
pythoncurl (on Unix)cmakelibssl-dev package on ubuntu)cargo and rustcFirst, you'll want to check out this repository
git clone --recursive https://github.com/rust-lang/cargo cd cargo
With cargo already installed, you can simply run:
cargo build --release
Otherwise, you can also use a more traditional approach:
./configure make make install
More options can be discovered through ./configure, such as compiling cargo for more than one target. For example, if you'd like to compile both 32 and 64 bit versions of cargo on unix you would use:
$ ./configure --target=i686-unknown-linux-gnu,x86_64-unknown-linux-gnu
To run cargo's tests, use cargo test. If you do not have the cross-compilers installed locally, ignore the cross-compile test failures, or disable them by using CFG_DISABLE_CROSS_TESTS=1 cargo test.
Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See the Wiki page for more details and a list of known community-developed subcommands.
To contribute to the docs, all you need to do is change the markdown files in the src/doc directory. To view the rendered version of changes you have made locally, run:
./configure make doc open target/doc/index.html
High level release notes are available as part of Rust's release notes. Cargo releases coincide with Rust releases.
| Rust version | Cargo version |
|---|---|
| 1.12.0 | 0.13.0 |
| 1.11.0 | 0.12.0 |
| 1.10.0 | 0.11.0 |
| 1.9.0 | 0.10.0 |
| 1.8.0 | 0.9.0 |
| 1.7.0 | 0.8.0 |
| 1.6.0 | 0.7.0 |
| 1.5.0 | 0.6.0 |
| 1.4.0 | 0.5.0 |
| 1.3.0 | 0.4.0 |
| 1.2.0 | 0.3.0 |
| 1.1.0 | 0.2.0 |
| 1.0.0 | 0.1.0 |
Found a bug? We'd love to know about it!
Please report all issues on the github issue tracker.
Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
In binary form, this product includes software that is licensed under the terms of the GNU General Public License, version 2, with a linking exception, which can be obtained from the upstream repository.