Remove lingering unstable flag `-Zfeatures` From [Zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/.E2.9C.94.20-Zfeatures): > Eric Huss: When trying to validate that the feature resolver resolves features in the same way as the dependency resolver. I think it is identical, but there are a lot of complex use cases and flags that aren't covered in the testsuite so I'm not entirely confident. If we ever come across a scenario where it isn't the same, the compare option can be useful to see what differs. In the future we could pick
|6 days ago|
|.github||2 weeks ago|
|crates||2 weeks ago|
|src||6 days ago|
|tests||1 week ago|
|CHANGELOG.md||2 weeks ago|
|Cargo.toml||7 days ago|
Cargo downloads your Rust project’s dependencies and compiles your project.
To start using Cargo, learn more at The Cargo Book.
To start developing Cargo itself, read the Cargo Contributor Guide.
Code documentation: https://docs.rs/cargo/
Cargo is distributed by default with Rust, so if you've got
locally you probably also have
cargo installed locally.
Compiling from Source
Cargo requires the following tools and packages to build:
- A C compiler for your platform
git(to clone this repository)
The following are optional based on your platform and needs.
pkg-config— This is used to help locate system packages, such as
libsslheaders/libraries. This may not be required in all cases, such as using vendored OpenSSL, or on Windows.
OpenSSL — Only needed on Unix-like systems and only if the
vendored-opensslCargo feature is not used.
This requires the development headers, which can be obtained from the
libssl-devpackage on Ubuntu or
openssl-develwith apk or yum or the
opensslpackage from Homebrew on macOS.
If using the
vendored-opensslCargo feature, then a static copy of OpenSSL will be built from source instead of using the system OpenSSL. This may require additional tools such as
On macOS, common installation directories from Homebrew, MacPorts, or pkgsrc will be checked. Otherwise it will fall back to
On Windows, the system-provided Schannel will be used instead.
LibreSSL is also supported.
Optional system libraries:
The build will automatically use vendored versions of the following libraries. However, if they are provided by the system and can be found with
pkg-config, then the system libraries will be used instead:
libcurl— Used for network transfers.
libgit2— Used for fetching git dependencies.
libssh2— Used for SSH access to git repositories.
libz(aka zlib) — Used for data compression.
It is recommended to use the vendored versions as they are the versions that are tested to work with Cargo.
First, you'll want to check out this repository
git clone https://github.com/rust-lang/cargo cd cargo
cargo already installed, you can simply run:
cargo build --release
Adding new subcommands to Cargo
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.
Found a bug? We'd love to know about it!
Please report all issues on the GitHub issue tracker.
See the Cargo Contributor Guide for a complete introduction to contributing to Cargo.
Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
Third party software
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://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.
See LICENSE-THIRD-PARTY for details.