mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README.md: Remove prompts from code blocks

Browse Source
This commit is contained in:
qlcom 2020-09-18 21:08:48 +06:00 committed by GitHub
parent 2c69266c06
commit 18ce4c1cfc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -44,8 +44,8 @@ by running `./x.py --help` or reading the [rustc dev guide][rustcguidebuild].
2. Clone the [source] with `git`: 2. Clone the [source] with `git`:
```sh ```sh
$ git clone https://github.com/rust-lang/rust.git git clone https://github.com/rust-lang/rust.git
$ cd rust cd rust
``` ```
[source]: https://github.com/rust-lang/rust [source]: https://github.com/rust-lang/rust
@ -57,7 +57,7 @@ by running `./x.py --help` or reading the [rustc dev guide][rustcguidebuild].
Copy the default `config.toml.example` to `config.toml` to get started. Copy the default `config.toml.example` to `config.toml` to get started.
```sh ```sh
$ cp config.toml.example config.toml cp config.toml.example config.toml
``` ```
If you plan to use `x.py install` to create an installation, it is recommended 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].
4. Build and install: 4. Build and install:
```sh ```sh
$ ./x.py build && ./x.py install ./x.py build && ./x.py install
``` ```
When complete, `./x.py install` will place several programs into When complete, `./x.py install` will place several programs into
@ -106,7 +106,7 @@ build.
```sh ```sh
# Update package mirrors (may be needed if you have a fresh install of MSYS2) # Update package mirrors (may be needed if you have a fresh install of MSYS2)
$ pacman -Sy pacman-mirrors pacman -Sy pacman-mirrors
# Install build tools needed for Rust. If you're building a 32-bit compiler, # Install build tools needed for Rust. If you're building a 32-bit compiler,
# then replace "x86_64" below with "i686". If you've already got git, python, # then replace "x86_64" below with "i686". If you've already got git, python,
@ -114,7 +114,7 @@ build.
# that it is important that you do **not** use the 'python2', 'cmake' and 'ninja' # that it is important that you do **not** use the 'python2', 'cmake' and 'ninja'
# packages from the 'msys2' subsystem. The build has historically been known # packages from the 'msys2' subsystem. The build has historically been known
# to fail with these packages. # to fail with these packages.
$ pacman -S git \ pacman -S git \
make \ make \
diffutils \ diffutils \
tar \ tar \
@ -127,7 +127,7 @@ build.
4. Navigate to Rust's source code (or clone it), then build it: 4. Navigate to Rust's source code (or clone it), then build it:
```sh ```sh
$ ./x.py build && ./x.py install ./x.py build && ./x.py install
``` ```
#### MSVC #### MSVC
@ -145,7 +145,7 @@ With these dependencies installed, you can build the compiler in a `cmd.exe`
shell with: shell with:
```sh ```sh
> python x.py build python x.py build
``` ```
Currently, building Rust only works with some known versions of Visual Studio. If 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
by manually calling the appropriate vcvars file before running the bootstrap. by manually calling the appropriate vcvars file before running the bootstrap.
```batch ```batch
> CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat" CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvars64.bat"
> python x.py build python x.py build
``` ```
#### Specifying an ABI #### Specifying an ABI
@ -181,8 +181,8 @@ While it's not the recommended build system, this project also provides a
configure script and makefile (the latter of which just invokes `x.py`). configure script and makefile (the latter of which just invokes `x.py`).
```sh ```sh
$ ./configure ./configure
$ make && sudo make install make && sudo make install
``` ```
When using the configure script, the generated `config.mk` file may override the 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
If you’d like to build the documentation, it’s almost the same: If you’d like to build the documentation, it’s almost the same:
```sh ```sh
$ ./x.py doc ./x.py doc
``` ```
The generated documentation will appear under `doc` in the `build` directory for The generated documentation will appear under `doc` in the `build` directory for