We should document the exact minimum versions of build tools required to build a given Rust toolchain
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
As noticed in https://github.com/rust-lang/rust/pull/128722#issuecomment-2297605573 when trying to bump cc to a version which drops support for VS 2013.
Also cc:
We also don't document minium versions of binutils etc on the platform support page. Maybe we should! But that's a pre-existing issue and bumping cc or not doesn't change that.
Originally posted by @ChrisDenton in https://github.com/rust-lang/rust/issues/129290#issuecomment-2298050637
INSTALL.md exists, but that seems more like some general advice for getting started, but not actual documented guarantees in terms of what kind of build environment is supported.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading INSTALL.md and the existing platform support page, then review the linked discussion about cc and VS 2013. Document the exact minimum supported versions of build tools for each relevant Rust toolchain or platform, clearly distinguishing guarantees from general setup advice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100