Cargo

The Cargo binary distributed through with Rust is maintained by the Cargo team for use by the wider ecosystem. For all other uses of this crate (as a binary or library) this is maintained by the Cargo team, primarily for use by Cargo and not intended for external use (except as a transitive dependency). This crate may make major changes to its APIs. This requires the development headers, which can be obtained from the libssl-dev package on Ubuntu or openssl-devel with apk or yum or the openssl package from Homebrew on macOS. If using the vendored-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 as perl and make . 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 by the above C libraries for data compression. (Rust code uses zlib-rs instead.) It is recommended to use the vendored versions as they are the versions that are tested to work with Cargo. Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See [the Wiki page][third-party-subcommands] for more details and a list of known community-developed subcommands. Cargo releases coincide with Rust releases. High level release notes are available as part of [Rust's release notes][rel]. Detailed release notes are available in the [changelog]. See the [Cargo Contributor Guide] for a complete introduction to contributing to Cargo.