OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
51,990 Commits 1 Branch 0 Tags 636 MiB
Rust 97.9%
Python 0.5%
JavaScript 0.4%
C++ 0.3%
Shell 0.3%
Other 0.4%
9c462b84c8
Go to file
Alex Crichton 9c462b84c8 std: Fix linking against signal on Android 
Currently the minimum supported Android version of the standard library is
API level 18 (android-18). Back in those days [1] the `signal` function was
just an inline wrapper around `bsd_signal`, but starting in API level
android-20 the `signal` symbols was introduced [2]. Finally, in android-21
the API `bsd_signal` was removed [3].

Basically this means that if we want to be binary compatible with multiple
Android releases (oldest being 18 and newest being 21) then we need to check
for both symbols and not actually link against either.

This was first discovered in rust-lang/libc#236 with a fix proposed in
rust-lang/libc#237. I suspect that we'll want to accept rust-lang/libc#237 so
Rust crates at large continue to be compatible with newer releases of Android
and crates, like the standard library, that want to opt into older support can
continue to do so via similar means.

Closes rust-lang/libc#236

[1]: https://chromium.googlesource.com/android_tools/+/20ee6d20/ndk/platforms/android-18/arch-arm/usr/include/signal.h
[2]: https://chromium.googlesource.com/android_tools/+/fbd420/ndk_experimental/platforms/android-20/arch-arm/usr/include/signal.h
[3]: https://chromium.googlesource.com/android_tools/+/20ee6d/ndk/platforms/android-21/arch-arm/usr/include/signal.h
2016-04-04 21:54:59 -07:00
man allow RUST_BACKTRACE=0 to act as if unset 2016-03-31 23:02:59 +02:00
mk move const_eval and check_match out of librustc 2016-03-30 13:43:36 +02:00
src std: Fix linking against signal on Android 2016-04-04 21:54:59 -07:00
.gitattributes std: Remove msvc/valgrind headers 2015-07-27 16:21:15 -07:00
.gitignore Add *.pdb to .gitignore 2016-02-13 20:24:31 +01:00
.gitmodules Update .gitmodules 2016-02-20 20:37:30 +09:00
.mailmap Add another email address corresponding to Guillaume Gomez account 2016-02-18 11:38:59 +01:00
.travis.yml Use Travis trusty infrastructure 2015-10-19 18:31:02 -04:00
COMPILER_TESTS.md doc: fix typo 2016-03-29 19:48:46 +02:00
configure mk: A few build fixes for i586-pc-windows-msvc 2016-03-29 16:43:49 -07:00
CONTRIBUTING.md allow RUST_BACKTRACE=0 to act as if unset 2016-03-31 23:02:59 +02:00
COPYRIGHT Mention initial copyright year 2016-01-28 09:44:04 +05:30
LICENSE-APACHE
LICENSE-MIT Mention initial copyright year 2016-01-28 09:44:04 +05:30
Makefile.in mention debug-assertions 2016-02-25 10:21:32 +05:30
README.md Adding #rust-beginners to README and pointing the two channels on getting-started 2016-03-31 02:49:05 -06:00
RELEASES.md documentation fix in RELEASES.md 2016-03-17 20:33:01 +01:00

README.md

The Rust Programming Language

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

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.7 (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

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:

  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

Download MinGW from here, and choose the version=4.9.x,threads=win32,exceptions=dwarf/seh flavor when installing. Also, make sure to install to a path without spaces in it. After installing, add its bin directory to your PATH. This is due to #28260, in the future, installing from pacman should be just fine.

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

$ pacman -S base-devel

  1. 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.

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

    $ ./configure
$ make && make install

MSVC

MSVC builds of Rust additionally require an installation of Visual Studio 2013 (or later) so rustc can use its linker. Make sure to check the “C++ tools” option. In addition, cmake needs to be installed to build LLVM.

With these dependencies installed, the build takes two steps:

$ ./configure
$ make && make install

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 between 600MiB and 1.5GiB to build, depending on platform. 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 would be #rust-beginners.

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.