-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve top-level docs #105465
Improve top-level docs #105465
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
|
||
* `g++` 5.1 or later or `clang++` 3.5 or later |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we probably have C/C++ dependencies somewhere in the compiler tree? At minimum, these are needed for any Rust compilation as we typically invoke the linker through cc, right? (Not sure about Windows, but I believe this is the case on Ubuntu at least).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need at least cc, but not a full C++ compiler. I can say that explicitly if you like, but I think most people assume they need at least a C compiler for most things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm. I guess I would probably not call that an implicit assumption we can make; I think we should say it. Folks coming from languages like Node or Python might not realize that they need extra compilers to work on std, for example.
(And long-term I think we should try to remove this system dependency, e.g., by including clang in our artifacts. But that's a very separate conversation).
r=me with last comment resolved and commits squashed (at least a bit) |
The other places are more accurate and up-to-date. - Link to `std-dev-guide` in CONTRIBUTING.md Thom and Mara said the guide is in reasonably good shape, and it's tailored more closely to people working on the standard library. - Link to CONTRIBUTING.md instead of rustc-dev-guide in the main readme CONTRIBUTING.md has more information and also links the std-dev-guide. - Link to forge for the list of tested platforms; the one in the readme was hopelessly out of date.
The goal is to remove this altogether from the dev-guide once this PR is merged.
This sets several useful defaults, like `extended = true`, and gives us a path forward for changing global defaults without breaking distros.
@bors r=Mark-Simulacrum rollup |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#105465 (Improve top-level docs) - rust-lang#105872 (Suggest remove last method call when type coerce with expected type) - rust-lang#106032 (std: only use LFS function on glibc) - rust-lang#106078 (Provide more context on FileCheck failures) - rust-lang#106100 (Codegen test for derived `<` on trivial newtype [TEST ONLY]) - rust-lang#106109 (rustdoc: make line number CSS for doc comment and scraped the same) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
See a detailed explanation in the commit messages. This is a companion PR to rust-lang/rustc-dev-guide#1528.
config.mk
profile = "user"
in the READMEstd-dev-guide
in CONTRIBUTING.md