You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-12
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Read ["Installation"] from [The Book].
22
22
## Installing from Source
23
23
24
24
The Rust build system uses a Python script called `x.py` to build the compiler,
25
-
which manages the bootstrapping process. It lives in the root of the project.
25
+
which manages the bootstrapping process. It lives at the root of the project.
26
26
27
27
The `x.py` command can be run directly on most systems in the following format:
28
28
@@ -32,7 +32,7 @@ The `x.py` command can be run directly on most systems in the following format:
32
32
33
33
This is how the documentation and examples assume you are running `x.py`.
34
34
35
-
Systems such as Ubuntu 20.04 LTS do not create the necessary `python` command by default when Python is installed that allows `x.py` to be run directly. In that case you can either create a symlink for `python` (Ubuntu provides the `python-is-python3` package for this), or run `x.py` using Python itself:
35
+
Systems such as Ubuntu 20.04 LTS do not create the necessary `python` command by default when Python is installed that allows `x.py` to be run directly. In that case, you can either create a symlink for `python` (Ubuntu provides the `python-is-python3` package for this), or run `x.py` using Python itself:
36
36
37
37
```sh
38
38
# Python 3
@@ -103,22 +103,21 @@ by running it with the `--help` flag or reading the [rustc dev guide][rustcguide
103
103
### Building on Windows
104
104
105
105
There are two prominent ABIs in use on Windows: the native (MSVC) ABI used by
106
-
Visual Studio, and the GNU ABI used by the GCC toolchain. Which version of Rust
107
-
you need depends largely on what C/C++ libraries you want to interoperate with:
108
-
for interop with software produced by Visual Studio use the MSVC build of Rust;
109
-
for interop with GNU software built using the MinGW/MSYS2 toolchain use the GNU
110
-
build.
106
+
Visual Studio and the GNU ABI used by the GCC toolchain. Which version of Rust
107
+
you need depends largely on what C/C++ libraries you want to interoperate with.
108
+
Use the MSVC build of Rust to interop with software produced by Visual Studio and
109
+
the GNU build to interop with GNU software built using the MinGW/MSYS2 toolchain.
111
110
112
111
#### MinGW
113
112
114
113
[MSYS2][msys2] can be used to easily build Rust on Windows:
115
114
116
115
[msys2]: https://www.msys2.org/
117
116
118
-
1. Grab the latest [MSYS2 installer][msys2] and go through the installer.
117
+
1. Download the latest [MSYS2 installer][msys2] and go through the installer.
119
118
120
-
2. Run `mingw32_shell.bat` or `mingw64_shell.bat` from wherever you installed
121
-
MSYS2 (i.e. `C:\msys64`), depending on whether you want 32-bit or 64-bit
119
+
2. Run `mingw32_shell.bat` or `mingw64_shell.bat` from the MSYS2 installation
120
+
directory (e.g. `C:\msys64`), depending on whether you want 32-bit or 64-bit
122
121
Rust. (As of the latest version of MSYS2 you have to run `msys2_shell.cmd
123
122
-mingw32` or `msys2_shell.cmd -mingw64` from the command line instead)
124
123
@@ -168,7 +167,7 @@ shell with:
168
167
python x.py build
169
168
```
170
169
171
-
Currently, building Rust only works with some known versions of Visual Studio. If
170
+
Right now, building Rust only works with some known versions of Visual Studio. If
172
171
you have a more recent version installed and the build system doesn't understand,
173
172
you may need to force rustbuild to use an older version. This can be done
174
173
by manually calling the appropriate vcvars file before running the bootstrap.
@@ -225,7 +224,7 @@ the ABI used. I.e., if the ABI was `x86_64-pc-windows-msvc`, the directory will
225
224
226
225
Since the Rust compiler is written in Rust, it must be built by a
227
226
precompiled "snapshot" version of itself (made in an earlier stage of
228
-
development). As such, source builds require a connection to the Internet, to
227
+
development). As such, source builds require an Internet connection to
229
228
fetch snapshots, and an OS that can execute the available snapshot binaries.
230
229
231
230
Snapshot binaries are currently built and tested on several platforms:
0 commit comments