rust
/
cargo
mirror of https://github.com/rust-lang/cargo
0
0
Fork 0
Code Issues Releases Wiki Activity
17,393 Commits 75 Branches 97 Tags 85 MiB
Rust 95.2%
Roff 4.4%
JavaScript 0.2%
Shell 0.1%
Go to file
bors 82dca28700 Auto merge of #13791 - epage:msrv-unset, r=Eh2406 
fix(resolver): Treat unset MSRV as compatible

### What does this PR try to resolve?

Have the resolver treat no-MSRV as `rust-version = "*"`, like `cargo add` does for version-requirement selection

### How should we test and review this PR?

We last tweaked this logic in #13066.
However, we noticed this was inconsistent with `cargo add` in automatically selecting version requirements.

It looks like this is a revert of #13066, taking us back to the behavior in #12950.
In #12950 there was a concern about the proliferation of no-MSRV and whether we should de-prioritize those to make the chance of success more likely.

There are no right answes here, only which wrong answer is ok enough.
- Do we treat lack of rust version as `rust-version = "*"` as some people expect or do we try to be smart?
- If a user adds or removes `rust-version`, how should that affect the priority?

One piece of new information is that the RFC for this has us trying to fill the no-MSRV gap with
`rust-version = some-value-representing-the-current-toolchain>`.

See also https://github.com/rust-lang/cargo/issues/9930#issuecomment-1977471059

r? `@Eh2406`

### Additional information
 		2024-05-01 16:56:30 +00:00
.cargo test: Ensure snapbox works until CARGO_RUSTC_CURRENT_DIR is stabilized 2024-02-16 10:27:48 -06:00
.github chore: tell renovatebot to not touch openssl (temporarily) 2024-04-10 09:29:03 -04:00
benches chore: Rename `Config` to `GlobalContext` 2024-02-20 11:55:15 -07:00
ci ci: big ⚠️ to ensure the CNAME file is always there 2023-10-18 21:31:10 -04:00
crates fix(toml): Warn, rather than fail publish, if build.rs is excluded 2024-04-29 12:25:19 -05:00
credential cargo-credential: bump version to 0.4.5 2024-04-20 10:38:49 +03:00
src Auto merge of #13791 - epage:msrv-unset, r=Eh2406 2024-05-01 16:56:30 +00:00
tests Auto merge of #13805 - Muscraft:im-a-teapot-lint-unstable, r=epage 2024-05-01 13:59:51 +00:00
.gitignore Fix target entry in .gitignore 2024-04-29 07:39:04 +10:00
.ignore
…
CHANGELOG.md docs(changelog): typo fixes 2024-04-29 23:05:41 -04:00
CODE_OF_CONDUCT.md
…
CONTRIBUTING.md docs: remove review capacity notice 2023-10-18 13:24:09 -04:00
Cargo.lock chore(deps): update compatible 2024-05-01 15:09:07 +00:00
Cargo.toml chore(deps): update compatible 2024-05-01 15:09:07 +00:00
LICENSE-APACHE
…
LICENSE-MIT
…
LICENSE-THIRD-PARTY
…
README.md doc: point to nightly cargo doc 2023-06-07 10:13:05 +01:00
build.rs add support for reading git-commit-info 2024-04-30 10:44:27 +02:00
clippy.toml chore: Communicate motivation for AtomucU64 2023-11-16 12:34:02 -06:00
deny.toml Fix some typos 2023-09-24 23:10:07 +08:00
publish.py Chore(publish.py): Add cargo-test-* to publication list 2024-03-26 11:17:34 +01:00
triagebot.toml refactor(schema): Make manifest its own directory 2024-03-04 16:44:05 -06:00
windows.manifest.xml Add a windows manifest file 2023-12-07 14:24:58 +00:00

README.md

Cargo

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 Status

CI

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

Installing Cargo

Cargo is distributed by default with Rust, so if you've got rustc installed locally you probably also have cargo installed locally.

Compiling from Source

Requirements

Cargo requires the following tools and packages to build:

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 for data compression.

It is recommended to use the vendored versions as they are the versions that are tested to work with Cargo.

Compiling

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

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.

Releases

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 this repo at CHANGELOG.md.

Reporting issues

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

Please report all issues on the GitHub issue tracker.

Contributing

See the Cargo Contributor Guide for a complete introduction to contributing to Cargo.

License

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.

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.