| tag | 1afe04bce500614e29ae4c837206a6bcb1c95eb1 | |
|---|---|---|
| tagger | Brian Anderson <banderson@mozilla.com> | Thu Jul 07 10:21:26 2016 -0700 |
| object | 259324cd8f9bb6e1068a3a2b77685e90fda3e3b6 |
0.11.0 release
| commit | 259324cd8f9bb6e1068a3a2b77685e90fda3e3b6 | [log] [tgz] |
|---|---|---|
| author | bors <bors@rust-lang.org> | Fri May 20 18:52:38 2016 -0700 |
| committer | bors <bors@rust-lang.org> | Fri May 20 18:52:38 2016 -0700 |
| tree | 9b54efec2f72141f69055d2c1d84c1de1fb2f865 | |
| parent | f13ca72e52de666e6bb326d6894eb7337258360b [diff] | |
| parent | 75848a2a6972a3de95dd8d0a52ff2cf0443adad7 [diff] |
Auto merge of #2687 - alexcrichton:panic-abort, r=wycats Implement the `panic` profile option This is the Cargo half of the implementation of [RFC 1513] which adds a new `profile.*.panic` option to customize the `-C panic` argument to the compiler. This is not passed by default and can otherwise be specified as `abort` or `unwind` on the nightly compiler. [RFC 1513]: https://github.com/rust-lang/rfcs/pull/1513 The `profile.*.panic` option is *only* used from the top-level crate, not each crate individually. This means that applications should customize this value as they see fit, and libraries will only use their own value when they're being tested. Cargo also has specific knowledge that when *testing* a crate it can't pass `-C panic=abort` for now as the default test harness requires `panic=unwind`. This essentially just means that `cargo test` will continue to work for crates that specify `panic=abort` in Cargo.toml.
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.
If, however, you would like to install Cargo from the nightly binaries that are generated, you may also do so! Note that these nightlies are not official binaries, so they are only provided in one format with one installation method. Each tarball below contains a top-level install.sh script to install Cargo.
x86_64-unknown-linux-gnui686-unknown-linux-gnux86_64-apple-darwini686-apple-darwinx86_64-pc-windows-gnui686-pc-windows-gnux86_64-pc-windows-msvcNote that if you're on Windows you will have to run the install.sh script from inside an MSYS shell, likely from a MinGW-64 installation.
Cargo requires the following tools and packages to build:
pythoncurl (on Unix)cmakelibssl-dev package on ubuntu)First, you'll want to check out this repository
git clone --recursive https://github.com/rust-lang/cargo cd cargo
If you already have rustc and cargo installed elsewhere, you can simply run
cargo build --release
Otherwise, if you have rustc installed and not Cargo, you can simply run:
./configure make make install
If, however, you have neither rustc nor cargo previously installed you can run:
python -B src/etc/install-deps.py ./configure --local-rust-root="$PWD"/rustc make make install
Note: if building for 32 bit systems run BITS=32 python -B ..
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
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.
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.