|
| 1 | +# Appveyor configuration template for Rust using rustup for Rust installation |
| 2 | +# https://github.com/starkat99/appveyor-rust |
| 3 | + |
| 4 | +## Operating System (VM environment) ## |
| 5 | + |
| 6 | +# Rust needs at least Visual Studio 2013 Appveyor OS for MSVC targets. |
| 7 | +os: Visual Studio 2015 |
| 8 | + |
| 9 | +## Build Matrix ## |
| 10 | + |
| 11 | +# This configuration will setup a build for each channel & target combination (12 windows |
| 12 | +# combinations in all). |
| 13 | +# |
| 14 | +# There are 3 channels: stable, beta, and nightly. |
| 15 | +# |
| 16 | +# Alternatively, the full version may be specified for the channel to build using that specific |
| 17 | +# version (e.g. channel: 1.5.0) |
| 18 | +# |
| 19 | +# The values for target are the set of windows Rust build targets. Each value is of the form |
| 20 | +# |
| 21 | +# ARCH-pc-windows-TOOLCHAIN |
| 22 | +# |
| 23 | +# Where ARCH is the target architecture, either x86_64 or i686, and TOOLCHAIN is the linker |
| 24 | +# toolchain to use, either msvc or gnu. See https://www.rust-lang.org/downloads.html#win-foot for |
| 25 | +# a description of the toolchain differences. |
| 26 | +# See https://github.com/rust-lang-nursery/rustup.rs/#toolchain-specification for description of |
| 27 | +# toolchains and host triples. |
| 28 | +# |
| 29 | +# Comment out channel/target combos you do not wish to build in CI. |
| 30 | +# |
| 31 | +# You may use the `cargoflags` and `RUSTFLAGS` variables to set additional flags for cargo commands |
| 32 | +# and rustc, respectively. For instance, you can uncomment the cargoflags lines in the nightly |
| 33 | +# channels to enable unstable features when building for nightly. Or you could add additional |
| 34 | +# matrix entries to test different combinations of features. |
1 | 35 | environment:
|
2 |
| - PATH: 'C:\msys64\mingw64\bin;C:\msys64\usr\bin;%PATH%;C:\Rust\bin' |
| 36 | + matrix: |
| 37 | + |
| 38 | +### MSVC Toolchains ### |
| 39 | + |
| 40 | + # Stable 64-bit MSVC |
| 41 | + - channel: stable |
| 42 | + target: x86_64-pc-windows-msvc |
| 43 | + # Stable 32-bit MSVC |
| 44 | + # - channel: stable |
| 45 | + # target: i686-pc-windows-msvc |
| 46 | + # Beta 64-bit MSVC |
| 47 | + # - channel: beta |
| 48 | + # target: x86_64-pc-windows-msvc |
| 49 | + # Beta 32-bit MSVC |
| 50 | + # - channel: beta |
| 51 | + # target: i686-pc-windows-msvc |
| 52 | + # Nightly 64-bit MSVC |
| 53 | + # - channel: nightly |
| 54 | + # target: x86_64-pc-windows-msvc |
| 55 | + #cargoflags: --features "unstable" |
| 56 | + # Nightly 32-bit MSVC |
| 57 | + # - channel: nightly |
| 58 | + # target: i686-pc-windows-msvc |
| 59 | + #cargoflags: --features "unstable" |
| 60 | + |
| 61 | +### GNU Toolchains ### |
3 | 62 |
|
| 63 | + # Stable 64-bit GNU |
| 64 | + # - channel: stable |
| 65 | + # target: x86_64-pc-windows-gnu |
| 66 | + # Stable 32-bit GNU |
| 67 | + # - channel: stable |
| 68 | + # target: i686-pc-windows-gnu |
| 69 | + # Beta 64-bit GNU |
| 70 | + # - channel: beta |
| 71 | + # target: x86_64-pc-windows-gnu |
| 72 | + # Beta 32-bit GNU |
| 73 | + # - channel: beta |
| 74 | + # target: i686-pc-windows-gnu |
| 75 | + # Nightly 64-bit GNU |
| 76 | + # - channel: nightly |
| 77 | + # target: x86_64-pc-windows-gnu |
| 78 | + # #cargoflags: --features "unstable" |
| 79 | + # Nightly 32-bit GNU |
| 80 | + # - channel: nightly |
| 81 | + # target: i686-pc-windows-gnu |
| 82 | + #cargoflags: --features "unstable" |
| 83 | + |
| 84 | +### Allowed failures ### |
| 85 | + |
| 86 | +# See Appveyor documentation for specific details. In short, place any channel or targets you wish |
| 87 | +# to allow build failures on (usually nightly at least is a wise choice). This will prevent a build |
| 88 | +# or test failure in the matching channels/targets from failing the entire build. |
| 89 | +matrix: |
| 90 | + allow_failures: |
| 91 | + - channel: nightly |
| 92 | + |
| 93 | +# If you only care about stable channel build failures, uncomment the following line: |
| 94 | + #- channel: beta |
| 95 | + |
| 96 | +## Install Script ## |
| 97 | + |
| 98 | +# This is the most important part of the Appveyor configuration. This installs the version of Rust |
| 99 | +# specified by the 'channel' and 'target' environment variables from the build matrix. This uses |
| 100 | +# rustup to install Rust. |
| 101 | +# |
| 102 | +# For simple configurations, instead of using the build matrix, you can simply set the |
| 103 | +# default-toolchain and default-host manually here. |
4 | 104 | install:
|
5 |
| - - ps: Start-FileDownload "https://static.rust-lang.org/dist/rust-nightly-x86_64-pc-windows-gnu.msi" |
6 |
| - - msiexec /passive /i "rust-nightly-x86_64-pc-windows-gnu.msi" ADDLOCAL=Rustc,Cargo,Std INSTALLDIR=C:\Rust |
7 |
| - - rustc -V |
8 |
| - - cargo -V |
| 105 | + - appveyor DownloadFile https://win.rustup.rs/ -FileName rustup-init.exe |
| 106 | + - rustup-init -yv --default-toolchain %channel% --default-host %target% |
| 107 | + - set PATH=%PATH%;%USERPROFILE%\.cargo\bin |
| 108 | + - rustc -vV |
| 109 | + - cargo -vV |
| 110 | + |
| 111 | +## Build Script ## |
9 | 112 |
|
| 113 | +# 'cargo test' takes care of building for us, so disable Appveyor's build stage. This prevents |
| 114 | +# the "directory does not contain a project or solution file" error. |
10 | 115 | build: false
|
11 | 116 |
|
| 117 | +# Uses 'cargo test' to run tests and build. Alternatively, the project may call compiled programs |
| 118 | +#directly or perform other testing commands. Rust will automatically be placed in the PATH |
| 119 | +# environment variable. |
12 | 120 | test_script:
|
13 |
| - - cargo test --verbose |
| 121 | + - cargo test --verbose %cargoflags% |
0 commit comments