-
Notifications
You must be signed in to change notification settings - Fork 2
/
appveyor.yml
139 lines (119 loc) · 4.76 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
# Appveyor configuration template for Rust using rustup for Rust installation
# https://github.com/starkat99/appveyor-rust
## Operating System (VM environment) ##
# Rust needs at least Visual Studio 2013 Appveyor OS for MSVC targets.
os: Visual Studio 2015
cache:
- C:\protobuf-3.0.0
- C:\Users\appveyor\.cargo
## Build Matrix ##
# This configuration will setup a build for each channel & target combination (12 windows
# combinations in all).
#
# There are 3 channels: stable, beta, and nightly.
#
# Alternatively, the full version may be specified for the channel to build using that specific
# version (e.g. channel: 1.5.0)
#
# The values for target are the set of windows Rust build targets. Each value is of the form
#
# ARCH-pc-windows-TOOLCHAIN
#
# Where ARCH is the target architecture, either x86_64 or i686, and TOOLCHAIN is the linker
# toolchain to use, either msvc or gnu. See https://www.rust-lang.org/downloads.html#win-foot for
# a description of the toolchain differences.
# See https://github.com/rust-lang-nursery/rustup.rs/#toolchain-specification for description of
# toolchains and host triples.
#
# Comment out channel/target combos you do not wish to build in CI.
#
# You may use the `cargoflags` and `RUSTFLAGS` variables to set additional flags for cargo commands
# and rustc, respectively. For instance, you can uncomment the cargoflags lines in the nightly
# channels to enable unstable features when building for nightly. Or you could add additional
# matrix entries to test different combinations of features.
environment:
matrix:
### MSVC Toolchains ###
# Stable 64-bit MSVC
- channel: stable
target: x86_64-pc-windows-msvc
## We only want to do a single build off of each toolchain as appveyor is super slow
# # Stable 32-bit MSVC
# - channel: stable
# target: i686-pc-windows-msvc
# # Beta 64-bit MSVC
# - channel: beta
# target: x86_64-pc-windows-msvc
# # Beta 32-bit MSVC
# - channel: beta
# target: i686-pc-windows-msvc
# # Nightly 64-bit MSVC
# - channel: nightly
# target: x86_64-pc-windows-msvc
# #cargoflags: --features "unstable"
# # Nightly 32-bit MSVC
# - channel: nightly
# target: i686-pc-windows-msvc
# #cargoflags: --features "unstable"
### GNU Toolchains ###
# Stable 64-bit GNU
- channel: stable
target: x86_64-pc-windows-gnu
## We only want to do a single build off of each toolchain as appveyor is super slow
# # Stable 32-bit GNU
# - channel: stable
# target: i686-pc-windows-gnu
# # Beta 64-bit GNU
# - channel: beta
# target: x86_64-pc-windows-gnu
# # Beta 32-bit GNU
# - channel: beta
# target: i686-pc-windows-gnu
# # Nightly 64-bit GNU
# - channel: nightly
# target: x86_64-pc-windows-gnu
# #cargoflags: --features "unstable"
# # Nightly 32-bit GNU
# - channel: nightly
# target: i686-pc-windows-gnu
# #cargoflags: --features "unstable"
### Allowed failures ###
# See Appveyor documentation for specific details. In short, place any channel or targets you wish
# to allow build failures on (usually nightly at least is a wise choice). This will prevent a build
# or test failure in the matching channels/targets from failing the entire build.
matrix:
allow_failures:
- channel: nightly
# If you only care about stable channel build failures, uncomment the following line:
#- channel: beta
## Install Script ##
# This is the most important part of the Appveyor configuration. This installs the version of Rust
# specified by the 'channel' and 'target' environment variables from the build matrix. This uses
# rustup to install Rust.
#
# For simple configurations, instead of using the build matrix, you can simply set the
# default-toolchain and default-host manually here.
install:
- if not exist C:\protobuf-3.0.0 (
cd C:\ &&
curl -L -o protobuf-3.0.0.zip https://github.com/google/protobuf/archive/v3.0.0.zip &&
7z x protobuf-3.0.0.zip &&
mkdir protobuf-3.0.0\build_msvc &&
cd protobuf-3.0.0\build_msvc &&
cmake -Dprotobuf_BUILD_SHARED_LIBS=ON -Dprotobuf_UNICODE=ON -Dprotobuf_BUILD_TESTS=OFF ../cmake &&
msbuild protobuf.sln &&
cd C:\projects\mjolnir
)
- appveyor DownloadFile https://win.rustup.rs/ -FileName rustup-init.exe
- rustup-init -yv --default-toolchain %channel% --default-host %target%
- set PATH=%PATH%;%USERPROFILE%\.cargo\bin;C:\protobuf-3.0.0\build_msvc\Debug
- rustc -vV
- cargo -vV
## Build Script ##
build_script:
- cargo build --all --verbose %cargoflags%
# Uses 'cargo test' to run tests and build. Alternatively, the project may call compiled programs
# directly or perform other testing commands. Rust will automatically be placed in the PATH
# environment variable.
test_script:
- cargo test --verbose %cargoflags%