| commit | da60c8575e02ed54fcffcb7f2f9289b4705b60ff | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <[email protected]> | Thu Dec 19 14:56:55 2019 -0800 |
| committer | Chih-Hung Hsieh <[email protected]> | Thu Dec 19 14:56:55 2019 -0800 |
| tree | c6c259d93ff15ce0eab9bcbdc881cfb925aef20d | |
| parent | fd666f2f11b6b870cdfff85689e078cd371668e2 [diff] |
Importing rustc-1.37.0
This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.
Read “Installation” from The Book.
Note: If you wish to contribute to the compiler, you should read this chapter of the rustc-guide instead.
Make sure you have installed the dependencies:
g++ 4.7 or later or clang++ 3.x or laterpython 2.7 (but not 3.x)make 3.81 or latercmake 3.4.3 or latercurlgitClone the source with git:
$ git clone https://github.com/rust-lang/rust.git $ cd rust
Build and install:
$ ./x.py build && sudo ./x.py install
If after running sudo ./x.py install you see an error message like
error: failed to load source for a dependency on 'cc'
then run these two commands and then try sudo ./x.py install again:
$ cargo install cargo-vendor
$ cargo vendor
Note: Install locations can be adjusted by copying the config file from
./config.toml.exampleto./config.toml, and adjusting theprefixoption under[install]. Various other options, such as enabling debug information, are also supported, and are documented in the config file.
When complete, sudo ./x.py install will place several programs into /usr/local/bin: rustc, the Rust compiler, and rustdoc, the API-documentation tool. This install does not include Cargo, Rust's package manager, which you may also want to build.
There are two prominent ABIs in use on Windows: the native (MSVC) ABI used by Visual Studio, and the GNU ABI used by the GCC toolchain. Which version of Rust you need depends largely on what C/C++ libraries you want to interoperate with: for interop with software produced by Visual Studio use the MSVC build of Rust; for interop with GNU software built using the MinGW/MSYS2 toolchain use the GNU build.
MSYS2 can be used to easily build Rust on Windows:
Grab the latest MSYS2 installer and go through the installer.
Run mingw32_shell.bat or mingw64_shell.bat from wherever you installed MSYS2 (i.e. C:\msys64), depending on whether you want 32-bit or 64-bit Rust. (As of the latest version of MSYS2 you have to run msys2_shell.cmd -mingw32 or msys2_shell.cmd -mingw64 from the command line instead)
From this terminal, install the required tools:
# Update package mirrors (may be needed if you have a fresh install of MSYS2) $ pacman -Sy pacman-mirrors # 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, # or CMake installed and in PATH you can remove them from this list. Note # that it is important that you do **not** use the 'python2' and 'cmake' # packages from the 'msys2' subsystem. The build has historically been known # to fail with these packages. $ pacman -S git \ make \ diffutils \ tar \ mingw-w64-x86_64-python2 \ mingw-w64-x86_64-cmake \ mingw-w64-x86_64-gcc
Navigate to Rust's source code (or clone it), then build it:
$ ./x.py build && ./x.py install
MSVC builds of Rust additionally require an installation of Visual Studio 2017 (or later) so rustc can use its linker. The simplest way is to get the Visual Studio, check the “C++ build tools” and “Windows 10 SDK” workload.
(If you‘re installing cmake yourself, be careful that “C++ CMake tools for Windows” doesn’t get included under “Individual components”.)
With these dependencies installed, you can build the compiler in a cmd.exe shell with:
> python x.py build
Currently, building Rust only works with some known versions of Visual Studio. If you have a more recent version installed the build system doesn't understand then 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.
> CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build\vcvars64.bat" > python x.py build
Each specific ABI can also be used from either environment (for example, using the GNU ABI in PowerShell) by using an explicit build triple. The available Windows build triples are:
i686-pc-windows-gnux86_64-pc-windows-gnui686-pc-windows-msvcx86_64-pc-windows-msvcThe build triple can be specified by either specifying --build=<triple> when invoking x.py commands, or by copying the config.toml file (as described in Building From Source), and modifying the build option under the [build] section.
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 $ make && sudo make install
When using the configure script, the generated config.mk file may override the config.toml file. To go back to the config.toml file, delete the generated config.mk file.
If you’d like to build the documentation, it’s almost the same:
$ ./x.py doc
The generated documentation will appear under doc in the build directory for the ABI used. I.e., if the ABI was x86_64-pc-windows-msvc, the directory will be build\x86_64-pc-windows-msvc\doc.
Since the Rust compiler is written in Rust, it must be built by a precompiled “snapshot” version of itself (made in an earlier stage of development). As such, source builds require a connection to the Internet, to fetch snapshots, and an OS that can execute the available snapshot binaries.
Snapshot binaries are currently built and tested on several platforms:
| Platform / Architecture | x86 | x86_64 |
|---|---|---|
| Windows (7, 8, 10, ...) | ✓ | ✓ |
| Linux (2.6.18 or later) | ✓ | ✓ |
| OSX (10.7 Lion or later) | ✓ | ✓ |
You may find that other platforms work, but these are our officially supported build environments that are most likely to work.
There is more advice about hacking on Rust in CONTRIBUTING.md.
The Rust community congregates in a few places:
To contribute to Rust, please see CONTRIBUTING.
Rust has an IRC culture and most real-time collaboration happens in a variety of channels on Mozilla's IRC network, irc.mozilla.org. The most popular channel is #rust, a venue for general discussion about Rust. And a good place to ask for help would be #rust-beginners.
The rustc guide might be a good place to start if you want to find out how various parts of the compiler work.
Also, you may find the rustdocs for the compiler itself useful.
Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.
See LICENSE-APACHE, LICENSE-MIT, and COPYRIGHT for details.
The Rust programming language is an open source, community project governed by a core team. It is also sponsored by the Mozilla Foundation (“Mozilla”), which owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”).
If you want to use these names or brands, please read the media guide.
Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.