Rust - Empowering everyone to build reliable and efficient software.

The Rust Programming Language

Last update: Dec 28, 2022

Related tags

Overview

The Rust Programming Language

This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.

Note: this README is for users rather than contributors. If you wish to contribute to the compiler, you should read the Getting Started section of the rustc-dev-guide instead. You can ask for help in the #new members Zulip stream.

Quick Start

Read "Installation" from The Book.

Installing from Source

The Rust build system uses a Python script called x.py to build the compiler, which manages the bootstrapping process. It lives in the root of the project.

The x.py command can be run directly on most systems in the following format:

./x.py <subcommand> [flags]

This is how the documentation and examples assume you are running x.py.

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:

# Python 3
python3 x.py <subcommand> [flags]

# Python 2.7
python2.7 x.py <subcommand> [flags]

More information about x.py can be found by running it with the --help flag or reading the rustc dev guide.

Building on a Unix-like system

Make sure you have installed the dependencies:
- g++ 5.1 or later or clang++ 3.5 or later
- python 3 or 2.7
- GNU make 3.81 or later
- cmake 3.13.4 or later
- ninja
- curl
- git
- ssl which comes in libssl-dev or openssl-devel
- pkg-config if you are compiling on Linux and targeting Linux

Clone the source with git:

git clone https://github.com/rust-lang/rust.git
cd rust

Configure the build settings:

The Rust build system uses a file named config.toml in the root of the source tree to determine various configuration settings for the build. Copy the default config.toml.example to config.toml to get started.
```
cp config.toml.example config.toml
```
If you plan to use x.py install to create an installation, it is recommended that you set the prefix value in the [install] section to a directory.

Create install directory if you are not installing in default directory
Build and install:
```
./x.py build && ./x.py install
```
When complete, ./x.py install will place several programs into $PREFIX/bin: rustc, the Rust compiler, and rustdoc, the API-documentation tool. This install does not include Cargo, Rust's package manager. To build and install Cargo, you may run ./x.py install cargo or set the build.extended key in config.toml to true to build and install all tools.

Building on Windows

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.

MinGW

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', 'cmake' and 'ninja'
# 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-python \
            mingw-w64-x86_64-cmake \
            mingw-w64-x86_64-gcc \
            mingw-w64-x86_64-ninja

Navigate to Rust's source code (or clone it), then build it:
```
./x.py build && ./x.py install
```

MSVC

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 and the build system doesn't understand, 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\Community\VC\Auxiliary\Build\vcvars64.bat"
python x.py build

Specifying an ABI

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:

GNU ABI (using GCC)
- i686-pc-windows-gnu
- x86_64-pc-windows-gnu
The MSVC ABI
- i686-pc-windows-msvc
- x86_64-pc-windows-msvc

The 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 Installing From Source), and modifying the build option under the [build] section.

Configure and Make

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.

Building Documentation

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.

Notes

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 (kernel 2.6.32, glibc 2.11 or later)	✓	✓
macOS (10.7 Lion or later)	(*)	✓

(*): Apple dropped support for running 32-bit binaries starting from macOS 10.15 and iOS 11. Due to this decision from Apple, the targets are no longer useful to our users. Please read our blog post for more info.

You may find that other platforms work, but these are our officially supported build environments that are most likely to work.

Getting Help

The Rust community congregates in a few places:

Stack Overflow - Direct questions about using the language.
users.rust-lang.org - General discussion and broader questions.
/r/rust - News and general discussion.

Contributing

If you are interested in contributing to the Rust project, please take a look at the Getting Started guide in the rustc-dev-guide.

License

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.

Trademark

The Rust Foundation 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.

Comments

How to promote a specific target from "Tier 2" to "Tier1"

Hi, Even though I've carefully read target tier policy and platform support docs, I still have something to ask. https://doc.rust-lang.org/nightly/rustc/platform-support.html https://doc.rust-lang.org/nightly/rustc/target-tier-policy.html

We are currently considering to adopt rust to our platform. (commercial use not only for developing test) But, our target is mainly based on "armv7-unknown-linux-gnueabihf" which is placed to "Tier2". According to the docs, I read that "Tier1 is guaranteed to work" and "Tier2 is guaranteed to build".

If we have a plan to release the target as a product, It means "armv7-unknown-linux-gnueabihf" is NOT GUARANTEED TO WORK at all (including a sub-compatibility)? That makes us to hesitate to adopt rust to our product....

If Tier2 CANNOT be guaranteed to work or sub-compatibility, we'd love to the target is being promoted to Tier1. Is it possible? Although I read the doc about "Target Tier Policy", the process of promoting to "Tier1" is a bit ambiguous to me. What kind of things are required for that? And where can I start suggesting or raising issue "armv7-unknown-linux-gnueabihf" to promote to Tier1?

Thanks in advance.

opened by prozanne 0
Back button doesn't work from error_codes/error-index.html

Was looking thought the doc.rust-lang.org site to see what was new and looked at the compiler error codes page. when trying to navigate back to the main site by pressing back it simply flashes "if you are not redirected please ..." and then immediately goes back to error_codes/error-index.html. Pretty easy to repro, can provide more detail if needed!

opened by matthagan15 0
Rollup of 6 pull requests
Successful merges:

#105846 (Account for return-position impl Trait in trait in opt_suggest_box_span)

#106385 (Split -Zchalk flag into -Ztrait-solver=(classic|chalk|next) flag)

#106403 (Rename hir::Map::{get_,find_}parent_node to hir::Map::{,opt_}parent_id, and add hir::Map::{get,find}_parent)

#106462 (rustdoc: remove unnecessary wrapper around sidebar and mobile logos)

#106464 (Update Fuchsia walkthrough with new configs)

#106478 (Tweak wording of fn call with wrong number of args)

Failed merges:

r? @ghost @rustbot modify labels: rollup

Create a similar rollup
A-testsuite T-rustdoc T-compiler S-waiting-on-bors rollup
opened by compiler-errors 3
Rename `glue` and refactor `push_tree`

Renamed the glue function to check_is_multiple_char_token and added some comments.

And I think the push_tree function could only check the !Self::try_glue_to_last condition, so I refactored it.

thanks
T-compiler S-waiting-on-review

opened by notJoon 1
C string literals can't just use a trivial conversion from regular string or byte literals

Initial comment

In the "Rationale and alternatives" section of RFC 3348, it mentions a hypothetical FromStringLiteral. While I like the idea, it couldn't be as simple as a From<&'static str>/TryFrom<&'static str>: error messages would need at least a character offset + string message to be more useful than just "hey, this string contains a problem character". Also, &CStrs are really more like byte string literals, and that offset would have to be a byte offset, not a char offset, too.

This probably could justify the existence of such a trait, though. C string literals in particular wouldn't push the boundaries much, but I could see other things like regular expressions benefitting a ton from it.

opened by dead-claudia 0