blob: 5b4c681c25eca91d1ad2e8f47de1ee2b51bdb194 [file] [log] [blame] [view]
Alex Crichtond9962f42015-09-17 17:45:10 -07001The goal of the libc crate is to have CI running everywhere to have the
2strongest guarantees about the definitions that this library contains, and as a
3result the CI is pretty complicated and also pretty large! Hopefully this can
4serve as a guide through the sea of scripts in this directory and elsewhere in
5this project.
6
Alex Crichton145ac092015-09-17 17:52:13 -07007# Files
8
Alex Crichtond9962f42015-09-17 17:45:10 -07009First up, let's talk about the files in this directory:
10
Alex Crichtond9962f42015-09-17 17:45:10 -070011* `msys2.ps1` - a PowerShell script which is used to install MSYS2 on the
12 AppVeyor bots. As of this writing MSYS2 isn't installed by default, and this
13 script will install the right version/arch of msys2 in preparation of using
14 the contained C compiler to compile C shims.
15
16* `run-travis.sh` - a shell script run by all Travis builders, this is
17 responsible for setting up the rest of the environment such as installing new
18 packages, downloading Rust target libraries, etc.
19
20* `run.sh` - the actual script which runs tests for a particular architecture.
21 Called from the `run-travis.sh` script this will run all tests for the target
22 specified.
23
24* `cargo-config` - Cargo configuration of linkers to use copied into place by
25 the `run-travis.sh` script before builds are run.
26
27* `dox.sh` - script called from `run-travis.sh` on only the linux 64-bit nightly
28 Travis bots to build documentation for this crate.
29
30* `landing-page-*.html` - used by `dox.sh` to generate a landing page for all
31 architectures' documentation.
32
Alex Crichton145ac092015-09-17 17:52:13 -070033# CI Systems
34
35Currently this repository leverages a combination of Travis CI and AppVeyor for
36running tests. The triples tested are:
37
38* AppVeyor
39 * `{i686,x86_64}-pc-windows-{msvc,gnu}`
40* Travis
41 * `{i686,x86_64,mips,aarch64}-unknown-linux-gnu`
42 * `x86_64-unknown-linux-musl`
43 * `arm-unknown-linux-gnueabihf`
44 * `arm-linux-androideabi`
Alex Crichtonbaef6112015-09-19 23:20:53 -070045 * `{i686,x86_64}-apple-{darwin,ios}`
Alex Crichton145ac092015-09-17 17:52:13 -070046
47The Windows triples are all pretty standard, they just set up their environment
48then run tests, no need for downloading any extra target libs (we just download
49the right installer). The Intel Linux/OSX builds are similar in that we just
50download the right target libs and run tests. Note that the Intel Linux/OSX
51builds are run on stable/beta/nightly, but are the only ones that do so.
52
53The remaining architectures look like:
54
Alex Crichton2995f552015-10-29 16:34:55 -070055* Android runs in a [docker image][android-docker] with an emulator, the NDK,
56 and the SDK already set up. The entire build happens within the docker image.
Alex Crichton145ac092015-09-17 17:52:13 -070057* The MIPS, ARM, and AArch64 builds all use QEMU to run the generated binary to
58 actually verify the tests pass.
59* The MUSL build just has to download a MUSL compiler and target libraries and
60 then otherwise runs tests normally.
Alex Crichtonbaef6112015-09-19 23:20:53 -070061* iOS builds need an extra linker flag currently, but beyond that they're built
62 as standard as everything else.
Alex Crichton145ac092015-09-17 17:52:13 -070063
Alex Crichton2995f552015-10-29 16:34:55 -070064[android-docker]: https://github.com/rust-lang/rust-buildbot/blob/master/slaves/android/Dockerfile
65
Alex Crichton145ac092015-09-17 17:52:13 -070066Hopefully that's at least somewhat of an introduction to everything going on
67here, and feel free to ping @alexcrichton with questions!
68