Repository files navigation

Cargo downloads your Rust project’s dependencies and compiles your project.

To start using Cargo, learn more atThe Cargo Book.

To start developing Cargo itself, read theCargo Contributor Guide.

The Cargo binary distributed through with Rust is maintained by the Cargoteam for use by the wider ecosystem.For all other uses of this crate (as a binary or library) this is maintainedby the Cargo team, primarily for use by Cargo and not intended for externaluse (except as a transitive dependency). This crate may make major changes toits APIs.

Code documentation:https://doc.rust-lang.org/nightly/nightly-rustc/cargo/

Cargo requires the following tools and packages to build:

• cargo andrustc
• A C compilerfor your platform
• git (to clone this repository)

Other requirements:

The following are optional based on your platform and needs.

• pkg-config — This is used to help locate system packages, such aslibssl headers/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 thevendored-openssl Cargo feature is not used.

  This requires the development headers, which can be obtained from thelibssl-dev package on Ubuntu oropenssl-devel with apk or yum or theopenssl package from Homebrew on macOS.

  If using thevendored-openssl Cargo feature, then a static copy of OpenSSL will be built from source instead of using the system OpenSSL.This may require additional tools such asperl andmake.

  On macOS, common installation directories from Homebrew, MacPorts, or pkgsrc will be checked. Otherwise it will fall back topkg-config.

  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 withpkg-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.gitcd cargo

Withcargo already installed, you can simply run:

cargo build --release

Cargo is designed to be extensible with new subcommands without having to modifyCargo itself. Seethe Wiki page for more details anda list of known community-developed subcommands.

Cargo releases coincide with Rust releases.High level release notes are available as part ofRust's release notes.Detailed release notes are available in thechangelog.

Found a bug? We'd love to know about it!

Please report all issues on the GitHubissue tracker.

See theCargo Contributor Guide for a complete introductionto contributing to Cargo.

Cargo is primarily distributed under the terms of both the MIT licenseand the Apache License (Version 2.0).

SeeLICENSE-APACHE andLICENSE-MIT for details.

This product includes software developed by the OpenSSL Projectfor use in the OpenSSL Toolkit (https://www.openssl.org/).

In binary form, this product includes software that is licensed under theterms of the GNU General Public License, version 2, with a linking exception,which can be obtained from theupstream repository.

SeeLICENSE-THIRD-PARTY for details.