Skip to content

Commit 18ce4c1

Browse files
author
qlcom
authored
README.md: Remove prompts from code blocks
1 parent 2c69266 commit 18ce4c1

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

README.md

+13-13
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,8 @@ by running `./x.py --help` or reading the [rustc dev guide][rustcguidebuild].
4444
2. Clone the [source] with `git`:
4545

4646
```sh
47-
$ git clone https://github.com/rust-lang/rust.git
48-
$ cd rust
47+
git clone https://github.com/rust-lang/rust.git
48+
cd rust
4949
```
5050

5151
[source]: https://github.com/rust-lang/rust
@@ -57,7 +57,7 @@ by running `./x.py --help` or reading the [rustc dev guide][rustcguidebuild].
5757
Copy the default `config.toml.example` to `config.toml` to get started.
5858

5959
```sh
60-
$ cp config.toml.example config.toml
60+
cp config.toml.example config.toml
6161
```
6262

6363
If you plan to use `x.py install` to create an installation, it is recommended
@@ -68,7 +68,7 @@ by running `./x.py --help` or reading the [rustc dev guide][rustcguidebuild].
6868
4. Build and install:
6969

7070
```sh
71-
$ ./x.py build && ./x.py install
71+
./x.py build && ./x.py install
7272
```
7373

7474
When complete, `./x.py install` will place several programs into
@@ -106,15 +106,15 @@ build.
106106
107107
```sh
108108
# Update package mirrors (may be needed if you have a fresh install of MSYS2)
109-
$ pacman -Sy pacman-mirrors
109+
pacman -Sy pacman-mirrors
110110
111111
# Install build tools needed for Rust. If you're building a 32-bit compiler,
112112
# then replace "x86_64" below with "i686". If you've already got git, python,
113113
# or CMake installed and in PATH you can remove them from this list. Note
114114
# that it is important that you do **not** use the 'python2', 'cmake' and 'ninja'
115115
# packages from the 'msys2' subsystem. The build has historically been known
116116
# to fail with these packages.
117-
$ pacman -S git \
117+
pacman -S git \
118118
make \
119119
diffutils \
120120
tar \
@@ -127,7 +127,7 @@ build.
127127
4. Navigate to Rust's source code (or clone it), then build it:
128128
129129
```sh
130-
$ ./x.py build && ./x.py install
130+
./x.py build && ./x.py install
131131
```
132132
133133
#### MSVC
@@ -145,7 +145,7 @@ With these dependencies installed, you can build the compiler in a `cmd.exe`
145145
shell with:
146146
147147
```sh
148-
> python x.py build
148+
python x.py build
149149
```
150150
151151
Currently, building Rust only works with some known versions of Visual Studio. If
@@ -154,8 +154,8 @@ you may need to force rustbuild to use an older version. This can be done
154154
by manually calling the appropriate vcvars file before running the bootstrap.
155155
156156
```batch
157-
> CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat"
158-
> python x.py build
157+
CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat"
158+
python x.py build
159159
```
160160
161161
#### Specifying an ABI
@@ -181,8 +181,8 @@ While it's not the recommended build system, this project also provides a
181181
configure script and makefile (the latter of which just invokes `x.py`).
182182
183183
```sh
184-
$ ./configure
185-
$ make && sudo make install
184+
./configure
185+
make && sudo make install
186186
```
187187
188188
When using the configure script, the generated `config.mk` file may override the
@@ -194,7 +194,7 @@ When using the configure script, the generated `config.mk` file may override the
194194
If you’d like to build the documentation, it’s almost the same:
195195
196196
```sh
197-
$ ./x.py doc
197+
./x.py doc
198198
```
199199
200200
The generated documentation will appear under `doc` in the `build` directory for

0 commit comments

Comments
 (0)