nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-10-31 06:22:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
Empowering everyone to build reliable and efficient software.
47,681 Commits 7 Branches 139 Tags 1.9 GiB
Rust 96.2%
RenderScript 0.7%
Shell 0.6%
JavaScript 0.6%
Fluent 0.4%
Other 1.3%
71409184dc
Go to file
bors 71409184dc Auto merge of #29177 - vadimcn:rtstuff, r=alexcrichton 
Note: for now, this change only affects `-windows-gnu` builds.

So why was this `libgcc` dylib dependency needed in the first place?
The stack unwinder needs to know about locations of unwind tables of all the modules loaded in the current process.  The easiest portable way of achieving this is to have each module register itself with the unwinder when loaded into the process.  All modules compiled by GCC do this by calling the __register_frame_info() in their startup code (that's `crtbegin.o` and `crtend.o`, which are automatically linked into any gcc output).
Another important piece is that there should be only one copy of the unwinder (and thus unwind tables registry) in the process.  This pretty much means that the unwinder must be in a shared library (unless everything is statically linked). 

Now, Rust compiler tries very hard to make sure that any given Rust crate appears in the final output just once.   So if we link the unwinder statically to one of Rust's crates, everything should be fine.

Unfortunately, GCC startup objects are built under assumption that `libgcc` is the one true place for the unwind info registry, so I couldn't find any better way than to replace them.  So out go `crtbegin`/`crtend`, in come `rsbegin`/`rsend`!  

A side benefit of this change is that rustc is now more in control of the command line that goes to the linker, so we could stop using `gcc` as the linker driver and just invoke `ld` directly.
2015-11-01 17:15:29 +00:00
man rustc: Support output filenames for each emit type 2015-09-30 11:12:30 -07:00
mk Auto merge of #29177 - vadimcn:rtstuff, r=alexcrichton 2015-11-01 17:15:29 +00:00
src Auto merge of #29177 - vadimcn:rtstuff, r=alexcrichton 2015-11-01 17:15:29 +00:00
.gitattributes std: Remove msvc/valgrind headers 2015-07-27 16:21:15 -07:00
.gitignore Ignore KDevelop 4 (and 5 pre-release) project files 2015-06-25 23:26:05 +00:00
.gitmodules Use rust-installer for installation 2014-12-11 17:14:17 -08:00
.mailmap Update mailmap 2015-10-28 13:40:52 -07:00
.travis.yml Use Travis trusty infrastructure 2015-10-19 18:31:02 -04:00
AUTHORS.txt Update AUTHORS.txt for 1.5 2015-10-28 13:42:20 -07:00
COMPILER_TESTS.md Correct spelling in docs 2015-10-13 09:44:11 -04:00
configure Revert "Build compiler-rt/builtins with MSVC" 2015-10-30 10:36:38 -07:00
CONTRIBUTING.md docs: add rustdoc example to CONTRIBUTING.md 2015-10-03 03:42:28 +03:00
COPYRIGHT Remove references to removed Valgrind headers 2015-09-08 19:01:26 -04:00
LICENSE-APACHE Update license, add license boilerplate to most files. Remainder will follow. 2012-12-03 17:12:14 -08:00
LICENSE-MIT Bump LICENSE copyright year 2015-01-17 10:51:07 -05:00
Makefile.in Fixed an apparent typo 2015-09-19 08:10:54 -04:00
README.md Auto merge of #29229 - SingingTree:reflect_28260_in_readme, r=alexcrichton 2015-10-24 23:19:14 +00:00
RELEASES.md Add 1.3 release date 2015-09-18 09:19:20 +02:00

README.md

The Rust Programming Language

Rust is a fast systems programming language that guarantees memory safety and offers painless concurrency (no data races). It does not employ a garbage collector and has minimal runtime overhead.

This repo contains the code for the compiler (rustc), as well as standard libraries, tools and documentation for Rust.

Quick Start

Read "Installing Rust" from The Book.

Building from Source

  1. Make sure you have installed the dependencies:

    • g++ 4.7 or clang++ 3.x
    • python 2.6 or later (but not 3.x)
    • GNU make 3.81 or later
    • curl
    • git

  2. Clone the source with git:

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

  1. Build and install:

    $ ./configure
$ make && make install

    Note: You may need to use sudo make install if you do not normally have permission to modify the destination directory. The install locations can be adjusted by passing a --prefix argument to configure. Various other options are also supported – pass --help for more information on them.

    When complete, make 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.

Building on Windows

MSYS2 can be used to easily build Rust on Windows:

  1. Grab the latest MSYS2 installer and go through the installer.

  2. From the MSYS2 terminal, install the mingw64 toolchain and other required tools.

    # Update package mirrors (may be needed if you have a fresh install of MSYS2)
$ pacman -Sy pacman-mirrors

# Choose one based on platform:
$ pacman -S mingw-w64-i686-toolchain
$ pacman -S mingw-w64-x86_64-toolchain

# Make git available in MSYS2 (if not already available on path)
$ pacman -S git

$ pacman -S base-devel

  3. Run mingw32_shell.bat or mingw64_shell.bat from wherever you installed MSYS2 (i.e. C:\msys), depending on whether you want 32-bit or 64-bit Rust.

  4. Navigate to Rust's source code, configure and build it:

    $ ./configure
$ make && make install

Note: gcc versions >= 5 currently have issues building LLVM on Windows resulting in a segmentation fault when building Rust. In order to avoid this it may be necessary to obtain an earlier version of gcc such as 4.9.x. Installers for earlier Windows builds of gcc are available at the Mingw-Builds project. For more information on this see issue #28260.

Building Documentation

If you’d like to build the documentation, it’s almost the same:

./configure
$ make docs

Building the documentation requires building the compiler, so the above details will apply. Once you have the compiler built, you can

$ make docs NO_REBUILD=1

To make sure you don’t re-build the compiler because you made a change to some documentation.

The generated documentation will appear in a top-level doc directory, created by the make rule.

Notes

Since the Rust compiler is written in Rust, it must be built by a precompiled "snapshot" version of itself (made in an earlier state 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, Server 2008 R2) ✓ ✓
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.

Rust currently needs about 1.5 GiB of RAM to build without swapping; if it hits swap, it will take a very long time to build.

There is more advice about hacking on Rust in CONTRIBUTING.md.

Getting Help

The Rust community congregates in a few places:

Contributing

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.

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.