| Age | Commit message (Collapse) | Author | Lines |
|---|
|
In other words, enforce what was documented in #30626 (and also stop blaming it on LLVM, we have at least one Python script of our own).
Also, there is no Python later than 2.7 and there never will be.
|
|
|
|
▲
▲ ▲
|
|
Fixes #30618
|
|
Fixes #29649
|
|
Fixes #30618
|
|
Running `/usr/bin/time -v make` to build rust (using local llvm) shows the maximum memory usage at 715 megabytes on 32-bit x86 (on arm linux it's even less @ 580M).
Reworded according to @brson's input.
|
|
|
|
|
|
|
|
This PR adds a note to the end of the Windows build instructions to reflect the issues detailed in #28260, as well as a work around using older versions of gcc. I've avoided going into detail as I did not wish to bloat the README, and so that the changes are easy to yank once the issue is resolved.
|
|
|
|
|
|
|
|
Remove leading newlines; replace lines containing only whitespace with empty lines; replace multiple trailing newlines with a single newline; remove trailing whitespace in lines
|
|
|
|
Use suggested composite command instead of 2 separate commands.
|
|
Folded in suggestion from @brson to simply put the mirror update step in the regular set of tool chain install commands.
|
|
Encountered an issue going through the guide for installing the `mingw` toolchain on Windows with msys2, after some googling I found the [solution](https://github.com/Alexpux/MSYS2-packages/issues/163#issuecomment-73555971) and thought it would be good to update the README so people don't get frustrated. :)
|
|
Fixes #27632
|
|
Also fixes a few outdated links.
|
|
|
|
|
|
|
|
|
|
Tries to make the introductory portion of the README flow better.
|
|
|
|
|
|
A minor change to avoid making the reader think 'where is this'.
|
|
- Various grammatical changes.
- Use triple-backtick syntax and sh highlighting for code blocks.
- Fix indentation of code block in step 2 of "Building on Windows".
- Use title case for "Getting Help" subheading.
|
|
|
|
|
|
|
|
Most people don't know what Rust is.
|
|
|
|
The page we want them to find is 'getting started developing'.
|
|
Just a hint.
|
|
I believe that few enough people build from source tarballs that
we don't have to talk about it explicitly.
|
|
This redux of CONTRIBUTING.md adds in more information, including
subsuming both compliment-bugreport.md and Note-development-policy
in the wiki.
I only glanced at the broad TOC of Note-development-policy, and did
not use the text as the basis for the re-write. This will then address
the last outstanding part of #5831.
|
|
The quick start already links to the book. I think its not necessary
to do in the build instructions.
|
|
|
|
|
|
|
|
|
|
|
|
There's only one build-critical path in which perl is used, and it was to do a text replacement trivially achievable with sed(1).
I ported the indenter script because it [appears to be used][indenter], but removed check links because it appears to be entirely out of date.
[indenter]: https://github.com/rust-lang/rust/blob/master/src/librustc/util/common.rs#L60-70
|
|
|
|
|
|
This is much more helpful.
|
|
This pulls all of our long-form documentation into a single document,
nicknamed "the book" and formally titled "The Rust Programming
Language."
A few things motivated this change:
* People knew of The Guide, but not the individual Guides. This merges
them together, helping discoverability.
* You can get all of Rust's longform documentation in one place, which
is nice.
* We now have rustbook in-tree, which can generate this kind of
documentation. While its style is basic, the general idea is much
better: a table of contents on the left-hand side.
* Rather than a almost 10,000-line guide.md, there are now smaller files
per section.
|
