Skip to content

Commit

Permalink
Use AppVeyor for Windows builds
Browse files Browse the repository at this point in the history
  • Loading branch information
malu committed Jul 23, 2018
1 parent 5576584 commit a3ad5b7
Show file tree
Hide file tree
Showing 2 changed files with 106 additions and 2 deletions.
2 changes: 0 additions & 2 deletions .travis.yml
Expand Up @@ -19,8 +19,6 @@ matrix:
os: osx
- env: TARGET=x86_64-apple-darwin FEATURES=+popcnt
os: osx
- env: TARGET=x86_64-pc-windows-gnu FEATURES=-popcnt
- env: TARGET=x86_64-pc-windows-gnu FEATURES=+popcnt
- env: TARGET=x86_64-unknown-linux-gnu FEATURES=-popcnt
rust: nightly
- env: TARGET=x86_64-unknown-linux-gnu FEATURES=+popcnt
Expand Down
106 changes: 106 additions & 0 deletions appveyor.yml
@@ -0,0 +1,106 @@
# Based on the "trust" template v0.1.2
# https://github.com/japaric/trust/tree/v0.1.2

environment:
global:
# TODO This is the Rust channel that build jobs will use by default but can be
# overridden on a case by case basis down below
RUST_VERSION: stable

# TODO Update this to match the name of your project.
CRATE_NAME: asymptote

# TODO These are all the build jobs. Adjust as necessary. Comment out what you
# don't need
matrix:
# MinGW
- TARGET: i686-pc-windows-gnu
FEATURES: -popcount
- TARGET: i686-pc-windows-gnu
FEATURES: +popcount
- TARGET: x86_64-pc-windows-gnu
FEATURES: -popcount
- TARGET: x86_64-pc-windows-gnu
FEATURES: +popcount

# MSVC
- TARGET: i686-pc-windows-msvc
FEATURES: -popcount
- TARGET: i686-pc-windows-msvc
FEATURES: +popcount
- TARGET: x86_64-pc-windows-msvc
FEATURES: -popcount
- TARGET: x86_64-pc-windows-msvc
FEATURES: +popcount

# Testing other channels
- TARGET: x86_64-pc-windows-gnu
RUST_VERSION: nightly
- TARGET: x86_64-pc-windows-msvc
RUST_VERSION: nightly

install:
- ps: >-
If ($Env:TARGET -eq 'x86_64-pc-windows-gnu') {
$Env:PATH += ';C:\msys64\mingw64\bin'
} ElseIf ($Env:TARGET -eq 'i686-pc-windows-gnu') {
$Env:PATH += ';C:\msys64\mingw32\bin'
}
- curl -sSf -o rustup-init.exe https://win.rustup.rs/
- rustup-init.exe -y --default-host %TARGET% --default-toolchain %RUST_VERSION%
- set PATH=%PATH%;C:\Users\appveyor\.cargo\bin
- set RUSTFLAGS="-C target-feature=%FEATURES%"
- rustc -Vv
- cargo -V

# TODO This is the "test phase", tweak it as you see fit
test_script:
# we don't run the "test phase" when doing deploys
- if [%APPVEYOR_REPO_TAG%]==[false] (
cargo build --target %TARGET% &&
cargo build --target %TARGET% --release &&
cargo test --target %TARGET% &&
cargo test --target %TARGET% --release &&
cargo run --target %TARGET% &&
cargo run --target %TARGET% --release
)

before_deploy:
# TODO Update this to build the artifacts that matter to you
- cargo rustc --target %TARGET% --release -- -C lto -C target-feature=%FEATURES%
- ps: ci\before_deploy.ps1

deploy:
artifact: /.*\.zip/
# TODO update `auth_token.secure`
# - Create a `public_repo` GitHub token. Go to: https://github.com/settings/tokens/new
# - Encrypt it. Go to https://ci.appveyor.com/tools/encrypt
# - Paste the output down here
auth_token:
secure: O6KD5XQDiJ/RUauyhmUVSlmJ0la1Ps+08aRl13AtFrJS/Vi72oTygOiisp1QCHsX
description: ''
on:
# TODO Here you can pick which targets will generate binary releases
# In this example, there are some targets that are tested using the stable
# and nightly channels. This condition makes sure there is only one release
# for such targets and that's generated using the stable channel
RUST_VERSION: stable
appveyor_repo_tag: true
provider: GitHub

cache:
- C:\Users\appveyor\.cargo\registry
- target

branches:
only:
# Release tags
- /^v\d+\.\d+\.\d+.*$/
- master

notifications:
- provider: Email
on_build_success: false

# Building is done in the test phase, so we disable Appveyor's build phase.
build: false

0 comments on commit a3ad5b7

Please sign in to comment.