| commit | e4162389d67c603d25ba6e25b0e9423fcb8daa64 | [log] [tgz] |
|---|---|---|
| author | Ed Page <eopage@gmail.com> | Wed Jul 02 19:44:20 2025 +0000 |
| committer | GitHub <noreply@github.com> | Wed Jul 02 19:44:20 2025 +0000 |
| tree | 45f15d0a03e4eed8a63432f0fed53ef0b26567f9 | |
| parent | eba6d5b03275dcdec6f20b763aa116d6eaee7355 [diff] | |
| parent | e4a616b6fde9866f57a00444928b2392fc921933 [diff] |
implement package feature unification (#15684) ### What does this PR try to resolve? Implements another part of feature unification (#14774, [rfc](https://github.com/rust-lang/rfcs/blob/1c590ce05d676e72e2217845ee054758d3a6df34/text/3692-feature-unification.md)). The `workspace` option was implemented in #15157, this adds the `package` option. ### How to test and review this PR? The important change is changing `WorkspaceResolve` so it can contain multiple `ResolvedFeature`s. Along with that, it also needs to know which specs those features are resolved for. This was used in several other places: - `cargo fix --edition` (from 2018 to 2021) - I think it should be ok to disallow using `cargo fix --edition` when someone already uses this feature. - building std - it should be safe to assume std is not using this feature so I just unwrap there. I'm not sure if some attempt to later feature unification would be better. - `cargo tree` - I just use the first feature set. This is definitely not ideal, but I'm not entirely sure what's the correct solution here. Printing multiple trees? Disallowing this, forcing users to select only one package? Based on comments in #15157 I've added tests first with `selected` feature unification and then changed that after implementation. I'm not sure if that's how you expect the tests to be added first, if not, I can change the history. I've expanded the test checking that this is ignored for `cargo install` although it should work the same way even if it is not ignored (`selected` and `package` are the same thing when just one package is selected).
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.
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.
Code documentation: https://doc.rust-lang.org/nightly/nightly-rustc/cargo/
Cargo requires the following tools and packages to build:
cargo and rustcgit (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 as libssl 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 the vendored-openssl Cargo feature is not used.
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.
On macOS, common installation directories from Homebrew, MacPorts, or pkgsrc will be checked. Otherwise it will fall back to pkg-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 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.
First, you'll want to check out this repository
git clone https://github.com/rust-lang/cargo.git cd cargo
With cargo already installed, you can simply run:
cargo build --release
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.
Cargo releases coincide with Rust releases. High level release notes are available as part of Rust's release notes. Detailed release notes are available in the changelog.
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).
See LICENSE-APACHE and LICENSE-MIT for details.
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.